Shows the properties of the specified service detection rule for opaque and external web requests.
The request produces an application/json
payload.
GET | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/service/detectionRules/OPAQUE_AND_EXTERNAL_WEB_REQUEST/{id} |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/service/detectionRules/OPAQUE_AND_EXTERNAL_WEB_REQUEST/{id} |
To execute this request, you need an access token with ReadConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
The ID of the required service detection rule.
Refer to JSON models to find all JSON models that depend on the type of the model.
Failed. The rule with the specified ID doesn't exist.
OpaqueAndExternalWebRequestRule
objectThe service detection rule of the OPAQUE_AND_EXTERNAL_WEB_REQUEST
type.
The contribution to the service ID calculation from the detected application ID.
You have two mutually exclusive options:
A list of conditions of the rule.
If several conditions are specified, the AND logic applies.
The contribution to the service ID calculation from the detected context root.
The context root is the first segment of the request URL after server name. For example, in the www.dynatrace.com/support/help/dynatrace-api/
URL the context root is support
.
You have two options:
You can use one or both options. If you use both, the transformation applies to the modified URL.
A short description of the rule.
The rule is enabled(true
) or disabled (false
).
The ID of the service detection rule.
The management zone (specified by the ID) of the process group for which this service detection rule should be created.
You can specify only 1 management zone here.
The name of the rule.
The order of the rule in the rules list.
The rules are evaluated from top to bottom. The first matching rule applies.
The contribution to the service ID calculation from the port, where the web request has been detected.
The contribution to the service ID calculation from the domain name where the web request has been detected.
You have two mutually exclusive options:
The type of the service detection rule.
ApplicationId
objectThe contribution to the service ID calculation from the detected application ID.
You have two mutually exclusive options:
The value to be used instead of the detected value.
TransformationBase
objectConfiguration of transformation of the detected value.
If several transformations are specified, they are handled sequentially from top to bottom. Each transformation is applied to the result of the preceding transformation. For example, the second transformation is applied to the result of the first transformation.
The actual set of fields depends on the type of the transformation. Find the list of actual objects in the description of the type field or see Service detection API - JSON models.
Defines the actual set of fields depending on the value. See one of the following objects:
BEFORE
-> BeforeTransformationAFTER
-> AfterTransformationBETWEEN
-> BetweenTransformationREPLACE_BETWEEN
-> ReplaceBetweenTransformationREMOVE_NUMBERS
-> RemoveNumbersTransformationREMOVE_CREDIT_CARDS
-> RemoveCreditCardNumbersTransformationREMOVE_IBANS
-> RemoveIBANsTransformationREMOVE_IPS
-> RemoveIPsTransformationSPLIT_SELECT
-> SplitSelectTransformationTAKE_SEGMENTS
-> TakeSegmentsTransformationAFTER
BEFORE
BETWEEN
REMOVE_CREDIT_CARDS
REMOVE_IBANS
REMOVE_IPS
REMOVE_NUMBERS
REPLACE_BETWEEN
SPLIT_SELECT
TAKE_SEGMENTS
ConditionsOpaqueAndExternalWebRequestAttributeTypeDto
objectA condition of the service detection rule.
The type of the attribute to be checked.
IP
PG_TAG
TOP_LEVEL_DOMAIN
URL
URL_HOST_NAME
URL_PATH
URL_PORT
A list of conditions for the rule.
If several conditions are specified, the AND logic applies.
CompareOperation
objectThe condition of the rule.
The actual set of fields depends on the type of the condition. Find the list of actual objects in the description of the type field or see Service detection API - JSON models.
Defines the actual set of fields depending on the value. See one of the following objects:
EQUALS
-> EqualsCompareOperationSTRING_CONTAINS
-> StringContainsCompareOperationSTARTS_WITH
-> StartsWithCompareOperationENDS_WITH
-> EndsWithCompareOperationEXISTS
-> ExistsCompareOperationIP_IN_RANGE
-> IpInRangeCompareOperationLESS_THAN
-> LessThanCompareOperationGREATER_THAN
-> GreaterThanCompareOperationINT_EQUALS
-> IntEqualsCompareOperationSTRING_EQUALS
-> StringEqualsCompareOperationTAG
-> TagCompareOperationENDS_WITH
EQUALS
EXISTS
GREATER_THAN
INT_EQUALS
IP_IN_RANGE
LESS_THAN
STARTS_WITH
STRING_CONTAINS
STRING_EQUALS
TAG
ContextRoot
objectThe contribution to the service ID calculation from the detected context root.
The context root is the first segment of the request URL after server name. For example, in the www.dynatrace.com/support/help/dynatrace-api/
URL the context root is support
.
You have two options:
You can use one or both options. If you use both, the transformation applies to the modified URL.
The number of segments of the URL to be kept.
The URL is divided by slashes (/
), the indexing starts with 1 at context root.
For example, if you specify 2
for the www.dynatrace.com/support/help/dynatrace-api/
URL, the value of support/help
is used.
ContextRootTransformation
objectConfiguration of transformation of the detected value.
If several transformations are specified, they are handled sequentially from top to bottom. Each transformation is applied to the result of the preceding transformation. For example, the second transformation is applied to the result of the first transformation.
The actual set of fields depends on the type
of the transformation.
Defines the actual set of fields depending on the value. See one of the following objects:
BEFORE
-> BeforeTransformationREPLACE_BETWEEN
-> ReplaceBetweenTransformationREMOVE_NUMBERS
-> RemoveNumbersTransformationREMOVE_CREDIT_CARDS
-> RemoveCreditCardNumbersTransformationREMOVE_IBANS
-> RemoveIBANsTransformationREMOVE_IPS
-> RemoveIPsTransformationBEFORE
REMOVE_CREDIT_CARDS
REMOVE_IBANS
REMOVE_IPS
REMOVE_NUMBERS
REPLACE_BETWEEN
ConfigurationMetadata
objectMetadata useful for debugging
Dynatrace version.
A sorted list of the version numbers of the configuration.
A sorted list of version numbers of the configuration.
Port
objectThe contribution to the service ID calculation from the port, where the web request has been detected.
The port is used (false
) or isn't used (true
) in the service ID calculation.
PublicDomainName
objectThe contribution to the service ID calculation from the domain name where the web request has been detected.
You have two mutually exclusive options:
Use (true
) or don't use (false
) the detected host name as base for transformation.
Not applicable if the override is specified.
The value to be used instead of the detected value.
{"applicationId": {"valueOverride": "abc"},"conditions": [{"attributeType": "URL_HOST_NAME","compareOperations": [{"ignoreCase": "false","type": "STRING_CONTAINS","values": ["value1","value2"]}]}],"contextRoot": {"segmentsToCopyFromUrlPath": 2,"transformations": [{"delimiter": "/","type": "BEFORE"}]},"description": "REST API example","enabled": true,"managementZones": ["zone1"],"name": "My sample rule","port": {"doNotUseForServiceId": "true"},"publicDomainName": {"copyFromHostName": "true","transformations": [{"delimiter": "/","type": "BEFORE"}]},"type": "OPAQUE_AND_EXTERNAL_WEB_REQUEST"}