Agree on identifiers that work when a Business Critical Service spans UX, CDN, origin, network, and platform—and when async steps mean there is no single trace.id to follow. This BCS edition replaces a checkout-only “one process / one trace” framing with session, content, and message bridges (TV streaming as the running example).
When to use it
Use before building multi-layer BCS dashboards or DORA-style composite SLOs. Pair with the End-to-End Observability hub and the BCS health dashboard.
What is included
- BCS model, personas, and layer contracts
- Async join patterns (session, entity, message, topology+time)
- Field map and cardinality rules
- Code samples for BCS labels (Node, Python, OTel-style Java)
- Starter ES|QL for session and content bridges
Compatibility
Elastic Observability / ECS-oriented fields. Adapt CDN and network field names to your integrations. Compatibility checked against Elastic APM label guidance; no fixed Stack version claimed.
Source and license
Original Elastic Content Share documentation (CC BY 4.0).
| Tested versions | |
| ECS compliant |
You must log in to submit a review.