Back to Changelog
Back to Changelog

July 18, 2024

On-Call

👯‍♀️ On-Call Shadowing

👯‍♀️ On-Call Shadowing

Shadowing experienced responders is one of the most effective ways for folks who are new to on-call to gain the confidence and knowledge to handle incidents independently. Traditionally, shadow rotations are cumbersome to set up, involving duplicating and editing an existing schedule. For Rootly On-Call users, setting up shadow rotations couldn’t be easier with our new native Shadowing feature. Here are a few highlights:

Easy to use: Shadowing is enabled out-of-the-box and ready for you to start using today.

Seamless integration: It won’t interfere with your current schedules and allows new users to shadow without stress.

No manual setup: No need to set up duplicate schedules or manually add/remove team members – it’s all handled automatically.

Multiple shadows: You can have multiple team members shadow at the same time, making it easier to train larger groups.

Shadow schedule or users: You can create shadows for an entire schedule OR only shadow a specific on-call user that's part of the given schedule. 

Limit hours or days for shadowing: Want to avoid complications due to trainees getting paged on weekends or evenings? You can specify the hours your shadow users are active within any schedule without impacting your 24/7 coverage.

Set a specific time frame for shadowing: You can predefine the start and end date for a specific user to shadow. For example, you can have a mandatory 1 month shadow period for new team members, you can set it and forget it. No need to go in at the end of the period and remove them from the shadow schedule.

Shadows are available now in any on-call schedule. Navigate to On-Call > Schedules and open an existing schedule or create a new one. From there, you’ll see a Shadows tab on the left side.

Set up shadow rotations from the On-Call Schedules tab.

For full instructions to configure Shadows and a video demo, visit our Help Docs!

🌝 New & Improved

🆕 List active incidents Slack command (/rootly list) can now be further filtered by impacted services.

🆕 Amazon CloudWatch can now be integrated as a native alert source to Rootly On-Call.

💅 Improved user experience for manually adding incident timeline events. Input field is now inline with the timeline, instead of using a pop-up modal.

💅 Incident metrics graphs can now grouped by “Incident Creator”.

🐛 Fixed inability to save updates made to existing status page configurations.

🐛 Fixed bug where previous incident role attribute is not being saved when updates are made through Slack.

🐛 Fixed inability to filter audit log by date.

Previous post
Previous post
You are viewing the latest post

Backfill and Import Past Incidents

Customizable Interactive Tutorials

Workflow Debugger

Required, Default, and Customizable Fields

Zapier Integration

Scheduled Maintenance

Branded Emails and Custom SMTP Server

🕵️On-Call Schedule Owners & Gap Finder

Incident Variable Explorer

Statuspage.io Integration - Component & Template Support

Sandbox Environments

Rollbar Integration

Beautiful Incident Timeline Pages

Manage Workflows via API, Terraform, and Pulumi

Customizable Incident Metrics

Microsoft Teams Integration

Microsoft Azure Active Directory SSO Integration

Backstage Integration

Linear Integration

Workflow Versioning

Incident Feedback

Retroactively Create Incidents and Modify Timestamps

Pulumi Provider for Rootly

Notion Integration

SCIM