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 Initial Runbook Readme.md #26

Merged
merged 6 commits into from
Jun 17, 2018

Conversation

StevenACoffman
Copy link
Contributor

I noticed that the monitoring-mixin rules/alerts don't come with any runbook links defined, which I feel is a missed opportunity. For an alert detecting standard problems, a link to a remediation (or at least description of the problem being measured) is very welcome.

I have not altered the ksonnet files to add the runbook annotations that are missing (compared to prometheus-operator rules), nor do I have a plan to automatically generate this markdown file from the ksonnet files if that's possible or desirable.

This is an initial effort, and I won't feel bad if someone does this better. I had not added meaningful descriptions to these alerts, but I hope that it can be improved over time.

@tomwilkie
Copy link
Member

Love it! I think as an MVP we should put the links in the alerts, and I see no problem with the being straight back to the github repo. WDYT?

I hope that it can be improved over time.

Thats my philosophy too! This is a great starting point.

@StevenACoffman
Copy link
Contributor Author

StevenACoffman commented Jun 7, 2018

Thanks! I do not currently speak ksonnet, so I'd rather have adding the links be a follow-up or get assistance.

@tomwilkie
Copy link
Member

No worries I'm sure I can whip something up; mind if I push to this branch?

@StevenACoffman
Copy link
Contributor Author

Sounds great!

Copy link
Member

@brancz brancz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content like this is typically licenced under creative commons, should we make a distinction here?

(apart from that there is no license specified at all in the repo, which we should fix @tomwilkie )


```
annotations:
runbook: https://github.com/StevenACoffman/kubernetes-mixin/tree/master/runbooks#alert-name-kubeapidown
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use the alert name in a template here, so we can just re-use the same runbook template link of all alerts.

@tomwilkie
Copy link
Member

Looking into this today

Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
@tomwilkie
Copy link
Member

I've added the magic to automatically add the links (yay jsonnet!), sorry it took so long. Let me know what you think @StevenACoffman @brancz!

@tomwilkie tomwilkie self-requested a review June 17, 2018 10:18
Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
@StevenACoffman
Copy link
Contributor Author

Ah! Your last commit fixed my ksonnet issue when I tested it out. LGTM
Thanks!

@tomwilkie
Copy link
Member

Content like this is typically licenced under creative commons, should we make a distinction here?
(apart from that there is no license specified at all in the repo, which we should fix @tomwilkie )

Missed this - I say we keep it simple right now, one license for the repo. Will make a PR for license.

@tomwilkie tomwilkie merged commit 3c42248 into kubernetes-monitoring:master Jun 17, 2018
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.

3 participants