GRC Store

Search / finos-ccc/ccc.tracing.cp / v2026.06-rc4

Release · v2026.06-rc4

FINOS-CCC/CCC.Tracing.CP Capability Catalog

FINOS-CCC/CCC.Tracing.CP

Capabilities for Cloud Tracing & Observability technologies, as defined by the FINOS Common Cloud Controls project.

Published by FINOS Common Cloud Controls

Install

OCI v1.1
$grcli unpack --repository finos-ccc/ccc.tracing.cp --tag v2026.06-rc4
Coordinate
oci.grc.store/finos-ccc/ccc.tracing.cp:v2026.06-rc4
Manifest digest
sha256:f1c732468b0d2387b4cf6f5f887938d1b938327216016135255156a703e681d7

Provenance

1 layer
Digest Media type Size
634388b1e27c… application/vnd.gemara.artifact.v1+yaml 5.2 KiB
Bundle config blob 
{
  "bundle-version": "1.0",
  "gemara-version": "v1.2.0",
  "metadata": {
    "provenance": {
      "buildDefinition": {
        "buildType": "https://grc.store/grcli/buildtype/v0",
        "externalParameters": {
          "artifact": {
            "id": "CCC.Tracing.CP",
            "type": "CapabilityCatalog"
          },
          "target": {
            "registry": "oci.grc.store",
            "repository": "finos-ccc/ccc.tracing.cp",
            "tag": "v2026.06-rc4"
          }
        },
        "internalParameters": {
          "CI": "true",
          "GITHUB_ACTIONS": "true",
          "GITHUB_ACTOR": "eddie-knight",
          "GITHUB_REF": "refs/heads/main",
          "GITHUB_REPOSITORY": "eddie-knight/common-cloud-controls",
          "GITHUB_RUN_ATTEMPT": "1",
          "GITHUB_RUN_ID": "26770748733",
          "GITHUB_SHA": "2b6dab4c1307a0ac67d90c99829f6c1825154c84",
          "GITHUB_WORKFLOW": "Batch Release All Catalogs",
          "RUNNER_OS": "Linux"
        },
        "resolvedDependencies": [
          {
            "name": "artifacts/management/tracing/capabilities.yaml",
            "uri": "file://artifacts/management/tracing/capabilities.yaml",
            "digest": {
              "sha256": "634388b1e27c22ec864c2fb925f5035d87e7afb93250be5c97b873586914f3cc"
            }
          },
          {
            "name": "source",
            "uri": "git+https://github.com/eddie-knight/common-cloud-controls@2b6dab4c1307a0ac67d90c99829f6c1825154c84",
            "digest": {
              "gitCommit": "2b6dab4c1307a0ac67d90c99829f6c1825154c84"
            }
          }
        ]
      },
      "runDetails": {
        "builder": {
          "id": "https://github.com/eddie-knight/common-cloud-controls/actions/runs/26770748733",
          "version": {
            "go": "go1.25.0",
            "go-arch": "amd64",
            "go-os": "linux",
            "grcli": "v0.2.2"
          }
        },
        "metadata": {
          "invocationId": "26770748733-1",
          "startedOn": "2026-06-01T17:30:04.627093966Z",
          "finishedOn": "2026-06-01T17:30:04.860228118Z"
        },
        "byproducts": [
          {
            "name": "capabilities.yaml",
            "digest": {
              "sha256": "634388b1e27c22ec864c2fb925f5035d87e7afb93250be5c97b873586914f3cc"
            }
          }
        ]
      }
    }
  },
  "artifacts": [
    {
      "name": "capabilities.yaml",
      "type": "CapabilityCatalog",
      "id": "CCC.Tracing.CP",
      "role": "artifact"
    }
  ]
}

CCC Cloud Tracing & Observability Capabilities

Capabilities for Cloud Tracing & Observability technologies, as defined by the FINOS Common Cloud Controls project.

ID
CCC.Tracing.CP
Version
v2026.06-rc4
Gemara version
v1.2.0
Author
FINOS Common Cloud Controls

Observability

The Observability group covers entries related to logging, monitoring, metrics, alerting, and event publication. This includes audit trail integrity, enumeration detection, and protection against tampering or unauthorized access to operational telemetry.

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

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

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

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

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

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

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

  8. 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).

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

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