Render

This guide configures logs, traces, metrics. Replace YOUR_INGEST_KEY with your key on your server, never in a public example.

1. Set server environment variables

Set these on the running service. Keep the key out of source control, client bundles and build logs.

export OTEL_SERVICE_NAME='my-service'
export OTEL_RESOURCE_ATTRIBUTES='deployment.environment.name=production'
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT='https://otlp.siteqwality.com/v1/logs'
export OTEL_EXPORTER_OTLP_LOGS_HEADERS='Authorization=YOUR_INGEST_KEY'
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT='https://otlp.siteqwality.com/v1/traces'
export OTEL_EXPORTER_OTLP_TRACES_HEADERS='Authorization=YOUR_INGEST_KEY'
export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT='https://otlp.siteqwality.com/v1/metrics'
export OTEL_EXPORTER_OTLP_METRICS_HEADERS='Authorization=YOUR_INGEST_KEY'
export OTEL_LOGS_EXPORTER=otlp
export OTEL_TRACES_EXPORTER=otlp
export OTEL_METRICS_EXPORTER=otlp

2. Configure your Render service

Direct OTLP/HTTP from your application works independently of Render log streams. Render’s native log streams send syslog, and syslog over TLS is not available yet. For platform stdout, run a forwarder of your own (for example the OpenTelemetry Collector or Vector) that receives Render’s stream and exports OTLP/HTTP.

Open the service Environment settings and add the selected OTEL variables as secret values. Use your language guide to install and start instrumentation, then save and redeploy.

3. Use a Node.js start command

Install packages from the Node.js guide first, or use the start command from your language guide. Generate a request and log record. Render native log streams cannot send to Site Qwality directly until syslog over TLS is available.

node --require @opentelemetry/auto-instrumentations-node/register app.js

See your data

Open Logs, Traces or Metrics. New data usually shows up within a minute, and a page that says it is waiting for data switches to your data on its own. Nothing arriving? See what each status code means in failure handling.

Production checklist

Store the key in your platform secret mechanism, rotate it when exposed and remove test keys. Set a stable service.name and deployment.environment.name; avoid user IDs or unbounded values in metric labels. Prefer a persistent queue, bounded retries and exporter failure monitoring. Review redaction and processors before increasing traffic.