InterWorx Usage Data
As of InterWorx 5.0, InterWorx collects and reports some usage data to hone our focus and development. This data is anonymous, and is encrypted before transmission.
Seeing What Is Collected
InterWorx collects three types of data – environmental data, login data, and system errors.
Each time a user logs in, data is recorded in the login.log file. This data helps track browser statistics (in the web), and simple usage statistics for the CLI, XMLRPC, and SOAP environments.
Login data is stored in the login.log. This file is kept in:
When sent, InterWorx rotates the login.log file, keeping a maximum of 5 weeks data locally.
InterWorx collects certain information about the system itself as part of a separate log. This data is collected at the time the login.log is gathered and packaged to be sent to InterWorx, and is not permanently stored in a log file.
To view this data, run the following command:
This will output the exact points of data sent to InterWorx.
Two types of system errors are currently collected by InterWorx. InterWorx stacktraces are collected in
stack.log, and any failed MySQL queries are collected in the
failed-query.log. Both files are found in
Collecting this information allows InterWorx to respond more quickly to find and fix problems.
Both logs are rotated when the file is sent to InterWorx.
Data sent to InterWorx is identifiable via a UUID, or Universally Unique Id. This UUID string is generated randomly, and is in the form of a version 4 UUID. The UUID generated by InterWorx is truly random; it does not make use of the system MAC address.
To opt out of the usage data collection, simply run this command:
Data collection is not done on Cluster Nodes.