Logback custom converters
Atoti provides three Logback converters you can register in yourlogback.xml to enrich log patterns with server-specific context.
The example below registers all three converters and uses
%thread and %user in an appender pattern.
Blocked-thread watchdog
The blocked-thread watchdog is an opt-in component that periodically scans for blocked JVM threads. When it detects a change in the blocked-thread count, it logs a summary on theatoti.server.monitoring.health logger and writes a full thread dump on the atoti.server.monitoring.health.blocked-thread logger.
The watchdog is disabled by default because a full thread dump is verbose. Enable it only when you need to diagnose lock contention.
Loggers per modules
Check the logger documentation of the component you want to monitor:Cube loggers
These loggers cover what a cube does:- the transactions applied to it
- the planning of the queries it answers
- the continuous queries registered against it
- the post-processors it evaluates
atoti.server.pivot. The more granular loggers below
each narrow that down to one aspect.
Here is the exhaustive list of the loggers available on the cube:
- atoti.server.pivot
- atoti.server.pivot.transaction
- atoti.server.pivot.query
- atoti.server.pivot.query.planning
- atoti.server.pivot.query.continuous
- atoti.server.pivot.query.continuous.mdx
- atoti.server.pivot.query.continuous.drillthrough
- atoti.server.pivot.query.continuous.streaming
- atoti.server.pivot.postprocessor