Skip to main content
Observability forwards the OpenTelemetry traces and metrics from your agents’ runs to your own observability provider. Use it to watch sessions, LLM calls, and errors in the tooling your team already uses. You can forward to Datadog or Splunk Observability Cloud, one provider per account. The setting belongs to an account. It covers every session in a workspace that account owns. In an organization, only admins can open it.

​
Open Observability

1

Choose the account

Use the account switcher at the top of the left nav to choose your personal account or an organization.
2

Go to Observability

Click Access & setup in the left nav, then Observability.
Direct URLs:
  • Personal account: https://app.guild.ai/settings/observability
  • Organization: https://app.guild.ai/organizations/{org-name}/settings/observability

​
Connect Datadog

You need your Datadog site and a Datadog API key. An application key isn’t needed.
1

Choose the provider

Under Provider, select Datadog.
2

Choose your site

Under Site, select the Datadog site your organization signs in to: US1, US3, US5, EU1, AP1, or AP2.
3

Enter your API key

Under API key, paste a Datadog API key. Create one under Organization Settings > API Keys in Datadog.
4

Save

Click Save.
Guild sends traces to https://otlp.{site}/v1/traces and metrics to https://otlp.{site}/v1/metrics, Datadog’s OTLP intake. It authenticates with your API key in the dd-api-key header. It also asks Datadog to compute APM trace metrics, such as request counts and latency, from the spans. After you save, the page shows the site and a masked API key. See the Datadog integration page for troubleshooting.

​
Connect Splunk

You need your Splunk Observability Cloud realm and an access token that can ingest data.
1

Choose the provider

Under Provider, select Splunk.
2

Enter your realm

Under Realm, enter your Splunk Observability Cloud realm, for example us0.
3

Enter your token

Under Access token, paste a Splunk access token with ingest permission.
4

Save

Click Save.
Guild sends traces to https://ingest.{realm}.observability.splunkcloud.com/v2/trace/otlp and metrics to https://ingest.{realm}.observability.splunkcloud.com/v2/datapoint/otlp. It authenticates with your token in the X-SF-Token header. After you save, the page shows the realm and a masked token.

​
What Guild sends

Guild forwards only the spans and metrics from sessions in workspaces the account owns. Spans follow the OpenTelemetry GenAI semantic conventions, so Datadog’s and Splunk’s AI monitoring views can read them. Each span carries these attributes:

​
Change or remove the provider

  • To change the site, realm, or key, click Edit, update the fields, and click Save.
  • To switch providers, click Edit, choose the other provider, enter its details, and click Save. An account forwards to one provider at a time, so the new provider replaces the old one.
  • To stop forwarding, click Delete, then confirm. Guild stops forwarding traces. Deleting can’t be undone: to reconnect, enter your details again.
Guild restarts its trace collector after each change, so there can be a short delay before new settings apply.
  • Sessions to inspect a single run inside Guild
  • Usage for spend and token counts
Last modified on November 10, 2026