Skip to content

Latest commit

 

History

History
 
 

sqlserverreceiver

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
internal/metadata
internal/metadata
 
 
testdata
testdata
 
 
Makefile
Makefile
 
 
README.md
README.md
 
 
config.go
config.go
 
 
config_others.go
config_others.go
 
 
config_others_test.go
config_others_test.go
 
 
config_test.go
config_test.go
 
 
config_windows.go
config_windows.go
 
 
config_windows_test.go
config_windows_test.go
 
 
doc.go
doc.go
 
 
documentation.md
documentation.md
 
 
factory.go
factory.go
 
 
factory_others.go
factory_others.go
 
 
factory_others_test.go
factory_others_test.go
 
 
factory_test.go
factory_test.go
 
 
factory_windows.go
factory_windows.go
 
 
generated_component_test.go
generated_component_test.go
 
 
generated_package_test.go
generated_package_test.go
 
 
go.mod
go.mod
 
 
go.sum
go.sum
 
 
metadata.yaml
metadata.yaml
 
 
queries.go
queries.go
 
 
queries_test.go
queries_test.go
 
 
recorders.go
recorders.go
 
 
recorders_test.go
recorders_test.go
 
 
scraper.go
scraper.go
 
 
scraper_test.go
scraper_test.go
 
 
scraper_windows.go
scraper_windows.go
 
 
scraper_windows_test.go
scraper_windows_test.go
 
 

README.md

Microsoft SQL Server Receiver

Status
Stability beta: metrics
Distributions contrib
Issues Open issues Closed issues
Code Owners @djaglowski, @StefanKurek | Seeking more code owners!

The sqlserver receiver grabs metrics about a Microsoft SQL Server instance. The receiver works by either using the Windows Performance Counters, or by directly connecting to the instance and querying it. Windows Performance Counters are only available when running on Windows.

Make sure to run the collector as administrator in order to collect all performance counters for metrics.

Configuration

The following settings are optional:

  • collection_interval (default = 10s): The interval at which metrics should be emitted by this receiver.
  • instance_name (optional): The instance name identifies the specific SQL Server instance being monitored. If unspecified, metrics will be scraped from all instances. If configured, the computer_name must also be set when running on Windows.

Direct connection options (optional, but all must be specified to enable):

  • username: The username used to connect to the SQL Server instance.
  • password: The password used to connect to the SQL Server instance.
  • server: IP Address or hostname of SQL Server instance to connect to.
  • port: Port of the SQL Server instance to connect to.

Windows-specific options:

  • computer_name (optional): The computer name identifies the SQL Server name or IP address of the computer being monitored. If specified, instance_name is also required to be defined. This option is ignored in non-Windows environments.

Example:

    receivers:
      sqlserver:
        collection_interval: 10s
      sqlserver/1:
        collection_interval: 5s
        username: sa
        password: securepassword
        server: 0.0.0.0
        port: 1433

When a named instance is used on Windows, a computer name and a instance name must be specified. Example with named instance:

    receivers:
      sqlserver:
        collection_interval: 10s
        computer_name: CustomServer
        instance_name: CustomInstance
        resource_attributes:
          sqlserver.computer.name:
            enabled: true
          sqlserver.instance.name:
            enabled: true

The full list of settings exposed for this receiver are documented here with detailed sample configurations here.

Metrics

Details about the metrics produced by this receiver can be found in documentation.md