Blog Post Title

What can you do with OpenTelemetry entity events?

Blog Post Outline

An educational post on consuming OpenTelemetry entity events: once a producer emits them, what does a consumer actually do to turn the stream into something you can query? Uses one Apache-2.0 consumer (Toise) as a worked example, with an affiliation disclosure; vendor-neutral throughout.

Outline:

1. Primer — entity events as OTLP log records (type, id, attributes, lifecycle)
2. Event-source the stream, don't store mutable state
3. Be bi-temporal on purpose (event time vs recorded time; reality vs audit view)
4. Immutable identity — match exactly; volatile facts go in descriptive attributes

• GraphQL — open specification
• Toise — Apache-2.0, the example open-source consumer

Technologies Used

• OpenTelemetry entity events / Entity Data Model (carried over OTLP logs)
• Model Context Protocol (MCP) — open protocol
• GraphQL — open specification
• Toise — Apache-2.0, the example open-source consumer

Related Special Interest Groups (SIGs)

• Specification: Entities (owns the entity data model)
• Semantic Conventions (entity attribute conventions — area:entities)

Sponsoring SIG

Specification: Entities

Sponsor Name

seeking

Additional Information

The draft is already written and ready for review (~1100 words, vendor-neutral): ([https://github.com/toise-dev/toise/blob/main/docs/outreach/opentelemetry.io/content/en/blog/2026/consuming-opentelemetry-entity-events/index.md])

Disclosure: I work on Toise (Apache-2.0). It appears only as a worked example with a disclosure line — the post is educational about consuming entity events, not a product pitch. It also surfaces the open relationships question (OTEP 0256 Future Work), which I'd like to bring to the SIG.

I'm looking for a sponsor and happy to present it at a Monday "Specification: Entities" meeting or in #otel-entities.