This action is an Endpoint Action that samples traces based on span attributes values.
endpoint_filters
can be configured within the same action.actionName
string
: Allows you to attach a meaningful name to the action for convenience.notes
string
: Allows you to attach notes regarding the action for convenience.disabled
boolean
: Allows you to temporarily disable the action, but keep it saved for future use.false
signals *
string[]
: An array with the signals that the processor will act on.TRACES
endpoints_filters *
object[]
: An array of objects representing the filters for the service and http route.minimum_latency_threshold *
string
: Specifies the minimum latency in milliseconds; traces with latency below this threshold are ignored.service_name *
string
: The rule applies to a specific service name. Only traces originating from this service’s root span will be considered.http_route *
string
: The specific HTTP route prefix to match for sampling. Only traces with routes beginning with this prefix will be considered. For instance, configuring /buy
will also match /buy/product
.fallback_sampling_ratio *
string
: Specifies the percentage of traces that meet the service/http_route filter but fall below the threshold that you still want to retain. For example, if a rule is set for service A and http_route B with a minimum latency threshold of 1 second, you might still want to keep some traces below this threshold. Setting the ratio to 20% ensures that 20% of these traces will be retained.minimum_latency_threshold
for a specified service
and http_route
will sample any request with a duration exceeding this threshold for that particular service
and http_route
combination.Otherwise, the trace will be dropped. It is recommended to still keep a portion of these traces using the fallback_sampling_ratio
setting. This allows you to retain a specified percentage of traces that fall below the threshold.frontend
service and /buy
http route. Additionally, it retains 20% of the traces that fall below the 1000ms threshold.