What's missing in your current JSON log filtering setup?

I debug microservice logs daily and kept running into the same gaps with existing tools — hl, humanlog, lnav all pretty-print JSON well but none of them let me trace a full request flow across services with a single pattern, or save my filter setup between sessions. Built something that solves these specifically and wanted to get feedback from people who deal with this daily before I invest more time into it. Three things I built around: Hier path filter: --hier "payment.**" to trace an entire flow across services instead of grepping service by service Named profiles: tired of retyping --service X --level warn --hier "Y" every session TTL noise suppression: kills repeated log spam by fingerprinting message patterns, not exact strings Genuinely curious whether these match real pain points or if I'm solving the wrong problems. What does your log debugging workflow actually look like? What do you reach for and what frustrates you about it? If anyone wants to poke at it and tell me what's