Skip to content

Commit 86bd8d7

Browse files
Apoorvkudesia-sumologicApoorvkudesia-sumologic
committed
update sql
1 parent a770881 commit 86bd8d7

File tree

1 file changed

+48
-49
lines changed
  • docs/integrations/microsoft-azure

1 file changed

+48
-49
lines changed

‎docs/integrations/microsoft-azure/sql.md‎

Lines changed: 48 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -57,21 +57,21 @@ The Sumo Logic app for Azure SQL app uses the following log types:
5757

5858
```json title="Database Wait Statistics Event"
5959
{
60-
"LogicalServerName":"npande-test-db-server",
61-
"SubscriptionId":"c088dc46-d123-12ad-a8b7-9a123d45ad6a"",""ResourceGroup"":""npandeTestDBResGrp"",""time"":""2018-07-09T05":"13":34.520Z",""resourceId"":"/SUBSCRIPTIONS/c088dc46-d123-12ad-a8b7-9a123d45ad6a"/RESOURCEGROUPS/NPANDETESTDBRESGRP/PROVIDERS/MICROSOFT.SQL/SERVERS/NPANDE-TEST-DB-SERVER/DATABASES/NPANDETESTDB",
62-
"category":"DatabaseWaitStatistics",
63-
"operationName":"DatabaseWaitStatistcsEvent",
64-
"properties":{
65-
"ElasticPoolName":"",
66-
"DatabaseName":"npandeTestDB",
67-
"start_utc_date":"2018-07-09T05:13:34.520Z",
68-
"end_utc_date":"2018-07-09T05:18:36.050Z",
69-
"wait_type":"WRITELOG",
70-
"delta_max_wait_time_ms":0,
71-
"delta_signal_wait_time_ms":0,
72-
"delta_wait_time_ms":12,
73-
"delta_waiting_tasks_count":2
74-
}
60+
"LogicalServerName":"npande-test-db-server",
61+
"SubscriptionId":"c088dc46-d123-12ad-a8b7-9a123d45ad6a"",""ResourceGroup"":""npandeTestDBResGrp"",""time"":""2018-07-09T05":"13":34.520Z",""resourceId"":"/SUBSCRIPTIONS/c088dc46-d123-12ad-a8b7-9a123d45ad6a"/RESOURCEGROUPS/NPANDETESTDBRESGRP/PROVIDERS/MICROSOFT.SQL/SERVERS/NPANDE-TEST-DB-SERVER/DATABASES/NPANDETESTDB",
62+
"category":"DatabaseWaitStatistics",
63+
"operationName":"DatabaseWaitStatistcsEvent",
64+
"properties":{
65+
"ElasticPoolName":"",
66+
"DatabaseName":"npandeTestDB",
67+
"start_utc_date":"2018-07-09T05:13:34.520Z",
68+
"end_utc_date":"2018-07-09T05:18:36.050Z",
69+
"wait_type":"WRITELOG",
70+
"delta_max_wait_time_ms":0,
71+
"delta_signal_wait_time_ms":0,
72+
"delta_wait_time_ms":12,
73+
"delta_waiting_tasks_count":2
74+
}
7575
}
7676
```
7777

@@ -98,9 +98,11 @@ You must explicitly enable diagnostic settings for each Azure SQL database that
9898

9999
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/SQL/Logs`, `Azure/SQL/ActivityLogs`, and `Azure/SQL/Metrics`.
100100

101-
### Configure metrics collection
101+
### Configure collector
102102

103-
1. Create a hosted collector if not already configured and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
103+
Create a hosted collector if not already configured and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). Make sure you create the required sources in this collector. <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
104+
105+
### Configure metrics collection
104106

105107
import MetricsSourceBeta from '../../reuse/metrics-source-beta.md';
106108

@@ -112,30 +114,27 @@ import MetricsSourceBeta from '../../reuse/metrics-source-beta.md';
112114

113115
In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub.
114116

115-
1. Create a hosted collector if not already configured and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
116117
1. To set up the Azure Event Hubs source in Sumo Logic, refer to the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
117118
1. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform below steps for each Azure SQL database that you want to monitor.
118-
* Choose `Stream to an event hub` as the destination.
119-
* Select all the log types except `SQL Security Audit Event`.
120-
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
121-
122-
<img src={useBaseUrl('img/integrations/microsoft-azure/Azure-SQL-Configure-Diagnostic-Logs.png')} alt="Azure Database for MySql Tag Location" style={{border: '1px solid gray'}} width="800" />
123-
124-
3. Tag the location field in the source with right location value.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Database for MySql Tag Location" style={{border: '1px solid gray'}} width="400" />
119+
* Choose `Stream to an event hub` as the destination.
120+
* Select all the log types except `SQL Security Audit Event`.
121+
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-SQL-Configure-Diagnostic-Logs.png')} alt="Azure Database for MySql Tag Location" style={{border: '1px solid gray'}} width="800" />
122+
1. Tag the location field in the source with right location value.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Location.png')} alt="Azure Database for MySql Tag Location" style={{border: '1px solid gray'}} width="400" />
125123

126124
:::note
127125
Auto Tuning logs will be collected when Auto Tuning feature is enabled in Azure SQL. Click [here](https://learn.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable?view=azuresql) to learn more on how to enable this feature.
128126
:::
127+
129128
#### Enable SQL Security Audit logs
130129
In this section, you will configure a pipeline for shipping diagnostic logs from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) to an Event Hub.
131130

132131
1. To enable the Audit logs in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#configure-auditing-for-your-server). Perform below steps for each Azure SQL database that you want to monitor.
133-
* Choose `Event Hub` as the destination. Refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#audit-to-event-hubs-destination).
134-
* Use the same Event hub namespace and Event hub name as configured in `Diagnostic logs` in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-SQL-Configure-Auditing.png')} alt="Configure Auditing" style={{border: '1px solid gray'}} width="800" />
132+
* Choose `Event Hub` as the destination. Refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/auditing-setup?view=azuresql#audit-to-event-hubs-destination).
133+
* Use the same Event hub namespace and Event hub name as configured in `Diagnostic logs` in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.<br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-SQL-Configure-Auditing.png')} alt="Configure Auditing" style={{border: '1px solid gray'}} width="800" />
135134
1. By default, auditing is enabled only for the below action groups. Refer to [Azure help](https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions) for more details on supported action groups and actions.
136-
* "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP"
137-
* "FAILED_DATABASE_AUTHENTICATION_GROUP"
138-
* "BATCH_COMPLETED_GROUP"
135+
* "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP"
136+
* "FAILED_DATABASE_AUTHENTICATION_GROUP"
137+
* "BATCH_COMPLETED_GROUP"
139138

140139
Follow the below command to update the audit policy with new actions using Azure CLI. If you want to use any other mechanism, refer to the [Microsoft documentation](https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/create-a-server-audit-and-database-audit-specification?view=sql-server-ver16).
141140
).
@@ -389,7 +388,7 @@ For more information about the statistics presented on the QueryStoreWaitStats d
389388

390389
**Wait Category Trend.** A stacked column chart that shows the count of wait events by category per timeslice over the last 24 hours.
391390

392-
**Total Wait Time for Query by Wait Category**. A stacked column chart that shows, for each query, the length of time a query spent waiting in each Wait Category over the last 24 hours.
391+
**Total Wait Time for Query by Wait Category**. A stacked column chart that shows, for each query, the length of time a query spent waiting in each Wait Category over the last 24 hours.
393392

394393
**Wait Details**. The table displays wait statistics as encountered by queries on a given database, residing on a given logical server in the last 24 hours.
395394

@@ -424,7 +423,7 @@ For more information about the data presented on the Timeouts dashboard, see [Ti
424423

425424
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-Timeouts.png')} alt="Timeouts" />
426425

427-
**Timeouts**. The count of timeouts over the last 7 days.
426+
**Timeouts**. The count of timeouts over the last 7 days.
428427

429428
**Top 10 Error States**. A table that lists the top 10 errors states that have occurred over the last 7 days and the count of errors in each state.
430429

@@ -437,8 +436,8 @@ For more information about the data presented on the Timeouts dashboard, see [Ti
437436
The **Azure SQL - Health** dashboard provides information of any service health incidents or resource health events associated with SQL database service or resource in your azure account.
438437

439438
Use this dashboard to:
440-
* View recent resource and service health incidents.
441-
* View distribution of service and resource health by incident type.
439+
* View recent resource and service health incidents.
440+
* View distribution of service and resource health by incident type.
442441

443442

444443
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-Health.png')} alt="Azure SQL health dashboard" style={{border: '1px solid gray'}} width="800" />
@@ -448,11 +447,11 @@ Use this dashboard to:
448447
The **Azure SQL - Policy and Recommendations** dashboard provides information of all effect action operations performed by Azure Policy and recommendations events from Azure Advisor.
449448

450449
Use this dashboard to:
451-
* Monitor policy events with warnings and errors.
452-
* View recent failed policy events.
453-
* View total recommendation events.
454-
* Identify High Impact recommendations.
455-
* View recent recommendation events and navigate to the affected resource.
450+
* Monitor policy events with warnings and errors.
451+
* View recent failed policy events.
452+
* View total recommendation events.
453+
* Identify High Impact recommendations.
454+
* View recent recommendation events and navigate to the affected resource.
456455

457456
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-Policy-and-Recommendations.png')} alt="Azure SQL - Policy and Recommendations dashboard" style={{border: '1px solid gray'}} width="800" />
458457

@@ -462,9 +461,9 @@ Use this dashboard to:
462461
The **Azure SQL - Administrative Operations** dashboard provides details on read/write/delete specific changes, different operations used, top 10 operations that caused most errors, and users performing admin operations.
463462

464463
Use this dashboard to:
465-
* Identify top users performing administrative operations.
466-
* View Top 10 operations that caused the most errors.
467-
* View recent read, write, and delete operations.
464+
* Identify top users performing administrative operations.
465+
* View Top 10 operations that caused the most errors.
466+
* View recent read, write, and delete operations.
468467

469468
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-Administrative-Operations.png')} alt="Azure SQL Administrative Operations dashboard" style={{border: '1px solid gray'}} width="800" />
470469

@@ -473,9 +472,9 @@ Use this dashboard to:
473472
The **Azure SQL - SQL Security Audit** dashboard provides audit information on server level events and database level events including DML and DDL statements executed.
474473

475474
Use this dashboard to:
476-
* Identify failed login and their geo locations.
477-
* View recent DDL, DML, DQL, and TCL statements.
478-
* Track who (host name, service principal, ip address) and what (object, database, server) information associated with any database operation.
475+
* Identify failed login and their geo locations.
476+
* View recent DDL, DML, DQL, and TCL statements.
477+
* Track who (host name, service principal, ip address) and what (object, database, server) information associated with any database operation.
479478

480479

481480
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-SQL-Security-Audit.png')} alt="Azure SQL Security Audit dashboard" style={{border: '1px solid gray'}} width="800" />
@@ -485,9 +484,9 @@ Use this dashboard to:
485484
The **Azure SQL - Automatic Tuning** dashboard provides information about automatic tuning recommendations for a database.
486485

487486
Use this dashboard to:
488-
* View recent changes in tuning configuration.
489-
* View create index recommendations.
490-
* View drop index recommendations.
487+
* View recent changes in tuning configuration.
488+
* View create index recommendations.
489+
* View drop index recommendations.
491490

492491
<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Azure-SQL/Azure-SQL-Automatic-Tuning.png')} alt="Azure SQL Automated Tuning dashboard" style={{border: '1px solid gray'}} width="800" />
493492

@@ -524,4 +523,4 @@ These alerts are metrics-based and will work for Azure SQL.
524523
| `Azure SQL - Data IO percentage` | This monitor triggers alerts when High Data IO percentage is detected in Azure SQL. | Count > 90 | Count =< 90 |
525524
| `Azure SQL - DTU Percentage` | This monitor triggers alerts when High average DTU consumption percentage is detected in Azure SQL. | Count > 80 | Count =< 80 |
526525
| `Azure SQL - Tempdb Percent Log Used` | This monitor triggers alerts when High Tempdb Percent Log Usage is detected in Azure SQL. | Count > 60 | Count =< 60 |
527-
| `Azure SQL - High Worker Usage` | This monitor triggers alerts when High Worker Usage is detected in Azure SQL. | Count > 60 | Count =< 60 |
526+
| `Azure SQL - High Worker Usage` | This monitor triggers alerts when High Worker Usage is detected in Azure SQL. | Count > 60 | Count =< 60 |

0 commit comments

Comments
 (0)