| ID | Title | Description |
|---|---|---|
| CCC.Monitor.CP01 | Metric collection | Gathering numerical (quantitative) data points about the performance, health, or behaviour of systems, applications or infrastructure. |
| CCC.Monitor.CP02 | Tracing | An observability technique providing an end-to-end view of a request or transaction flow through a complex system to enable a single action to be linked to resulting events in multiple downstream systems. |
| CCC.Monitor.CP03 | Reporting | Summarised view of metrics in a structured, sharable format. |
| CCC.Monitor.CP04 | Health Checks | A type of monitoring that focuses on the operational status and readiness of components or entire systems. |
| CCC.Monitor.CP05 | SLO Monitoring | Define and monitor Service Level Objectives (SLO) using Service Level Indicators (SLI) based on metrics. |
| CCC.Monitor.CP06 | Synthetic Monitoring | Proactively checking sample user interactions to identify issues before real users are impacted. |
| CCC.Monitor.CP07 | Uptime Monitoring | Checking whether a specific service or application is accessible from an external perspective. |
| CCC.Monitor.CP08 | Application Performance Monitoring (APM) | A comprehensive approach to monitoring the performance, availability and user experience of an application through multiple levels of data collection |
| CCC.Monitor.CP09 | Dashboard | A visual representation of the health of systems being monitored. Pulling together metrics, current alerts, SLO/SLI's, health checks and other monitoring features into a single location to enable a view of the health of the overall system. |
| CCC.Monitor.CP10 | Triggering | Automatically initiating actions like alerts, notifications or automated workflows based on pre-defined conditions being met. |
| CCC.Monitor.CP11 | Integration with Third-Party Tools | Monitoring tools are able to integrate with a number of downstream systems in order to send notifications and alerts, raise tickets and create incident reports. |
Management / Monitoring
Capabilities
Version: