Send production telemetry

Once you've verified telemetry locally, use the same instrumentation to understand your deployed app. Configure its production exporter for Everr Cloud and keep development pointed at the local collector.

Create an ingestion key

Under API Keys, choose the key for your runtime:

• Server: create a new API Key selecting the Send telemetry flag
• Browser: create a new Public Key and restrict it to your app's origins. Follow Browser telemetry for client configuration.

API Keys are shared within the organization, and only admins can create them.

Configure your deployed app

If your agent set up telemetry, you should find a Telemetry section in your project's README. It lists the endpoint, key variables, and activation steps used by your app. Ask for help with any remaining production configuration:

/everr-setup-telemetry Prepare this app's production export to Everr Cloud using the existing instrumentation. Document the required deployment settings and how to verify ingestion.

If you're configuring production manually, here are the common environment variables:

export OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.everr.dev/
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <ingestion-key>"

The ingestion-key is the API Key generated above. Don't forget to set deployment.environment.name to production and keep the same stable service.name used in local development.

Rebuild, redeploy, or restart as required by your runtime. If you already run your own OpenTelemetry Collector in production, configure its exporter instead. See Production telemetry for collector configuration and authentication details.

Verify Cloud ingestion

Trigger a request or job covered by your production instrumentation. Run everr cloud login if needed, then everr cloud status to confirm the saved session's organization owns the ingestion key. To use another installation or account, log in again; see Authentication.

Then, you can ask your AI agent:

/everr-use-telemetry verify cloud telemetry sent from production environment

Or, use the CLI manually, replacing my-service with your service name:

everr cloud query "$(cat <<'SQL'
SELECT Timestamp, ServiceName, SpanName, Duration / 1e6 AS duration_ms, TraceId
FROM traces
WHERE ServiceName = 'my-service'
  AND Timestamp >= now() - INTERVAL 15 MINUTE
  AND toString(ResourceAttributes.`deployment.environment.name`) = 'production'
ORDER BY Timestamp DESC
LIMIT 20
SQL
)"

Or, open Everr Cloud, select the organization that owns the ingestion key, and find fresh data for your service and production environment in Traces or Logs.

If data is missing, check the deployed exporter settings and that the SDK has flushed. A 401 response means the key is missing, invalid, or lacks Send telemetry. With an agent, ask everr-setup-telemetry to trace the export and ingestion path.