-
Notifications
You must be signed in to change notification settings - Fork 27
Added Dashboard Group and Sample Detectors for Inferred Services #80
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
Added Dashboard Group and Sample Detectors for Inferred Services #80
Conversation
|
CLA Assistant Lite bot CLA Assistant Lite bot All contributors have signed the COC ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
|
I have read the Code of Conduct and I hereby accept the Terms |
greatestusername-splunk
left a comment
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.
A few ease of use asks but otherwise approved.
This looks great and thank you so much for contributing this!
| @@ -0,0 +1,90 @@ | |||
| curl --location 'https://api.us1.signalfx.com/v2/detector' \ | |||
| --header 'Content-Type: application/json' \ | |||
| --header 'X-SF-TOKEN: REPLACEME' \ | |||
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.
Might I suggest pulling from an environment variable in these scripts and noting the env var to use in the README so folks don't have to put their key in a file?
Thoughts?
| @@ -0,0 +1,57 @@ | |||
| curl --location 'https://api.us1.signalfx.com/v2/detector' \ | |||
| --header 'Content-Type: application/json' \ | |||
| --header 'X-SF-TOKEN: REPLACEME' \ | |||
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.
same thought here RE: env var
| ## Inferred Services - Sample Detectors | ||
|  | ||
|
|
||
| Use curl command to post the detector (replace `Token` and `Realm` as required). |
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.
typo? Uses
Maybe "This script uses the curl command..."?
| @@ -0,0 +1,90 @@ | |||
| curl --location 'https://api.us1.signalfx.com/v2/detector' \ | |||
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.
please chmod the *.sh files to something like 766 so anyone can read/write but only owner can execute. Currently script isn't executable without chmoding it.
|
|
||
| Use curl command to post the detector (replace `Token` and `Realm` as required). | ||
|
|
||
| These can be used as a starting point to customise signals, thresholds, messaging etc. |
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.
Would you mind noting something along the lines of
"The created detector will not be filtered to any specific inferred service and will not have any notification paths set unless you make those changes in the detector or script."
Just so folks know they are going to need to configure a few things in particular?
Assets to help using new inferred.services metrics: Dashboard group & Sample detectors.