Cloud Tracing & Observability
Services that provide distributed tracing and performance telemetry for cloud-native and hybrid applications. These tools enable developers and operators to visualise end‑to‑end request flows, identify performance bottlenecks, correlate traces with logs and metrics, and analyse application dependencies. They integrate with managed compute platforms, container orchestrators, serverless runtimes, and service meshes to provide centralised observability with sampling, tagging, and context‑propagation support.
Release Details
Version:
DEV
Assurance Level:
Release Manager:
DB
Development Build
Contributors
DT
Development Team
Change Log
- Development build - no formal changelog available
Capabilities
| ID | Title | Description | Threat Mappings |
|---|---|---|---|
| CCC.Tracing.CP01 | Distributed Telemetry Collection | Collects end-to-end telemetry (spans, segments, and trace events) from instrumented applications and infrastructure, and aggregates them into complete request flows that reveal execution paths, behavior, and performance across distributed systems. | 0 |
| CCC.Tracing.CP02 | Dependency Mapping and Visualization | Automatically builds visual or logical graphs of upstream and downstream dependencies (services, functions, databases, external endpoints), showing call relationships, traffic patterns, and health signals to clarify how requests traverse the system. | 0 |
| CCC.Tracing.CP03 | Distributed Context Propagation | Propagates trace and span identifiers across service boundaries using standardized headers/protocols so operations for the same request can be correlated across asynchronous calls and heterogeneous runtimes. | 0 |
| CCC.Tracing.CP04 | Performance Profiling | Analyzes trace data to surface runtime characteristics such asexecution durations, slow operations, bottlenecks, and regressions for providing granular insight into identifying bottlenecks inside distributed workflows. | 0 |
| CCC.Tracing.CP05 | Error Correlation | Detects errors, exceptions, faults, and retry patterns within spans and correlates them to affected request paths so users can pinpoint the component and operation causing failures. | 0 |
| CCC.Tracing.CP06 | Sampling | Provides configurable sampling strategies such as rules-based, rate-based, and adaptive to control trace volume and balance observability needs with cost and system performance. | 0 |
| CCC.Tracing.CP07 | Trace Querying & Filtering | Offers a query and filtering interface to retrieve traces by latency, error status, service name, operation, tag values, time windows, and other attributes to isolate behaviours or anomalies quickly. | 0 |
| CCC.Tracing.CP08 | Integration with Logs and Metrics | Correlates traces with logs and metrics from related resources to provide unified observability; users can pivot between telemetry types using shared identifiers (e.g., trace or span IDs). | 0 |
| CCC.Tracing.CP09 | Trace Retention | Stores trace data for configurable retention periods and supports time-to-live policies driven by workload needs, cost constraints, or compliance requirements. | 0 |
| CCC.Tracing.CP10 | Assistance for Root Cause Analysis | Analyzes trace patterns, latency anomalies, and error flows to surface likely sources of failures or performance degradation and highlight trends or problematic components to accelerate diagnosis and remediation. | 0 |
| CCC.Core.CP01 | Encryption in Transit Enabled by Default | The service automatically encrypts all data using industry-standard cryptographic protocols prior to transmission via a network interface. | 0 |
| CCC.Core.CP02 | Encryption at Rest Enabled by Default | The service automatically encrypts all data using industry-standard cryptographic protocols prior to being written to a storage medium. | 0 |
| CCC.Core.CP03 | Access Log Publication | The service automatically publishes structured, verbose records of activities performed within the scope of the service by external actors. | 0 |
| CCC.Core.CP06 | Access Control | The service automatically enforces user configurations to restrict or allow access to a specific component or a child resource based on factors such as user identities, roles, groups, or attributes. | 0 |
| CCC.Core.CP09 | Metrics Publication | The service automatically publishes structured, numeric, time-series data points related to the performance, availability, and health of the service or its child resources. | 0 |
| CCC.Core.CP10 | Log Publication | The service automatically publishes structured, verbose records of activities, operations, or events that occur within the service. | 0 |
| CCC.Core.CP14 | API Access | The service exposes a port enabling external actors to interact programmatically with the service and its resources using HTTP protocol methods such as GET, POST, PUT, and DELETE. | 0 |
| CCC.Core.CP20 | Resource Tagging | The service provides users with the ability to tag a child resource with metadata that can be reviewed or queried. | 0 |
| CCC.Core.CP22 | Location Lock-In | The service may be configured to restrict the deployment of child resources to specific geographic locations. | 0 |
| CCC.Core.CP28 | Command-line Interface | The service includes a component that reads and translates text into commands that can be executed by the service. | 0 |