Network Observability and Reporting
Observe the service, not just the components.
Cloud Gateway Observe maps approved operational telemetry from eligible managed connectivity and security services to the customer, service and dependency context around it. By bringing service health together with incidents, changes and known coverage gaps, Observe helps teams understand what the available evidence says – and where action belongs.
More signals do not automatically create more understanding.
A circuit portal shows link state. A firewall console shows device health and blocks. An access platform shows sessions. An ITSM tool records incidents and changes. Each source describes its own component, using its own identifiers and time line. During a service issue, the team still has to establish which signals refer to the same customer service, what changed, which users are affected, which dependency is responsible and whether the data itself is current.
- A green component dashboard can coexist with a failing end-to-end service.
Observability is a context system,
not a screen.
The value is not the number of graphs. It is the discipline that makes operational data usable: define the service boundary, inventory the sources, map identifiers to customers and services, track source freshness, preserve incident and change context, expose known gaps, and route findings into an owned operational process.
- Replace dashboard archaeology with a shared account of the in-scope service.
How observe works
Define
the service
Record the managed service scope, network and security endpoints, dependencies, criticality, owners, service levels and the questions the customer needs to answer throughout the life of the engagement.
Inventory
the signals
Identify approved service-health telemetry, supplier status, logs, metrics, events, incidents and changes available from in-scope services. Record ownership, expected freshness, retention and known limitations.
Map
the context
Associate the available source identifiers with the correct customer tenant, service, site, user group, application or dependency as supported by the service design. These are our sources of data and scope of truth.
Check
data quality
Detect stale, unavailable or incomplete supported sources so that an absence of data is excluded without knowledge or silently presented as service health by omission.
Present
the evidence
Use standard health views, reporting and supported search or alerting functions to make relevant service information accessible to the people who operate and review it.
Connect it
to action
Relate available evidence to incident, change, escalation and service-review processes. Observability without an owner and a response route is another monitoring silo.
What Observe helps you answer
Observe surfaces the signals that answer your operational questions, not just raw data. What you see depends on which capabilities are in scope – as your service footprint grows, so does the picture.
What does the available evidence show about the current condition of the managed service?
What changed before the service behaviour changed, and was the activity approved?
Which in-scope service, site, user group, path or dependency appears affected by the condition visible in the data?
Does the next action sit with Cloud Gateway, the customer or an underlying supplier?
Which sources are current, stale, unavailable or outside the service boundary?
What do incidents, changes, open issues and available service-level indicators show over the review period?
Start with Observe Essentials
A supportable first layer of service assurance.
Observe Essentials combines approved telemetry from eligible Cloud Gateway-managed services with relevant Cloud Gateway incident and change records. It provides a standard read-only service-health view, a source inventory, telemetry-freshness checks and a monthly assurance summary within the agreed scope.
Data governance, coverage and boundaries
Control model
Define tenant isolation, RBAC, authentication, encryption, processing and storage locations, retention and deletion, sensitive-field handling, source credentials, export controls and privileged support access for every released source and view.
Customer responsibility
The customer approves the sources and users in scope, provides lawful access to customer-controlled data, and identifies classification, privacy or retention requirements that affect the service design.
Boundary
Observe is not, by default, unrestricted log analytics, a customer data lake, code-level application observability, synthetic monitoring, digital experience monitoring, SIEM, SOC, MDR, threat hunting or automated remediation. Wider sources, custom analytics, APIs, correlation and alerting require a separately approved service scope and maturity confirmation.
Control centre
Observe is the capability that defines, maps and interprets approved service telemetry within an operational process. The Control Centre is a customer-experience layer that may present released Observe views alongside other service, report, support or federated experiences. One is not an entitlement to the other unless the Service Definition says so.
Common questions
about Observe
What is observability, and how is it different from monitoring?
Traditional monitoring tells you whether something is up or down. Observability goes further: it turns the operating data from your connectivity and security services into answers, evidence and confidence. That means correlating telemetry across network, security and access to identify likely incident cause, tracking SLA and SLO delivery with evidence you can use in service reviews and audits, and giving executives and governance teams reporting they can actually use – not raw dashboards.
What can I see in Cloud Gateway Observe?
Cloud Gateway’s solutions shows service health and performance, SLA and SLO delivery, security policy enforcement and incident data, change records, and a service inventory for your tenant. Data is available through one login, and can be exported to existing ITSM and SIEM tools.
Does Cloud Gateway integrate with ServiceNow, Splunk and Microsoft Sentinel?
Cloud Gateway’s role is not to displace Datadog, Dynatrace, New Relic, Splunk, Microsoft Sentinel or your ITSM platform. Observe focuses on the secure connectivity services Cloud Gateway manages and the operational context Cloud Gateway holds. Supported integrations can complement the customer’s wider toolchain when explicitly designed and contracted. This is on our roadmap.
Start with the questions your current dashboards cannot answer.
Bring one recurring incident, fragmented service review or evidence gap. We will map the service boundary, available signals, missing context and responsibility model before proposing a telemetry scope.