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

remove all node-exporter job label filters #49

Merged
merged 1 commit into from
May 30, 2023
Merged

Conversation

uhthomas
Copy link
Contributor

Pull Request

Required Fields

🔎 What kind of change is it?

  • fix

🎯 What has been changed and why do we need it?

  • The label 'job' is not set to 'node-exporter' when using Grafan Agent, which breaks the dashboard. There doesn't seem to be a clear reason for using the label filter, so removing it should allow the dashboard(s) to work agnostically across different metrics collectors.

Optional Fields

✔️ Which issue(s) this PR fixes?

💬 Additional information?

  • ...

The label 'job' is not set to 'node-exporter' when using Grafan Agent, which
breaks the dashboard. There doesn't seem to be a clear reason for using the
label filter, so removing it should allow the dashboard(s) to work agnostically
across different metrics collectors.

Fixes dotdc#48
@uhthomas uhthomas requested a review from dotdc as a code owner May 26, 2023 20:08
Copy link
Owner

@dotdc dotdc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will test that on a kube-prometheus-stack deployment before merge, but lgtm!

@dotdc dotdc merged commit 7934fef into dotdc:master May 30, 2023
@dotdc
Copy link
Owner

dotdc commented Apr 25, 2024

🎉 This PR is included in version 1.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@dotdc dotdc added the released label Apr 25, 2024
@tlemarchand
Copy link
Contributor

tlemarchand commented Apr 27, 2024

This PR re-introduced this bug : #36
When theses dashboards are used with kube-prometheus-stack, if the filter is not used, metrics from all node-exporters (including those who are not in the cluster) are shown. That is the clear reason.

For example :
Screenshot from 2024-04-27 07-25-28

My cluster currently has 6 nodes.
I don't know how to manage both this case and the "Grafana Agent" case.

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

Successfully merging this pull request may close these issues.

[bug] metrics which filter by the node-exporter job don't work with Grafana Agent
3 participants