Action log reference
Spotfire Server action logs capture usage data, such as when a user logs in, opens a file from the library, adds bookmarks, pages through analyses, and so on. Action logs capture events from Spotfire Server and can also be configured to capture events from Automation Services, Spotfire Analyst, and Spotfire Business Author.
You can use the action logs to log users' actions in Spotfire, but you cannot use it to log the user state. For example, you can log when a user changes licenses or access permissions for another user (user actions), but you cannot log which actions a user is allowed to perform (user state).
Actions are collected in the logs and stored in files or in a database. Actions that do not originate from the server are sent to
Spotfire Server through a web service.
- You must enable and configure the web service if you want actions that do not originate from the server to be logged.
- When you enable action logging, you must restart all service instances. If you do not restart all service instances, your logging changes will not take effect.
- Action log entries
When you analyze an action log, you can organize the data into categories, actions, and properties (identifiers and arguments). You can map these to database columns, which you can display in a Spotfire visualization. - Action log generic entries
Each log entry contains the generic information described in this topic. - Action log categories
When you enable action logging, you can enable any of the following categories. When you configure the web service, you can specify from which services to accept requests. When you read the action logs, you can look at these categories for information about where user actions are being logged from. You can specify some or all categories from the command line or from the configuration tool. - Action log properties
Each action log entry contains generic information, the category of the action, the action logged, and identifying information (id1 and id2), as well as arguments providing more detail about the action. The identifying information and arguments are the properties described in this reference. - Sample action log output
Reading the output from an action log file can be challenging. The sample shown below demonstrates a series of user actions and the resulting log entry that the system provides.
- Action log entries
When you analyze an action log, you can organize the data into categories, actions, and properties (identifiers and arguments). You can map these to database columns, which you can display in a Spotfire visualization. - Action log generic entries
Each log entry contains the generic information described in this topic. - Action log categories
When you enable action logging, you can enable any of the following categories. When you configure the web service, you can specify from which services to accept requests. When you read the action logs, you can look at these categories for information about where user actions are being logged from. You can specify some or all categories from the command line or from the configuration tool. - Action log properties
Each action log entry contains generic information, the category of the action, the action logged, and identifying information (id1 and id2), as well as arguments providing more detail about the action. The identifying information and arguments are the properties described in this reference. - Sample action log output
Reading the output from an action log file can be challenging. The sample shown below demonstrates a series of user actions and the resulting log entry that the system provides.
Parent topic: Action logs and system monitoring