![]() To create a Runbook step to kick off a Splunk On-Call incident: Select the routing keys you wish to import and link them to existing services (or create new services).Ĭreating a Splunk On-Call incident from a Runbook step.From the Select an import source dropdown menu, select VictorOps.In the FireHydrant left nav, go to Service Catalog > Services.To configure the link and import process: Refer to Splunk On-Call's documentation for details on managing alert Routing Keys. If services you have linked to a Routing Key are impacted during an incident, FireHydrant directs an alert to the linked Routing Key-which in turn alerts the team members associated with its targeted escalation policy. FireHydrant allows you to import Routing Keys and link them to specific services so that the proper teams are paged whenever services are impacted by an incident. Using Routing Keys is the preferred way to create and route alerts to the right team or escalation policy in Splunk On-Call. That Routing Key dictates one or more escalation policies that will be alerted. With Splunk On-Call (VictorOps), you submit an alert to a Routing Key. Importing and linking routing keys to new or existing services To view or modify them, you must have administrative credentials. Note: Splunk On-Call Outgoing Webhooks are an Enterprise service level feature. Select the Any-Incident value from the event dropdown.(Splunk On-Call sends a default payload to FireHydrant.) Click Add Webhook and enter in the URL provided in FireHydrant.Click Integrations > Outgoing Webhooks.This opens your VictorOps configuration details page, where a webhook URL has been generated for you. Return to the configuration page by clicking the VictorOps tile on the Integrations page.Synching an incident state from Splunk On-CallĪfter you have configuring your integration, you need to set up an outgoing Splunk On-Call (VictorOps) webhook, so FireHydrant can synchronize incident states from Splunk On-Call. FireHydrant creates a new installed integration for VictorOps on your Connected & Available integrations list. (For details, see the Splunk On-Call documentation.) If the REST endpoint integration has not been enabled, click the blue Enable button to generate your endpoint destination URL. Under URL to notify, your routing key is included in the destination URL, between /alert/ and /$routing_key. To find your REST Endpoint Token, go to Splunk On-Call's Integrations page and locate the REST integration.If you don’t see them, reach out to your organization’s administrator. You can find and generate these on the Spl unk On-Call Integrations page under the API tab. Enter your Splunk On-Call API ID and an API Key.Enter your Splunk On-Call (VictorOps) Organization name.(This tile is still labeled "VictorOps" in the FireHydrant UI, although the product was recently renamed "Splunk On-Call.") ![]() On the VictorOps integration tile, click Setup.Click Integrations in the FireHydrant left nav.Installing the Splunk On-Call Integration This is a great way to coordinate your incident response, from right within FireHydrant, after an initial alert comes in from Splunk On-Call. With our Splunk On-Call integration, you can easily link your incidents in Splunk On-Call (formerly VictorOps) to your incidents in FireHydrant.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |