FAQ: Understanding Humio Log Error Levels
Last Updated: 2021-12-17
Humio generates a number of logs, with each event in the logs identified with a specific log-level. These log levels can help you to identify the severity of an issue:
General information about the system and execution.
This serves to provide us with snapshots of what is happening in Humio, and where the server may be during execution. Anything logged as info should always be the correct behaviour and not an error.
This level is a warning about behaviour that goes against intended use, but is not erroneous per se.
For instance, invalid input for a query function such as invalid arguments of arguments of the wrong type be highlighted as indicating a failure to execute correctly, but does indicate that the system has failed or that Humio itself has failed.
These events are more about loss of precision of the output, faulty user input, and so on.
This level should be reserved for internal errors.
This is the level on which Humio fails and execution cannot proceed. Humio may have got to a bad state is unable to continue or from which the server is nable to recover easily recover.
For an error, Humio has no choice but to stop execution and start over.