Question 1

How do I install LoggerPro using BOSS package manager?

Accepted Answer

First, install BOSS from GitHub releases and add it to PATH. Then, run 'boss init' in your project folder to create boss.json, followed by 'boss install github.com/danieleteti/loggerpro' to download it into the modules folder and update search paths automatically.

Question 2

LoggerPro vs built-in Delphi logging: which is better for production apps?

Accepted Answer

LoggerPro is superior for production due to its async design, thread safety, and 20+ appenders, whereas built-in logging is simpler but lacks performance and flexibility. Choose LoggerPro for scalable, cross-platform needs; built-in is fine for basic debugging.

Question 3

How to log to multiple destinations like file and ElasticSearch at once?

Accepted Answer

Use the fluent builder API: chain WriteToFile and WriteToElasticSearch methods in the LoggerProBuilder, then call Done and Build. This configures concurrent logging without extra code, as shown in the README examples.

Question 4

Can LoggerPro handle high-volume logging without slowing down my app?

Accepted Answer

Yes, its async architecture processes logs in background threads, preventing blocking. However, in extreme cases, the internal queue might grow, so monitor memory usage and adjust log levels or appenders as needed.

Question 5

How to integrate LoggerPro with ElasticSearch with authentication?

Accepted Answer

Use the WriteToElasticSearch appender with methods like WithBasicAuth, WithAPIKey, or WithBearerToken in the builder API. The README provides code snippets for each authentication type, ensuring secure log transmission.

Question 6

Is LoggerPro safe to use in Delphi DLLs or plugins?

Accepted Answer

Yes, it automatically detects DLL contexts and avoids Windows Loader Lock deadlocks during initialization. Initialize in DLL_PROCESS_ATTACH and call Shutdown before unloading to flush queued messages, as noted in the documentation.

Question 7

What's the best way to structure logs for better analysis in LoggerPro?

Accepted Answer

Use structured logging with LogParam classes to add key-value pairs (e.g., order_id, customer) to log messages. This enables easier parsing and integration with tools like ElasticSearch for advanced querying and dashboards.

LoggerPro

What is LoggerPro?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions