The Visibility Console provides users with the single pane-of-glass experience to effectively monitor their digital operations in real time. This feature provides Central Ops / NOC teams and technical stakeholders with context on their technical environment at a glance, allowing them to quickly understand the health of their digital operations.
The interactive, read-only version of the Visibility Console is available as part of our Business Plan. The fully editable and customizable version of the Visibility Console is available as part of our Digital Operations plan.
Please contact our Sales Team if you would like to sign up for a trial or upgrade to a plan with this feature suite.
Each user in an account will have access to their own Visibility Console under Incidents Visibility and changes will be unique to their account. The console has several modules available with global filtering capabilities, which allow users to filter the modules by a combination of teams, services, and incident priorities. Data flows into the Visibility Console in real-time and each module auto-refreshes every 30 seconds.
To show a specific group of services or incidents, simply add filter tags to the global filter bar. Click the filter bar dropdown and select your preferred tags:
- Team: The team tag will add all the services owned by a team to the group of services shown.
- Service: The service tag will add the specific service to the group of services shown.
- Priority: The priority tag will filter the incidents module to show only the incidents with that have priority (priority tag only filters the Incidents module).
Filtering only impacts the Service Activity, Services, Incidents and On-Call Responders modules.
The Incidents module displays a real-time list of the most recent open incidents that have triggered based on the filters selected. It sorts the incidents by most recent trigger time and shows the status, priority, title of the incident, the service impacted, and the responders assigned. The module can be filtered by All Incidents, High Urgency and Low Urgency. To take action on incidents in the module, select the checkbox to the left of the incident(s) and click your desired action: Acknowledge, Resolve or Change Priority.
The Services module is ordered in the same way as the Service Activity module and offers additional context on the current state of a given service. Each service will display the associated team (if there is one configured), the number of open incidents, the time of the last incident, and the current state of the service.
Definitions of different technical service states:
- Awaiting Response: The service currently has one or more incidents in a triggered state waiting on a response.
- Response in Progress: The service currently has one or more incidents in an acknowledged state waiting on resolution.
- Maintenance Window: The service is currently in maintenance mode or is disabled, meaning any incoming events on the service will not trigger an incident.
- Without Open Incidents: The service currently has zero open incidents.
The Status Dashboard module brings the information from the status page and adds that context to the console so users can monitor the status of their business services in one place. Business services can be expanded to show the status of supporting technical services ensuring stakeholders and response teams are always up to date with the live status of system health.
The Status Dashboard module is only available to accounts who have Visibility and Status Dashboard features.
The Service Activity module allows users to see incident activity across a multitude of their services at once, so that they can quickly understand their digital operations health, and identify if there’s a widespread major incident. It is ordered by most recently impacted service, and will reorder itself when new incidents are triggered. It has different time windows so eyes on glass teams can monitor their digital operations in real-time, but can also see service activity in the last 7 days or the last 24, 12, 6 or 1 hour(s). You can click each cell for more details about the incidents affecting service activity. This module can be filtered to any set of teams and services.
The On-Call Responders module provides a quick and easy way to search which users are on-call across all escalation policies. Search for your desired escalation policy and click the to view and drill down into further details about users currently on-call.
The Incidents and Changes Timeline Module displays a timeline of incidents and change events across all services. The module can be filtered by the last 7 days, 24 hours, 12 hours, 6 hours or 1 hour.
The Markdown module allows users to add any text / notes to their console. This could be used to display instructions, add hyperlinks to frequently used documentation, link to runbooks, or take general notes during an on-call shift or investigation.
The Custom URL module allows users to embed external web pages into an iframe, in order to add external monitoring to the Visibility Console. Any PagerDuty webpage is embeddable, as well as many external status pages, and public dashboard URLs.
Not all webpages will allow themselves to be embedded, please read the details below to learn more.
The Custom URL module has some limitations in place to ensure security.
Please ensure the following for any URL that you would like to embed:
- You must use the
Content-Security-Policy: frame-ancestorsin the response header for the URL.
- Xframe is obsolete in most modern browsers, but if you are running into this issue, you may need to set the ALLOW-FROM field.
Some URLs may not load for the following reasons:
- The page has restricted CSP.
- The page explicitly blocks Xframes.
- The page cannot be served over HTTPs (PagerDuty only serves over HTTPs).
Customers on the Digital Operations plan can customize the Visibility Console. Customers using our Visibility Beta on Business plans will not be able to customize the Visibility Console and will have a default view.
Each module can be added, moved, edited or removed from the Visibility Console.
To add a module that is not currently present in the console, click the Add Module dropdown at the top right of the screen. Select your preferred module and it will appear below.
To move modules to different locations in the Visibility Console, hover over the icon at the top right of each module and drag and drop to your desired location.
To edit a module, click the at the top right of the module, make your desired edits and click Save.
To remove a module from the console, click the X at the top right of the module. You will see a dialog that confirms this will remove all of its associated configuration, click OK to remove.
No. Currently, each user will have their own Visibility Console that they can customize. The layout will be saved for the user on their next session and will not affect other users.
The Infrastructure Health module module is not available in the current version of the Visibility Console. However, new modules and functionality may be added to solve similar needs. Please reach out to our Support team with any feature requests.
Currently, the Incidents, Services, and Service Activity modules load the top 100 most recent results. However, users can use the filtering capabilities to narrow their search and show more relevant results if needed. If there are any requests, please reach out to support.
Due to security issues both to PagerDuty and the user, the iframe is built to ensure the Visibility Console is safe and secure. Therefore, there are limitations to what can be embedded and what cannot.
Yes! There are currently other modules in development that are aimed to help users and organizations better monitor their real-time digital operations.
If you have any questions, please reach out to [email protected].
Updated about a month ago