зеркало из https://github.com/microsoft/BCTech.git
deadlock draft query
This commit is contained in:
Родитель
e6159785e7
Коммит
ae9c2ee7ff
|
@ -0,0 +1,44 @@
|
|||
// KQL samples - SQL Deadlocks
|
||||
|
||||
// Not fully tested yet, minor changes might be added before release
|
||||
|
||||
// SQL deadlocks (RAW data)
|
||||
traces
|
||||
| where timestamp > ago(60d) // adjust as needed
|
||||
| where customDimensions.eventId == 'RT0028' // starting from version 16.1, the eventId is used to identity signal types
|
||||
| where customDimensions.alObjectId > 0 // filter out internal server calls
|
||||
| extend eventId = customDimensions.eventId
|
||||
, aadTenantId = customDimensions.aadTenantId
|
||||
, environmentName = customDimensions.environmentName
|
||||
, environmentType = customDimensions.environmentType
|
||||
, companyName = customDimensions.companyName
|
||||
, extensionId = customDimensions.extensionId
|
||||
, extensionPublisher = customDimensions.extensionPublisher
|
||||
, extensionName = customDimensions.extensionName
|
||||
, extensionVersion = customDimensions.extensionVersion
|
||||
, sessionId = customDimensions.sessionId
|
||||
, alObjectId = customDimensions.alObjectId
|
||||
, alObjectName = customDimensions.alObjectName
|
||||
, alObjectType = customDimensions.alObjectType
|
||||
, alStackTrace = customDimensions.alStackTrace
|
||||
, clientType = customDimensions.clientType
|
||||
, sqlStatement = tostring(customDimensions.sqlStatement)
|
||||
, sqlServerSessionId = customDimensions.sqlServerSessionId
|
||||
| extend operationType = case(
|
||||
sqlStatement startswith "UPDATE", "UPDATE"
|
||||
, sqlStatement startswith "DELETE", "DELETE"
|
||||
, sqlStatement startswith "BeginTransaction", "BEGIN_TRANS"
|
||||
, sqlStatement matches regex "INSERT INTO", "INSERT"
|
||||
, sqlStatement startswith "SELECT", "SELECT"
|
||||
, sqlStatement matches regex "IF EXISTS \\(SELECT (.*)\\) SELECT", "SELECT'"
|
||||
, sqlStatement has "SELECT NEXT VALUE FOR", "SELECT_SEQUENCE_VALUE"
|
||||
, sqlStatement has "SELECT @@SPID", "SELECT_SPID"
|
||||
, sqlStatement matches regex "(.*)WITH", "SELECT"
|
||||
, sqlStatement startswith "CREATE TABLE", "CREATE_TABLE"
|
||||
, sqlStatement startswith "ALTER TABLE", "ALTER_TABLE"
|
||||
, sqlStatement startswith "exec sp_rename", "RENAME_TABLE"
|
||||
, sqlStatement matches regex "(.*)DROP TABLE", "DROP_TABLE"
|
||||
, sqlStatement startswith "SET LOCK_TIMEOUT", "SET_LOCK_TIMEOUT"
|
||||
, sqlStatement has "sp_getapplock", "GET_APP_LOCK"
|
||||
, "UNKNOWN"
|
||||
)
|
|
@ -66,13 +66,13 @@ Signal is added incrementally to Business Central. In this table you can see in
|
|||
| Use of read scale-out in reporting | 2021 release wave 2 (19.1) | https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-reports-trace |
|
||||
| Feature Telemetry | 2021 release wave 2 (19.1) | (pending docs) |
|
||||
| Task Scheduler Telemetry | 2021 release wave 2 (19.1) | https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-task-scheduler-trace |
|
||||
| Database deadlocks | 2022 release wave 1 (20.0) | No KQL sample yet, https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/telemetry-when-database-deadlock-occurs-this-logged-telemetry |
|
||||
| Database deadlocks | 2022 release wave 1 (20.0) | Draft KQL sample ready, https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/telemetry-when-database-deadlock-occurs-this-logged-telemetry |
|
||||
| Database wait statistics | 2022 release wave 1 (20.0) | KQL sample ready, https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/performance-partners-get-database-insights-through-virtual-tables-in-client-pages |
|
||||
| Verbose telemetry enabled | 2022 release wave 1 (20.0) | KQL sample ready, https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/telemetry-action-enabling-detailed-telemetry-logged-telemetry |
|
||||
| General error dialogs | 2022 release wave 1 (20.0) | KQL sample ready, https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/telemetry-error-dialogs-are-logged-telemetry |
|
||||
| Permission error dialogs | 2022 release wave 1 (20.0) | (pending link to release note) |
|
||||
| Use of read scale-out in web service calls | 2022 release wave 1 (20.0) | (pending link to release note) |
|
||||
| Report action and document type in reporting | 2022 release wave 1 (20.0) | https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-reports-trace |
|
||||
| Report action and document type in reporting | 2022 release wave 1 (20.0) | KQL sample ready, https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-reports-trace |
|
||||
| Environment lifecycle and configuration changes| 2022 release wave 1 (20.0) | (pending link to release note) |
|
||||
| Session stops | 2022 release wave 1 (20.0) | (pending link to release note) |
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче