Manage Grafana OnCall OSS on Grafana Labs

Manage users and teams for Grafana OnCall OSS

Fri, 03 Apr 2026 19:43:06 +0000

Manage users and teams for Grafana OnCall OSS

Grafana OnCall OSS relies on the teams and user permissions configured at the organization level of your self-hosted Grafana instance. Organization administrators can invite users, configure teams, and manage user permissions in your Grafana installation.

User roles and permissions

Note: User roles and teams cannot be managed directly from Grafana OnCall OSS.

User roles and permissions are assigned and managed at the Grafana organization level. There are two ways to manage user roles and permissions for Grafana OnCall OSS.

Basic role authorization

By default, authorization within Grafana OnCall relies on the basic user roles configured at the organization level. All users are assigned a basic role by the organization administrator. There are three available roles: Viewer, Editor, and Admin.

Role-based access control (RBAC)

RBAC for Grafana plugins allows for fine-grained access control so you can define custom roles and actions for users in Grafana OnCall. Use RBAC to grant specific permissions within the Grafana OnCall plugin without changing the user’s basic role at the organization level. You can fine-tune basic roles to add or remove certain Grafana OnCall RBAC roles.

For example, a user with the basic Viewer role at the organization level needs to edit on-call schedules. You can assign the Grafana OnCall RBAC role of Schedules Editor to allow the user to view everything in Grafana OnCall, as well as allow them to edit on-call schedules.

To learn more about RBAC for Grafana OnCall, refer to the following documentation:

Available Grafana OnCall RBAC roles + granted actions

Note: granting any of the following roles will also grant the user the plugins.app:access action with a scope of plugins:id:grafana-oncall-app (ie. granting the user the ability to access the plugin). Additionally, all of the following RBAC roles do not currently support scopes. To further control which Grafana OnCall objects specific groups of users can view, refer to Manage Teams in Grafana OnCall.

Role	Description	Granted Actions	Basic Roles Granted To
Admin	Read/write access to everything in OnCall	`grafana-oncall-app.alert-groups:read` `grafana-oncall-app.alert-groups:write` `grafana-oncall-app.alert-groups:direct-paging` `grafana-oncall-app.integrations:read` `grafana-oncall-app.integrations:write` `grafana-oncall-app.integrations:test` `grafana-oncall-app.escalation-chains:read` `grafana-oncall-app.escalation-chains:write` `grafana-oncall-app.schedules:read` `grafana-oncall-app.schedules:write` `grafana-oncall-app.schedules:export` `grafana-oncall-app.chatops:read` `grafana-oncall-app.chatops:write` `grafana-oncall-app.chatops:update-settings` `grafana-oncall-app.outgoing-webhooks:read` `grafana-oncall-app.outgoing-webhooks:write` `grafana-oncall-app.maintenance:read` `grafana-oncall-app.maintenance:write` `grafana-oncall-app.api-keys:read` `grafana-oncall-app.api-keys:write` `grafana-oncall-app.notifications:read` `grafana-oncall-app.notification-settings:read` `grafana-oncall-app.notification-settings:write` `grafana-oncall-app.user-settings:read` `grafana-oncall-app.user-settings:write` `grafana-oncall-app.user-settings:admin` `grafana-oncall-app.other-settings:read` `grafana-oncall-app.other-settings:write`	Grafana Admin, Admin
Editor	Similar to the Admin role, minus the abilities to: create Integrations, create Escalation Chains, create Outgoing Webhooks, update ChatOps settings, update other user’s settings, and update general OnCall setings.	`grafana-oncall-app.alert-groups:read` `grafana-oncall-app.alert-groups:write` `grafana-oncall-app.alert-groups:direct-paging` `grafana-oncall-app.integrations:read` `grafana-oncall-app.integrations:test` `grafana-oncall-app.escalation-chains:read` `grafana-oncall-app.schedules:read` `grafana-oncall-app.schedules:write` `grafana-oncall-app.schedules:export` `grafana-oncall-app.chatops:read` `grafana-oncall-app.chatops:write` `grafana-oncall-app.outgoing-webhooks:read` `grafana-oncall-app.maintenance:read` `grafana-oncall-app.maintenance:write` `grafana-oncall-app.notifications:read` `grafana-oncall-app.notification-settings:read` `grafana-oncall-app.notification-settings:write` `grafana-oncall-app.user-settings:read` `grafana-oncall-app.user-settings:write` `grafana-oncall-app.other-settings:read`	Editor
Reader	Read-only access to everything in OnCall	`grafana-oncall-app.alert-groups:read` `grafana-oncall-app.integrations:read` `grafana-oncall-app.escalation-chains:read` `grafana-oncall-app.schedules:read` `grafana-oncall-app.chatops:read` `grafana-oncall-app.outgoing-webhooks:read` `grafana-oncall-app.maintenance:read` `grafana-oncall-app.notification-settings:read` `grafana-oncall-app.user-settings:read` `grafana-oncall-app.other-settings:read`	Viewer
Notifications Receiver	Grants the ability to receive OnCall alert notifications. By virtue, also grants the user the ability to edit their own OnCall settings.	`grafana-oncall-app.notifications:read` `grafana-oncall-app.user-settings:write`	N/A
OnCaller	Grants read access to everything in OnCall. In addition, grants edit access to Alert Groups, Schedules and own settings	`grafana-oncall-app.alert-groups:read` `grafana-oncall-app.alert-groups:write` `grafana-oncall-app.alert-groups:direct-paging` `grafana-oncall-app.integrations:read` `grafana-oncall-app.escalation-chains:read` `grafana-oncall-app.schedules:read` `grafana-oncall-app.schedules:write` `grafana-oncall-app.chatops:read` `grafana-oncall-app.outgoing-webhooks:read` `grafana-oncall-app.maintenance:read` `grafana-oncall-app.notifications:read` `grafana-oncall-app.notification-settings:read` `grafana-oncall-app.user-settings:read` `grafana-oncall-app.user-settings:write` `grafana-oncall-app.other-settings:read`	N/A
Alert Groups Reader	Read-only access to OnCall Alert Groups	`grafana-oncall-app.alert-groups:read`	N/A
Alert Groups Editor	Read access to OnCall Alert Groups + ability to act on Alert Groups (ie. ack, resolve, etc)	`grafana-oncall-app.alert-groups:read` `grafana-oncall-app.alert-groups:write`	N/A
Alert Groups Direct Paging	Grants the ability to be able to manually create new Alert Groups (aka Direct Paging)	`grafana-oncall-app.alert-groups:direct-paging`	N/A
Integrations Reader	Read-only access to OnCall Integrations	`grafana-oncall-app.integrations:read`	N/A
Integrations Editor	Read/write access to OnCall Integrations	`grafana-oncall-app.integrations:read` `grafana-oncall-app.integrations:write` `grafana-oncall-app.integrations:test`	N/A
Escalation Chains Reader	Read-only access to OnCall Escalation Chains	`grafana-oncall-app.escalation-chains:read`	N/A
Escalation Chains Editor	Read/write access to OnCall Escalation Chains	`grafana-oncall-app.escalation-chains:read` `grafana-oncall-app.escalation-chains:write`	N/A
Schedules Reader	Read-only access to OnCall Schedules	`grafana-oncall-app.schedules:read`	N/A
Schedules Editor	Read/write access to OnCall Schedules	`grafana-oncall-app.schedules:read` `grafana-oncall-app.schedules:write` `grafana-oncall-app.schedules:export`	N/A
ChatOps Reader	Read-only access to OnCall ChatOps	`grafana-oncall-app.chatops:read`	N/A
ChatOps Editor	Read/write access to OnCall ChatOps	`grafana-oncall-app.chatops:read` `grafana-oncall-app.chatops:write` `grafana-oncall-app.chatops:update-settings`	N/A
Outgoing Webhooks Reader	Read-only access to OnCall Outgoing Webhooks	`grafana-oncall-app.outgoing-webhooks:read`	N/A
Outgoing Webhooks Editor	Read/write access to OnCall Outgoing Webhooks	`grafana-oncall-app.outgoing-webhooks:read` `grafana-oncall-app.outgoing-webhooks:write`	N/A
Maintenance Reader	Read-only access to OnCall Maintenance	`grafana-oncall-app.maintenance:read`	N/A
Maintenance Editor	Read/write access to OnCall Maintenance	`grafana-oncall-app.maintenance:read` `grafana-oncall-app.maintenance:write`	N/A
API Keys Reader	Read-only access to OnCall API Keys	`grafana-oncall-app.api-keys:read`	N/A
API Keys Editor	Read/write access to OnCall API Keys. Also grants access to be able to consume the API.	`grafana-oncall-app.api-keys:read` `grafana-oncall-app.api-keys:write`	N/A
Notification Settings Reader	Read-only access to OnCall Notification Settings	`grafana-oncall-app.notification-settings:read`	N/A
Notification Settings Editor	Read/write access to OnCall Notification Settings	`grafana-oncall-app.notification-settings:read` `grafana-oncall-app.notification-settings:write`	N/A
User Settings Reader	Read-only access to own OnCall User Settings	`grafana-oncall-app.user-settings:read`	N/A
User Settings Editor	Read/write access to own OnCall User Settings + ability to view basic information about other OnCall users	`grafana-oncall-app.user-settings:read` `grafana-oncall-app.user-settings:write`	N/A
User Settings Admin	Read/write access to your own, plus other’s OnCall User Settings	`grafana-oncall-app.user-settings:read` `grafana-oncall-app.user-settings:write` `grafana-oncall-app.user-settings:admin`	N/A
Settings Reader	Read-only access to OnCall Settings	`grafana-oncall-app.other-settings:read`	N/A
Settings Editor	Read/write access to OnCall Settings	`grafana-oncall-app.other-settings:read` `grafana-oncall-app.other-settings:write`	N/A

Manage Teams in Grafana OnCall

Teams in Grafana OnCall enable the configuration of visibility and filtering of resources, such as alert groups, integrations, escalation chains, and schedules. OnCall teams are automatically synced with Grafana teams created at the organization level of your Grafana instance. To modify global settings like team name or team members, navigate to Configuration > Teams. For OnCall-specific team settings, go to Alerts & IRM > OnCall > Settings > Teams and Access Settings.

This section displays a list of teams, allowing you to configure team visibility and access to team resources for all Grafana users, or only admins and team members. You can also set a default team, which is a user-specific setting; the default team will be pre-selected each time a user creates a new resource. The team list includes a No team tag, signifying that the resource has no team and is accessible to everyone.

Admins can view the list of all teams, while editors and viewers can only see teams (and their resources) they are members of or if the team setting “who can see the team name and access the team resources” is set to “all users of Grafana”.

⚠️ In the main Grafana teams section, users can set team-specific user permissions, such as Admin, Editor, or Viewer, but only for resources within that team. Currently, Grafana OnCall ignores this setting and uses global roles instead.

Teams help filter resources on their respective pages, improving organization. You can assign a resource to a team when creating it. Alert groups created via the Integration API inherit the team from the integration.

Resources from different teams can be connected with one another. For instance, you can create an integration in one team, set up multiple routes for the integration, and utilize escalation chains from other teams. Users, schedules, and outgoing webhooks from other teams can also be included in the escalation chain. If a user only has access to the first team and not others, they will be unable to view the resource, which will display as 🔒 Private resource. This feature enables the distribution of escalations across various teams.

Notifications for OnCall OSS

Fri, 03 Apr 2026 19:43:06 +0000

Notifications for OnCall OSS

Grafana OnCall OSS directly supports the export of alert notifications to some popular messaging applications like Slack and Telegram. You can use Webhook as a personal notification channel and Outgoing webhooks for applications that aren’t directly supported.

Warning
As of March 24, 2026, Cloud Connection features for phone calls, SMS, and push notifications will no longer be supported in Grafana OnCall OSS. Refer to the documentation for phone and SMS and push notifications for alternative setup options.

To learn more about this update, refer to the Maintenance mode notice for Grafana OnCall (OSS)

Configure user notification rules

Notification rules are a configurable set of notification steps that determine how you’re notified of alert in OnCall OSS. Users with the Admin or Editor role are able to receive notifications. Users can verify phone numbers and email addresses in the Users tab of Grafana OnCall OSS.

Default notification rules dictate how a user is notified for most escalation thresholds.
Important notification rules are labeled in escalation chains. If an escalation event is marked as an important notification, it will bypass Default notification rules settings and notify the user by the method specified.

NOTE: You cannot add users or manage permissions in Grafana OnCall OSS. User settings are found on the organizational level of your Grafana instance in Configuration > Users.

To configure a user’s notification rules:

Navigate to the Users tab of Grafana OnCall OSS and search for or select a user.
Click Edit to the right of a user to open the User Info window.
Verify that there is a valid and verified phone number, along with ChatOps accounts in order to receive notifications via those methods.
Click Add notification step and use the dropdowns to specify the notification method and frequency. Notification steps will be followed in the order they are listed.

On-call schedules for OnCall OSS

Fri, 03 Apr 2026 19:43:06 +0000

On-call schedules for OnCall OSS

Grafana OnCall OSS provides flexible scheduling options to manage on-call rotations for your team. This documentation covers the different ways you can create and manage on-call schedules during the product’s maintenance period.

Before you begin

Users with Admin or Editor roles can create, edit and delete schedules.
Users with Viewer role cannot receive alert notifications, therefore, cannot be on-call.

For more information about permissions, refer to Manage users and teams for Grafana OnCall

Web-based schedule

Configure and manage on-call schedules directly in the Grafana OnCall plugin. Easily configure and preview rotations, see teammates’ time zones, and add overrides.

For more information, refer to Web-based on-call schedules.

iCal import

Use any calendar service that uses the iCal format to manage and customize on-call schedules - Import rotations and shifts from your calendar app to Grafana OnCall for widely accessible scheduling. iCal imports appear in Grafana OnCall as read-only schedules but can be leveraged similarly to a web-based schedule.

For more information, refer top Import on-call schedules.

Terraform

Use the Grafana OnCall Terraform provider to manage schedules within your “as-code” workflow. Rotations configured via Terraform are automatically added to your schedules in Grafana OnCall. Similar to the iCal import, these schedules read-only and cannot be edited from the UI.

To learn more, read our Get started with Grafana OnCall and Terraform blog post.

Shift swap requests

Sometimes you may need someone to cover your scheduled on-call shifts (e.g. you are going on vacation for a couple of weeks). You can then create a shift swap request, which will let your teammates know about this as well as allowing them to volunteer and take your affected shifts for that period.

For more information, refer to Shift swap requests.

Insight logs and metrics

Fri, 03 Apr 2026 19:43:06 +0000

Insight Logs and Metrics

Metrics

Grafana OnCall Metrics represents certain parameters, such as:

A total count of alert groups for each integration in every state (firing, acknowledged, resolved, silenced). It is a gauge, and its name has the suffix alert_groups_total
Response time on alert groups for each integration (mean time between the start and first action of all alert groups for the last 7 days in selected period). It is a histogram, and its name has the suffix alert_groups_response_time with the histogram suffixes such as _bucket, _sum and _count
Resolution time on alert groups for each integration (mean time between the start and resolution of all resolved alert groups for the last 7 days in selected period). It is a histogram, and its name has the suffix alert_groups_resolution_time with the histogram suffixes such as _bucket, _sum and _count
A total count of alert groups users were notified of for each user and service. It is a counter, and its name has the suffix user_was_notified_of_alert_groups_total. This metric includes the service_name label to track notifications per service.

You can find more information about metrics types in the Prometheus documentation.

To retrieve Prometheus metrics use PromQL. If you are not familiar with PromQL, check this documentation.

For Grafana Cloud customers

OnCall application metrics are collected in preinstalled grafanacloud_usage datasource and are available for every cloud instance.

Metrics have prefix grafanacloud_oncall_instance, e.g. grafanacloud_oncall_instance_alert_groups_total, grafanacloud_oncall_instance_alert_groups_response_time_seconds_bucket, grafanacloud_oncall_instance_alert_groups_resolution_time_seconds_bucket and grafanacloud_oncall_instance_user_was_notified_of_alert_groups_total.

For open source customers

To collect OnCall application metrics you need to set up Prometheus and add it to your Grafana instance as a datasource. You can find more information about Prometheus setup in the OSS documentation

Metrics will have the prefix oncall, e.g. oncall_alert_groups_total, oncall_alert_groups_response_time_seconds_bucket, oncall_alert_groups_resolution_time_seconds_bucket and oncall_user_was_notified_of_alert_groups_total. The open source version supports the same labels as the cloud version, including the service_name label for user notification metrics.

Your metrics may also have additional labels, such as pod, instance, container, depending on your Prometheus setup.

Metrics: Alert groups total

This metric has the following labels:

Label Name	Description
`id`	ID of Grafana instance (stack)
`slug`	Slug of Grafana instance (stack)
`org_id`	ID of Grafana organization
`team`	Team name
`integration`	OnCall Integration name
`service_name`	Value of Alert group `service_name` label
`state`	Alert groups state. May be `firing`, `acknowledged`, `resolved` and `silenced`

Query example:

Get the number of alert groups in “firing” state in integration “Grafana Alerting” in Grafana stack “test_stack”:

grafanacloud_oncall_instance_alert_groups_total{slug="test_stack", integration="Grafana Alerting", state="firing"}

Metrics: Alert groups response time

This metric has the following labels:

Label Name	Description
`id`	ID of Grafana instance (stack)
`slug`	Slug of Grafana instance (stack)
`org_id`	ID of Grafana organization
`team`	Team name
`integration`	OnCall Integration name
`service_name`	Value of Alert group `service_name` label
`le`	Histogram bucket value in seconds. May be `60`, `300`, `600`, `3600` and `+Inf`

Query example:

Get the number of alert groups with response time more than 10 minutes (600 seconds) in integration “Grafana Alerting” in Grafana stack “test_stack”:

grafanacloud_oncall_instance_alert_groups_response_time_seconds_bucket{slug="test_stack", integration="Grafana Alerting", le="600"}

Metrics: Alert groups resolution time

This metric has the following labels:

Label Name	Description
`id`	ID of Grafana instance (stack)
`slug`	Slug of Grafana instance (stack)
`org_id`	ID of Grafana organization
`team`	Team name
`integration`	OnCall Integration name
`service_name`	Value of Alert group `service_name` label
`le`	Histogram bucket value in seconds. May be `60`, `300`, `600`, `3600` and `+Inf`

Query example:

Get the number of alert groups with resolution time more than 10 minutes (600 seconds) in integration “Grafana Alerting” in Grafana stack “test_stack”:

grafanacloud_oncall_instance_alert_groups_resolution_time_seconds_bucket{slug="test_stack", integration="Grafana Alerting", le="600"}

Metrics: Alert groups user was notified of

This metric has the following labels:

Label Name	Description
`id`	ID of Grafana instance (stack)
`slug`	Slug of Grafana instance (stack)
`org_id`	ID of Grafana organization
`username`	User username
`service_name`	Value of Alert group `service_name` label

Query examples:

Get the number of alert groups user with username “alex” was notified of in Grafana stack “test_stack”:

grafanacloud_oncall_instance_user_was_notified_of_alert_groups_total{slug="test_stack", username="alex"}

Get the number of alert groups user with username “alice” was notified of for the “payments” service:

grafanacloud_oncall_instance_user_was_notified_of_alert_groups_total{username="alice", service_name="payments"}

Get the rate of notifications for all users for the “auth” service in the last 5 minutes:

rate(grafanacloud_oncall_instance_user_was_notified_of_alert_groups_total{service_name="auth"}[5m])

Get the total notifications per user across all services using aggregation:

sum by (username) (grafanacloud_oncall_instance_user_was_notified_of_alert_groups_total)

Note: The service_name label is extracted from alert group labels. Alert groups without a service_name label will have the value “No service” for this label.

Dashboard

You can find the “OnCall Insights” dashboard in the list of your dashboards in the folder General, it has the tag oncall. In the datasource dropdown select your Prometheus datasource (for Cloud customers it’s grafanacloud_usage). You can filter data by your Grafana instances, teams and integrations.

To re-import OnCall metrics dashboard go to Administration -> Plugins page, find OnCall in the plugins list, open Dashboards tab at the OnCall plugin settings page and click “Re-import” near “OnCall Metrics”. After that you can find the “OnCall Metrics” dashboard in your dashboards list.

Be aware: if you have made changes to the dashboard, they will be lost after re-importing or after the plugin update. To save your changes go to the “OnCall Metrics” dashboard settings, click “Save as” and save a copy of the dashboard.

You can also view Insights from Grafana OnCall.

To view Insights, complete the following steps.

Open Grafana OnCall.
Click the Insights sub-section in the navigation menu.

Logs

Note: Grafana OnCall insight logs are available in Grafana Cloud only. We’re in the process of rolling out Insight Logs to all customers, if you don’t see insight logs in your Grafana Cloud stack, please reach out to support.

Grafana OnCall Insights Logs represents certain activities, such as when:

A user creates, updates, or deletes a resource.
A Maintenance mode is started or finished for an integration.
A user configures a ChatOps integration.

This configuration is done for you in Grafana Cloud with Usage Insights Loki data source. You can use this query to retrieve all logs related to your OnCall instance.

{instance_type="oncall"} | logfmt | __error__=``

Resource logs

Logs are created each time a user modifies any resource in Grafana OnCall.

These logs will have action_type=resource field and can be retrieved with following query:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `resource`

Format

Logs contain the following fields, where the fields followed by * are always available, and the others depend on the logged event:

Field Name	Description
`action_name`*	Type of the resource action, which can be `created`, `updated` or `deleted`.
`action_type`*	Insight Log type. For resource insight logs it will be `resource`.
`author`*	Username of user who performed action.
`author_id`*	ID of user who performed action.
`prev_state`	JSON representation of resource before update.
`new_state`	JSON representation of resource after update.
`resource_id`*	ID of target resource.
`resource_name`*	Name of target resource.
`resource_type`*	Type of target resource (See available types below).
`team`*	Name of team to which resource belongs.
`team_id`	ID of team to which resource belongs.
`integration`	Name of integration to which resource belongs.
`integration_id`	ID of integration to which resource belongs.
`escalation_chain`	Name of team to which resource belongs.
`escalation_chain_id`	ID of team to which resource belongs.
`schedule`	Name of schedule to which resource belongs.
`schedule_id`	ID of schedule to which resource belongs .

resource types are: integration_heartbeat, escalation_chain, integration, outgoing_webhook, escalation_policy, public_api_token, schedule_export_token,user_schedule_export_token, oncall_shift, web_schedule, ical_schedule, calendar_schedule, shift_swap_request, organization, user, webhook.

Maintenance logs

Logs are created every time when a maintenance mode is started or finished for an integration.

These logs will have action_type=maintenace field and can be retrieved with following query:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `maintenance`

Format

Logs of maintenance insights contain the following fields, where the fields followed by * are always available, and the others depend on the logged event:

Field Name	Description
`action_name`*	Name of the maintenance action, which can be `started` or `finised`.
`action_type`*	Insight Log type. For Maintenance Insight logs it will be `maintenance`.
`author`	Username of user who performed action.
`author_id`	Grafana OnCall ID of user who performed action.
`maintenance_mode`*	Type of the maintenance, which can be `maintenance` or `debug`
`resource_id`*	ID of target integration.
`resource_name`*	Name of target integration.
`team`*	Name of team to which integration belongs.
`team_id`	ID of team to which integration belongs.

ChatOps logs

Logs are created when user modifies ChatOps settings.

These log lines will have action_type=chat_ops field and can be retrieved with following query:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `chat_ops`

Format

Logs of chatops insight logs contain the following fields, where the fields followed by * are always available, and the others depend on the logged event:

Field Name	Description
`action_name`*	Name of the chatops action (See available names below).
`action_type`*	Insight Log type. For Chatops Insight logs it always will be `chat_ops`.
`author`*	Username of user who performed action
`author_id`*	Grafana OnCall ID of user who performed action
`сhat_ops_type`*	Type of chatops integration. Can be `telegram`, `slack`, `msteams`, `mobile_app`
`linked_user`	Username of user linked to chatops integration
`linked_user_id`	Grafana OnCall ID of user linked to chatops integration
`channel_name`	Name of the channel linked to chatops integration
`prev_channel`	Name of team to which resource belongs
`new_channel`	Grafana OnCall ID of team to which resource belongs

chatops action names: workspace_connected, workspace_disconnected, channel_connected, channel_disconnected, user_linked, used_unlinked, default_channel_changed.

Examples

Here is some examples of practical queries to Grafana OnCall insight logs. LogQL is used to retrieve them. If you aren’t familiar with LogQL, refer to LogQL: Log query language.

Resource IDs are used a lot in insight logs. You can find them in web ui (example for integration):

Open Grafana OnCall.
Navigate to resource.
The URL looks like https://<YOUR_STACK_SLUG>/a/grafana-oncall-app/integrations/C5VXMIFKKP67K.
Integration ID is C5VXMIFKKP67K.

Alternatively you can find the resource ID using the [Grafana OnCall API] or browser dev tools.

Actions performed by user:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `resource` and author="<username>"

Actions performed with all schedules:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `resource` and (resource_type=`web_schedule` or resource_type=`calendar_schedule` or resource_type=`ical_schedule`)

Changes of escalation policies for escalation chain:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `resource` and resource_type=`escalation_policy` and escalation_chain_id=`<ESCALATION_CHAIN_ID>`

Maintenance events for integration:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `maintenance` and resource_id=`CSA67IQW2NMVL`

Actions performed with slack chatops integration:

{instance_type="oncall"} | logfmt | __error__=`` | action_type = `chat_ops` and chat_ops_type=`slack`