Foglight is not picking up deadlock activity on a monitored SQLServer instance.
Foglight generates an email notification or alarm advising a deadlock condition has occurred, but the Activity dashboard does not display any data indicating a deadlock has or is ocurring.
Some deadlocks cannot be captured by the trace mechanism.
No Deadlocks are occurring on the SQL Instance. Confirm on the SQL Instance it is registering deadlocks.
Foglight initially displays only the last 60 minutes of activity by default.
Foglight only recognized International standard date and time format. FglAM and the SQL Server is using Thailand date and time format. For e.g. 2555-MM-DD.
The is a maximum limit of 100 rows set for the deadlocks displaying in the Foglight view.
The number of deadlocks may be limited by the DBSS-MaxDeadlocks registry value.
Performance issues on the host caused by the Extended Events collection used by default in the Deadlocks collection
SQL Server Extended Events deadlock collection hanging and failing on time out
Deadlock SQL text field content size is truncated for SQL Server
Deadlocks not detected with "Failed to Process Deadlock XML" in SQL Server agent logs
Please note that beginning with the 5.9.4.20 SQL Server cartridge the deadlock collection has changed to use Extended Events instead of traces for SQL Server versions above SQL Server 2005. It is recommended to upgrade the SQL Server cartridge to the 5.9.4.20 or higher release.
A. Confirm deadlock activity on the SQL instance by enabling TRACE FLAGS 1204 and 1222 with Global option(-1) and check the SQL Server Error log
Check enabled Trace options with: DBCC TRACESTATUS
- or -
B. Execute query on SQL Server Instance to view current Extended Events(MSSQL 2008+) system health data:
NOTE: If no events are returned or activity logged , deadlocks should not register in Foglight, but the above query may only evaluate current data in cache and my not contain past historical events due to instance restarts or log rolls.
Confirmed by creating a test deadlocks on a test DB and tables and using the above methods and if monitored in Foglight, che
cking the monitored instance dashboards: Activity | Deadlocks view(adjust time zonar to match event occurance). New deadlocks will register within 5 mins or as fast as 60 seconds.
Note the actual time of the event in the Alarm or Email Notification and adjust the dashboard Timeline (zonar) to match the timeframe of the actual event. e.g. 4h, 8h, 24h, 48h, Yesterday, Last week, etc
Setup FglAM and SQL Server instance to use International standard date and time format.
The 100 record limit in the deadlock collection can be changed in the view definition in Foglight as shown in the image below.
The number of deadlocks displayed in the SQL Server agent is managed by the DBSS-MaxDeadlocks registry value.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center