list_environments
List Environments
List all environments configured in Rootly (e.g., production, staging, development). Use this to find environment IDs when creating incidents or alerts.
list_environments
List all environments configured in Rootly (e.g., production, staging, development). Use this to find environment IDs when creating incidents or alerts.
create_incident
Create a new incident in Rootly. Optionally associate it with services, environments, severities, and teams. The incident title is auto-generated if not provided.
list_incidents
Search and list incidents in Rootly. Filter by status, severity, services, or teams. Supports pagination and sorting. Use this to find active incidents, review past incidents, or audit incident history.
list_on_call
List who is currently on call. Returns active on-call assignments across schedules and escalation policies. Use this to find who is responsible for responding to incidents right now.
update_incident
Update an existing incident in Rootly. Change status, severity, title, summary, linked services, or add mitigation/resolution messages. Use this to transition incidents through their lifecycle (e.g., triage → mitigated → resolved).
create_action_item
Create a follow-up action item for an incident. Action items track tasks that need to be completed after an incident. Assign to a user, set priority, and optionally set a due date.
list_severities
List all severity levels configured in the Rootly organization. Use this to find severity IDs when creating or updating incidents.
list_teams
List teams in Rootly. Search by name, slug, or keyword. Use this to find team IDs for filtering incidents or assigning ownership.
get_incident
Retrieve detailed information about a specific incident by its ID or slug. Returns full incident details including status, severity, assigned services, timeline timestamps, and linked integrations.
list_alerts
Search and list alerts from monitoring and observability tools. Filter by status, source, services, or environments. Use this to review incoming alerts, find unacknowledged alerts, or audit alert history.
create_alert
Ingest a new alert into Rootly from an external source. Alerts can be routed to escalation policies, services, or specific users. Supports deduplication keys to prevent duplicate alerts and labels for categorization.
update_action_item
Update an existing action item. Change status, reassign, update priority or due date.
list_schedules
List on-call schedules. Search by name or keyword to find specific schedules. Returns schedule configuration details including rotation settings and coverage information.
list_heartbeats
List heartbeat monitors configured in Rootly. Heartbeats monitor system health by expecting periodic pings. Returns heartbeat status (waiting, active, expired), interval configuration, and alert settings.
list_users
List users in the Rootly organization. Search by name or email. Use this to find user IDs for assigning incidents, action items, or notification targets.
list_workflows
List automated workflows configured in Rootly. Workflows are triggered by incident or alert events and perform automated tasks. Search by name to find specific workflow automations.
create_heartbeat
Create a new heartbeat monitor. Heartbeats expect periodic pings and trigger alerts if a ping is missed. Configure the expected interval and notification target for when the heartbeat expires.
list_services
List services from the Rootly service catalog. Search by name, slug, or keyword. Use this to find service IDs for linking to incidents or alerts.
list_escalation_policies
List escalation policies configured in Rootly. Escalation policies define how alerts escalate when responders don't acknowledge. Optionally include escalation levels and paths for full policy details.
manage_alert
Acknowledge or resolve an alert. Use this to update alert status as part of incident response.
list_action_items
List follow-up action items across all incidents. Filter by status to find open or completed items. Action items track post-incident follow-up tasks.
Manage the full incident lifecycle including creating, updating, triaging, mitigating, and resolving incidents. Ingest and route alerts from monitoring tools, configure alert sources, and attach alerts to incidents. Manage on-call schedules, rotations, override shifts, and escalation policies with multi-level routing. Create automated workflows triggered by incident or alert events. Track post-incident retrospectives and action items. Maintain a service catalog with custom properties, functionalities, and environments. Configure status pages to communicate outage information. Define playbooks with ordered tasks for standardized incident response. Manage teams, users, notification rules, and role assignments. Create dashboards with panels for incident metrics. Monitor system health via heartbeats, configure live call routing to on-call responders, and manage outbound webhooks for real-time event notifications.
Common questions about connecting Rootly to AI agents with Metorial.