Skip to content
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

Live Metrics Displayed for Deleted Pods #544

Open
abhipatwari17 opened this issue Jul 12, 2024 · 2 comments
Open

Live Metrics Displayed for Deleted Pods #544

abhipatwari17 opened this issue Jul 12, 2024 · 2 comments

Comments

@abhipatwari17
Copy link

Steps to Reproduce
Enable pod-level metrics in Retina.
Observe metrics for active pods.
Delete some pods.
Continue to observe the metrics display.
Expected Behavior
Metrics data and graphs should only be displayed for active pods. Deleted pods should no longer appear in the live metrics display.

Actual Behavior
Metrics data and graphs are still being displayed for pods that have been deleted.

Environment
Retina version: v0.0.12
Kubernetes version: 1.28
Platform: Grafana ui

Here you can see the metrics for "monitoring-kube-prometheus-operator-9b8fb7d86-fwv6z",But this pod doesn't exist in my cluster.
image

Additional Information
Any guidance on resolving this issue would be greatly appreciated. If you need further information, please let me know.

Thank you for your assistance.

@rbtr
Copy link
Collaborator

rbtr commented Jul 12, 2024

I believe this is intended behavior of Prometheus/Grafana - the historical data still exists for those Pods

@vakalapa
Copy link
Contributor

vakalapa commented Aug 5, 2024

@abhipatwari17 feel free to contribute, there is a way to fix this. Whenever we get a delete notification, we can loop over all the existing timeseries and check if this is used in a dimension and delete that specific time series. This will help in reducing cardinality greatly !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants