Type to search.

MSSQL module

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

This is the Microsoft SQL 2017 Metricbeat module. It is still under active development to add new Metricsets and introduce enhancements.

The module is being tested with 2017 GA version under Linux

1.transaction_log :

  • sys.databases
  • sys.dm_db_log_space_usage
  • sys.dm_db_log_stats(DB_ID)

2.performance :

  • sys.dm_os_performance_counters

If you browse MSDN for above tables, you will find "Permissions" section which defines the permission needed, e.g Permissions

The following Metricsets are already included:

transaction_log Metricset fetches information about the operation and transaction log of each MSSQL database in the monitored instance. All data is extracted from the Database Dynamic Management Views

performance Metricset fetches information from what’s commonly known as Performance Counters in MSSQL.

When configuring the hosts option, you can specify native user credentials as part of the host string with the following format:

Text
hosts: ["sqlserver://sa@localhost"]

To use Active Directory domain credentials, you can separately specify the username and password using the respective configuration options to allow the domain to be included in the username:

Text
metricbeat.modules:
- module: mssql
  metricsets:
    - "transaction_log"
    - "performance"
  hosts: ["sqlserver://localhost"]
  username: domain\username
  password: verysecurepassword
  period: 10

Store sensitive values like passwords in the secrets keystore.

The MSSQL module supports the standard configuration options that are described in Modules. Here is an example configuration:

YAML
metricbeat.modules:
- module: mssql
  metricsets:
    - "transaction_log"
    - "performance"
  hosts: ["sqlserver://localhost"]
  username: domain\username
  password: verysecurepassword
  period: 10s

The following metricsets are available: