By default, the Express log in GBase 8a outputs only ERROR and WARN messages — not INFO or DEBUG. This is a deliberate choice that prioritizes production performance while keeping logs readable and manageable.
Primary Reason: Performance First
INFO and DEBUG levels capture extensive execution details — query plan steps, intermediate results, function call stacks. In a high‑concurrency environment, logging all this information generates massive write volumes that drain disk I/O and CPU, directly slowing down query execution. If every SQL statement triggered INFO logging, the log subsystem could become a synchronous bottleneck, inflating response times. Limiting the default to errors and warnings keeps the logging overhead minimal in your gbase database.
Secondary Reason: Readability and Operational Efficiency
Concise logs help DBAs quickly zero in on real issues — failed queries, syntax errors, permission exceptions — without sifting through routine noise. It also prevents log files from ballooning, extending retention periods and reducing storage pressure.
The Design Philosophy: Balancing Observability and Speed
GBase 8a’s Express engine is built for production. The default configuration favours stability and throughput. When deep troubleshooting is necessary, you can temporarily raise the log level to INFO or DEBUG via the gcluster_log_level parameter — giving you diagnostic flexibility without sacrificing everyday performance.
Summary
The Express log’s default level is a performance‑conscious smart default. It keeps a gbase database running at full speed, while still providing the detailed diagnostics you need on demand. It's not a missing feature — it's a production‑grade best practice.
Top comments (0)