-
Notifications
You must be signed in to change notification settings - Fork 3.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
Helm: Fix Prometheus rule LokiTooManyCompactorsRunning #7049
Conversation
Signed-off-by: Calvin Bui <3604363+calvinbui@users.noreply.github.com>
Signed-off-by: Calvin Bui <3604363+calvinbui@users.noreply.github.com>
CLA signed and chart version bumped |
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. + ingester 0%
+ distributor 0%
+ querier 0%
+ querier/queryrange 0%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @calvinbui for the PR. Sounds reasonable to me. Leave it to @trevorwhitney for final approval.
Added one minor suggestion to the changelog entry.
Co-authored-by: Kaviraj Kanagaraj <kavirajkanagaraj@gmail.com>
On second thought, I'm not sure if this is the best approach as there'll be two alerts if it does go >1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, I'm not sure if this is the best approach as there'll be two alerts if it does go >1
Agreed. I think instead we should only scrape 1 of those services. My inclination would be to drop loki-headless
, WDYT?
what about the simple-scalable services? they use -read and -write suffixed services |
Hej, looking forward for this fix, what's the current state ? |
yeah, good point, looks like maybe we want to always deploy the |
If I'm not mistaken, |
…binary headless service
agreed, the best solution. PR updated |
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. + ingester 0%
+ distributor 0%
+ querier 0%
+ querier/queryrange 0%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! thanks!
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. + ingester 0%
+ distributor 0%
+ querier 0%
- querier/queryrange -0.1%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
@calvinbui looks like this just needs a |
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. + ingester 0%
+ distributor 0%
+ querier 0%
+ querier/queryrange 0%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
@calvinbui looks like a markdown linting error? |
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. + ingester 0%
+ distributor 0%
+ querier 0%
+ querier/queryrange 0%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
I've updated my branch. I didn't do any changes to the markdown before, and this time around either. |
@calvinbui looks like all we need is one more rebase, a lot moving on the helm chart these past few days 😄 Thanks! |
./tools/diff_coverage.sh ../loki-main/test_results.txt test_results.txt ingester,distributor,querier,querier/queryrange,iter,storage,chunkenc,logql,loki Change in test coverage per package. Green indicates 0 or positive change, red indicates that test coverage for a package fell. - ingester -0.1%
+ distributor 0%
+ querier 0%
+ querier/queryrange 0%
+ iter 0%
+ storage 0%
+ chunkenc 0%
+ logql 0%
+ loki 0% |
😦😩 |
) **What this PR does / why we need it**: Ignore the headless service from the Prometheus service-monitor as it was resulting in duplicate metrics. Replaces #7049
…afana#7638) **What this PR does / why we need it**: Ignore the headless service from the Prometheus service-monitor as it was resulting in duplicate metrics. Replaces grafana#7049
Signed-off-by: Calvin Bui 3604363+calvinbui@users.noreply.github.com
What this PR does / why we need it:
The Helm chart deploys two services,
loki
andloki-headless
.The
loki_boltdb_shipper_compactor_running
metric will show all loki pods attached to both services.The Prometheus rule in the chart,
LokiTooManyCompactorsRunning
, does an aggregation over an entire namespace, which will always double the amount of compactors it detects.Which issue(s) this PR fixes:
Fixes N/A
Special notes for your reviewer:
Checklist
CHANGELOG.md
.docs/sources/upgrading/_index.md