PHP performance integration guide

Step-by-step instructions for adding performance monitoring and distributed tracing to your PHP projects.

BugSnag’s serverside performance monitoring leverages OpenTelemetry. With the wealth of open source OpenTelemetry instrumentation available for PHP, you can easily send spans and traces from your service to BugSnag by installing the OpenTelemetry SDK and completing some simple configuration.

OpenTelemetry SDK installation

The easiest way to get your app instrumented is to use the OpenTelemetry PHP extension to automatically instrument your application.

To automatically instrument your PHP app in this way, first install some build tools:

sudo apt-get install gcc make autoconf

brew install gcc make autoconf

Then build the extension with PECL:

pecl install opentelemetry

Add the extension to your php.ini file:

[opentelemetry]
extension=opentelemetry.so

Verify that it is installed and enabled:

php --ri opentelemetry

Finally add dependencies that are required for automatic instrumentation of your app:

composer config allow-plugins.php-http/discovery false
composer require \
  open-telemetry/sdk \
  open-telemetry/opentelemetry-auto-slim

If you would prefer to have more visibility and control over what instrumentation is being added, you can configure instrumentation in code. To do this see the OpenTelemetry Manual Instrumentation guide.

To send the generated spans to your BugSnag dashboard you need to install and configure an Exporter. A BugSnag plugin is provided to make this as straightforward as possible and allows you to use our managed sampling functionality. Alternatively, if you have more advanced requirements, you can configure the built-in HTTP or gRPC exporters directly – see OpenTelemetry SDK configuration.

OpenTelemetry SDK configuration

Next you need to set some configuration:

export OTEL_EXPORTER_OTLP_ENDPOINT="https://<PROJECT_API_KEY>.otlp.bugsnag.com:4318"
export OTEL_EXPORTER_METRICS_EXPORTER="none"
export OTEL_EXPORTER_TRACES_EXPORTER="otlp,console"
export OTEL_SERVICE_NAME="your-service-name"
export OTEL_RESOURCE_ATTRIBUTES="deployment.environment=<RELEASE_STAGE>,service.version=<APP_VERSION>"

• <PROJECT_API_KEY> can be found in project settings in the BugSnag dashboard.
• OTEL_SERVICE_NAME should uniquely identify your service. We recommend using the same name as your project name.
• <RELEASE_STAGE> and <APP_VERSION> must be the same as you are passing to your BugSnag Error SDK. They are case sensitive.

Traces can be received by BugSnag via either gRPC or HTTP (protobuf or JSON). In most cases the simplest way to send traces to BugSnag is to export an environment variable with your BugSnag project’s dedicated OpenTelemetry endpoint before running your OpenTelemetry instrumented app:

export OTEL_EXPORTER_OTLP_PROTOCOL="grpc"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://<PROJECT_API_KEY>.otlp.bugsnag.com:4317"

export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://<PROJECT_API_KEY>.otlp.bugsnag.com:4318/v1/traces"

Finally, running your app will start sending span information to BugSnag:

php -S localhost:8080

Sampling

Spans use up your unmanaged quota. No spans will be ingested by BugSnag once your daily quota is exhausted. To ensure you have span coverage throughout the day, we recommend you use sampling. This section explains how to control sampling if you are not using the BugSnag Sampler.

By default the OpenTelemetry SDK will use the parentbased_always_on sampler, which will sample according to the sample decision from the incoming network request if there is one, and always sample if there is not. To use this requires clients of your PHP server be instrumented in such a way that they pass their sampling information.

To apply a fixed sampling rate to all your PHP spans, you can use the traceidratio sampler:

export OTEL_TRACES_SAMPLER="traceidratio"
export OTEL_TRACES_SAMPLER_ARG="0.25" # 25% of your traces will be sampled

php -S localhost:8080

Alternatively you can use the parentbased_traceidratio sampler. This will sample at a constant rate, unless the trace context was propagated from a client, in which case it will use the same sample decision that the client used:

export OTEL_TRACES_SAMPLER="parentbased_traceidratio"
export OTEL_TRACES_SAMPLER_ARG="0.25" # 25% of traces not started in a client will be sampled

php -S localhost:8080

Collectors

An OpenTelemetry Collector is an open source component that OpenTelemetry users can host on their own infrastructure. It can receive telemetry data from multiple sources, process it in various ways, and send it on to multiple telemetry back-ends, including BugSnag.

An important use of Collectors is to enable tail-based sampling, where a trace can be inspected in its entirety before making a sampling decision, for example looking to see whether it contained any errors.

To learn about using a collector with BugSnag, see our dedicated page on using a collector.

Span batch size

The maximum payload size for BugSnag’s OpenTelemetry trace endpoints is 1MB. OpenTelemetry payload sizes can be controlled via the batch size in the SDK or collector configuration.

The appropriate batch size will largely depend on the number of attributes getting added to your spans and therefore you may need to experiment to find the appropriate setting. The batch size can be controlled by setting an environment variable; we generally recommend 200 as a good starting point, which is lower than the default of 512 spans per batch.

export OTEL_BSP_MAX_EXPORT_BATCH_SIZE=200

Custom spans

For higher resolution information into the performance of your application, you can create your own spans whenever you like. To do this, get a tracer:

use OpenTelemetry\API\Globals;

$tracer = Globals::tracerProvider()->getTracer('serviceName');

Then wrap some work in a span:

$span = $tracer
        ->spanBuilder('some interesting work')
        ->startSpan();

// do some work

$span->end();

For more information see the PHP OpenTelemetry instrumentation documentation.

If you would like BugSnag to aggregate your custom span to provide you with summary statistics on its performance, then you need to set a bugsnag.span.first_class attribute on the span. BugSnag will then automatically create a grouping for that span based on its name. This will appear under the ‘Custom Spans’ tab of your Performance dashboard.

$span->setAttribute('bugsnag.span.first_class', true);