[Verse 1]
When your Kafka cluster starts to grow
Debug and info levels need to flow
Brokers humming with their chatter loud
Configure logging to cut through the crowd
Set the root logger to what you need
WARN for production, DEBUG to feed
Your troubleshooting when things go wrong
Structured data keeps the story strong
[Chorus]
Log it right, ship it tight
Fluentd flowing through the night
Elasticsearch storing all your traces
Loki keeping all the bases
Level up from INFO high
To ERROR when the systems cry
Structured logs in JSON form
Navigate through any storm
[Verse 2]
Connect workers need their own sweet tune
Set their levels or you'll debug soon
Operator logs will tell the tale
Of reconciliation without fail
Use log4j properties to control
What messages reach your monitoring goal
Filter noise but keep the signal clear
Performance metrics crystal clear
[Chorus]
Log it right, ship it tight
Fluentd flowing through the night
Elasticsearch storing all your traces
Loki keeping all the bases
Level up from INFO high
To ERROR when the systems cry
Structured logs in JSON form
Navigate through any storm
[Bridge]
Fluent Bit for lighter weight
When resources can't wait
Parse and forward every line
Timestamp correlation fine
Labels matter, tags are key
Search and query easily
Grafana dashboard shows
Where every error goes
[Verse 3]
Best practices keep you on the track
JSON structure, no looking back
Correlation IDs thread the story
From request start to final glory
Don't log secrets, keep them safe
Sampling helps when logs chafe
Retention policies save your space
While audit trails keep up the pace
[Final Chorus]
Log it right, ship it tight
Monitoring shining bright
Elasticsearch or Loki's grace
Both will give you searching space
DEBUG, INFO, WARN, ERROR too
Each level serves a purpose true
Structured logs in JSON form
Navigate through any storm
[Outro]
When Strimzi logs are flowing free
Observability is the key
From brokers to Connect and more
Logging opens every door