You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-metrics-diag-logging.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,9 @@ You can use the **Diagnostics settings** menu in the Azure portal to enable and
80
80
> [!IMPORTANT]
81
81
> Logging of diagnostic telemetry is not enabled by default.
82
82
83
-
# [Elastic pool](#tab/elastic-pool)
83
+
# [Azure portal](#tab/azure-portal)
84
+
85
+
**Elastic pools**
84
86
85
87
You can set up an elastic pool resource to collect the following diagnostics telemetry:
86
88
@@ -115,7 +117,7 @@ To enable streaming of diagnostics telemetry for an elastic pool resource, follo
115
117
> [!IMPORTANT]
116
118
> In addition to configuring diagnostics telemetry for an elastic pool, you also need to configure diagnostics telemetry for each database in the elastic pool.
117
119
118
-
# [Single or pooled database](#tab/single-or-pooled-database)
120
+
**Single and pooled databases**
119
121
120
122
You can set up a single or pooled database resource to collect the following diagnostics telemetry:
121
123
@@ -144,7 +146,7 @@ To enable streaming of diagnostics telemetry for a single or a pooled database,
144
146
> [!TIP]
145
147
> Repeat these steps for each single and pooled database you want to monitor.
146
148
147
-
# [Managed instance](#tab/managed-instance)
149
+
**Managed instance**
148
150
149
151
You can set up a managed instance resource to collect the following diagnostics telemetry:
150
152
@@ -180,7 +182,7 @@ To enable streaming of diagnostics telemetry for a managed instance resource, fo
180
182
> [!IMPORTANT]
181
183
> In addition to configuring diagnostics telemetry for a managed instance, you also need to configure diagnostics telemetry for each instance database.
182
184
183
-
# [Instance database](#tab/instance-database)
185
+
**Instance database**
184
186
185
187
You can set up an instance database resource to collect the following diagnostics telemetry:
0 commit comments