[Website]: Doc enhancements to the Managed OTel Input #2162
Description
Type of issue
None
What documentation page is affected
https://www.elastic.co/docs/reference/opentelemetry/motlp
What happened?
Some items which should be reviewed with SMEs:
- Is there a minimum version of semconv we should respect to use Managed OTLP Input?
- We should state if we have guarnateed delivery (at least once? something else?)
- Highlight the reason/advantage of using Managed OTLP Input, in particular the fact it can act as an EDOT Gateway (except if the use case requires features which are not available such as TBS or specific processing via OTTL processors)
- We should have a section which tells where the data will end up depending on the signal, similar to what we have for APM Server/Integration https://www.elastic.co/docs/solutions/observability/apm/data-streams#apm-data-streams-list
- List what are the products we test against Managed OTel Input (e.g. EDOT Collector, EDOT SDKs, EDOT Cloud Forwarder, etc...)
- How a user can change the data retention period
- Is the service rate limited or throttled? Are there limits on the throughput?
- How can the user add fields or tweak the number of shards/replicas/policy per namespace?
- Is this service billed?
Additional info
No response