**Is your feature request related to a problem? Please describe.** This format presents a particular challenge as it seems it wasn't really designed for direct analysis. It is JSON lines, but it writes the log messages in batches in each JSON line under a `resourceLogs` key, rather than just one message per line as you'd expect. And each such message can come from a different `resource` or `service` so to speak, so you would often want to split this up or filter it down to find the logs that you are interested in. **Describe the solution you'd like** Support for this format, or some way to add support for it. **Describe alternatives you've considered** Writing a script to pre-process this format externally into something that lnav can grok. **Additional context** https://opentelemetry.io/docs/specs/otel/protocol/file-exporter/ https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/fileexporter/README.md Sample: [log.jsonl.zip](https://github.com/user-attachments/files/23833683/log.jsonl.zip)