This example service is showing a more complex example with nested groups and so on - reflecting a more complex service with many components that necessitates a bit more structure.
This app is also business critical, so includes a bit more detail on the processes involved there.
It is a UI service that mainly serves Category Pages and Product pages. It also hosts some of the components that we use across the website via ESI. See General Information section for more information what the app does.
Follow this decision flow in order to manage the triggered incident. Acknowledge the alert and then first check the following key support channels to see if an incident is already in progress:
If a major incident hasn’t already been triggered, and you think it is required trigger it before doing anything else.
Trigger it immediately using the ‘run a play’ button on the PagerDuty Incident.
Diagram of incident decision process was here - removed
See investigating issues for details on how to debug live issues with this service.
| System | URL | Additional URL |
|---|---|---|
| Grafana Dashboards | Link to 4GS dashboard | Link to custom dashboard |
| Kibana Logging | Link to saved queries | Link to visualisations |
| New Relic Dashboards | Link to Client Dashboard | Link to Server Dashboard |
| PagerDuty | Link to Service’s open alerts | Link to Rota |
| Monetate | Link to active Experiences | |
| Code | Link to Gitlab Group | |
| ServiceNow | Link to Group’s open INCs | Link to Group’s CHGs |
| Service Catalogue | Link to Service on the SC |