What kind of information does the telemetry function store to help replicate issues?
You can search for the Telemetry Log records by running the following SQL query on the Orchestrate database:
Select * from TelemetryLog
The telemetry log categories and provides details of certain activites on the plan. For example:
Orchestrate Login - Login attempt for user CLOUD\reg014ngural01, Login attempt for user CLOUD\reg014ngural01
Info - Plan opened in 38 seconds
Shuffling Starting - Job Code: d4a43ff2-7d91-4612-9071-1656f11b5650 Job Code: 2b02f32b-f4bb-49fc-8401-1542e82a7144 Job Code: 102e9546-89af-47a1-81b6-ec27ea442931 Job Code: 31940b32-8257-4f94-b1b8-da64b28bbe49 Job Code: 0b3af413-1016-49e2-acf3-b6207954f00e Job Code: 4606b313-0a46-48e1-a2e6-3a285f221709 Job Code: 8788c2a9-30f8-4faa-beb3-00468001d780 Job Code: cc2a0990-c336-41f5-bb73-f5912d864818
Shuffling Finished Plan Shuffling succeeded.
Info - Refreshing Plan ...
Delete Tasks - Also Delete Relateds: False Prompt User: True Delete from Database: False Job Code: d4a43ff2-7d91-4612-9071-1656f11b5650
Reduce Waiting Time - Allow Secondary Resources to Move in Resource Group: True Same Resource Links Only: True Tasks to Unplan: Job Code: 519393/16_1
Info - Planning: 519393/17Info Saving Plan ...
Info Clearing Old Data...
Info Old Data cleared
Info Publishing to SFDC ...
Info Refreshing Plan ...
Info Refreshing Plan ...
Info Publishing to SFDC Finished
Orchestrate Login Login attempt for user admin
Orchestrate Login User admin signed in successfully
Log Out User admin signed out successfully
These details would help us with troubleshooting. For instance, when the application crashes, user's cannot remember what they were doing on the plan or what other user's were doing, but the telemetry logs will show what each planner was going before the plan crashed.