Enum ELogSeverity

• Defined in File log.idl

Enum Documentation

enum class sdv::core::ELogSeverity : uint32_t

Enumeration for the severity level of the logging from sdv platform abstraction.

Values:

enumerator trace

level: this is a code smell if used in production. This should be used during development to track bugs, but never committed to your VCS.

enumerator debug

level: log at this level about anything that happens in the program. This is mostly used during debugging, and I’d advocate trimming down the number of debug statement before entering the production stage, so that only the most meaningful entries are left, and can be activated during troubleshooting.

enumerator info

level: log at this level all actions that are user-driven, or system specific (i.e. regularly scheduled operations…) (not included) NOTICE level: this will certainly be the level at which the program will run when in production. Log at this level all the notable events that are not considered an error.

enumerator warning

level: log at this level all events that could potentially become an error. For instance if one database call took more than a predefined time, or if an in-memory cache is near capacity. This will allow proper automated alerting, and during troubleshooting will allow to better understand how the system was behaving before the failure.

enumerator error

level: log every error condition at this level. That can be API calls that return errors or internal error conditions.

enumerator fatal

level: too bad, it’s doomsday. Use this very scarcely, this shouldn’t happen a lot in a real program. Usually logging at this level signifies the end of the program. For instance, if a network daemon can’t bind a network socket, log at this level and exit is the only sensible thing to do.

enumerator trace

level: this is a code smell if used in production. This should be used during development to track bugs, but never committed to your VCS.

enumerator trace

level: this is a code smell if used in production. This should be used during development to track bugs, but never committed to your VCS.

enumerator debug

level: log at this level about anything that happens in the program. This is mostly used during debugging, and I’d advocate trimming down the number of debug statement before entering the production stage, so that only the most meaningful entries are left, and can be activated during troubleshooting.

enumerator debug

level: log at this level about anything that happens in the program. This is mostly used during debugging, and I’d advocate trimming down the number of debug statement before entering the production stage, so that only the most meaningful entries are left, and can be activated during troubleshooting.

enumerator info

level: log at this level all actions that are user-driven, or system specific (i.e. regularly scheduled operations…) (not included) NOTICE level: this will certainly be the level at which the program will run when in production. Log at this level all the notable events that are not considered an error.

enumerator info

level: log at this level all actions that are user-driven, or system specific (i.e. regularly scheduled operations…) (not included) NOTICE level: this will certainly be the level at which the program will run when in production. Log at this level all the notable events that are not considered an error.

enumerator warning

level: log at this level all events that could potentially become an error. For instance if one database call took more than a predefined time, or if an in-memory cache is near capacity. This will allow proper automated alerting, and during troubleshooting will allow to better understand how the system was behaving before the failure.

enumerator warning

level: log at this level all events that could potentially become an error. For instance if one database call took more than a predefined time, or if an in-memory cache is near capacity. This will allow proper automated alerting, and during troubleshooting will allow to better understand how the system was behaving before the failure.

enumerator error

level: log every error condition at this level. That can be API calls that return errors or internal error conditions.

enumerator error

level: log every error condition at this level. That can be API calls that return errors or internal error conditions.

enumerator fatal

level: too bad, it’s doomsday. Use this very scarcely, this shouldn’t happen a lot in a real program. Usually logging at this level signifies the end of the program. For instance, if a network daemon can’t bind a network socket, log at this level and exit is the only sensible thing to do.

enumerator fatal

level: too bad, it’s doomsday. Use this very scarcely, this shouldn’t happen a lot in a real program. Usually logging at this level signifies the end of the program. For instance, if a network daemon can’t bind a network socket, log at this level and exit is the only sensible thing to do.