Add flag to only use prometheus exporter on kubernetes cluster #231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcpomfret
force-pushed
the
prometheus-k8s-switch
branch
from
f4e2b81 to
1d2978a
Compare
theseanything
approved these changes
Apr 7, 2022
marcpomfret
force-pushed
the
prometheus-k8s-switch
branch
from
1d2978a to
d493c8b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable prometheus_exporter on EKS only, extra latency and 500 errors caused on EC2 instances running unicorn, don't expect to see the same on EKS with puma
(Collections 2712)Had to be reverted due to increased latency being seen on the controllers of the collections app running on EC2 instances.
