Issue Summary

It has been observed that the deadlock captured in Jira Align logs (Splunk) are significantly fewer compared to the deadlock report captured in SQL Server's xml_deadlock_report.

Steps to Reproduce

1. Check Jira Align logs/Splunk and search for "deadlocked"
2. Now, check the deadlocks reported in SSMS > Management > Extended Events > Session > system_health

Expected Results

What's captured in SQL Server should somehow reflect in Jira Align logs.

Actual Results

There is a discrepancy with Jira Align deadlocks vs SQL Servers deadlock report

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available