Skip to main content
Obsy reads collector health metrics and creates dashboards and monitors in your observability platform. You need at least one platform connected to use OTel Collector health reports, reliability reports, and alert monitors. Go to Integrations in the sidebar to manage platform connections.

Datadog

Prerequisites

  • A Datadog account with Admin or Standard role.
  • An API key and an Application key.

Steps

  1. In Datadog, go to Organization Settings → API Keys and click New Key. Name it obsy and copy the value.
  2. Go to Organization Settings → Application Keys and click New Key. Name it obsy and copy the value. The application key must belong to a user with Admin role.
  3. In Obsy, go to Integrations, find the Datadog card, and click Connect.
  4. Paste the API key and application key, enter your Datadog site (default datadoghq.com — change to datadoghq.eu for EU), and click Save.
Obsy verifies the keys by making a lightweight validate API call. A green Connected badge appears when successful.

What Obsy does with Datadog


Grafana Cloud

Prerequisites

  • A Grafana Cloud stack.
  • A service account or API key with Editor role.

Steps

  1. In your Grafana Cloud stack, go to Administration → Users and access → Service accounts.
  2. Click Add service account, name it obsy, and assign the Editor role.
  3. Click Add service account token and copy the token.
  4. In Obsy, go to Integrations, find the Grafana Cloud card, and click Connect.
  5. Enter your Grafana instance URL (e.g. https://myorg.grafana.net) and the service account token.
  6. Fill in your Prometheus datasource UID — find this in Grafana under Connections → Data sources → your Prometheus source → Settings (the UID is in the URL).
  7. Click Save.

What Obsy does with Grafana


AWS Managed Grafana

Prerequisites

  • An AWS account with an Amazon Managed Grafana workspace.
  • An IAM user with grafana:* permissions (or an IAM role for cross-account access).
  • Your workspace must have CloudWatch and/or Amazon Managed Prometheus configured as data sources.

Steps

  1. If you don’t have a workspace yet, go to the Amazon Managed Grafana console and click Create workspace. Enable CloudWatch, X-Ray, and optionally Amazon Managed Prometheus as data sources.
  2. Create an IAM user (e.g., obsy-grafana-access) with this policy:
  1. Create an access key for the IAM user (Security credentials → Create access key → Third-party service).
  2. In Obsy, go to Integrations, find the AWS Managed Grafana card, and click Connect.
  3. Enter:
    • Region — where your workspace is deployed (e.g., us-east-1)
    • Workspace ID — starts with g- (found in the AMG console)
    • Access Key ID and Secret Access Key — from the IAM user
    • AMP Workspace ID (optional) — if using Amazon Managed Prometheus (starts with ws-)
  4. Click Test Connection then Save.

What Obsy does with AWS Managed Grafana

Your telemetry data stays within your AWS account. OTel data is exported directly to CloudWatch, X-Ray, and AMP using native AWS OTLP endpoints with SigV4 authentication.
For detailed setup including cross-account access and troubleshooting, see AWS Managed Grafana integration.

Updating or removing a platform

Open Integrations, find the connected platform card, and use the Edit or Disconnect actions.
Disconnecting a platform removes the stored credentials but does not delete dashboards or monitors already created in that platform.

Multiple platforms

You can connect Datadog, Grafana Cloud, and AWS Managed Grafana at the same time. When creating dashboards or monitors, Obsy asks which platform to use. You can set one as primary and another as secondary for automatic fallback. Webhook routing is per-platform — see Webhooks for how to set up alert routing for each.