Service detection API - JSON models
JSON models of the Service detection rules API vary greatly, depending on the type of some objects. Here you can find JSON models for each variation.
Variations of the ServiceDetectionRule object
The ServiceDetectionRule object is the base for all service detection rules. The actual set of fields depends on the type of the rule.
FULL_WEB_REQUEST
The FullWebRequestRule object
The service detection rule of the FULL_WEB_REQUEST type.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | The type of the service detection rule. | required |
| metadata | Configuration | Metadata useful for debugging | optional |
| managementZones | string[] | 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. | optional |
| id | string | The ID of the service detection rule. | optional |
| order | string | The order of the rule in the rules list. The rules are evaluated from top to bottom. The first matching rule applies. | optional |
| name | string | The name of the rule. | required |
| description | string | A short description of the rule. | optional |
| enabled | boolean | The rule is enabled( | required |
| conditions | Conditions | A list of conditions of the rule. If several conditions are specified, the AND logic applies. | optional |
| applicationId | Application | The contribution to the service ID calculation from the detected application ID. You have two mutually exclusive options:
| optional |
| contextRoot | Context | 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 You have two options:
You can use one or both options. If you use both, the transformation applies to the modified URL. | optional |
| serverName | Server | The contribution to the service ID calculation from the detected server name. You have two mutually exclusive options:
| optional |
The ConfigurationMetadata object
Metadata useful for debugging
| Element | Type | Description | Required |
|---|---|---|---|
| currentConfigurationVersions | string[] | A sorted list of version numbers of the configuration. | optional |
| clusterVersion | string | Dynatrace version. | optional |
| configurationVersions | integer[] | A sorted list of the version numbers of the configuration. | optional |
The ConditionsFullWebRequestAttributeTypeDto object
A condition of the service detection rule.
| Element | Type | Description | Required |
|---|---|---|---|
| attributeType | string | The type of the attribute to be checked. The element can hold these values
| required |
| compareOperations | Compare | A list of conditions for the rule. If several conditions are specified, the AND logic applies. | optional |
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ApplicationId object
The contribution to the service ID calculation from the detected application ID.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ContextRoot object
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:
- Keep a part of the detected URL. Specify the number of segments to be kept in the segmentsToCopyFromUrlPath field.
- Dynamically transform the detected URL. Specify the transformation parameters in the transformations field.
You can use one or both options. If you use both, the transformation applies to the modified URL.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Context | Transformations to be applied to the detected value. | optional |
| segmentsToCopyFromUrlPath | integer | The number of segments of the URL to be kept. The URL is divided by slashes ( For example, if you specify | optional |
The ContextRootTransformation object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ServerName object
The contribution to the service ID calculation from the detected server name.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
json{
"type": "FULL_WEB_REQUEST",
"id": "f69d6702-9b6e-4c47-b94c-628acc391995",
"order": "1",
"name": "string",
"description": "string",
"enabled": true,
"conditions": [
{
"attributeType": "URL_PATH",
"compareOperations": [
{
"type": "STRING_CONTAINS",
"negate": false,
"ignoreCase": true,
"values": [
"string"
]
}
]
}
],
"applicationId": {
"transformations": [],
"valueOverride": "string"
},
"contextRoot": {
"transformations": [
{
"type": "AFTER",
"delimiter": "string"
}
],
"segmentsToCopyFromUrlPath": 2
},
"serverName": {
"transformations": [
{
"type": "BEFORE",
"delimiter": "string"
}
]
}
}OPAQUE_AND_EXTERNAL_WEB_REQUEST
The OpaqueAndExternalWebRequestRule object
The service detection rule of the OPAQUE_AND_EXTERNAL_WEB_REQUEST type.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | The type of the service detection rule. | required |
| metadata | Configuration | Metadata useful for debugging | optional |
| managementZones | string[] | 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. | optional |
| id | string | The ID of the service detection rule. | optional |
| order | string | The order of the rule in the rules list. The rules are evaluated from top to bottom. The first matching rule applies. | optional |
| name | string | The name of the rule. | required |
| description | string | A short description of the rule. | optional |
| enabled | boolean | The rule is enabled( | required |
| conditions | Conditions | A list of conditions of the rule. If several conditions are specified, the AND logic applies. | optional |
| applicationId | Application | The contribution to the service ID calculation from the detected application ID. You have two mutually exclusive options:
| optional |
| contextRoot | Context | 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 You have two options:
You can use one or both options. If you use both, the transformation applies to the modified URL. | optional |
| port | Port | The contribution to the service ID calculation from the port, where the web request has been detected. | optional |
| publicDomainName | Public | The contribution to the service ID calculation from the domain name where the web request has been detected. You have two mutually exclusive options:
| optional |
The ConfigurationMetadata object
Metadata useful for debugging
| Element | Type | Description | Required |
|---|---|---|---|
| currentConfigurationVersions | string[] | A sorted list of version numbers of the configuration. | optional |
| clusterVersion | string | Dynatrace version. | optional |
| configurationVersions | integer[] | A sorted list of the version numbers of the configuration. | optional |
The ConditionsOpaqueAndExternalWebRequestAttributeTypeDto object
A condition of the service detection rule.
| Element | Type | Description | Required |
|---|---|---|---|
| attributeType | string | The type of the attribute to be checked. The element can hold these values
| required |
| compareOperations | Compare | A list of conditions for the rule. If several conditions are specified, the AND logic applies. | optional |
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ApplicationId object
The contribution to the service ID calculation from the detected application ID.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ContextRoot object
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:
- Keep a part of the detected URL. Specify the number of segments to be kept in the segmentsToCopyFromUrlPath field.
- Dynamically transform the detected URL. Specify the transformation parameters in the transformations field.
You can use one or both options. If you use both, the transformation applies to the modified URL.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Context | Transformations to be applied to the detected value. | optional |
| segmentsToCopyFromUrlPath | integer | The number of segments of the URL to be kept. The URL is divided by slashes ( For example, if you specify | optional |
The ContextRootTransformation object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The Port object
The contribution to the service ID calculation from the port, where the web request has been detected.
| Element | Type | Description | Required |
|---|---|---|---|
| doNotUseForServiceId | boolean | The port is used ( | optional |
The PublicDomainName object
The contribution to the service ID calculation from the domain name where the web request has been detected.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
| copyFromHostName | boolean | Use ( Not applicable if the override is specified. | optional |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
json{
"type": "OPAQUE_AND_EXTERNAL_WEB_REQUEST",
"id": "9c22d0b1-e731-4baf-b3d0-140d14ead3c5",
"order": "2",
"name": "string",
"description": "string",
"enabled": true,
"conditions": [
{
"attributeType": "TOP_LEVEL_DOMAIN",
"compareOperations": [
{
"type": "ENDS_WITH",
"negate": false,
"ignoreCase": true,
"values": [
"string"
]
}
]
}
],
"applicationId": null,
"contextRoot": {
"transformations": [],
"segmentsToCopyFromUrlPath": 1
},
"port": null,
"publicDomainName": null
}FULL_WEB_SERVICE
The FullWebServiceRule object
The service detection rule of the FULL_WEB_SERVICE type.
If you have a condition with the attributeType set to FRAMEWORK, the values field from compareOperations is limited to the following possible values:
AXISCXFHESSIANJAX_WS_RIJBOSSJERSEYPROGRESSRESTEASYRESTLETSPRINGTIBCOWEBLOGICWEBMETHODSWEBSPHEREWINK
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | The type of the service detection rule. | required |
| metadata | Configuration | Metadata useful for debugging | optional |
| managementZones | string[] | 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. | optional |
| id | string | The ID of the service detection rule. | optional |
| order | string | The order of the rule in the rules list. The rules are evaluated from top to bottom. The first matching rule applies. | optional |
| name | string | The name of the rule. | required |
| description | string | A short description of the rule. | optional |
| enabled | boolean | The rule is enabled( | required |
| conditions | Conditions | A list of conditions of the rule. If several conditions are specified, the AND logic applies. | optional |
| detectAsWebRequestService | boolean | Detect the matching requests as full web services ( Setting this field to Default is | optional |
| webServiceName | Web | The contribution to the service ID calculation from the detected web service name. You have two mutually exclusive options:
| optional |
| webServiceNameSpace | Web | The contribution to the service ID calculation from the detected web service name space. You have two mutually exclusive options:
| optional |
| applicationId | Application | The contribution to the service ID calculation from the detected application ID. You have two mutually exclusive options:
| optional |
| contextRoot | Context | 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 You have two options:
You can use one or both options. If you use both, the transformation applies to the modified URL. | optional |
| serverName | Server | The contribution to the service ID calculation from the detected server name. You have two mutually exclusive options:
| optional |
The ConfigurationMetadata object
Metadata useful for debugging
| Element | Type | Description | Required |
|---|---|---|---|
| currentConfigurationVersions | string[] | A sorted list of version numbers of the configuration. | optional |
| clusterVersion | string | Dynatrace version. | optional |
| configurationVersions | integer[] | A sorted list of the version numbers of the configuration. | optional |
The ConditionsFullWebServiceAttributeTypeDto object
A condition of the service detection rule.
| Element | Type | Description | Required |
|---|---|---|---|
| attributeType | string | The type of the attribute to be checked. The element can hold these values
| required |
| compareOperations | Compare | A list of conditions for the rule. If several conditions are specified, the AND logic applies. | optional |
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The WebServiceName object
The contribution to the service ID calculation from the detected web service name.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The WebServiceNameSpace object
The contribution to the service ID calculation from the detected web service name space.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
The ApplicationId object
The contribution to the service ID calculation from the detected application ID.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
The ContextRoot object
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:
- Keep a part of the detected URL. Specify the number of segments to be kept in the segmentsToCopyFromUrlPath field.
- Dynamically transform the detected URL. Specify the transformation parameters in the transformations field.
You can use one or both options. If you use both, the transformation applies to the modified URL.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Context | Transformations to be applied to the detected value. | optional |
| segmentsToCopyFromUrlPath | integer | The number of segments of the URL to be kept. The URL is divided by slashes ( For example, if you specify | optional |
The ContextRootTransformation object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
The ServerName object
The contribution to the service ID calculation from the detected server name.
You have two mutually exclusive options:
- Override the detected value with a specified static value. Specify the new value in the valueOverride field.
- Dynamically transform the detected value. Specify the transformation parameters in the transformations field.
| Element | Type | Description | Required |
|---|---|---|---|
| transformations | Transformation | Transformations to be applied to the detected value. | optional |
| valueOverride | string | The value to be used instead of the detected value. | optional |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
json{
"type": "FULL_WEB_SERVICE",
"id": "string",
"order": "1",
"name": "string",
"description": "string",
"enabled": true,
"conditions": [
{
"attributeType": "URL_PATH",
"compareOperations": [
{
"type": "STRING_CONTAINS",
"negate": false,
"ignoreCase": true,
"values": [
"string"
]
}
]
}
],
"detectWebRequestOnly": false,
"webServiceName" : {
"valueOverride": "string",
"transformations": []
},
"webServiceNameSpace": {
"valueOverride": "string",
"transformations": []
},
"applicationId": {
"transformations": [],
"valueOverride": "string"
},
"contextRoot": {
"transformations": [
{
"type": "AFTER",
"delimiter": "string"
}
],
"segmentsToCopyFromUrlPath": 2
},
"serverName": {
"transformations": [
{
"type": "BEFORE",
"delimiter": "string"
}
]
}
}Variations of the CompareOperation object
The CompareOperation object is the base for all comparison operations. The actual set of fields depends on the type of the comparison.
STRING_CONTAINS
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "STRING_CONTAINS",
"negate": false,
"ignoreCase": true,
"values": [
"compareValue1",
"compareValue2"
]
}STRING_EQUALS
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "STRING_EQUALS",
"negate": false,
"ignoreCase": true,
"values": [
"compareValue1",
"compareValue2"
]
}STARTS_WITH
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "STARTS_WITH",
"negate": false,
"ignoreCase": true,
"values": [
"compareValue1",
"compareValue2"
]
}ENDS_WITH
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "ENDS_WITH",
"negate": false,
"ignoreCase": true,
"values": [
"compareValue1",
"compareValue2"
]
}EXISTS
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "EXISTS",
"negate": false
}IP_IN_RANGE
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "IP_IN_RANGE",
"negate": false,
"lower": "192.168.0.1",
"upper": "192.168.0.10"
}INT_EQUALS
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "INT_EQUALS",
"negate": false,
"values": [
128,
258,
512
]
}LESS_THAN
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "LESS_THAN",
"value": 512
}GREATER_THAN
The CompareOperation object
The 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "GREATER_THAN",
"value": 256
}Variations of the TransformationBase object
The TransformationBase object is the base for all transformation operations. The actual set of fields depends on the type of the transformation.
BEFORE
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "BEFORE",
"delimiter": "/"
}AFTER
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "AFTER",
"delimiter": "/"
}BETWEEN
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "BETWEEN",
"after": "support",
"before": "/"
}REPLACE_BETWEEN
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "REPLACE_BETWEEN",
"after": "support",
"before": "/",
"replacement": "newValue"
}REMOVE_NUMBERS
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "REMOVE_NUMBERS",
"minDigitCount": 2,
"includeHexNumbers": true
}REMOVE_CREDIT_CARDS
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "REMOVE_CREDIT_CARDS"
}REMOVE_IBANS
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "REMOVE_IBANS"
}REMOVE_IPS
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "REMOVE_IPS"
}SPLIT_SELECT
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "SPLIT_SELECT",
"delimiter": "/",
"itemIndex": 2
}TAKE_SEGMENTS
The TransformationBase object
Configuration 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.
| Element | Type | Description | Required |
|---|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
The element can hold these values
| required |
json{
"type": "TAKE_SEGMENTS",
"delimiter": "/",
"takeFromEnd": false
}