builtin:span-entry-points)
OpenTelemetry spans can start new PurePaths. Define rules that define which spans should not be considered as entry points.
Note: This config does not apply to Trace ingest.
builtin:span-entry-points
group:service-monitoring
group:service-monitoring.spans
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:span-entry-points |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:span-entry-points | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:span-entry-points |
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
SpanEntrypointRule
objectruleName
ruleAction
CREATE_ENTRYPOINT
DONT_CREATE_ENTRYPOINT
SpanMatcher
objectsource
SPAN_NAME
SPAN_KIND
ATTRIBUTE
INSTRUMENTATION_SCOPE_NAME
INSTRUMENTATION_SCOPE_VERSION
sourceKey
type
affects value
EQUALS
CONTAINS
STARTS_WITH
ENDS_WITH
DOES_NOT_EQUAL
DOES_NOT_CONTAIN
DOES_NOT_START_WITH
DOES_NOT_END_WITH
value
evaluated at span start
spanKindValue
INTERNAL
SERVER
CLIENT
PRODUCER
CONSUMER
caseSensitive
affects value and key