Once you have enabled device logging and have started to collect logs for a particular ConsumerId/DeviceId, the next step is understanding how to interpret the captured logs. Below is a guide to how these logs can be checked, which covers a brief overview of what information is included in the logs that may assist in troubleshooting certain scenarios.
Assumption: You have already enabled device logging for a specific Consumer ID or Device Id.
- Log into the Plexure platform
- Under Owner level, go to Settings and navigate to Developer Tools
- Under Developer Tools navigate to Device and Consumer Logs
- Find the Name of the profile device logging was enabled for
- Click Download Logs
- The logs will download as a .csv file from the platform
- Open the .csv file
- The logs should now include a list of API calls the consumer/device has made to the Plexure platform
The device logs will include a few columns, below is a brief explanation of each column. This may assist in troubleshooting and understanding what may have been happening at that point in time.
- Date - The date (in UTC time) when the request was made to the platform
- API - The Plexure API the request was made to e.g. act-vmob.vmobapps.com (Activity API), con-vmob.vmobapps.com (Consumer API), off-vmob.vmobapps.com (Offer API)
- Endpoint - The endpoint at which Plexure API the request was made to. Note, for some Plexure API's, there are several endpoints
- Method - The HTTP method used e.g. POST, GET, PUT, DELETE etc
- Status Code - HTTP response code returned, e.g. 200,201, 400, 409 etc
- Response Time - The response time in which the request completed (in ms)
- Request Headers - The SDK headers passed in the request to the platform
- Request Content - The content of the request that was sent to the platform
- Response Headers - The response headers included in the response from the platform
- Response Content - The content of the response returned from the platform. Note, in some scenarios where the response is too long, the response may be truncated
The below video shows how you can use device logging to monitor a device when troubleshooting geofences. E.g. in order for a geofence message to be received, the app/sdk needs to have triggered a "geofence-entry" to the platform in order for the push notification to be sent and received by the end user.