opentelemetry export format

[aybabtme]

Add the ability to parse opentelemetry data.

• can parse logs
• can parse other events types, and do nothing with them for now

Later we will ingest the non-log stuff, but for starts we focus ok just the logs.

[ferh6t]

Hi @aybabtme,
I want to implement the consumer of the OpenTelemetry exported data which is defined as OTLP here. Before starting to implement it, I want to clarify some details.

The examples in (00005-otel) look unfamiliar with the examples. I guess these are recognized as fmtlogs and humanlog processes them as fmt logs. Are they on purpose or just random logs?

Is the OTLP logs enough for the initial step? As I remember, and the examples are showing that, they are basically json formatted logs with special standardized fields that can be handled with the correct configuration with JSON parser.

[aybabtme]

@ferh6t i havent been following OTEL much in recent years since they were changing theirs spec quite frequently and i found it annoying.

I'll guess the example logs i have are from a otel logger that is no longer conformant?

My goal is to support out of the box most formats out there, conformant or not. So we should suppoort 00005-otel and also the new formats :)

However, I would like for special knowledge about OTEL components to be detected and extracted where possible. In particular, if they encode special meanings in special places, like log-levels, request/trace IDs, span IDs, etc. The logevent type is fairly limited now, but later it may gain more special fields.