Questo contenuto non è disponibile nella lingua selezionata.
Chapter 8. Logging subsystem tuning
You can further improve upon JBoss EAP logging subsystem performance in production environments by disabling logging to the console, configuring appropriate logging levels, and specifying the best location to store log files.
8.1. Disabling logging to the console Copia collegamentoCollegamento copiato negli appunti!
Disabling console logging can improve JBoss EAP performance. Although outputting logs to the console can be useful in development and testing environments, for production environments, in most cases, it is not necessary.
The JBoss EAP root logger includes a console log handler for all default standalone server profiles except standalone-full-ha
. The default managed domain profiles do not include a console handler.
Procedure
To remove the default console handler from the root logger, use the following management CLI command:
/subsystem=logging/root-logger=ROOT:remove-handler(name=CONSOLE)
/subsystem=logging/root-logger=ROOT:remove-handler(name=CONSOLE)
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
8.2. Configuring logging levels Copia collegamentoCollegamento copiato negli appunti!
For ideal performance, ensure that you configure the logging levels for your production environment appropriately. For example, although INFO
or DEBUG
levels might be appropriate for development or testing environments, in most cases you should set your production environment logging level to something higher, such as WARN
or ERROR
.
8.3. Configuring the location of the log files Copia collegamentoCollegamento copiato negli appunti!
You should consider the storage location of log files as a potential performance issue. If you save logs to a file system or disk configuration that has poor I/O throughput, it has the potential to affect the whole platform’s performance.
To prevent logging from impacting JBoss EAP performance, set your log locations to high-performance dedicated disks that have a lot of space.