Title | Link | # of reactions | Reactions |
---|---|---|---|
Capture request and response bodies | open-telemetry/semantic-conventions#857 | 29 | {'+1': 28, '-1': 1, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Introduce semantic conventions for modern AI (LLMs, vector databases, etc.) | open-telemetry/semantic-conventions#327 | 11 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 8, 'confused': 0, 'heart': 3, 'rocket': 0, 'eyes': 0} |
Improve GraphQL semantic conventions | open-telemetry/semantic-conventions#182 | 8 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 6, 'eyes': 1} |
Discuss ECS' field reuse concept for OTel semantic attributes | open-telemetry/semantic-conventions#339 | 7 | {'+1': 7, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Define semantic conven |
- Which one to use Otel or Micrometer. Why?
- Semantic conventions - how users can pick which ones they want? will libs need to provide all possible options?
- What's the story in other languages/ecosystems? I need my python messaging consumer to be consistent with my java messaging producer.
- Which libraries beyond Spring are all-in on Micrometer?
- How do you prioritize features? What if something is missing? (E.g. structured events on spans, adding link after span creation, etc)
- is Micrometer targeting feature-parity with OTel specification? Will micrometer introduce profling API?
- How big is the community? Are there community calls? Who makes decisions?
-
Schemaprocessor in collector-contrib. It's a stub and does not do anything. It's not included into collector-contib image.
-
Search for https://opentelemetry.io/schemas/ does not show if anyone uses transformation logic.
-
There is no schema transformation logic in exporters in
opentelemetry-collector-contrib
repo. -
There is a schema parser https://pkg.go.dev/go.opentelemetry.io/otel/schema/v1.1