Class LogOverride

java.lang.Object
com.tccc.kos.core.service.log.LogOverride

public class LogOverride extends Object
Log level override definition. Log overrides are scoped to node types. That is, an override applied to a node type and all KOS nodes of that type will have the override applied. This provides some granularity in log overrides as they don't apply to the entire device.

The type property defines what the override applies to. Types are defined as colon-separated strings that match a particular type of logging. For example, java log overrides use the following types:

  • java:class: Applies the override to a particular java class or package.
  • java:group: Applies the override to a particular Log group.
Blink connections that implement the kos.logging iface can support log overrides. To override log levels for a blink connection, the type should be blink:{logType}, where the type is provided by the device as part of the iface. This allows log overrides to be specified for each distinct blink connection type.

Finally, the level is desired log level to apply and may be relative to the receiving logger implementation. In java the values should be the standard TRACE, DEBUG, INFO, WARN, FATAL values. For C or other languages, the level may be defined as needed.

When used with blink loggers, the log level is converted to a numeric value using one of the LEVEL_XXX constants. Any string that doesn't match a known level will be converted to LEVEL_INFO.

Version:
2025-02-13