builtin:apis.detection-rules)
Modern applications use a lot of different frameworks, so stacktraces in method hotspots and exceptions can become quite long. APIs allow you to spot a component and the respective ownership that is responsible for a hotspot or degradation faster.
API detection rules look at a stacktrace frame and classify it based on classes (Java, .NET and PHP) or files (Node.js, PHP and GO) depending on the technology. The rules are executed in order and the first match decides the API. Marking APIs as third party will allow you to focus on non-third party APIs.
builtin:apis.detection-rules
group:service-monitoring
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:apis.detection-rules |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:apis.detection-rules | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:apis.detection-rules |
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.
apiName
apiColor
This color will be used to highlight APIs when viewing code level data, such as distributed traces or method hotspots.
technology
Restrict this rule to a specific technology.
Go
Nodejs
PHP
Java
dotNet
thirdPartyApi
apiRule
objectbase
FQCN
FILE_NAME
PACKAGE
matcher
BEGINS_WITH
CONTAINS
pattern