Component Log Files
During ThingWorx Analytics operations, information about each component is written to an individual log file on your host computer. Depending on the logging level configured in your system-environment-variables.properties file, each log file can contain error messages, warnings, and other process information that can be useful for debugging. If you have issues during normal operations, consult the logs for information.
Component Log Files for ThingWorx Analytics Server
The log files listed below are available in the following directory:
/opt/ThingworxAnalytics/ThingWorxAnalyticsServer/data/logs
• async.log – Contains information about asynchronous jobs.
• sync.log – Contains information about synchronous processes and queries.
• twas-twx-adapter.log – Contains information about communication activities between ThingWorx and ThingWorx Analytics APIs.
• worker.log – Contains information about common worker activities.
A log file for the ZooKeeper component is also available but the file extension is different and it is located in the following path:
/opt/ThingWorxAnalytics/ThingWorxAnalyticsServer/zookeeper/zookeeper.out
 |
If your directory structure is different because, for example, you upgraded from an earlier release, adjust your navigation accordingly. For more information, see:
|
Component Logs Files for Platform Analytics
The log files listed below are available in the following directory:
/opt/ThingWorxAnalytics/PlatformAnalytics/logs
• configuration.log – Contains information about Property Transform processes.
• descriptive-analytics-microservice.log – Contains information about Descriptive Analytics processes.
• security-tool.log – Contains information about encrypting and decrypting security keys and passwords.
|
|
If your directory structure is different because, for example, you upgraded from an earlier release, adjust your navigation accordingly. For more information, see:
|
Logging Levels
Logging levels determine what level of information is written to the component log files. In the following table, see the logging levels that are available for configuration and the types of information each level generates.
|
Log Level
|
Description
|
|---|---|
|
OFF
|
Turns off logging.
|
|
FATAL
|
Returns severe error events that could lead the application to abort.
|
|
ERROR
|
Returns error events that occur but do not prevent the application from continuing to run.
|
|
WARN
|
Returns potentially harmful situations.
|
|
INFO
|
Returns informational messages that highlight the progress of the application at a high level.
|
|
DEBUG
|
Returns detailed informational events that can be used to debug the application.
|
|
TRACE
|
Returns even more detailed information events than the DEBUG level.
|
|
ALL
|
Turns on all messaging.
|
|
|
The TRACE and ALL logging levels use more resources than the other levels. Using TRACE or ALL could affect application performance.
|
The logging level is controlled by a system variable in a properties file.ThingWorx Analytics components are installed with a logging level of WARN, but you can change the level as follows:
1. Open a terminal window as the root user and navigate to the properties file at one of the following paths:
◦ For Analytics Server: /opt/ThingWorxAnalytics/ThingWorxAnalyticsServer/config/system—environment-variables.properties
◦ For Platform Analytics: /opt/ThingWorxAnalytics/PlatformAnalytics/platform-analytics-environment.properties
2. Find the#default level of all loggerssection.
Example:
3. Change the logging level on the second line.
Example: logging.default.level=DEBUG
4. Restart the server.