feat(formats): add OpenTelemetry Collector log format and converter #1613
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
relative issue: #1600
The OpenTelemetry Collector's file exporter writes log records in batched JSON Lines format, where each line contains multiple log records nested under
resourceLogs.This makes it difficult to analyze with lnav without preprocessing.
Changes
src/formats/otel_collector_log.json: Log format definition with field mappings for OTEL log records (timestamp, severity, trace_id, span_id, service.name, etc.)src/scripts/otel_collector_log-converter.sh: Converter script usingjqto flatten batched records into one-per-line formattest/logfile_otel_collector.jsonl: Test data covering various scenarios (multiple services, all severity levels, edge cases)Test plan
make checkpasseslnav -n test/logfile_otel_collector.jsonlDependencies
Requires
jqto be installed for the converter to work.