This is the guide to all things Rootly.
The Setup Guide is designed to take you on a brief tour of the main features available in Rootly and where to find the documentation to configure them.
Quick Start Guide
If you haven't already signed up for a Rootly account, see our Quick Start Guide to get signed up with Rootly before you go any further with this Setup Guide.
Add an Integration
Rootly integrates tightly with third-party services such as PagerDuty or Slack to provide an enhanced incident management experience. Configuring an integration only takes a few minutes. We've provided complete documentation to get you started.
At a minimum, we recommend adding Slack for chat functionality; an alerting integration such as PagerDuty, Opsgenie, or VictorOps; and a conferencing solution such as Zoom or Google Meet to automate creating a virtual war room when an incident occurs.
For other integrations see the full list of integrations Rootly supports. Next up is to invite fellow team members to Rootly.
Unless you're flying solo, you'll have other team members you want to invite to Rootly to help manage incidents. Inviting users only takes a few seconds each. They can be invited directly in the Rootly administrative interface, or through third-party integrations such as Slack, PagerDuty, VictorOps, or Opsgenie.
See the Rootly user administration documentation for more information.
Teams let you group staff together into a logical unit to which you can attach functionality such as Slack channels, email notifications, status pages, and linking to third party services. Once you've added your users, you'll want to group them into teams based on area of responsibility.
You can create teams and assign users via the Rootly web UI, or by importing them directly from third-party services such as PagerDuty, VictorOps, or Opsgenie. Instructions for adding teams are provided on the teams documentation page.
When using Rootly, a service provides a way to send alerts to team members and stakeholders when something isn't working right. Services let you attach what actions should be taken when things break, and also defines who owns a service and who should be notified.
Status pages let users know when something might be wrong with your application. They can be used to let business stakeholders know whether the services they use are fully functional and when they aren't.
It only takes about a minute to configure a status page, so give it a try.
Incidents are at the heart of how Rootly helps make your life easier. Now that you've added integrations, team members, and services it's time to create an incident.
Check out the Rootly documentation to learn about all of the features available to you with Rootly.
Book a demo for an in person explanation of Rootly's features.
For more personalized help, see the online chat in the web interface.