Skip to main content

Observe Export

Once Causely exports Issues and Diagnoses to Observe, Observe's AI SRE can answer reliability questions from the Diagnoses Causely has already identified, instead of inferring the cause from raw telemetry. This makes its answers more consistent and helps users resolve problems faster.

Why export to Observe​

An AI SRE that works only from raw telemetry has to work out the cause of a problem on its own. It reads metrics, logs, and traces, forms a hypothesis, and may reach a different answer each time it is asked.

Causely has already done that work. It identifies the Diagnosis behind each Issue from the relationships between your services and infrastructure. When this data is available in Observe, the AI SRE can start from the cause instead of searching for it.

For AI SRE use cases, this means:

  • Faster triage. The AI SRE starts from the Diagnosis behind an Issue, so it spends less time searching telemetry for a cause.
  • More consistent answers. The same Issue leads to the same cause, instead of a new hypothesis each time.
  • Shared context. Responders and the AI SRE work from the same Diagnosis, so they discuss the same problem.

What Causely exports​

Causely exports the following to Observe:

Configuration​

Exporting to Observe is configured per Causely repository. It is currently available for BYOC deployments of Causely. To learn more about BYOC installation, see BYOC (Self-Hosted) Deployment.

To set up the export, you need:

  • A Causely deployment that supports export to Observe.
  • Your Observe customer ID and a datastream token that accepts the data.

To discover Kubernetes clusters, application services, metrics, and container logs from Observe, see the Observe telemetry source.