> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalasset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring

> Ensuring highly available, performant and reliable services for our clients

## Overview

Digital Asset actively monitors the suite of services that support the functionality of the **Registry** application on Canton Network. We maintain a comprehensive observability strategy that facilitates our **24/7 Global Support Team** to:

* **Detect**: Identify infrastructure anomalies and performance regressions in real time.
* **Diagnose**: Rapidly isolate root causes across distributed systems.
* **Resolve**: Mitigate operational issues swiftly; often before they impact clients.

The following sections provide a technical overview of how we monitor our production environment, manage telemetry data and maintain continuous operational resilience.

<Tabs>
  <Tab title="Support Coverage">
    Digital Asset support teams are geographically distributed across the world, utilising the "follow-the-sun" model to ensure 24/7 coverage.

    Teams in different time zones have overlapping shift windows, daily handoffs, a shared knowledge base amongst other procedures and tooling at their disposal to ensure the availability and reliability of our services for our customers.

    A 24/7 on-call rotation is maintained to ensure our systems are available to respond to any incidents or raised alerts:

    | Severity | Definition                                                                                                                                                                                         |
    | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | 1        | Application is not operational and/or all production data is inaccessible. Dataflow is completely stopped resulting in a critical impact on the client's business. **No workaround** is available. |
    | 2        | Application is operational but severely restricted functionality or degradation impacting the client's operations. **No workaround** is available.                                                 |
    | 3        | Application is operational with functional limitations or restrictions, that are not critical to the overall client's operations.                                                                  |
    | 4        | Application is operational with no current impact on client's operations, but errors have been identified that will potentially impact client operations.                                          |
  </Tab>

  <Tab title="Observability">
    We employ a consolidated, best-in-class tooling ecosystem to monitor our services:

    <Steps>
      <Step title="Cloud Infrastructure">
        Native cloud based metrics and logging for baseline resource health across our entire cloud footprint (Compute, Kubernetes, SQL, etc.).
      </Step>

      <Step title="Centralized Observability">
        A single pane for dashboards, metrics and distributed tracing (APM) which provides insights from the overall health of our services to tracing individual requests through our distributed system.
      </Step>

      <Step title="Incident Management">
        Alerts are generated by our cloud infrastructure and centralised observability stack, get routed to the correct team with both the alert context and severity rating.

        Critical alerts contain a **runbook** to assist engineers on how to investigate and mitigate issues quickly.
      </Step>
    </Steps>
  </Tab>
</Tabs>

<Note>
  For instructions on configuring monitoring for your own validator, please consult the Canton Network documentation [here](https://docs.canton.network/global-synchronizer/production-operations/monitoring-setup).
</Note>