elastic / elastic/docs-content
[REQUEST]: Managed Input pages should not be under the Opentelemetry section
- Dominant language
- No language data
- Stars
- 47
- Forks
- 261
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 116
Description
### Description
Currently the managed inputs are all under: https://www.elastic.co/docs/reference/opentelemetry/managed-inputs
We have been adding inputs in to the managed inputs infrastructure which are not solely in the OTEL domain (promethues, _bulk and others). Let's rethink how managed inputs can have their own more prominent place in the docs.
### Resources
https://www.elastic.co/docs/reference/opentelemetry/managed-inputs
### Collaboration
TBD. The docs and product team will work together to determine the best path forward.
### Point of contact.
**Main contact:** @perk
**Stakeholders:**
@ishleenk17 @nimarezainia
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the current managed-inputs page at https://www.elastic.co/docs/reference/opentelemetry/managed-inputs and the issue's examples of inputs outside the OTEL domain. Coordinate with @perk and the listed docs and product stakeholders to determine the new information architecture. Done means managed inputs have a more prominent location that is not confined to the OpenTelemetry section.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100