builtin:service-detection.external-web-service)Rules are evaluated from top to bottom, and the first matching rule applies. Rule conditions are evaluated before Service Id Contributors are applied. Note that conditions do not modify attributes of requests. If conditions match, then Service Id Contributors are applied. All of the Contributors are always applied. But it is possible to influence the creation of Services by choosing how they get transformed.
More extensive information on Service detection rules can be found here.
builtin:service-detection.external-web-servicegroup:service-detectionenvironment| GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:service-detection.external-web-service |
| SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:service-detection.external-web-service | |
| Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:service-detection.external-web-service |
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.
enablednamedescriptionmanagementZonesDefine a management zone of the process group for which this service detection rule should be created. Note: in case of external requests/services the PG might not always be known. See here
idContributorsContributors to the Service Identifier calculation. URL path is always applied as an Id Contributor. You can exclude the port contribution by disabling the switch.
conditionsA list of conditions necessary for the rule to take effect. If multiple conditions are specified, they must all match a Request for the rule to apply. If there is no condition at all, the rule is always applied. Conditions are evaluated against attributes, but do not modify them.
idContributorsType objectdetectAsWebRequestServiceDetect the matching requests as web request services instead of web services.
This prevents detecting of matching requests as opaque web services. An opaque web request service is created instead. If you need to further modify the resulting web request service, you need to create a separate Opaque/external web request rule (<your-dynatrace-url>/builtin:service-detection.full-web-request).
portForServiceIdLet the port contribute to the Service Id
condition objectattributecompareOperationTypetextValuesIf multiple values are specified, at least one of them must match for the condition to match
tagValuesIf multiple values are specified, at least one of them must match for the condition to match
intValueintValuesipRangeFromipRangeToframeworkAXISCXFHESSIANJAX_WS_RIJBOSSJERSEYPROGRESSRESTEASYRESTLETSPRINGTIBCOWEBLOGICWEBMETHODSWEBSPHEREWINKignoreCaseIgnore case sensitivity for texts.
serviceIdContributor objectenableIdContributortransformationSet objectcontributionTypeDefines whether the original value should be used or if a transformation set should be used to override a value or transform it.
OriginalValueOverrideValueTransformValuetransformationsChoose how to transform a value before it contributes to the Service Id. Note that all of the Transformations are always applied. Transformations are applied in the order they are specified, and the output of the previous transformation is the input for the next one. The resulting value contributes to the Service Id and can be found on the Service overview page under Properties and tags.
valueOverride objectvaluetransformation objecttransformationTypeDefines what kind of transformation will be applied on the original value.
BEFOREAFTERBETWEENREPLACE_BETWEENREMOVE_NUMBERSREMOVE_CREDIT_CARDSREMOVE_IBANSREMOVE_IPSSPLIT_SELECTTAKE_SEGMENTSprefixsuffixreplacementValuesplitDelimiterselectIndexminDigitCountincludeHexNumberssegmentCountHow many segments should be taken.
takeFromEnd