-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Metrics UI] Allow user to view K8s container metrics when not using Docker #100229
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
@neptunian thanks for filing this. I think the work done by the Inventory Schema team should solve that by making each integration reporting container data report it in a common way, i.e. more aligned via ECS. |
Picking this up @neptunian - I agree with this. As we develop a new inventory, I'm sure we can refer to all containers generically (but allow users to understand/filter by the type of container). |
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing - will be fixing as part of improving our container views (work either in progress or on near roadmap) |
If a user is not using Docker with Kubernetes, which is more likely after Kubernetes 1.20+ where the default daemon for containers is not Docker, there is not a way to view container metrics. It might also be confusing for users to see "Docker" as a dropdown filter when they are not using Docker.
When not using the Docker and monitoring Kubernetes with the Kubernetes module, container metrics are sent to
kubernetes.container
:But when using Docker they're sent to
docker.cpu.total.pct
Perhaps we should think about removing the "Docker" filter dropdown item altogether in favor of something generic like "Container" and we can figure out where to look for container metrics whether or not they are from Docker.
The text was updated successfully, but these errors were encountered: