The PagerDuty Operations Console offers live visibility into incidents where users can create customized views to triage and take immediate action on issues. This feature provides central IT teams and technical stakeholders with context on their technical environment at a glance to be able to more effectively and efficiently triage incidents, minimizing their MTTA and MTTR.

📘

Availability

This feature is available with our PagerDuty AIOps add-on. If you would like to sign up for a trial of PagerDuty AIOps features, please read PagerDuty AIOps Trials.

View the Operations Console

In the web app, navigate to AIOps Operations Console.

Configure the Operations Console

The console offers great flexibility for users to customize the live incidents table, such as adding and removing columns to the incidents table, filtering, sorting, etc.

Column Selector

You can customize which fields are visible in the incidents table by adding, removing or reordering the fields. Click to open the column selector panel and select/deselect your desired columns. You can reorder columns by click / next to the corresponding column.

You can also resize a column's with by clicking and dragging the edge to your desired size.

Users can also sort by up to three columns simultaneously. (currently in development)

📘

Tip

Since each users may have a different view based on their permissions and configurations, changes in one user’s account will not affect other users’ view. You can share your view with team members via the Share button.

Filters and Search

At the highest level, you can show All incidents, or click My teams to display just incidents belonging to your Teams. You can also quickly filter by incident status: Open, Acknowledged, or Triggered.

For more granular filters:

1. Click to open the the filter panel.
2. Click Add and select from the following:
   1. Date
   2. Status
   3. Urgency
   4. Priority
   5. Teams
   6. Service
   7. Assignee: escalation policy or user
   8. Responder: escalation policy or user
   9. Custom Details (Available by request)
3. Depending on the field(s) you select, enter the appropriate criteria and click Apply Filters.

Additionally, users can perform keyword search to filter on incident Title, Incident number and Latest note.

Actions

To take action on incidents within Operations Console, select the checkbox to the left of the incident(s) and click your desired action:

• Resolve
• Acknowledge
• Add Responder
• Reassign
• Run
• Merge
• Snooze
• Update Priority
• Add Note

Bulk Actions

When you want to perform actions on multiple incidents at once, you can click the selection box at the top of the incident table. This will select the first 50 incidents on the current page, and list the bulk action options at the bottom of your screen. Select from the following actions:

• Acknowledge
• Resolve
• Add Responder
• Reassign
• Merge
• Snooze
• Update Priority
• Add Note

Custom Details

📘

Available By Request

This feature is available by request only. Please reach out to your account team to request this feature.

You can define and add specific custom details fields from your alert payload to the incidents table.

1. Click to open the column selector panel.
2. Scroll to the bottom of the list and click Add Custom Detail.
3. In the modal, enter a Table Header and the Custom Details Path (e.g., the name of the field as it appears in the alert payload, such as source or application).
   1. Optionally click + Add Column to add multiple custom detail columns at once.
4. Click Add Columns.

FAQ

How can I troubleshoot connection issues if the Operations Console does not load?

We use server-sent events (SSEs) to provide real-time updates. Your security or IT team may use a proxy/software to block these requests. If you encounter issues loading the Operations Console, please verify with your IT department whether SSEs are handled by proxies or third party software (e.g., antivirus programs or plugins). If so, you can request that they evaluate and enable our main SSE endpoint: /api/v1/opsconsole/incident_module/search.

You can analyze the HAR file for the affected session to check if the request to /api/v1/opsconsole/incident_module/search is present and successful. Missing, blocked, or canceled requests may indicate that something in your network is preventing the SSE connection.

Can I add event custom fields from the alert payload to the Operations Console?

How many event custom fields can I display in the Operations Console?