-
Notifications
You must be signed in to change notification settings - Fork 183
Description
Description
As part of https://github.com/elastic/observability-dev/issues/4716, we're going to update the 'kubernetes pods', 'docker container' and 'AWS' views in the infra inventory and their respective inventory rules to specifically work with the integrations. This will stop 'OTel' data (and other unsupported data) 'bleed' into the UI (and cause unexpected behaviour like missing metrics).
This issue is to update the infra inventory and inventory rule docs to make it clear that these entity types only support specific integrations.
Additionally:
-
The UI need be adding URLs which will need to point towards an anchor in this documentation which makes it clear which integrations are supported per entity type (you can see a list of which integrations are supported per entity type here.
-
We'll also be linking to these from the respective inventory rules we are updating for these same entity types - ideally, we can point users to the same place in the documentation rather than duplicate the documentation. The inventory alert rules and infrastructure inventory share the same code base for the 'entity types' they commonly refer to_
-
We should also communicate in the documentation that we are filtering the Host and Inventory UIs (and respective inventory rules) to only show data from the supported integrations - we need to detail the filters (as documented here) so that if users are not using these integrations, they at least know we're filtering by these fields so they can continue to 'mimic' them (which is not uncommon for customers using alternative shippers like Prometheus)
Resources
Implementation issue
Related metrics reference docs issue
Infra UI - Metrics Definitions : This has all of the details for the metrics and required integrations etc
Which documentation set does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
None
What release is this request related to?
9.3
Serverless release
15th Dec
Collaboration model
The documentation team
Point of contact.
Main contact: @roshan-elastic