Utilize configuration options to adapt the Elastic APM agent to your needs. One way to configure settings is with the php.ini file:

elastic_apm.service_name="My service"

The agent can also be configured using environment variables:

export ELASTIC_APM_SERVER_URL="http://localhost:8200"
export ELASTIC_APM_SERVICE_NAME="My service"

If you use environment variables to configure the agent, make sure the process running your PHP code inherits those environment variables after they were set.

Elasticsearch Service on Elastic Cloudedit

The agent can be configured to send data to an Elasticsearch Service APM instance by setting the server_url and secret_token options to the corresponding values found in the APM & Fleet section of Elastic Cloud.

Configure the agent, for example via php.ini:



The easiest way to configure the logging is by using the log_level_syslog configuration option.

Available log levels are:


For example, if you specify a WARNING log level, only log records with levels WARNING, ERROR, and CRITICAL will be emitted.

OFF is only used to disable agent logging.

The agent supports logging to the following sinks: syslog and stderr. Control the level of logging for individual sinks with the log_level_syslog and log_level_stderr options. When a sink-specific logging level is not explicitly set, the fallback setting log_level will be used.

For example, the following configuration sets the log level to WARNING for all the sinks:


Alternatively, the following configuration sets log level to WARNING for all the sinks except for syslog, where the log level is set to TRACE.



Some options (for example url_groups) support use of wildcard. A valid value for such configuration options is a comma separated list of wildcard expressions. Only the wildcard *, which matches zero or more characters, is supported.

Examples: *foo*, /foo/*/bar, /*/baz*.

Matching is case insensitive by default. Prepending an element with (?-i) makes the matching case sensitive. For example (?-i)/bar, /foo matches /bar` and /FOO but it doesn't match `/BAR on the other hand (?-i)/bar, (?-i)/foo matches /bar and /foo but doesn’t match neither /BAR nor /FOO.

Whitespace around commas separating wildcard expressions in the list is ignored. For example foo , bar is the same as foo,bar. On the other hand whitespace inside wildcard expressions is significant. For example *a b* matches a string only if it contains a followed by space and then b.

The input string is matched against wildcard expressions in the order they are listed and the first expression that matches is selected.

When configuration option is intended to matched against a input URL (for example url_groups and transaction_ignore_urls) only path part of the URL is tested against wildcard expressions. Other parts of the URL (such as query string, etc.) are not taken into account so including them in the wildcard expressions might lead to unexpected result. For example /user/* matches while /user/*?lang=* does not match