Verifies if the given DQL processor is valid.
The request produces an application/json payload.
| POST | SaaS | https://{your-environment-id}.apps.dynatrace.com/platform/openpipeline/v1/dqlProcessor/verify |
You can execute this request also with an OAuth2 client with openpipeline:configurations:read permission.
To learn how to obtain and use it, see OAuth clients.
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| body | D | Single DQL processor script to verify. | body | required |
DQLProcessorVerifyRequest object| Element | Type | Description | Required |
|---|---|---|---|
| configurationId | string | Identifier of the configuration. | optional |
| protectedFields | string[] | List of protected fields | optional |
| script | string | The unverified DQL script. | optional |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"script": "parse content, \"IPV4:ip LD HTTPDATE:time ']' LD:text\""}
| Code | Type | Description |
|---|---|---|
| 200 | Verify | Returns the verification result of the DQL processor script. |
| 4XX | Error | Client-side error. |
| 5XX | Error | Server-side error. |
VerifyResponse objectVerify response.
| Element | Type | Description |
|---|---|---|
| notifications | Metadata | The notifications related to the supplied input string. |
| valid | boolean | True if the supplied input string is valid. |
MetadataNotification objectThe message that provides additional information about the execution of the input string.
| Element | Type | Description |
|---|---|---|
| arguments | string[] | The arguments for the message format. |
| message | string | The complete message of the notification. |
| messageFormat | string | The message format of the notification, string.format based |
| messageFormatSpecifierTypes | string[] | The corresponding types for each format specifier used in the error message format. |
| notificationType | string | The notification type. |
| severity | string | The severity of the notification, currently: INFO, WARN, ERROR. |
| syntaxPosition | Token | The position of a token in the input string used for errors and notification to map the message to a specific part of the input. |
TokenPosition objectThe position of a token in the input string used for errors and notification to map the message to a specific part of the input.
| Element | Type | Description |
|---|---|---|
| end | Position | The exact position in the query string. |
| start | Position | The exact position in the query string. |
PositionInfo objectThe exact position in the query string.
| Element | Type | Description |
|---|---|---|
| column | integer | Input string position column zero based index. |
| index | integer | Input string position index. |
| line | integer | Input string position line zero based index. |
{"valid": false,"notifications": [{"severity": "ERROR","syntaxPosition": {"start": {"column": 1,"index": 0,"line": 1},"end": {"column": 6,"index": 5,"line": 1}},"message": "There's been an error during parsing: There's no command `parsee`."}]}
ErrorResponseEnvelope objectEncloses the encountered error.
| Element | Type | Description |
|---|---|---|
| error | Error | Basic information of the encountered error. |
ErrorResponse objectBasic information of the encountered error.
| Element | Type | Description |
|---|---|---|
| code | integer | The returned HTTP status code. |
| details | Error | Detailed information of the error. |
| message | string | Description of the encountered error. |
ErrorResponseDetails objectDetailed information of the error.
| Element | Type | Description |
|---|---|---|
| type | string | Defines the actual set of fields depending on the value. See one of the following objects:
|
ConstraintViolationDetails objectList of encountered constraint violations.
| Element | Type | Description |
|---|---|---|
| constraintViolations | Constraint | List of encountered constraint violations. |
ConstraintViolation objectInformation about a single constraint violation.
| Element | Type | Description |
|---|---|---|
| context | object | Structured context of the constraint violation. Well known keys that can be present are:
|
| message | string | Description of the constraint violation. |