.svg)
Catalog Sync in CLI
Catalog Sync is a new command-line tool that keeps your Rootly Catalog matched to the systems you already treat as the source of truth. Point it at GitHub repositories, Backstage, CSV files, REST or GraphQL APIs, local files, or the output of any command, and it reconciles services, teams, and metadata into Rootly on its own. No manual upkeep, no copy-paste drift.
It works the way infrastructure tools should. Run plan to preview every change before it happens, apply to execute, and status to verify the result. A single sync command does plan and apply in one step, watch keeps the loop running continuously, and tui opens an interactive view.
What's included
- Eight source types: inline entries, local files, GitHub repositories, Backstage, GraphQL endpoints, CSV files, HTTP REST APIs, and command output
- A Terraform-style workflow with
plan,apply, andstatus, plussync,watch, and an interactivetui - Safe-by-default operations: deletions are opt-in, an empty source aborts the run instead of wiping your catalog, and configurable prune thresholds stop accidental mass deletions
- Automatic creation of custom properties on services, teams, and other resources
- Reference linking between native Rootly resources and custom catalogs
- Install with Homebrew, Go, Docker, or Kubernetes Helm
Why it matters
A catalog maintained by hand goes stale the week after it is written, and a stale catalog quietly breaks the things built on top of it: alert routing, service ownership, and impact analysis during an incident. Catalog Sync makes your existing systems the single source of truth and keeps Rootly mirrored to them automatically. Get started with the Catalog Sync documentation.
Mute alerts on mobile
The Rootly mobile app now has a mute option to silence pages during alert storms. Muting disables push notifications, phone calls, and text message paging for a duration you choose, so your phone is not exploding with Alerts, and you can focus on your investigation. Alerts still fire and still escalate through your escalation policy; they just stop notifying you until the mute period ends.
What's included
- Mute straight from a notification with a long press, from the alert in the app, or from the icon on alert banners
- A mute duration you choose, after which notifications resume on their own
- Alerts keep firing and escalating while muted, so nothing is dropped and your team's escalation path still runs
- Available now for all customers on iOS and Android
Why it matters
During an alert storm, the flood of pages becomes its own incident: every new push, call, and text pulls you away from the thing you are trying to fix. Muting lets you quiet your own device without silencing the alerts themselves, so you keep your focus and your team keeps its safety net.
Upwind integration
Rootly now integrates with Upwind, the runtime cloud security platform. Set up Upwind to create alerts and incidents in Rootly based on runtime findings in Upwind, then page the relevant responder by routing the alert with alert routes and escalation policies.
Security findings are incidents too, but they often live in a separate tool with a separate process. Sending Upwind's runtime findings into Rootly pages the right on-call responders and puts security events through the same response process the rest of your organization already uses.
