Skip to main content

Observe

Telemetry Provided
  • Infrastructure Entities - Complete infrastructure topology including compute, storage, and networking resources
  • Logs - Application and container logs for correlation with Diagnoses
  • Metrics - Performance metrics from applications and infrastructure
  • Service Discovery - Automatic discovery of services, workloads, and infrastructure components
  • Signals - Automatic Signal detection from metrics, traces, and external monitoring systems

Causely integrates with Observe to discover the Kubernetes clusters that send data to your Observe tenant, and to use their metrics and container logs. Causely reads this data through the Observe API, so the Causely mediator doesn't need to run in, or have access to, the clusters themselves. Every cluster in your Observe tenant is discovered automatically, and new clusters are picked up without configuration changes.

How it works​

Causely reads the datasets that the Observe Agent's Kubernetes Explorer package writes:

Observe datasetUsed for
Kubernetes Explorer/Kubernetes EntityClusters, nodes, pods, containers, controllers, services, persistent volumes, and ingresses
Kubernetes Explorer/Prometheus MetricsContainer and node CPU, memory, and ephemeral storage usage, and node connection tracking
Kubernetes Explorer/Kubernetes LogsContainer logs, used as evidence for diagnoses

Causely refreshes the topology every 5 minutes, and metrics every minute. Container logs are read from Observe when Causely needs them for a diagnosis.

Causely builds the same entities as its native Kubernetes integration, including Signals from pod and container status such as crashes and out-of-memory kills.

Prerequisites​

  • The Observe Agent with the Kubernetes Explorer package, installed on each cluster you want Causely to discover.
  • Your Observe customer ID. It's the number in your Observe URL, for example 123456789012 in https://123456789012.observeinc.com.
  • An Observe API token with read access to the Kubernetes Explorer datasets.

Step 1: Create a Kubernetes Secret with the Observe credentials​

Create a Kubernetes Secret with your Observe customer ID and API token. The url key is optional and defaults to https://<customer-id>.observeinc.com:

kubectl create secret generic \
  --namespace causely observe-credentials \
  --from-literal=customer-id="..." \
  --from-literal=api-token="..."

Step 2: Update Causely configuration​

Once the secret is created, update the Causely configuration to enable the Observe scraper:

scrapers:
  observe:
    enabled: true
    accounts:
      - secretName: observe-credentials

To discover only some of the clusters in your Observe tenant, list them by name:

scrapers:
  observe:
    enabled: true
    accounts:
      - secretName: observe-credentials
        clusters:
          - production-east
          - production-west

Alternative: Enable Credentials Autodiscovery​

Causely supports credentials autodiscovery so you can add new accounts without editing config. Label the Kubernetes secret to enable autodiscovery for the Observe scraper:

kubectl --namespace causely label secret observe-credentials "causely.ai/scraper=Observe"