Microsoft SQL server receiver 🔗

The Microsoft SQL Server receiver queries and retrieves metrics from Microsoft SQL Server instances. The supported pipeline type is metrics. See Process your data with pipelines for more information.

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.

Note

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

Get started 🔗

Follow these steps to configure and activate the component:

Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:

Install the Collector for Linux with the installer script

Install the Collector for Windows with the installer script

Install the Collector for Kubernetes

Configure the MSSQL Server receiver as described in the next section.
Restart the Collector.

Sample configuration 🔗

To activate the receiver, add sqlserver to the receivers section of your configuration file:

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

Next, include the receiver in the metrics pipeline of the service section of your configuration file:

service:
  pipelines:
    metrics:
      receivers:
        - sqlserver

Configure a named instance on Windows 🔗

If you’re using a named instance on Windows, you need to specify a computer and instance name, for example:

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

Advanced configuration 🔗

The following settings are optional:

collection_interval. 10s by default. The interval at which the receiver emits metrics.
instance_name. Optional. The instance name identifies the specific SQL Server instance to monitor. If unspecified, metrics are scraped from all instances. If configured, you must also set computer_name when running on Windows.

These are the optional direct connection options:

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 the SQL Server instance to connect to.
port. Port of the SQL Server instance to connect to.

The following are Windows-specific optional options:

computer_name. The computer name identifies the SQL Server name or IP address of the computer being monitored. If specified, instance_name is also required. This option is ignored in non-Windows environments.

Settings 🔗

The following table shows the configuration options for the Microsoft SQL server receiver:

Metrics 🔗

The following metrics, resource attributes, and attributes, are available.

Activate or deactivate specific metrics 🔗

You can activate or deactivate specific metrics by setting the enabled field in the metrics section for each metric. For example:

receivers:
  samplereceiver:
    metrics:
      metric-one:
        enabled: true
      metric-two:
        enabled: false

The following is an example of host metrics receiver configuration with activated metrics:

receivers:
  hostmetrics:
    scrapers:
      process:
        metrics:
          process.cpu.utilization:
            enabled: true

Note

Deactivated metrics aren’t sent to Splunk Observability Cloud.

Troubleshooting 🔗

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Submit a case in the Splunk Support Portal .
Call Splunk Customer Support .

Available to prospective customers and free trial users

Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success .

Related Topics