☰

Introduction

Getting Started

Monitors

Creating Monitors
Recording Monitors

Scripting

Protocol Scripts
Browser Scripts
Code Blocks
Variables & Expressions

Configuration

Receiving Notifications
Managing Your Team

Integrations

Opsgenie Integration
PagerDuty Integration
Slack Integration
VictorOps Integration
Webhooks

Important Note

Speedway has moved into Loadster Site & API Monitoring.

If you have an existing Speedway account, you can use the same credentials to sign in to Loadster. Don't worry, your monitors haven't missed a beat and your monitoring data is intact. Everything that Speedway did, Loadster now does the same or better.

We're leaving the Speedway documentation up for the time being, but strongly encourage you to refer to the Site & API Monitoring section of the Loadster manual.

Integrating Speedway with VictorOps

VictorOps simplifies your approach to incident response. Whenever one of your monitors fails or recovers, Speedway will automatically create or update an incident in VictorOps. You can then set your own alert policies, route or escalate the issue automatically to whoever’s on call, and track of time to issue resolution across your entire organization.

It’s easy to integrate Speedway with VictorOps!

Enabling the VictorOps Integration

In your Speedway account, go to your Integrations page. Click the Enable VictorOps button in the VictorOps section.

You’ll be prompted for two things: a required Service API Key and an optional Routing Key. You’ll need to get these from your VictorOps account. To get a Service API Key that Speedway can use to communicate with VictorOps on your behalf, follow these steps:

  1. Log in to your VictorOps portal.
  2. Visit the Integrations tab.
  3. Find Speedway in the 3rd Party Integrations. If it’s not showing up, you can use the generic REST integration.
  4. Enable the Speedway integration.
  5. VictorOps will generate a Service API Key or Service API Endpoint that Speedway can use to communicate with the VictorOps API. If it’s a Service API Key, copy the key and paste it into Speedway. If it’s a Service API Endpoint, extract only the UUID portion of the URL near the end, and copy and paste it into Speedway.

You can also enter a Routing Key if you want Speedway incidents to follow specific routing rules when they are sent to VictorOps. If you don’t have a Routing Key in mind, or don’t know what this is for, simply leave it blank or enter everyone.

Testing the VictorOps Integration

Now that the integration is enabled, each time one of your Speedway monitors fails, an incident will be created in VictorOps. Incidents usually show up in VictorOps within seconds. When the same Speedway monitor recovers, the incident will be resolved in VictorOps.

You can test this by creating a Speedway monitor that points to an invalid location, submits invalid data, or is otherwise broken.

Getting Help

We’re happy to assist you if you have any trouble with the Speedway integration with VictorOps. If you encounter a problem that’s not covered on this page, get in touch at help@speedway.app and we’ll work through it with you.