-
Notifications
You must be signed in to change notification settings - Fork 25
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
[RabbitMQ] Updatings values.yaml to enable monitoring and readme instructions #5
base: master
Are you sure you want to change the base?
Conversation
- [Updating from 1.6.1](#updating-from-161) | ||
- [Exporting metric to Prometheus](#exporting-metric-to-prometheus) | ||
- [Verify metrics are being published](#verify-metrics-are-being-published) | ||
- [Finally verify that the target is in prometheus](#finally-verify-that-the-target-is-in-prometheus) |
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.
I like the ToC. Did you use a generator for this?
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.
@@ -97,3 +119,521 @@ rabbitmqAmqpsSupport: | |||
ssl_options.verify = verify_peer | |||
ssl_options.fail_if_no_peer_cert = false | |||
``` | |||
|
|||
# Updating from 1.6.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.
Can we put everything below this in another .md
file named updating_from_1.6.1.md
and either link to it or just leave it as another file, because this chart will be updated again and the question is, do you keep the 1.6.1 update here or do you delete it or what? I think moving it out to another file now makes the main README.md
clean and approachable.
No description provided.