Raise the priority for 'changed' event types so they're visible #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e default UI If your Puppet infrastructure never fails, let's say because you have a good testing pipeline, it might not be obvious to you that any Puppet events are being reported because everything but failures is 'low' priority. Datadog's web UI defaults to showing only things of 'normal' priority. This changes the priority of a 'changed' resource to 'normal' since a change of configuration is useful information to use when correlating data or showing events in a dashboard.
|
@rtyler thank you very much for this! We will be reviewing this shortly. |
talwai
added a commit
that referenced
this pull request
Jan 19, 2016
Raise the priority for 'changed' event types so they're visible
cegeka-jenkins
pushed a commit
to cegeka/puppet-datadog_agent
that referenced
this pull request
Jan 31, 2018
Raise the priority for 'changed' event types so they're visible
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If your Puppet infrastructure never fails, let's say because you have a good
testing pipeline, it might not be obvious to you that any Puppet events are
being reported because everything but failures is 'low' priority. Datadog's web
UI defaults to showing only things of 'normal' priority.
This changes the priority of a 'changed' resource to 'normal' since a change of
configuration is useful information to use when correlating data or showing
events in a dashboard.