Skip to content

Added VictorOps configuration to docs #724

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

Merged
merged 3 commits into from
Apr 28, 2017

Conversation

conr
Copy link
Contributor

@conr conr commented Apr 27, 2017

No description provided.

# The API key to use when talking to the VictorOps API.
api_key: <string>

# The VictorOps webhook URL.
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems more likely to be an API URL.

# A key used to map the alert to a team.
[ routing_key: <string> ]

# Describes the behavior of the alert.
Copy link
Contributor

Choose a reason for hiding this comment

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

You should mention the possible values, keeping in mind the munging we do.

@@ -408,6 +408,30 @@ api_key: <string>
# Comma separated list of tags attached to the notifications.
[ tags: <tmpl_string> ]
```
## `<victor_ops_config>`

VictorOps notifications are sent out via the [VictorOps API](https://portal.victorops.com/public/api-docs.html#/)
Copy link
Contributor

Choose a reason for hiding this comment

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

api_key: <string>

# The VictorOps API URL.
[ api_url: <string> ]
Copy link
Contributor

Choose a reason for hiding this comment

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

This is defaulted to the global setting

@brian-brazil brian-brazil merged commit a45d74f into prometheus:master Apr 28, 2017
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.

2 participants