Logging Device Events
The Updates and Insights module provides the ability for devices to log events in the Notification Server. Events are ways for devices to provide early and frequent feedback from the software installed on the device. They can be of particular interest to Product Managers in understanding, for example:
| • | How software is being used |
| • | Whether new features are being adopted |
| • | Whether certain activities (for example, a post-install test) have been completed |
| • | Precise difficulties an update might have experienced |
| • | Detailed information about the device's overall status |
Devices log events with the Notification Server after the software has been installed or upgraded on the device.
Only registered devices should log events. For more information about registering a device see Prequisites for Automated Updates.
What Is an Event?
An event consists of an event name and optionally the following elements:
| • | an event group, to be able to categorize and search for events across a range of devices |
| • | an event value, to add extra contextual information to the event. |
One example of an event might be:
event name: "postUpgradeTest"
event group: "upgrades"
event value: "passed"
The steps for logging an event are described in the following section.
Logging a Device Event
Before performing the following steps, ensure that the device is registered with FlexNet Operations. For detailed information about the /events API, see Events REST API.
To log a device event
| 1. | Send a POST request to the /events Notification Server end point with the appropriate payload. |
| 2. | Use the polling ID returned by the POST request to GET the response to the /events call, until a 200 response is received. |
Note:This step is optional. The polling should not take place too frequently; once per 10 seconds is adequate. The polling ID will become invalid after 5 minutes.