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

[RabbitMQ] Updatings values.yaml to enable monitoring and readme instructions #5

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

grebois
Copy link
Collaborator

@grebois grebois commented Jul 17, 2018

No description provided.

@grebois grebois changed the title Updatings values.yaml to enable monitoring and readme instructions [rabbit] Updatings values.yaml to enable monitoring and readme instructions Jul 19, 2018
@grebois grebois changed the title [rabbit] Updatings values.yaml to enable monitoring and readme instructions [RabbitMQ] Updatings values.yaml to enable monitoring and readme instructions Jul 19, 2018
- [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)
Copy link
Owner

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?

Copy link
Collaborator Author

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
Copy link
Owner

@sekka1 sekka1 Jul 20, 2018

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.

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.

2 participants