Solution

Bundled Observability

Production-grade observability bundled into the platform — logs, metrics, traces, SLOs with burn-rate alerts, synthetics and usage metering — without a separate observability contract.

Included
In the Standard and Enterprise licence — no separate observability contract
Burn rate
Alerting on error budgets, not raw thresholds
In-region
Telemetry stays in the deployment's region or perimeter

The challenge

Observability is usually a separate, expensive contract bolted onto the cloud platform, with its own identity, data and alerting to maintain.

  • 01

    A second identity system and a second bill for the monitoring tool.

  • 02

    Alerts fire on thresholds, so on-call is paged for noise and misses slow burns.

  • 03

    Telemetry and inventory disagree about what a service is, so incidents lose time on 'which host is this'.

How it works

The data path, end to end

  1. Step 1:

    Telemetry — logs, metrics and traces — is ingested from cloud services, OpenTelemetry agents and the Edge Agent.

  2. Step 2:

    Signals are correlated to inventory, so each one resolves to a workload and an owner.

  3. Step 3:

    SLOs are defined per service; alerts fire on error-budget burn rate; synthetics probe critical paths.

  4. Step 4:

    Breaches open ITSM incidents automatically and route to the owning team.

  5. Step 5:

    Usage metering feeds Whalenomics and Tenancy for cost and billing.

Observe: service level objectives with remaining error budget, beside channels-web's p95 latency crossing its objective and the incident it opened
Observe in the console. Illustrative screen with sample data.

Questions

Questions teams ask in the evaluation

Scope, permissions, integrations and what is live today.

01Can we keep our current APM tool during a transition?

Yes. Its alerts can open incidents in the platform through webhooks while you move dashboards and SLOs across at your own pace.

02How do you keep alert noise down?

Alerts are based on SLO error-budget burn rate and correlated to workloads, so one real problem produces one incident routed to its owner.

03Where is telemetry stored?

In the deployment's region on SaaS, in your accounts on BYOC, and inside the perimeter on sovereign or air-gapped deployments.

Next step

Bundled Observability, on your own estate.

Bring one cloud account or one on-prem site. We connect it read-only during the session, walk this workflow on your real resources, and leave you with the export.