big_data_service:logging
Table of Contents
Logging
On a default installation of the Big Data Service, Elasticsearch is configured to only log errors. This can be amended however…
Logging Level
Logging level is defined in the log configuration file:
%ProgramFiles/Intelligent Plant\Big Data\es\config\logging.yml
Valid logging levels are:
Level | Description |
---|---|
ALL | The ALL has the lowest possible rank and is intended to turn on all logging. |
TRACE | The TRACE Level designates finer-grained informational events than the DEBUG |
DEBUG | The DEBUG Level designates fine-grained informational events that are most useful to debug an application. |
INFO | The INFO level designates informational messages that highlight the progress of the application at coarse-grained level. |
WARN | The WARN level designates potentially harmful situations. |
ERROR | The ERROR level designates error events that might still allow the application to continue running. |
FATAL | The FATAL level designates very severe error events that will presumably lead the application to abort. |
OFF | The OFF has the highest possible rank and is intended to turn off logging. |
NB. When setting a log level, note that logging can introduce a performance overhead. Also, log files are not automatically recycled and can soon generate a significant footprint.
Log Files
By default, log files are written to:
%ProgramFiles/Intelligent Plant\Big Data\es\logs
An alternative location can be defined by setting the “path.logs” property in the elasticsearch configuration file:
%ProgramFiles/Intelligent Plant\Big Data\es\config\logging.yml
big_data_service/logging.txt · Last modified: 2022/11/16 12:41 by su