Need to extend existing deadlock capture event to include Deadlock Victim's AL code stack as well as the BC Username of the victim. Without the victim’s information such as NAV/BC user names and AL Code stacks for both successful and victim, it is harder to troubleshoot deadlocks using the current feature in reality in a busy multi-user system. It would be also vitally important to see the AL Code stack of the user who caused the deadlock. It would be better to drop AL ObjectType,AL ObjectNumber,AL ScopeName and replace it with AL Code stack of the user caused the deadlock. See https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/monitor-database-deadlocks for more detail.

It would be really useful to have this information available centrally (ideally in the SQL Server's event log rather than the service tier's event log) as there could be multiple host machines could be involved in a production environment hosting service tiers and users who connected through a service tier could deadlock user connected through another service tier and these service tiers will not necessarily running on the same windows server machine.

Further, can this be also included as a telemetry for Dynamics 365 Business Central for both On-Perm and for Saas implementations. Can this be addressed in the next release of Dynamics 365 Business Central.