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:Composer loggers (Atoti Technical Modules)
There are loggers available in the Atoti generic technical modules. They are used in a lot of places in Atoti Server. Here is the exhaustive list of the loggers available in the Atoti Composer:- atoti.server.tech
- atoti.server.tech.aggregation
- atoti.server.tech.arrow
- atoti.server.tech.bitmap
- atoti.server.tech.chunks
- atoti.server.tech.chunks.allocation
- atoti.server.tech.chunks.compression
- atoti.server.tech.chunks.creation
- atoti.server.tech.code-generation
- atoti.server.tech.concurrency
- atoti.server.tech.concurrency.fence
- atoti.server.tech.concurrency.numa
- atoti.server.tech.concurrency.stop-watch
- atoti.server.tech.concurrency.threads
- atoti.server.tech.condition
- atoti.server.tech.dictionary
- atoti.server.tech.formatter
- atoti.server.tech.jdbc
- atoti.server.tech.jmx
- atoti.server.tech.memory
- atoti.server.tech.mvcc
- atoti.server.tech.observability
- atoti.server.tech.observability.health-event
- atoti.server.tech.partitioning
- atoti.server.tech.property
- atoti.server.tech.records
- atoti.server.tech.registry
- atoti.server.tech.timings
- atoti.server.tech.utilities
- atoti.server.tech.vector