Logging
As with most server software, logging is an important method to report all events and activities of Iotellect Server. Iotellect Server uses an advanced logging facility easily configurable through an ordinary text file. Logging configuration can be changed at runtime without restarting the Iotellect Server.
 | Most important server operations are also logged as platform events to allow flexible security auditing. See event management section to figure out how to browse real time event streams and analyse historical events. |
Iotellect Server uses Apache Log4J logging library for log output. It is highly customizable and allows multiple levels and sources of logging information along with numerous log destinations. Logging output can be redirected to:
Console
Text files
XML files
Windows event logs
UNIX syslog
Database
Remote network server
E-mail messages
Java Message Service (JMS)
And many other destinations
The Iotellect Server logging configuration file is located in the installation directory and is called logging.xml. The structure of this file is briefly described in the logging configuration file section. It also contains a list of logging categories used by different components of Iotellect to produce logging output, as well as the default logging level for each category.
 | Default Logging Configuration File defines two logging destinations: console and log file called |
Log File Growth Issues
By default, the logging system is configured to log only important messages. However, on a highly loaded server even this conservative logging configuration preset may cause many thousands of log entries per day, causing extensive log file growth.
If you experience such undesired growth of log file size, consider switching logging categories that produce many messages to higher logging levels (e.g. to “fatal”) or even completely disabling logging for those categories.
See logging configuration file section to figure out how to configure logging in specific categories.
Was this page helpful?