Skip to main content

Splunk On-Call

Causely can send high-context causal insights directly to Splunk On-Call (formerly VictorOps), so your on-call team receives the signal, not the noise. With enriched context like impacted services, problem severity, and diagnostic summaries, alerts become more actionable and reduce time-to-resolution.

Splunk On-Call can be used as a notification destination in Causely.

All Splunk On-Call delivery runs through the Causely Mediator.

How you define Splunk On-Call destinations depends on your setup:

  • Managed Notifications (recommended)
    Routing rules and Splunk On-Call credentials are configured in the Causely UI. The UI stores configuration that the Mediator reads at runtime.

  • Mediator-based configuration (advanced)
    Define Splunk On-Call destinations programmatically with environment variables or Kubernetes secrets instead of the UI. Uses the same Mediator delivery path as managed notifications.

For routing rules and filters in the UI, see Set up notification routing in the UI.

Mediator-based configuration (advanced)

If you prefer not to use the UI, define Splunk On-Call destinations with a Kubernetes secret in the causely namespace:

apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: splunk-notification-config
namespace: causely
labels:
causely.ai/notif-config: Splunk
stringData:
notif_config_filters: "[]"
notif_config_filters_enabled: "true"
notif_config_global: "false"
notif_config_name: splunk
notif_config_token: "causely"
notif_config_type: Splunk
notif_config_url: https://alert.victorops.com/integrations/generic/12356789/alert/ab12cd34-ef56-7890-ab12-34cd56ef7890
note

Replace the placeholder values with your actual integration URL and routing key from Splunk On-Call.


Notification Payload Format

Causely sends structured alert payloads to Splunk On-Call, including rich metadata about the actual causes and their service-level impact.
For an example payload and explanation of each field, refer to the Notification Payload Format page.