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

feat(metrics): disable default Prometheus rules #3160

Merged
merged 1 commit into from Jul 20, 2023

Conversation

swiatekm-sumo
Copy link
Contributor

kube-prometheus-stack installs a bunch of alerting and recording rules by default, of which we use two for our own recording rules. The rest aren't necessary and make filtering existing metrics more difficult.

We don't support any of these, so it's not a breaking change, but I've called it out in the changelog for users who may have configured kube-prometheus-stack to use these.

Checklist

  • Changelog updated or skip changelog label added
  • Documentation updated
  • Template tests added for new features
  • Integration tests added or modified for major features

@swiatekm-sumo swiatekm-sumo force-pushed the feat/disable-default-prometheus-rules branch from fc4f30d to 2240b22 Compare July 20, 2023 10:42
@@ -359,6 +359,7 @@ var (
"otelcol_otelsvc_k8s_pod_deleted",
"otelcol_processor_batch_batch_size_trigger_send",
"otelcol_otelsvc_k8s_ip_lookup_miss",
"otelcol_otelsvc_k8s_other_deleted",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is unrelated, just another flaky metric I found running tests locally.

@swiatekm-sumo swiatekm-sumo merged commit 4aa0009 into main Jul 20, 2023
40 checks passed
@swiatekm-sumo swiatekm-sumo deleted the feat/disable-default-prometheus-rules branch July 20, 2023 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants