Internet of Things Integration Platform
Remote Monitoring, M2M and Device Management Software Platform
AggreGate Platform

Logging

As with most server software, AggreGate Server's spares no effort when it comes to logging. Everything can be logged, and logging configuration can be changed at runtime without restarting the server.

Logging output may be sent to:

  • Console
  • Text file
  • XML file
  • Windows event log
  • UNIX Syslog
  • Database
  • Remote network server
  • E-mail messages
  • Java Message Service (JMS)
  • And many other destinations

Logging output is divided into more than one hundred categories (such as database, device communications, GUI, etc.). Each category may be redirected into a separate set of destinations. There are five logging levels: Debug, Info, Warning, Error, and Fatal. Each category may have a different level.

Event-based Logging

While "classic" server logging is very suitable for debugging new developments (such as custom drivers and plugins) and diagnosing server problems, all valuable operational information is also logged in the form of server context events (see unified data model). Those events pass through the full event processing workflow and, thus, get delivered to remote system operators, revoking a necessity of server log file analysis and ensuring much higher manageability.