Skip to main content
Telemetry export sends your organization’s request metrics from Requesty to your own observability stack. Requesty pushes metrics over OTLP/HTTP to Datadog, Grafana Cloud, your own OpenTelemetry collector or any other OTLP/HTTP endpoint, so you can chart Requesty traffic next to the rest of your systems and alert on it with the tools you already use.
Set up telemetry export in the Requesty Console.
Telemetry export is available to organization admins on the Enterprise plan. Each organization has one export destination.

Set Up a Destination

  1. Go to the Admin Panel and open the Integrations tab
  2. Find the Telemetry export card and click Set up telemetry export
  3. Choose Datadog, Grafana Cloud or Other OTLP endpoint
  4. Fill in the destination details (see below) and click Save destination
  5. Click Check connection to confirm that the destination accepts exports
Requesty pushes metrics every minute while Export enabled is on.

Datadog

  1. Pick your Datadog site, for example US1 (datadoghq.com) or EU1 (datadoghq.eu)
  2. Paste a Datadog API key from Organization Settings → API Keys in Datadog
Requesty sends metrics to https://otlp.<your site>/v1/metrics as delta metrics, which is what Datadog’s OTLP intake accepts.

Grafana Cloud

  1. Copy the OTLP endpoint, for example https://otlp-gateway-prod-us-east-0.grafana.net/otlp, from your stack’s OpenTelemetry tile in the Grafana Cloud portal
  2. Enter the stack’s Instance ID
  3. Paste an API token from an access policy that can write metrics
Requesty authenticates with Basic auth built from the instance ID and token, and sends cumulative metrics, which Grafana Cloud’s Prometheus storage needs.

Other OTLP Endpoint

Starter Dashboards

The Datadog and Grafana Cloud set-ups include a starter dashboard. Click Download the Datadog starter dashboard (JSON) or Download the Grafana Cloud starter dashboard (JSON) in the set-up dialog or on the destination card, then import the file in Datadog or Grafana.

Manage a Destination

From the Telemetry export card you can:
  • Turn Export enabled off to pause exports without losing the configuration
  • Click Check connection to send a test export. The card shows whether the destination accepted it, or the error it returned.
  • Click Edit to change the URL, temporality or headers. Saving keeps the stored headers unless you click Replace headers.
  • Click Delete to stop exporting and delete the stored URL and headers

Metrics

Metrics follow the OpenTelemetry GenAI semantic conventions where a convention exists, and use requesty.* names where it does not.

Attributes

Every metric carries these attributes: Some metrics add one more attribute: Provider names use the GenAI convention values where one exists, for example aws.bedrock, gcp.vertex_ai, gcp.gemini, azure.ai, mistral_ai and x_ai. Other providers use their Requesty provider name.
Last modified on November 20, 2026