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

add ConfigMap generate script #1

Merged
merged 1 commit into from
Oct 31, 2016

Conversation

brancz
Copy link
Collaborator

@brancz brancz commented Oct 28, 2016

This also contains the generated ConfigMaps for the grafana dashboards
as well as for alerts. These will be updated in subsequent changes as
sets of alerts and dashboards are added/updated in the respective
subdirectories in /assets.

In general this allows the dashboards to actually be reviewed as changes in the json are now actually visible. To be able to review them best it would be good if we always format them the same way. Right now I did this with cat *-dashboard.json | python -m json.tool, which would be good to document at some point so people who want to contribute know the procedure. Let me know if you think we should do that straight away.

@fabxc also let me know what you think about removing the etcd alerts for now. If you want I can add them back in, but then they will be included in the set of alerts in the ConfigMap, I figured that that might not be what we want right now.

This also contains the generated ConfigMaps for the grafana dashboards
as well as for alerts. These will be updated in subsequent changes as
sets of alerts and dashboards are added/updated in the respective
subdirectories in `/assets`.
@fabxc
Copy link
Contributor

fabxc commented Oct 31, 2016

Okay, we can remove etcd3 alerts for now. Theoretically, it shouldn't matter as the alerts will simply have no effect in absence of the used metrics.

Rest sounds good. Documentation is the most important part of this repository, I'd say. So we should have it.
We might want to split out from the main README into distinct ones eventually.

👍

@brancz
Copy link
Collaborator Author

brancz commented Oct 31, 2016

sounds like a plan 👍 don't have merge rights ... if you would be so kind @fabxc 😁

@fabxc
Copy link
Contributor

fabxc commented Oct 31, 2016

You have now.

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.

None yet

2 participants