Direct OTLP Configuration for OpenTelemetry PHP
This document shows how to export telemetry to Uptrace using the OTLP exporter directly. If you prefer the wrapper, see Getting started with OpenTelemetry PHP.
Direct OTLP Configuration
If you prefer to use the OTLP exporter directly or are already using OpenTelemetry exporters, you can configure OpenTelemetry manually without the uptrace-php wrapper.
For more details on the OpenTelemetry APIs used below, see:
- OpenTelemetry PHP Tracing API - creating spans, recording errors, adding attributes
- OpenTelemetry PHP Metrics API - counters, histograms, and observers
- OpenTelemetry PHP Resource detectors - service name, environment, and deployment metadata
Uptrace fully supports the OpenTelemetry Protocol (OTLP) over both gRPC and HTTP transports.
If you already have an OTLP exporter configured, you can continue using it with Uptrace by simply pointing it to the Uptrace OTLP endpoint.
Connecting to Uptrace
Choose an OTLP endpoint from the table below and pass your DSN via the uptrace-dsn header for authentication:
| Transport | Endpoint | Port |
|---|---|---|
| gRPC | https://api.uptrace.dev:4317 | 4317 |
| HTTP | https://api.uptrace.dev | 443 |
When using HTTP transport, you often need to specify the full URL for each signal type:
https://api.uptrace.dev/v1/traceshttps://api.uptrace.dev/v1/logshttps://api.uptrace.dev/v1/metrics
Note: Most OpenTelemetry SDKs support both transports. Use HTTP unless you're already familiar with gRPC.
Recommended Settings
For performance and reliability, we recommend:
- Use
BatchSpanProcessorandBatchLogProcessorfor batching spans and logs, reducing the number of export requests. - Enable
gzipcompression to reduce bandwidth usage. - Prefer
deltametrics temporality (Uptrace converts cumulative metrics automatically). - Use Protobuf encoding instead of JSON (Protobuf is more efficient and widely supported).
- Use HTTP transport for simplicity and fewer configuration issues (unless you're already familiar with gRPC).
- Optionally, use the AWS X-Ray ID generator to produce trace IDs compatible with AWS X-Ray.
Common Environment Variables
You can use environment variables to configure resource attributes and propagators::
| Variable | Description |
|---|---|
OTEL_RESOURCE_ATTRIBUTES | Comma-separated resource attributes, e.g., service.name=myservice,service.version=1.0.0. |
OTEL_SERVICE_NAME=myservice | Sets the service.name attribute (overrides OTEL_RESOURCE_ATTRIBUTES). |
OTEL_PROPAGATORS | Comma-separated list of context propagators (default: tracecontext,baggage). |
Most language SDKs allow configuring the OTLP exporter entirely via environment variables:
# Endpoint (choose HTTP or gRPC)
export OTEL_EXPORTER_OTLP_ENDPOINT="https://api.uptrace.dev" # HTTP
#export OTEL_EXPORTER_OTLP_ENDPOINT="https://api.uptrace.dev:4317" # gRPC
# Pass DSN for authentication
export OTEL_EXPORTER_OTLP_HEADERS="uptrace-dsn=<FIXME>"
# Performance optimizations
export OTEL_EXPORTER_OTLP_COMPRESSION=gzip
export OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION=BASE2_EXPONENTIAL_BUCKET_HISTOGRAM
export OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=DELTA
Configure BatchSpanProcessor to balance throughput and payload size:
export OTEL_BSP_EXPORT_TIMEOUT=10000 # Max export timeout (ms)
export OTEL_BSP_MAX_EXPORT_BATCH_SIZE=10000 # Avoid >32MB payloads
export OTEL_BSP_MAX_QUEUE_SIZE=30000 # Adjust for available memory
export OTEL_BSP_MAX_CONCURRENT_EXPORTS=2 # Parallel exports
Dependencies
First, install the required packages:
composer require \
open-telemetry/opentelemetry \
open-telemetry/exporter-otlp \
open-telemetry/transport-grpc \
open-telemetry/auto-instrumentation
Exporting Traces
This example shows how to configure the OTLP trace exporter to send distributed traces to Uptrace. For information on creating spans and using the tracing API, see OpenTelemetry PHP Tracing.
<?php
declare(strict_types=1);
require __DIR__ . '/vendor/autoload.php';
use OpenTelemetry\API\Trace\SpanKind;
use OpenTelemetry\API\Trace\Propagation\TraceContextPropagator;
use OpenTelemetry\SDK\Sdk;
use OpenTelemetry\SDK\Common\Attribute\Attributes;
use OpenTelemetry\SDK\Common\Time\ClockFactory;
use OpenTelemetry\SDK\Resource\ResourceInfoFactory;
use OpenTelemetry\SDK\Resource\ResourceInfo;
use OpenTelemetry\SDK\Common\Export\TransportFactoryInterface;
use OpenTelemetry\SDK\Trace\TracerProvider;
use OpenTelemetry\SDK\Trace\SpanProcessor\BatchSpanProcessor;
use OpenTelemetry\SDK\Trace\Sampler\AlwaysOnSampler;
use OpenTelemetry\SDK\Trace\Sampler\ParentBased;
use OpenTelemetry\Contrib\Otlp\OtlpHttpTransportFactory;
use OpenTelemetry\Contrib\Otlp\SpanExporter;
$dsn = getenv('UPTRACE_DSN');
if (!$dsn) {
exit('UPTRACE_DSN environment variable is required');
}
// Configure service resource information
$resource = ResourceInfoFactory::emptyResource()->merge(
ResourceInfo::create(Attributes::create([
"service.name" => "my-php-service",
"service.version" => "1.0.0",
])),
ResourceInfoFactory::defaultResource()
);
// Set up OTLP HTTP transport
$transportFactory = new OtlpHttpTransportFactory();
$transport = $transportFactory->create(
'https://api.uptrace.dev/v1/traces',
'application/json',
['uptrace-dsn' => $dsn],
TransportFactoryInterface::COMPRESSION_GZIP,
);
// Create span exporter and processor
$spanExporter = new SpanExporter($transport);
$spanProcessor = new BatchSpanProcessor(
$spanExporter,
ClockFactory::getDefault(),
BatchSpanProcessor::DEFAULT_MAX_QUEUE_SIZE,
BatchSpanProcessor::DEFAULT_SCHEDULE_DELAY,
BatchSpanProcessor::DEFAULT_EXPORT_TIMEOUT,
BatchSpanProcessor::DEFAULT_MAX_EXPORT_BATCH_SIZE,
true,
);
// Build and register the tracer provider
$tracerProvider = TracerProvider::builder()
->addSpanProcessor($spanProcessor)
->setResource($resource)
->setSampler(new ParentBased(new AlwaysOnSampler()))
->build();
Sdk::builder()
->setTracerProvider($tracerProvider)
->setPropagator(TraceContextPropagator::getInstance())
->setAutoShutdown(true)
->buildAndRegisterGlobal();
// Now you can use the tracer
$tracer = \OpenTelemetry\API\Globals::tracerProvider()->getTracer('app_or_package_name');
Exporting Metrics
This example shows how to configure the OTLP metrics exporter to send OpenTelemetry metrics to Uptrace. For information on creating counters, histograms, and observers, see OpenTelemetry PHP Metrics.
<?php
declare(strict_types=1);
require __DIR__ . '/vendor/autoload.php';
use OpenTelemetry\SDK\Common\Attribute\Attributes;
use OpenTelemetry\SDK\Resource\ResourceInfoFactory;
use OpenTelemetry\SDK\Resource\ResourceInfo;
use OpenTelemetry\SDK\Metrics\MeterProvider;
use OpenTelemetry\SDK\Metrics\MetricReader\ExportingReader;
use OpenTelemetry\SDK\Common\Time\ClockFactory;
use OpenTelemetry\SDK\Common\Export\TransportFactoryInterface;
use OpenTelemetry\Contrib\Otlp\OtlpHttpTransportFactory;
use OpenTelemetry\Contrib\Otlp\MetricExporter;
$dsn = getenv('UPTRACE_DSN');
if (!$dsn) {
exit('UPTRACE_DSN environment variable is required');
}
// Configure resource information
$resource = ResourceInfoFactory::emptyResource()->merge(
ResourceInfo::create(Attributes::create([
"service.name" => "my-php-service",
"service.version" => "1.0.0",
])),
ResourceInfoFactory::defaultResource()
);
// Set up metrics export
$transportFactory = new OtlpHttpTransportFactory();
$reader = new ExportingReader(
new MetricExporter(
$transportFactory->create(
'https://api.uptrace.dev/v1/metrics',
'application/json',
['uptrace-dsn' => $dsn],
TransportFactoryInterface::COMPRESSION_GZIP,
)
),
ClockFactory::getDefault()
);
$meterProvider = MeterProvider::builder()
->setResource($resource)
->addReader($reader)
->build();
// Create and use metrics
$meter = $meterProvider->getMeter('app_or_package_name');
$counter = $meter->createCounter('http_requests_total', 'requests', 'Number of HTTP requests');
$histogram = $meter->createHistogram('http_request_duration', 'seconds', 'HTTP request duration');
// Example usage
$counter->add(1, ['method' => 'GET', 'status' => '200']);
$histogram->record(0.150, ['method' => 'GET', 'route' => '/api/users']);
Exporting Logs
This example shows how to configure the OTLP logs exporter to send logs to Uptrace. The logs are correlated with traces using the active span context.
<?php
declare(strict_types=1);
require __DIR__ . '/vendor/autoload.php';
use OpenTelemetry\API\Logs\EventLogger;
use OpenTelemetry\API\Logs\LogRecord;
use OpenTelemetry\SDK\Sdk;
use OpenTelemetry\SDK\Common\Attribute\Attributes;
use OpenTelemetry\SDK\Common\Time\ClockFactory;
use OpenTelemetry\SDK\Resource\ResourceInfoFactory;
use OpenTelemetry\SDK\Resource\ResourceInfo;
use OpenTelemetry\SDK\Common\Export\TransportFactoryInterface;
use OpenTelemetry\SDK\Logs\LoggerProvider;
use OpenTelemetry\SDK\Logs\Processor\BatchLogRecordProcessor;
use OpenTelemetry\Contrib\Otlp\OtlpHttpTransportFactory;
use OpenTelemetry\Contrib\Otlp\LogsExporter;
$dsn = getenv('UPTRACE_DSN');
if (!$dsn) {
exit('UPTRACE_DSN environment variable is required');
}
// Configure resource information
$resource = ResourceInfoFactory::emptyResource()->merge(
ResourceInfo::create(Attributes::create([
"service.name" => "my-php-service",
"service.version" => "1.0.0",
])),
ResourceInfoFactory::defaultResource()
);
// Set up log export
$transportFactory = new OtlpHttpTransportFactory();
$transport = $transportFactory->create(
'https://api.uptrace.dev/v1/logs',
'application/json',
['uptrace-dsn' => $dsn],
TransportFactoryInterface::COMPRESSION_GZIP,
);
$exporter = new LogsExporter($transport);
$processor = new BatchLogRecordProcessor($exporter, ClockFactory::getDefault());
$loggerProvider = LoggerProvider::builder()
->setResource($resource)
->addLogRecordProcessor($processor)
->build();
Sdk::builder()
->setLoggerProvider($loggerProvider)
->setAutoShutdown(true)
->buildAndRegisterGlobal();
// Create and use loggers
$logger = $loggerProvider->getLogger('my-app', '1.0.0');
$eventLogger = new EventLogger($logger, 'user-actions');
// Example usage
$record = (new LogRecord('User login successful'))
->setSeverityText('INFO')
->setAttributes([
'user.id' => '12345',
'user.email' => 'user@example.com',
'request.ip' => '192.168.1.100'
]);
$eventLogger->logEvent('user.login', $record);