# Operations Console

Gain live insight into incidents

The PagerDuty Operations Console offers live visibility into incidents, and you can create customized views to triage and take immediate action on issues. This feature provides central IT teams and technical stakeholders with at-a-glance context on their technical environment in order to more efficiently triage incidents, and minimize MTTA and MTTR. 

![An image of the PagerDuty web app showing the Operations Console with many triggered incidents](/images/kb/734f476f383d139e0fbbafe3ac3d42db73fb87ed271f241e11c9522baa8d3b12-operations_console.webp)

> **AIOps / Signal Intelligence Feature:** This feature is included with the [PagerDuty AIOps](/ai-automation/aiops/overview) add-on, or included as Signal Intelligence in PD Reliability Platform plans. To sign up for a trial of PagerDuty AIOps features, read [PagerDuty AIOps Trials](/ai-automation/aiops/overview#pagerduty-aiops-trials).

## View the Operations Console

In the web app, navigate to **AI**  →  **Operations Console**.

> **Japanese Language Support:** The Operations Console supports Japanese as a display and interface language. Depending on your permission level, you can update this at the account or profile level:
>
> - **For Account Admins (Global Default):**  
>   Navigate to **Account Settings** and locate the **Default Voice and Interface Language** dropdown to set the default for the entire organization.
> - **For Individual Users:**  
>   Navigate to **My Profile**, click the pencil icon next to **Voice Language Setting**, and select Japanese from the dropdown menu.

> **AIOps Service Incidents Only:** Only incidents on [AIOps services](/ai-automation/aiops/overview#aiops-service-configuration) will display in the Operations Console. If you would like to view incidents created on non-AIOps services, you must navigate to the **Incidents** page. Please see our [AIOps Service Configuration](/ai-automation/aiops/overview#aiops-service-configuration) article for more information on managing AIOps on services.

> **AIOps Service Configuration:** Your service configuration must have AIOps enabled to use this feature. AIOps Service Configuration is in Limited General Availability — see [Configurable Service Settings](/incident-management/services/configurable-service-settings#manage-aiops) for more information and enablement steps.

## Configure the Operations Console

The console offers users great flexibility to customize the live incidents table. This includes the ability to add or remove standard incident, alert, and custom-defined columns, as well as filter, sort, and apply other configurations.

### 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. Reorder columns by dragging and dropping them to their preferred location. 

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

Users can also sort by up to three columns simultaneously.

![A screenshot of the PagerDuty web app detailing the Operations Console's column selector](/images/kb/b10b041d229c93be1f3af0819ebb57e435994d32b6b27a8ccfdbba18ee5d2bea-column_selector.webp)
*Column selector*

You can also display [Custom Fields on Incidents](/incident-management/incidents/custom-fields-on-incidents) in the live incidents table by clicking **Custom Columns** at the bottom of the Column Selector and adding them to the table. You can add up to ten Custom Fields in the Operations Console's incident table. If you wish to display a new field but are unable to, please deselect an existing custom field first. You can sort on up to three columns in the incidents table.

![A screenshot of the PagerDuty web app detailing how to add Custom Fields as columns in the Operations Console](/images/kb/2f150a7cad1893b87978d1580b219bb129d4b0ca95dc98d306176aba0bdf4e32-custom_columns.webp)
*Custom columns*

> **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.

You can also export the all loaded incidents with your customized columns as a CSV file using the  menu.

![A screenshot of the PagerDuty web app showing how to export visible rows as a CSV file](/images/kb/0584b1b03d3148d43ae2d11e23cbd1a16990022fed64d0d5cfe94be5761e0e42-export_as_csv.webp)
*Export visible rows as CSV*

### Side Panel

You can view incident details by clicking on an incident's **Title** or alert count in the **Alerts** column. The side panel provides contextual information pertaining to the incident, including snoozed time (if applicable), alert grouping details (if applicable), alerts fields, alert custom details and so on, so you can view all things at a glance in one place. 

You can also change the width by dragging the side panel horizontally to view more or fewer alert columns. PagerDuty will remember your settings for later visits.

![A screenshot of the PagerDuty web app showing the Operations Console's side panel](/images/kb/af6f4303cefc300cba2ed1325bd18c39e7d68c518aeffcb05854bbf4feb6d995-side_panel.webp)
*Operations Console side panel*

### Filters and Search

At the highest level, you can show:

- **All** incidents 
- **My teams** to display just incidents belonging to your [Teams](/account-admin/teams). 

You can also quickly filter by incident status: 

- **Assigned to me**
- **Open**
- **Acknowledged**
- **Triggered**

> **AIOps Service Incidents Only:** Only incidents on [AIOps services](/ai-automation/aiops/overview#aiops-service-configuration) will display in the Operations Console. If you would like to view incidents created on non-AIOps services, you must navigate to the **Incidents** page.

For more granular filters:

1. Click  to open the filter panel.
2. Click **Add** and select from the following:
   1. **Alert Services**
   2. **Assignee**
   3. **Auto Resolved**
   4. **Duration**
   5. **Date**
   6. **Escalation Policy**
   7. **External Reference**
   8. **Incident Number**
   9. **Latest Note**
   10. **Main Service**
   11. **Priority**
   12. **Responder**
   13. **Status**
   14. **Teams**
   15. **Title**
   16. **Urgency**
   17. **User**
   18. [**Custom Fields on Incidents**](/incident-management/incidents/custom-fields-on-incidents)
   19. [**Custom Details**](#custom-details) on Alerts (Available by request)
3. Depending on the field(s) you select, enter the appropriate criteria and click **Apply Filters**.

![An image detailing filtering capabilities in the Operations Console](/images/kb/b49be95cf40eedd8b7e899d7ac9a22fa03fc3c76de4fde9c3de316c50e20ab2e-filters_and_search.webp)
*Filters and search*

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

> **Tip:** You can perform keyword search with conditions such as **contains**, **starts with**, **equals**, **does not contain**, and combine `AND`/`OR` operators to filter across a number of fields such as Incident Title, Incident Number, Last Notes. You can define up to five keywords with `AND`/`OR` operators.
>
> For optimal performance, enter at least three characters for searches with the **contains** filter.
>
> ![A screenshot of the PagerDuty web app showing how to use keyword search in the filters](/images/kb/945d8e1bfe44f8f14c5a2fd1bc36a78e03daf494ce8a46ef15f1a09004f88acc-keyword_search.webp)
> *Keyword search*

### 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**

![A screenshot of the PagerDuty web app detailing the various actions users can take on incidents in the Operations Console](/images/kb/20121dca06fa42e0af1c932d5aeb45ac581a012eb69ae1be03875b6dfe60e416-incident_actions.webp)
*Incident actions*

#### 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**

### Incident Feed Update Frequency

To optimize performance or during incident storms, you can toggle between **Live** and **Paused** update modes. By default, the console is set to **Live** updates, which continuously adds new incidents, and corresponding updates, to the feed.

![A screenshot of the PagerDuty web app showing that the Operations Console is set to Live updates](/images/kb/21b37b7593cebf8daabaa9c17476d08a6b97b78aee19f79c697ad5e0cee3db79-live_updates.webp)

You can optionally pause live updates by clicking the toggle. While **Paused**, new incidents will not be added to the Operations Console, but updates to existing incidents will still be displayed. Users can manually update the incident table by refreshing the page.

![A screenshot of the PagerDuty web app showing the Operations Console is set to Paused updates](/images/kb/79dde93b1dd25fc4cc34a89a19653bd911ce004da533771c512182c2590d12c9-paused_updates.webp)

### 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**.

![A screenshot of the PagerDuty web app showing custom columns in the Operations Console](/images/kb/24feb2be42db73cf1889833369a8c4d84543d6dcefd6e4cce6e5194f3b1671a4-custom_columns.webp)
*Custom columns*

## Service Health Visualization

Service Health Visualization aggregates active incidents by Service into an interactive graph in the Operations Console to quickly identify hotspots and emerging issues.

### Access Service Health Visualization

1. In the PagerDuty web app, click **AIOps**  →  **Operations Console**.
2. Click the **View by** dropdown.
3. Select **Service Health**.

![View by Service Health](/images/kb/920ae3476da97f959fb94bd139fdf8c9f8f1aae7cd97067c2b2bf3f18569a47c-a8e280302eb58fc0fb4b7f7f797d2e2cf247e9416199cdd60ec2bf92d2189701-view_by_service_health.webp)

### Use the Incidents-by-Service Graph

- **Multi-select filters**: Combine filters to refine results during active incidents.
- **Click to drill in**: Select a service and time to view incident count and links to incident details. If more than 20 incidents exist, a link to the full Open Incidents list is provided.
- Only services with active incidents will be accessible in the graph.
- Services are automatically sorted by the number of active incidents.

#### Apply Filters

1. Click  to open the filter panel.
2. Click **Add** and select from the following:
   - Created
   - Team
   - Service
   - Priority
3. Depending on the field(s) you select, enter the appropriate criteria and click **Apply Filters**.

#### Triage Example

1. **Spot the spike**: Identify a sudden increase in incidents for a particular service on the graph.
2. **Focus on service(s)**: Apply a service filter to isolate that service and any related dependencies.
3. **Drill in**: Click the service to view links to active incidents.
4. **Coordinate**: Use your incident workflows to mobilize teams and update stakeholders.

### Troubleshooting the Service Health Visualization

**The graph looks empty**

- Verify the time window—short ranges may show fewer incidents in quiet periods.
- Clear any Service filters.
- Confirm that incidents are actively open in the selected window.

**Incident count seems off**

- The graph updates automatically, but there may be a brief delay between incident creation and display. Refresh the page to capture the latest data.
- Confirm that your filters (time and service) match your expectations.

## 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.

![A screenshot of the PagerDuty UI indicating that incidents in the Operations Console are loading](/images/kb/bc0d5d5a58749dc6b38a2c5db70cfe0c220be289312fde26259f8f76ad84fa8e-loading_incidents.webp)
*Loading incidents...*

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

Yes, you can define custom fields as filters to narrow down results or search for specific incidents. Please read [Custom Details](#custom-details) above for more information.

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

You can add up to 10 custom details fields in the Operations Console's incident table. If there's a field you'd like to display but cannot, please deselect another custom field first.

**What happens if I manually merge an incident on a non-AIOps service with an incident on an AIOps service?**

The incident will merge as normal. All AIOps features on the incident shall be available.

**What happens if I manually reassign an incident on an AIOps service to a non-AIOps service?**

The incident will move as normal, however, the system will disable all AIOps features on the incident.

**What counts are shown in the Service Health Visualization?**

Active incidents associated with each service within the selected time window.

**Can I export the data in the Service Health Visualization?**

Not at this time. Use drill-through to work incidents directly from PagerDuty.

**Does the Service Health Visualization include Business Services?**

The visualization is centered on Technical Services. Please refer to the [Service Dependency graph](/incident-management/services/service-graph) to understand upstream/downstream impact.