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

Add node_exporter mixin #191

Merged
merged 3 commits into from Aug 26, 2019

Conversation

paulfantom
Copy link
Member

Switching to use node_exporter mixin instead of providing recording rules and alerts ourselves.

Some alerts related to node_exporter were left untouched as they are not (yet :) ) provided by node-mixin

/cc @brancz @lilic @metalmatze @s-urbaniak

@s-urbaniak
Copy link
Contributor

looking good at first glance 👍

Copy link
Contributor

@lilic lilic left a comment

Choose a reason for hiding this comment

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

👍 from me 🎉

Did we say we want to do another release of kube-prometheus before this is merged or not?

@paulfantom
Copy link
Member Author

We want release after it is merged.

@paulfantom paulfantom merged commit a8927ac into prometheus-operator:master Aug 26, 2019
@paulfantom paulfantom deleted the node-mixins branch August 26, 2019 11:46
@metalmatze
Copy link
Member

Awesome. Looking forward to a upstream community maintained mixin 🎉

s-urbaniak added a commit to s-urbaniak/kube-prometheus that referenced this pull request Aug 29, 2019
Currently, we use the node:node_memory_bytes_total:sum and node:node_memory_bytes_available:sum
recording rules for the memory node query.
These recording rules have been removed in prometheus-operator#191.

This fixes it by using raw queries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants