[Website]: EDOT flows and limitations #2238
Description
Type of issue
None
What documentation page is affected
https://www.elastic.co/docs/reference/opentelemetry/compatibility/limitations
What happened?
In the page https://www.elastic.co/docs/reference/opentelemetry/compatibility/features we show:
| Feature | Compatibility | Support |
|---|---|---|
| Tail-based Sampling (TBS) | Compatible | Not supported |
| Self-managed, OTel Collector-based TBS | Compatible | Not supported |
| TBS managed / hosted in Elastic Cloud | Incompatible | Not supported |
I think this needs to be expanded.
- What do we mean by "TBS" being Compatible?
- What do we mean by "Self-managed, OTel Collector-based TBS" being Compatible?
The fact TBS is not easy to implement and supported should be part of the limitations https://www.elastic.co/docs/reference/opentelemetry/compatibility/limitations
Other known limitations for APM/Tracing use cases and EDOT:
- You need tail-based sampling (TBS)
- You need RUM
- You need Universal Profiling
- You want to reuse existing Integrations and dashboards
- The user prefers not to manage EDOT or another OTel Collector as a gateway
- You rely on Ingest Pipelines to parse structured logs
This is an extract from our FAQ (A.4)
FYI @mlunadia @theletterf
Additional info
No response