You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We then use opentelemetry collector to parse this JSON and enrich the message by using the json_parser operator on the filelog receiver - here's a snippet from the otelcol config:
Describe the bug
When a field in a log entry from otel collector contains nested JSON, the field is omitted in quickwit v0.8.2
As a workaround for #5311 (which is not released yet), we've changed our app's logging to print JSON to stdout, e.g.:
We then use opentelemetry collector to parse this JSON and enrich the message by using the json_parser operator on the filelog receiver - here's a snippet from the otelcol config:
According to otelcol's debug exporter, this does what we want (only relevant line for brevity):
Expected behavior
The body should show up when queried in quickwit, but this is the result:
The same thing happens when a nested JSON field appears in any of the other fields (like resource_attributes) - the entry is dropped.
Configuration:
Please provide:
Output of
quickwit --version
:Quickwit 0.8.2 (x86_64-unknown-linux-gnu 2024-06-17T16:36:47Z 42766b8)
The index_config.yaml:
I tried with 2 distinct indexes: One that shares config with the
otel-logs-v0_7
index:And one with full dynamic mapping:
The text was updated successfully, but these errors were encountered: