Create a VictorOps notifier

To create a VictorOps notifier, create an API key in VictorOps and then create a VictorOps notifier in Chronosphere Observability Platform.

Create a service API key in VictorOps

Before creating a VictorOps notifier in Observability Platform, enable the Prometheus integration in VictorOps and create a service API key. See the REST endpoint integration guide in the VictorOps documentation for more information. To configure a VictorOps notifier:

In VictorOps, click the Integrations tab.
Search for Prometheus, and then click Enable Integration.
Copy the Service API Key value.
Open the pre-configured REST integration, and copy the URL to notify value.
In the navigation menu select Settings > Routing Keys and review your routing keys. If you have any routing keys defined, copy the appropriate value for the team you want to route this notifier to.

Create a VictorOps notifier in Observability Platform

After creating a service API key in VictorOps, you can create a VictorOps notifier in Observability Platform. You can use variables in your notifiers.

Web
Chronoctl
Terraform
API

To create a VictorOps notifier:

In the navigation menu select Alerting > Notifiers.
Click Create notifier.
Enter a descriptive name for the notifier.
Select VictorOps as the type of notifier you want to create.
In the API Key field, enter the value of your VictorOps API key.
In the API URL field, enter the URL to notify value you copied from VictorOps, which is called as a POST request. For example:
```
https://alert.victorops.com/integrations/generic/20131114/alert/
```
In the Routing Key field, enter the routing key you copied from VictorOps.
Optional: Select Notify when resolved to send a resolved alert notification.
Click Save.

To create one or more notifiers using Chronoctl, create a YAML file that defines them and apply the configuration to your instance.

You can use the notifiers scaffold command to generate an example notifier, and then copy the resource definition for your notifier type:

chronoctl notifiers scaffold

Define the resource definition for your VictorOps notifier:

api_version: v1/config
kind: Notifier
spec:
  name: NAME
  slug: SLUG
  skip_resolved: true
  victor_ops:
    - api_key: 'API_KEY'
      api_url: https://alert.victorops.com/integrations/generic/20131114/alert/
      routing_key: 'test'

Replace the following:

NAME: A descriptive name, such as test-victorops.
SLUG: A unique identifier, such as team-victorops.
API_KEY: Your VictorOps API key.

Enter the URL to notify value you copied from VictorOps as the value in the api_url field.
Enter the routing key you copied from VictorOps as the value in the routing_key field.
Apply the changes:
```
chronoctl apply -f FILE_NAME.yaml
```
Replace FILE_NAME with the name of your notifier YAML file.

To create a VictorOps notifier:

Create a VictorOps notifier with Terraform by using the chronosphere_victorops_alert_notifier type followed by a name in a resource declaration:

resource "chronosphere_victorops_alert_notifier" "test_victorops" {
  name          = "test-victorops"

  # Optional slug of the victorops notifier.
  slug = "vo-test-notifier"

  ## Notifier-specific required configuration
  # Detailed definitions can be found at: https://prometheus.io/docs/alerting/latest/configuration/#victorops_config
  api_key       = "0b590c67-20d6-40ba-afb4-84f0808dd969"
  api_url       = "https://alert.victorops.com/integrations/generic/20131114/alert/"
  routing_key   = "test"

  ## Notifier-specific optional configurations
  message_type = "CRITICAL" # (Default) OR: WARNING, INFO
  entity_display_name = "summary of the problem"
  state_message = "long explanation of the problem"
  monitoring_tool = "Chronosphere"

  # Can have multiple custom fields.
  custom_fields = {
    "first_field" = "interesting value"
  }

  ## (Optional) Base configuration common to all notifiers
  send_resolved = true # The default value

  ## (Optional) HTTP configuration common to HTTP notifiers
  basic_auth_username = "username"
  basic_auth_password = "strong+p@ssword"
  # Can use bearer_token instead of basic auth
  tls_insecure_skip_verify = false
}

Enter your VictorOps API key as the value in the api_key field.
Enter the URL to notify value you copied from VictorOps as the value in the api_url field.
Enter the routing key you copied from VictorOps as the value in the routing_key field.
Run terraform apply to create the notifier resource.
```
terraform apply
```

To complete this action with the Chronosphere API, use the victor_ops object in the CreateNotifier endpoint.Because the Chronosphere API requires authentication, include an API token with your curl request, as shown in the following example. For more details, see Create an API token.

export CHRONOSPHERE_API_TOKEN="TOKEN"
export CHRONOSPHERE_DOMAIN="INSTANCE.chronosphere.io"

curl -H "API-Token: ${CHRONOSPHERE_API_TOKEN}" \
     -X METHOD "https://${CHRONOSPHERE_DOMAIN}/ENDPOINT_PATH"

Replace the following:

TOKEN: Your API token.
INSTANCE: The subdomain name for your organization’s Observability Platform instance.
METHOD: The HTTP method to use with the request, such as GET or POST.
ENDPOINT_PATH: The specific endpoint you want to access.

Observability Platform

Telemetry Pipeline

More information

Create a service API key in VictorOps

Create a VictorOps notifier in Observability Platform

Observability Platform

Telemetry Pipeline

More information

Documentation Index

​Create a service API key in VictorOps

​Create a VictorOps notifier in Observability Platform

Create a service API key in VictorOps

Create a VictorOps notifier in Observability Platform