Chronicle Logger is an extremely fast java logger. We feel logging should not slow down your system.
Chronicle logger is able to aggregate all your logs to a central store. It has built in resilience, so you will never loose messages.
Chronicle logger supports most of the standard logging API’s including slf4j, sun logging, commons logging, log4j.
Today most programs require the logging of large amounts of data, especially in trading systems where this is a regulatory requirement. Loggers can affect your system performance, therefore logging is sometimes kept to a minimum, With chronicle we aim to eliminate this added overhead, freeing your system to focus on the business logic.
Chronicle logger is built on Chronicle Queue. It provides multiple Chronicle Queue adapters and is a low latency, high throughput synchronous writer. Unlike asynchronous writers, you will always see the last message before the application dies. As the last message is often the most valuable.
- Chronicle Logger can support over one million messages per second per node.
- Concurrent writers across processes and aggregation across machines. You can have one ore more aggregating node to process your logs.
- It supports querying of messages as well as real time event driven processing of messages.
- You want to log the message you have faster, but you don’t want to change your logging API.
- You want to log all your messages with out losing any data, even in the event of a system failure.
- You want to aggregate your logs across logging libraries, across processes, or across machines.
An example setup.
- You have a cluster of nodes running multiple applications with different loggers.
- All the logs can be consolidated via replication to a central log analyser.
- These analysers can trigger actions based on the content of the logs.
- They can be analysed later in chronological order despite being produced by different applications on different machines.