Telemetry
- Peter Damgaard Jørgensen
- Johannes Sebastian Nielsen
Minimum Requirements
- Mobile WMS extension MOB5.42
- Business Central 2022 release wave 1 (BC20)
Standard Business Central logs telemetry of each request from a mobile device as an incoming web service call, but with very limited details of each request.
They are all logged with the Event ID of RT0008 and details can be found here: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-webservices-trace
Mobile WMS has added custom telemetry to both enable detailed statistics and assist troubleshooting for partners and Tasklet.
The following custom events are being logged:
| EventID | Description | Telemetry from |
|---|---|---|
| ALMOB2000 | A mobile document request has been received and processed without any error | 5.42 |
| ALMOB2001 | A mobile document request has been received and processed resulting in an error | 5.42 |
| ALMOB2002 | A mobile document request has been received and processed and a ForceWarning has been returned to the user to confirm if the transaction should be completed. If the user confirms the warning, a new ALMOB2000 or ALMOB2001 will be logged. | 5.42 |
| ALMOB2010 | The Mobile Setup table has been changed. Both the current content of all fields and the xRec values of modified fields are logged. | 5.42 |
| ALMOB2100 | An outbound HTTP request to e.g. PrintNode.com or InterForm failed | 5.46 |
| ALMOB2200 | The Tasklet PrintNode connector received a list of printers from PrintNode.com | 5.46 |
| ALMOB2300 | Usage of the Sandbox Configuration Guide | 5.47 |
| ALMOB2400 | Specific Tracking Without Whse Tracking Detected (as part of Unplanned Move of License Plate) | 5.51 |
To track whether selected parts of Mobile WMS are Discovered or Set up or Used or Undiscovered, the following functional areas are being tracked:
| EventID | Description | Telemetry from Mobile WMS version |
|---|---|---|
| ALMOB1000 | Package No. implementation (Standard Mobile WMS) | 5.42 |
| ALMOB1001 | Package No. implementation (None/Customization) | 5.42 |
| ALMOB1010 | Pack & Ship Feature | 5.42 |
| ALMOB1020 | Mobile Print Feature | 5.42 |
| ALMOB1030 | Tasklet PrintNode Feature | 5.46 |
| ALMOB1040 | Mobile WMS Trial | 5.47 |
| ALMOB1050 | License Plating | 5.51 |
| ALMOB1060 | License Plating - Create LP during Receive | 5.51 |
| ALMOB1070 | License Plating - Put-away LP | 5.51 |
| ALMOB1080 | License Plating - Unplanned Move with LP | 5.51 |
| ALMOB1090 | License Plating - LP Created manually | 5.51 |
Recommendations to limit increased cost of telemetry
The cost of telemetry is determined on the volume of telemetry data your application sends (data ingestion) and how long time you want data to be available (data retention).
To avoid redundant information in Application Insights you can skip the generic successful incoming web service calls to Mobile WMS and only keep the detailed custom entries.
This can be done by creating a Data Collection Rule for the AppTraces table in the related Log Analytics Workspace specifying the following filters in the Transformation Editor:
source |
This excludes generic web service calls from Mobile WMS but keeps everything else - including the detailed custom ALMOB2000 to ALMOB2002 logs for mobile document requests.
If you on the other hand would like to exclude all custom telemetry logged by Mobile WMS you could create this Data Collection Rule:
| source | where (Properties.eventId !startswith_cs "ALMOB") |
For more information: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-control-cost