@@ -85,7 +85,7 @@ instances:
85
85
#
86
86
# exclude_hostname: false
87
87
88
- ## Controls how the database is identified. The default value is the resolved hostname for the instance,
88
+ ## Controls how the database is identified. The default value is the resolved hostname for the instance,
89
89
## which respects the `reported_hostname` option.
90
90
##
91
91
## This value will be used as-is for the display name of the instance but will be normalized
@@ -105,9 +105,11 @@ instances:
105
105
## - database: The connection database.
106
106
## - server_name: The resolved server name of the instance.
107
107
## - instance_name: The resolved instance name of the instance.
108
+ ## - full_server_name: The resolved full server name of the instance, which is the combination of
109
+ ## the server name and instance name, or more specifically, the exact value returned by `@@SERVERNAME`.
108
110
## In addition, you can use any key from the `tags` section of the configuration.
109
111
#
110
- # template: $env-$resolved_hostname:$port
112
+ # template: $full_server_name
111
113
112
114
## @param database_autodiscovery - boolean - optional - default: false
113
115
## Auto-discover and monitor databases. Supported for the metrics check.
@@ -165,9 +167,9 @@ instances:
165
167
##
166
168
## Set `ao_metrics.enabled` to true to enable collection of AlwaysOn metrics. Defaults to false.
167
169
##
168
- ## When `ao_metrics.enabled` is True, use `ao_metrics.availability_group` to specify the
169
- ## resource group id of a specific availability group that you would like to monitor.
170
- ## If no availability group is specified, then we will collect AlwaysOn metrics for all
170
+ ## When `ao_metrics.enabled` is True, use `ao_metrics.availability_group` to specify the
171
+ ## resource group id of a specific availability group that you would like to monitor.
172
+ ## If no availability group is specified, then we will collect AlwaysOn metrics for all
171
173
## availability groups on the current replica.
172
174
##
173
175
## Primary replicas may emit metrics for remote secondary replicas
@@ -179,11 +181,11 @@ instances:
179
181
# ao_metrics: {}
180
182
181
183
## @param db_fragmentation_metrics - mapping - optional
182
- ## Configure collection of database fragmentation metrics.
183
- ## Note these queries can be resource intensive on large datasets. Recommend to limit these via
184
+ ## Configure collection of database fragmentation metrics.
185
+ ## Note these queries can be resource intensive on large datasets. Recommend to limit these via
184
186
## autodiscovery or specific database instances.
185
187
##
186
- ## Set `db_fragmentation_metrics.enabled` to true to enable collection of
188
+ ## Set `db_fragmentation_metrics.enabled` to true to enable collection of
187
189
## database index fragmentation statistics. Defaults to false.
188
190
##
189
191
## Use `db_fragmentation_metrics.enabled_tempdb` to enable collection of database index fragmentation statistics
@@ -247,7 +249,7 @@ instances:
247
249
# master_files_metrics: {}
248
250
249
251
## @param primary_log_shipping_metrics - mapping - optional
250
- ## Configure collection of metrics for a log shipping setup. Required to run against the
252
+ ## Configure collection of metrics for a log shipping setup. Required to run against the
251
253
## primary instance in a transaction log shipping configuration. Note that
252
254
## the Datadog user needs to be present in msdb and must be added to the db_datareader role.
253
255
##
@@ -257,7 +259,7 @@ instances:
257
259
# primary_log_shipping_metrics: {}
258
260
259
261
## @param secondary_log_shipping_metrics - mapping - optional
260
- ## Configure collection of metrics for a log shipping setup. Required to run against the
262
+ ## Configure collection of metrics for a log shipping setup. Required to run against the
261
263
## secondary instance in a transaction log shipping configuration. Note that
262
264
## the Datadog user needs to be present in msdb and must be added to the db_datareader role.
263
265
##
@@ -277,13 +279,13 @@ instances:
277
279
## @param tempdb_file_space_usage_metrics - mapping - optional
278
280
## Configure collection of tempdb file space usage metrics for how space is used in tempdb data files.
279
281
##
280
- ## Set `tempdb_file_space_usage_metrics.enabled` to true to enable collection of
282
+ ## Set `tempdb_file_space_usage_metrics.enabled` to true to enable collection of
281
283
## tempdb file space usage metrics. Defaults to true.
282
284
#
283
285
# tempdb_file_space_usage_metrics: {}
284
286
285
287
## @param xe_metrics - mapping - optional
286
- ## Configure collection of extended events (XE) metrics.
288
+ ## Configure collection of extended events (XE) metrics.
287
289
##
288
290
## Set `xe_metrics.enabled` to true to enable collection of extended events metrics. Defaults to false.
289
291
#
@@ -647,12 +649,12 @@ instances:
647
649
# keep_identifier_quotation: false
648
650
649
651
## Configure the collection of raw query statements in query activity, execution plans, and XE events.
650
- ## To collect raw query statements from XE events, set `xe_collection.query_completions.enabled` and
652
+ ## To collect raw query statements from XE events, set `xe_collection.query_completions.enabled` and
651
653
## `xe_collection.query_errors.enabled` to `true`.
652
654
## Raw query statements and execution plans may contain sensitive information (e.g., passwords)
653
655
## or personally identifiable information in query text.
654
- ## Enabling this option will allow the collection and ingestion of raw query statements and
655
- ## execution plans into Datadog, which can then become viewable in query samples or explain plans.
656
+ ## Enabling this option will allow the collection and ingestion of raw query statements and
657
+ ## execution plans into Datadog, which can then become viewable in query samples or explain plans.
656
658
## This option is disabled by default.
657
659
## Note: Collection of raw query statements is currently in preview.
658
660
## If you are interested in participating, please reach out to your Datadog Customer Success Manager.
@@ -703,7 +705,7 @@ instances:
703
705
## of the item in this column:
704
706
## i. tag - This is the default tag type
705
707
## ii. tag_list - This allows multiple values to be attached
706
- ## to the tag name. For example:
708
+ ## to the tag name. For example:
707
709
##
708
710
## query = {
709
711
## "name": "example",
@@ -730,9 +732,9 @@ instances:
730
732
## 3. tags (optional) - A list of tags to apply to each metric.
731
733
## 4. collection_interval (optional) - The frequency at which to collect the metrics.
732
734
## If collection_interval is not set, the query will be run every check run.
733
- ## If the collection interval is less than check collection interval,
735
+ ## If the collection interval is less than check collection interval,
734
736
## the query will be run every check run.
735
- ## If the collection interval is greater than check collection interval,
737
+ ## If the collection interval is greater than check collection interval,
736
738
## the query will NOT BE RUN exactly at the collection interval.
737
739
## The query will be run at the next check run after the collection interval has passed.
738
740
## 5. metric_prefix (optional) - The prefix to apply to each metric.
@@ -813,12 +815,12 @@ instances:
813
815
##
814
816
## Set `query_completions.enabled` to `true` to enable the collection of query completion events.
815
817
##
816
- ## Use `query_completions.collection_interval` to set the interval (in seconds) for the collection of
818
+ ## Use `query_completions.collection_interval` to set the interval (in seconds) for the collection of
817
819
## query completion events. Defaults to 10 seconds. If you intend on updating this value,
818
820
## it is strongly recommended to use a consistent value throughout all SQL Server agent deployments.
819
821
##
820
- ## Use `query_completions.max_events` to set the maximum number of query completion events to process
821
- ## per collection. Note that SQL Server's ring buffer has a maximum of 1000 events per query,
822
+ ## Use `query_completions.max_events` to set the maximum number of query completion events to process
823
+ ## per collection. Note that SQL Server's ring buffer has a maximum of 1000 events per query,
822
824
## so values above 1000 will still be capped at 1000 by the database engine. Defaults to 1000.
823
825
#
824
826
# query_completions: {}
@@ -828,12 +830,12 @@ instances:
828
830
##
829
831
## Set `query_errors.enabled` to `true` to enable the collection of query error events.
830
832
##
831
- ## Use `query_errors.collection_interval` to set the interval (in seconds) for the collection of
833
+ ## Use `query_errors.collection_interval` to set the interval (in seconds) for the collection of
832
834
## query error events. Defaults to 10 seconds. If you intend on updating this value,
833
835
## it is strongly recommended to use a consistent value throughout all SQL Server agent deployments.
834
836
##
835
- ## Use `query_errors.max_events` to set the maximum number of query error events to process
836
- ## per collection. Note that SQL Server's ring buffer has a maximum of 1000 events per query,
837
+ ## Use `query_errors.max_events` to set the maximum number of query error events to process
838
+ ## per collection. Note that SQL Server's ring buffer has a maximum of 1000 events per query,
837
839
## so values above 1000 will still be capped at 1000 by the database engine. Defaults to 1000.
838
840
#
839
841
# query_errors: {}
0 commit comments