Support optional datadog events for haproxy check #103
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
|
@evan2645 Looks good, will add to the next round of fixes. Thanks! |
|
Hi @evan2645 This feature is currently disabled as it was a too spammy feature to be useful. There is a metric that exists that you can enable to get the status of of your backends: https://github.com/DataDog/dd-agent/blob/master/conf.d/haproxy.yaml.example#L9 You should probably use that instead. |
miketheman
added a commit
that referenced
this pull request
Mar 20, 2014
|
Hi @evan2645, |
n1koo
pushed a commit
to Shopify/chef-datadog
that referenced
this pull request
Oct 20, 2014
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.
The haproxy check that ships with datadog agent can optionally create events. That option is not currently supported in the yaml config shipped by chef-datadog; let's make it so.