is available out of the box with Opsview Monitor. Like PagerDuty, VictorOps is
a message platform where Users can send various messages to VictorOps, and
create rules within the VictorOps application to dispatch alerts via various
methods such as SMS, Email, etc to individuals or groups of Users. Users need
to setup an account on VictorOps and follow the steps below to activate it on
the Opsview system.
Activate the method by setting it to
‘Active’, like the screen above.
Once logged in, navigate to ‘Integrations’ and create a new REST
Next, navigate to ‘Settings > Schedules’ and add a new Team,
in order to get a Routing key for your Users:
Once the team is added scroll down until you see the team name
and its schedule and click on ‘Setup Routing’:
Once you have clicked on ‘Setup Routing’, scroll down to the
bottom of the page where you can view and add routing keys:
Now that we have the API key (as seen above) and the routing
key (as seen above), we can now configure Opsview Monitor. First, add the
API Key (from the step above, the big ugly bit after ‘/alert/’) to the Notification
Method , as shown below:
Next, simply add the routing key to the Users who you wish to
receive alerts. To do this, simply edit the User via ‘Settings > Users and Roles
>’ and open the User edit modal window. Within the window, click on the
‘Notifications’ tab and you will be able to see the ‘VictorOps Routing Key:’
field as below. If you do not see
this field, it is likely you have not set the Notification Method to ‘Active’
(see the first bullet).
And that’s all the
configuration that is required. In order to send notifications into VictorOps,
a Notification Profile that uses the ‘VictorOps’ Notification Method must be
configured. This is covered in Section ‘4.11.3. Notification Profiles’.
VictorOps only works with Nagios notifications; BSM notifications are not
Once the Notification
Profile is configured, Notifications should start arriving in VictorOps, as
If you have
configured your team schedules correctly, you should start receiving emails in
Please note: This Guide was written August 2015. The
VictorOps.com User interface may have changed since; therefore, please let us
know if any screens are out of date.