VictorOps¶

This page documents a legacy sink in Robusta classic

For new setups, we recommend HolmesGPT instead.

HolmesGPT triages your alerts instead of just forwarding them. Sinks are deterministic: they send every notification, unchanged, to a fixed destination, leaving you to read and prioritize each one yourself.

HolmesGPT instead uses AI to investigate each alert, surface the likely root cause, and escalate only what needs attention — so you get fewer, more actionable notifications. Set this up with Alerts Triage for alerts, or Triggered Workflows for custom events.

Robusta can report issues and events in your Kubernetes cluster to the VictorOps alerts API.

To configure VictorOps, a VictorOps REST endpoint (url) is needed.

Consult the VictorOps REST endpoint integration guide.

Configuring the VictorOps sink¶

Add this to your generated_values.yaml

sinksConfig:
    - victorops_sink:
        name: main_victorops_sink
        url: <REST endpoint> # e.g. https://alert.victorops.com/integrations/generic/20131114/alert/4a6a87eb-fca9-4117-931a-c842277ea90a/$routing_key

Save the file and run

 helm upgrade robusta robusta/robusta --values=generated_values.yaml

Example Output:

Typically you'll send alerts from Robusta to VictorOps and not deployment changes. We're showing a non-typical example with deployment changes because it helps compare the format with other sinks.