Error monitoring
[ Code errors ] [ Explanation for specific error codes ]
These tables return system errors and help you analyze different incidences and issues.
devo.internal.log.error
This table collects error messages from different background processes related to Devo components such as alerts, flows, data ingestion, etc. This table presents the following fields:
Field | Data type | Description |
---|---|---|
type |
| Error type. Currently, the only type shown is |
component |
| Devo component that is sending the error log. The components currently registering errors in this table are:
|
resource_id |
| ID of the resource that is failing. |
severity |
| Severity level of the incident. It can be one of the following:
|
error_code |
| Code of the error. The error code is always composed by a letter that indicates the Devo component plus a number that indicates the issue, following the rules specified in the section below. |
message |
| Definition of the incident. |
Code errors
Error codes displayed in this table are always composed of a letter and a number, as in the examples below:
I-201
Q-1103001
Letter
The letter indicates the Devo component that is affected. For example:
Q
stands for query.I
stands for data ingestion.
Number
The number indicates the error type. This number may be composed either of 3 or 7 digits.
Digit 1: Recoverability
Indicates the severity of the issue and informs whether it can be fixed or not.
Digit 1 | Recoverable | Description |
---|---|---|
| NO | The error cannot be fixed. |
| MANUAL | The error requires manual action over another part of the system. |
| MAYBE | The error can be fixed in a medium-long amount of time. |
| YES | The error can be fixed immediately. |
Digit 2-3: Kind
Kind of exception retrieved.
Digits 2-3 | Kind | Description |
---|---|---|
| UNKNOWN | General error. |
| CONNECTION_ERROR | Connection error. It may be a transient issue. |
| EXTERNAL_ERROR | An error related to external factors, such as client’s code. |
| SYSTEM_RESOURCE | An error related to a system-wide resource, such as RAM or file handlers. |
| SECURITY_ERROR | An error related to a resource that requires additional security checks, such as signed queries. |
| QUERY_CANCELLED | Query cancelled by an external entity. |
| CONFIG_PARSING_ERROR | Format error on reading input resources, such as files, fields, decoding… |
| INTERNAL_ERROR | Internal error. This is not a transient issue, and can be induced by a non-deterministic event. |
| MISSING_RESOURCE | A resource required to execute the query is missing. |
| QUERY_LIMIT | Query limit reached (for example, maximum result rows, time, RAM…) |
| QUERY_PARSING_ERROR | Syntax error in the query, probably a missing or misspelled token. Includes errors found in static analysis performed after parsing (refinement order, unknown operations, operations with unexpected arguments…) |
| UNSUPPORTED_FEATURE | Unsupported or not implemented feature. |
Digit 4-7: Specific error
The last 4 digits of the code are used to specify the detailed error of the exception. This detailed description is associated to the error type indicated by digits 2-3 explained above.
Digits 4-7 | Description |
---|---|
00 General error | |
| Unknown error. |
01 Connection error | |
| Affinity rules have changed during query execution and the query can no longer be processed. |
03 System resource error | |
| Required registry for a computation process is missing. |
| Provided registry is not suitable for the required operation. |
| Memory shortage. |
04 Security error | |
| Authentication failed. |
| Cannot change authentication for active cluster. |
06 Config parsing error | |
| Query is trying to access a file but cannot decode it. |
07 Internal error | |
| Unknown internal error. |
| A listed file cannot be found in the directory, usually because it has been compressed simultaneously. |
| Stall event received while executing a subquery. |
| Error while caching data. |
| Error while updating cached data. |
| Error while deleting cached data segments. |
| Error while deleting cached data entries. |
| Array index out of bounds. |
08 Missing resource | |
| Missing aggregated resource to execute the query (for example, an aggregation task). |
| Recursive definition for a union table. |
| Missing files for Geolocation operations that use MaxMind. |
| Missing files for Public suffix operations. |
| Missing files for User agent operations. |
| Unknown table. |
09 Query limits | |
| Maximum number of elements surpassed for the selected operation. |
| Stack overflow while processing the query. |
| Error limit reached. The query has failed n consecutive times and is quarantined for the following n minutes. |
10 Query parsing error | |
| No language provided when parsing a query. |
| Unknown query language. |
| No code provided. This error relates to any kind of language, including expressions and Ty Terms. |
| Query starting time no found. |
| Query ending time no found. |
| Cannot parse query. |
| Illegal time-based grouping clause. |
| Time-based group found over a non-time-based table or group. |
| Inferred time constraint spans to the future. |
| Reference to an identifier (table field or as-defined) that is not known or available at that stage. |
| Unknown operation or known operation expecting arguments with other properties (type, constancy...) |
| An identifier has been used more than once. |
| An expression with boolean type or a type that can by automatically converted to boolean was expected. |
| The operation expects some arguments to be constant, but a non-constant expression was given. |
| Invalid filter added to an operation. |
| The operation cannot be used with one or several of the given arguments. |
| The operation cannot be used with one or several of the given data types. |
| The operation cannot be used with the given arguments. |
| The operation cannot be called at stage 1. |
| Given argument for the selected operation is ambiguous. |
| Grouping over a key correctly typed but with no computable tyre PR. |
| Grouping over a key correctly typed but with no computable memory usage information. |
| Grouping computing a correctly typed aggregation but with no computable tyre PR. |
| Grouping computing a properly typed aggregation but with no computable memory usage information. |
| Inferred type does not match the explicit type given with the operation. |
Explanation for specific error codes
Code | Recoverable (digit 1) | Kind (digit 2-3) | SpecificError (digits 4-7) | Detail |
---|---|---|---|---|
| NO | OTHER | UNKNOWN | Unknown internal error. |
| NO | SYSTEM_RESOURCE | UNAVAILABLE_REGISTRY | Required registry for a computation process is missing. |
| NO | SYSTEM_RESOURCE | UNSUITABLE_REGISTRY | Provided registry is not suitable for the required operation. |
| NO | QUERY_LIMIT | MAXIMUM_NUMBER_SURPASSED | Maximum number of elements surpassed for the selected operation. |
| NO | QUERY_PARSING_ERROR | CANNOT_PARSE_QUERY | Invalid filter added to an operation. Check your query carefully. Usually, this happens when the query is not syntactically correct (like missing a select statement) |
| NO | QUERY_PARSING_ERROR | UNKNOWN_ID | Reference to an identifier (table field or as-defined) that is not known or available at that stage. If this is happening in a my.synthesis table, check the availability of the underlying tables |
| NO | QUERY_PARSING_ERROR | BOOLEAN_EXPECTED | An expression with boolean type or a type that can by automatically converted to boolean was expected. |
| NO | QUERY_PARSING_ERROR | CONSTANT_ARGUMENT_EXPECTED | The operation expects some arguments to be constant, but a non-constant expression was given. |
| MANUAL | CONNECTION_ERROR | AFFINITY_RULES_CHANGED | Affinity rules have changed during query execution and the query can no longer be processed. |
| MANUAL | SECURITY_ERROR | AUTH_FAILED | Authentication failed. |
| MANUAL | SECURITY_ERROR | CANNOT_CHANGE_AUTH_FOR_ACTIVE_CLUSTER | Cannot change authentication for active cluster. |
| MANUAL | CONFIG_PARSING_ERROR | INVALID_SEGMENT_FILE | Invalid cached data. |
| MANUAL | INTERNAL_ERROR | CANNOT_DELETE_ENTRY | Error while deleting cached data. |
| MANUAL | MISSING_RESOURCE | MISSING_PREAGGREGATED_DATA | Missing aggregated resource to execute the query (for example, an aggregation task). |
| MANUAL | MISSING_RESOURCE | RECURSIVE_UNION_TABLE | Recursive definition for a union table. |
| MANUAL | MISSING_RESOURCE | MISSING_MAXMIND_FILES | Missing files for Geolocation operations that use MaxMind |
| MANUAL | MISSING_RESOURCE | MISSING_PUBLICSUFFIX_FILES | Missing files for Public suffix operations. |
| MANUAL | MISSING_RESOURCE | MISSING_USERAGENT_FILES | Missing files for User agent operations. |
| MANUAL | MISSING_RESOURCE | UNKNOWN_TABLE | Unknown table. |
| MAYBE | SYSTEM_RESOURCE | MEMORY_SHORTAGE | Insufficient memory to continue the execution of the query. |
| YES | CONNECTION_ERROR | NO_CANDIDATE_SUITABLE | Affinity rules have changed during query execution and the query can no longer be processed. |
| YES | INTERNAL_ERROR | LOGFILE_LISTED_BUT_NOT_FOUND | A listed file cannot be found in the directory, usually because it has been compressed simultaneously. |