diff --git a/docs/platforms/php/common/configuration/options.mdx b/docs/platforms/php/common/configuration/options.mdx index f84f90cdf367d..0b4425b1072be 100644 --- a/docs/platforms/php/common/configuration/options.mdx +++ b/docs/platforms/php/common/configuration/options.mdx @@ -22,7 +22,7 @@ Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-uti - + If enabled, the SDK prints out debug information about if something went wrong while sending events. It isn't recommended to use this in production. @@ -111,7 +111,7 @@ For example, if your code is deployed in different locations across environments - + This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values: @@ -133,7 +133,7 @@ The number of characters after which the values containing text in the event pay - + This function is called with a breadcrumb object before the breadcrumb is added to the scope. When nothing is returned from the function, the breadcrumb is dropped. To pass the breadcrumb through, return the breadcrumb itself. @@ -147,7 +147,7 @@ Configures the sample rate for error events, in the range of `0.0` to `1.0`. The - + This function is called with an event object, and can return a modified event object, or `null` to skip reporting the event. This can be used, for instance, for manual PII stripping before sending. @@ -187,7 +187,7 @@ Either this or `traces_sampler` must be defined to enable tracing. - + A function responsible for determining the percentage chance a given transaction will be sent to Sentry. It will automatically be passed information about the transaction and the context in which it's being created, and must return a number between `0` (0% chance of being sent) and `1` (100% chance of being sent). Can also be used for filtering transactions, by returning `0` for those that are unwanted. @@ -201,7 +201,7 @@ A list of strings that match transaction names that shouldn't be sent to Sentry. - + This function is called with a transaction event object, and can return a modified transaction event object, or `null` to skip reporting the event. One way this might be used is for manual PII stripping before sending. @@ -221,7 +221,7 @@ To disable sending trace data to any downstream service, set this option to an e ## Cron Monitoring Options - + This function is called with a check-in event object, and can return a modified check-in event object, or `null` to skip reporting the event. @@ -259,13 +259,13 @@ This function is called with a metric object, and can return a modified metric o Transports are used to send events to Sentry. Transports can be customized to some degree to better support highly specific deployments. - + Switches out the transport used to send events. It can, for instance, be used to capture events for unit testing. - + Switches out the HTTP client used by the SDKs transport.