Read-only alert triage brief for Rootly. It reads alerts, services, teams, and recent incidents through recued-core.rootly, then summarizes noisy sources, related service/team context, likely incident candidates, and next triage steps. It never creates, acknowledges, resolves, or edits alerts or incidents, never mutates alert routes or sources, and never calls arbitrary Rootly API routes.

How it works 17 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (17 steps)

■ status_filter trim

Trim whitespace from setting status

■ source_filter trim

Trim whitespace from setting source

■ alerts_raw ?

■ services_raw ?

■ teams_raw ?

■ recent_incidents_raw ?

■ alerts default

Apply default

■ services default

Apply default

■ teams default

Apply default

■ recent_incidents default

Apply default

■ alert_count count

Count items in alerts

■ summarize ?

■ alert_rows slice

Take a subset of

■ incident_rows slice

Take a subset of

■ alert_table to_table

Format results as a data table

■ incident_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize Rootly alerts for status, noisy sources, affected services or teams, related recent incidents, and concrete triage next steps. Do not invent facts outside the Rootly data.

rootly setting =

source setting =

status setting =

page size setting = 25

row limit setting = 12

max length setting = 900