VictoriaMetrics/lib/protoparser/opentelemetry/pb
Andrii Chubatiuk c72d5690cc
lib/protoparser/opentelemetry: properly marshal nested attributes into JSON
Previously, opentelemetry attribute parsed added extra field names according to 
golang JSON parser spec for structs:

```
struct AnyValue{
 StringValue string
}
```
 Was serialized into:
```
{"StringValue": "some-string"}
```
 While opentelemetry-collector serializes it as
```
"some-string"
```

 This commit changes this behaviour it makes parses compatible with opentelemetry-collector format. See test cases for examples.

Related issue:
https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8384
2025-03-05 18:38:25 +01:00
..
common.go vlinsert: added opentelemetry logs support 2024-09-03 20:24:01 +02:00
helpers.go lib/protoparser/opentelemetry: properly marshal nested attributes into JSON 2025-03-05 18:38:25 +01:00
helpers.qtpl lib/protoparser/opentelemetry: properly marshal nested attributes into JSON 2025-03-05 18:38:25 +01:00
helpers.qtpl.go lib/protoparser/opentelemetry: properly marshal nested attributes into JSON 2025-03-05 18:38:25 +01:00
helpers_test.go lib/protoparser/opentelemetry: properly marshal nested attributes into JSON 2025-03-05 18:38:25 +01:00
logs.go app/vlinsert: add OpenTelemetry ingested logs trace_id and span_id 2025-02-12 12:47:42 +01:00
metrics.go make: bump golangci-lint to v1.63.4 ( 2025-01-13 07:23:21 +01:00
README.md lib/protoparser/opentelemetry: use github.com/VictoriaMetrics/easyproto for protobuf message unmarshaling and marshaling 2024-01-16 20:34:18 +02:00

The original protobuf definition is located at 34d29fe5ad/opentelemetry/proto