All Integrations / NATS and Microsoft SQL Server Integration

NATS and Microsoft SQL Server Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

Get This Integration for Free
info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider <a href="/integrations/nats_consumer-influxdb/">NATS and InfluxDB</a>.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

<p>The NATS Consumer Input Plugin enables real-time data consumption from NATS messaging subjects, integrating seamlessly into the Telegraf data pipeline for monitoring and metrics gathering.</p>

<p>Telegraf’s SQL plugin facilitates the storage of metrics in SQL databases. When configured for Microsoft SQL Server, it supports the specific DSN format and schema requirements, allowing for seamless integration with SQL Server.</p>

Integration details

NATS

<p>The NATS Consumer Plugin allows Telegraf to read metrics from specified NATS subjects and create metrics based on supported input data formats. Utilizing a Queue Group allows multiple instances of Telegraf to read from a NATS cluster in parallel, enhancing throughput and reliability. This plugin also supports various authentication methods, including username/password, NATS credentials files, and nkey seed files, ensuring secure communication with the NATS servers. It is particularly useful in environments where data persistence and message reliability are critical, thanks to features such as JetStream that facilitate the consumption of historical messages. Additionally, the ability to configure various operational parameters makes this plugin suitable for high-throughput scenarios while maintaining performance integrity.</p>

Microsoft SQL Server

<p>Telegraf’s SQL output plugin for Microsoft SQL Server is designed to capture and store metric data by dynamically creating tables and columns that match the structure of incoming data. This integration leverages the go-mssqldb driver, which follows the SQL Server connection protocol through a DSN that includes server, port, and database details. Although the driver is considered experimental due to limited unit tests, it provides robust support for dynamic schema generation and data insertion, enabling detailed time-stamped records of system performance. This flexibility makes it a valuable tool for environments that demand reliable and granular metric logging, despite its experimental status.</p>

Configuration

NATS

<pre><code class="language-toml">[[inputs.nats_consumer]] ## urls of NATS servers servers = ["nats://localhost:4222"] ## subject(s) to consume ## If you use jetstream you need to set the subjects ## in jetstream_subjects subjects = ["telegraf"] ## jetstream subjects ## jetstream is a streaming technology inside of nats. ## With jetstream the nats-server persists messages and ## a consumer can consume historical messages. This is ## useful when telegraf needs to restart it don't miss a ## message. You need to configure the nats-server. ## https://docs.nats.io/nats-concepts/jetstream. jetstream_subjects = ["js_telegraf"] ## name a queue group queue_group = "telegraf_consumers" ## Optional authentication with username and password credentials # username = "" # password = "" ## Optional authentication with NATS credentials file (NATS 2.0) # credentials = "/etc/telegraf/nats.creds" ## Optional authentication with nkey seed file (NATS 2.0) # nkey_seed = "/etc/telegraf/seed.txt" ## Use Transport Layer Security # secure = false ## Optional TLS Config # tls_ca = "/etc/telegraf/ca.pem" # tls_cert = "/etc/telegraf/cert.pem" # tls_key = "/etc/telegraf/key.pem" ## Use TLS but skip chain &amp; host verification # insecure_skip_verify = false ## Sets the limits for pending msgs and bytes for each subscription ## These shouldn't need to be adjusted except in very high throughput scenarios # pending_message_limit = 65536 # pending_bytes_limit = 67108864 ## Max undelivered messages ## This plugin uses tracking metrics, which ensure messages are read to ## outputs before acknowledging them to the original broker to ensure data ## is not lost. This option sets the maximum messages to read from the ## broker that have not been written by an output. ## ## This value needs to be picked with awareness of the agent's ## metric_batch_size value as well. Setting max undelivered messages too high ## can result in a constant stream of data batches to the output. While ## setting it too low may never flush the broker's messages. # max_undelivered_messages = 1000 ## Data format to consume. ## Each data format has its own unique set of configuration options, read ## more about them here: ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md data_format = "influx" </code></pre>

Microsoft SQL Server

<pre><code class="language-toml">[[outputs.sql]] ## Database driver ## Valid options: mssql (Microsoft SQL Server), mysql (MySQL), pgx (Postgres), ## sqlite (SQLite3), snowflake (snowflake.com), clickhouse (ClickHouse) driver = "mssql" ## Data source name ## For Microsoft SQL Server, the DSN typically includes the server, port, username, password, and database name. ## Example DSN: "sqlserver://username:password@localhost:1433?database=telegraf" data_source_name = "sqlserver://username:password@localhost:1433?database=telegraf" ## Timestamp column name timestamp_column = "timestamp" ## Table creation template ## Available template variables: ## {TABLE} - table name as a quoted identifier ## {TABLELITERAL} - table name as a quoted string literal ## {COLUMNS} - column definitions (list of quoted identifiers and types) table_template = "CREATE TABLE {TABLE} ({COLUMNS})" ## Table existence check template ## Available template variables: ## {TABLE} - table name as a quoted identifier table_exists_template = "SELECT 1 FROM {TABLE} LIMIT 1" ## Initialization SQL (optional) init_sql = "" ## Maximum amount of time a connection may be idle. "0s" means connections are never closed due to idle time. connection_max_idle_time = "0s" ## Maximum amount of time a connection may be reused. "0s" means connections are never closed due to age. connection_max_lifetime = "0s" ## Maximum number of connections in the idle connection pool. 0 means unlimited. connection_max_idle = 2 ## Maximum number of open connections to the database. 0 means unlimited. connection_max_open = 0 ## Metric type to SQL type conversion ## You can customize the mapping if needed. #[outputs.sql.convert] # integer = "INT" # real = "DOUBLE" # text = "TEXT" # timestamp = "TIMESTAMP" # defaultvalue = "TEXT" # unsigned = "UNSIGNED" # bool = "BOOL" </code></pre>

Input and output integration examples

NATS

<ol> <li> <p><strong>Real-Time Analytics Dashboard</strong>: Utilize the NATS plugin to gather metrics from various NATS subjects in real time and feed them into a centralized analytics dashboard. This setup allows for immediate visibility into live application performance, enabling teams to react swiftly to operational issues or performance degradation.</p> </li> <li> <p><strong>Distributed System Monitoring</strong>: Deploy multiple instances of Telegraf configured with the NATS plugin across a distributed architecture. This approach allows teams to aggregate metrics from various microservices efficiently, providing a holistic view of system health and performance while ensuring no messages are dropped during transmission.</p> </li> <li> <p><strong>Historical Message Recovery</strong>: Leverage the capabilities of NATS JetStream along with this plugin to recover and process historical messages after Telegraf has been restarted. This feature is particularly beneficial for applications that require high reliability, ensuring that no critical metrics are lost even in case of service disruptions.</p> </li> <li> <p><strong>Dynamic Load Balancing</strong>: Implement a dynamic load balancing scenario where Telegraf instances consume messages from a NATS cluster based on load. Adjust the queue group settings to control the number of active consumers, allowing for better resource utilization and performance scaling as demand fluctuations occur.</p> </li> </ol>

Microsoft SQL Server

<ol> <li> <p><strong>Enterprise Application Monitoring</strong>: Leverage the plugin to capture detailed performance metrics from enterprise applications running on SQL Server. This setup allows IT teams to analyze system performance, track transaction times, and identify bottlenecks across complex, multi-tier environments.</p> </li> <li> <p><strong>Dynamic Infrastructure Auditing</strong>: Deploy the plugin to create a dynamic audit log of infrastructure changes and performance metrics in SQL Server. This use case is ideal for organizations that require real-time monitoring and historical analysis of system performance for compliance and optimization.</p> </li> <li> <p><strong>Automated Performance Benchmarking</strong>: Use the plugin to continuously record and analyze performance metrics of SQL Server databases. This enables automated benchmarking, where historical data is compared against current performance, helping to quickly identify anomalies or degradation in service.</p> </li> <li> <p><strong>Integrated DevOps Dashboards</strong>: Integrate the plugin with DevOps monitoring tools to feed real-time metrics from SQL Server into centralized dashboards. This provides a holistic view of application health, allowing teams to correlate SQL Server performance with application-level events for faster troubleshooting and proactive maintenance.</p> </li> </ol>

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Useful Links

Documentation

Telegraf Quickstart Training

Infrastructure Monitoring with Telegraf

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration

Start building now

Download Telegraf today or learn more about InfluxDB.

telegraf Get started with InfluxDB
Product & Solutions
Developers
Company

548 Market St, PMB 77953
San Francisco, California 94104

© 2025 InfluxData Inc. All Rights Reserved.

Legal Security Cookie Policy Comparison