-
Notifications
You must be signed in to change notification settings - Fork 23
Add generic blackbox monitoring configuration #1028
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
Conversation
eba14f9
to
d9187c4
Compare
d9187c4
to
facde12
Compare
facde12
to
c7677ab
Compare
a3432dc
to
e7b4a9e
Compare
Marked as draft as recent changes are untested |
b244f26
to
1150cc7
Compare
16dc469
to
562affb
Compare
562affb
to
12815dd
Compare
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'm not opposed to merging this as-is, but it would be good to investigate the file based service discovery approach I mentioned upstream. We should be able to do something similar downstream, but using Kayobe to write out the service discovery file(s) instead of the KA roles.
is it ready to merge? it would be good to define blackbox exporter defaults |
From the monitoring R&D discussion, we're going to proceed with this style downstream, and investigate file based discovery upstream |
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.
Good stuff @Alex-Welsh
No description provided.