Type to search.

Rootly connector

Serverless Preview

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Preview

    This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Planned

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Planned

    We plan to add this functionality in a future Elastic Stack update. Subject to changes.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The Rootly connector connects directly to the Rootly API. It lets a workflow or agent declare an incident, read and query incidents and alerts, drive an incident through its lifecycle (triage, mitigate, resolve, cancel), track follow-up work, and acknowledge or resolve alerts.

You can use this connector in Agent Builder and Workflows.

The Rootly connector uses Rootly's JSON:API-based REST API with Bearer token authentication.

You can create a Rootly connector in Stack Management > Connectors.

Authentication
Bearer token. Use a Rootly API key (Organization Settings > API Keys).
Action Description
createIncident Declare a new incident. Parameters: title (required), summary, severityId, serviceIds, groupIds, status, private, labels.
getIncident Get a single incident by ID. Parameters: incidentId (required).
listIncidents List incidents with filters. Parameters: status, severityId, serviceIds, teamIds, search, createdAtGte, createdAtLte, pageSize, pageNumber.
updateIncident Patch an incident's title, summary, severity, services, teams, or labels. Parameters: incidentId (required), title, summary, severityId, serviceIds, groupIds, labels.
triageIncident Move an incident into triage. Parameters: incidentId (required).
mitigateIncident Move an incident to mitigated. Parameters: incidentId (required), message.
resolveIncident Move an incident to resolved. Parameters: incidentId (required), message.
cancelIncident Cancel an incident as a false positive. Parameters: incidentId (required), message.
assignIncidentUser Assign a responder to an incident role. Parameters: incidentId, userId, incidentRoleId (all required).
addIncidentSubscribers Subscribe stakeholders to incident updates. Parameters: incidentId (required), userIds (required).
createActionItem File a follow-up task on an incident. Parameters: incidentId, summary (required), description, kind, priority, status, assignedToUserId, dueDate.
listActionItems List action items, scoped to an incident or org-wide. Parameters: incidentId, status, priority.
createTimelineEvent Post a note/milestone to an incident's timeline. Parameters: incidentId, event (required), visibility.
listSeverities List severity definitions and their resource IDs.
listServices List the service catalog. Parameters: name.
listTeams List teams. Parameters: name.
listAlerts List alerts with filters. Parameters: status, source, pageSize, pageNumber.
getAlert Get a single alert by ID. Parameters: alertId (required).
acknowledgeAlert Acknowledge a triggered alert. Parameters: alertId (required).
resolveAlert Resolve an alert, optionally cascading to linked incidents. Parameters: alertId (required), resolutionMessage, resolveRelatedIncidents.

Use the Action configuration settings to customize connector networking, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use xpack.actions.customHostSettings to set per-host configurations.

  1. Log in to your Rootly account.
  2. Go to Organization Settings > API Keys.
  3. Create a new API key (a Global API Key is recommended for org-wide access).
  4. Copy the key and store it securely.
  5. When configuring the connector, enter the key as the Bearer token.