Conditional naming API - GET a naming rule
Gets parameters of the specified conditional naming rule.
The request produces an application/json payload.
| GET |
|
Authentication
To execute this request, you need the Read configuration (ReadConfig) permission assigned to your API token. To learn how to obtain and use it, see Tokens and authentication.
Parameters
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| type | string |
The type of the rule, defined by the type of Dynatrace entities to which the rule applies. |
path | required |
| id | string |
The ID of the required naming rule. |
path | required |
Response
Refer to JSON models to find all JSON models that depend on the type of the model.
Response codes
| Code | Description |
|---|---|
| 200 | Success |
Response body
The ConditionalNamingRule object
The rule for the conditional naming.
| Element | Type | Description |
|---|---|---|
| metadata |
Configuration |
|
| id | string | The ID of the naming rule. |
| type | string | The type of Dynatrace entities to which the rule applies. |
| nameFormat | string | The name to be assigned to matching entities. You can use the following placeholders here:
|
| displayName | string | The name of the rule |
| enabled | boolean | The rule is enabled ( |
| rules |
Entity |
A list of matching conditions of the rule. The rule applies only if all conditions are fulfilled. |
The EntityRuleEngineCondition object
A condition defines how to execute matching logic for an entity.
| Element | Type | Description |
|---|---|---|
| key | ConditionKey | |
| comparisonInfo | ComparisonBasic |
The ComparisonBasic object
Defines how the matching is actually performed: what and how are we comparing.
The actual set of fields and possible values of the operator field depend on the type of the comparison. \n\nFind the list of actual models in the description of the type field and check the description of the model you need.
| Element | Type | Description |
|---|---|---|
| operator | string | Operator of the comparison. You can reverse it by setting negate to Possible values depend on the type of the comparison. Find the list of actual models in the description of the type field and check the description of the model you need. |
| value | object | The value to compare to. |
| negate | boolean | Reverses the comparison operator. For example it turns the begins with into does not begin with. |
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
|
The ConditionKey object
The key to identify the data we're matching.
The actual set of fields and possible values vary, depending on the type of the key.
Find the list of actual objects in the description of the type field.
| Element | Type | Description |
|---|---|---|
| attribute | string | The attribute to be used for comparision. |
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
|
The ConfigurationMetadata object
Metadata useful for debugging
| Element | Type | Description |
|---|---|---|
| configurationVersions | integer[] | A Sorted list of the version numbers of the configuration. |
| currentConfigurationVersions | string[] | A Sorted list of string version numbers of the configuration. |
| clusterVersion | string | Dynatrace server version. |
{
"id": "4e88530c-edec-4e31-9cb4-3f2c63abc2b7",
"type": "PROCESS_GROUP",
"nameFormat": "TestNameFormat",
"displayName": "TestRule",
"enabled": true,
"rules": [
{
"key": {
"attribute": "PROCESS_GROUP_TECHNOLOGY"
},
"comparisonInfo": {
"type": "SIMPLE_TECH",
"operator": "EQUALS",
"value": {
"type": "JAVA"
},
"negate": "false"
}
},
{
"key": {
"attribute": "PROCESS_GROUP_PREDEFINED_METADATA",
"dynamicKey": "EXE_NAME",
"type": "PROCESS_PREDEFINED_METADATA_KEY"
},
"comparisonInfo": {
"type": "STRING",
"operator": "CONTAINS",
"value": "test",
"negate": "false",
"caseSensitive": true
}
}
]
}