Database lock timeout telemetry in Application Insights for partners
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| End users by admins, makers, or analysts |  May 1, 2020 |
May 1, 2020 |
Business value
A partner can use this to troubleshoot locking issues.
Feature details
When a user receives the message, "The operation could not complete because a record in the table was locked by another user," the root cause in the database is a lock timeout.
With this feature, the server will now log an entry to telemetry when this happens as well as entries for all other locks currently occurring in the database.