health-check
requests where the service name is wikipedia-service
and the environment starts with prod
.
Setting a rule matcher for Service Name and Environment is mandatory.
You can then choose to create extra conditions for your rules.
Possible matchers for the extra conditions are:/api/users/5ffc067eb3fe9c9520611f34
)https://my.domain.com/api/users?page=6&size=10
)GET
, POST
, etc.)PostmanRuntime/7.2
) HTTP Request Path equals "/user"
, and my flow starts with a request to an endpoint called /account
, which internally calls the /user
endpoint, the rule will not apply, even though the user endpoint was involved. wikipedia-service
and the environment equals prod
.http.status_code
is 4xx
format and their duration > 15 seconds.
You can then choose to create extra conditions for your rules.
Possible matchers for tail-based sampling are (in addition to the head-based sampling matchers):200
, 404
, 5xx
, etc.)userId
equals 12345
, etc.)Error is exist
, and I set also a head-based rule to collect 0% of the traces where HTTP Request Path equals "/health-check".
When call to "/health-check"
will fail and will contain error, the tail-based rule will not apply and the trace with the error will not be sampled because it already not sampled by the head-based rule in the beginning of the trace."HELLO" contains "he"
will match)samplingRate
option or 100% if none provided).