NSQ and AWS Redshift Integration
Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.
5B+
Telegraf downloads
#1
Time series database
Source: DB Engines
1B+
Downloads of InfluxDB
2,800+
Contributors
Table of Contents
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 NSQ Telegraf plugin reads metrics from the NSQD messaging system, allowing for real-time data processing and monitoring.</p>
<p>This plugin enables Telegraf to send metrics to Amazon Redshift using the PostgreSQL plugin, allowing metrics to be stored in a scalable, SQL-compatible data warehouse.</p>
Integration details
NSQ
<p>The NSQ plugin interfaces with NSQ, a real-time messaging platform, enabling the reading of messages from NSQD. This plugin is categorized as a service plugin, meaning it actively listens for metrics and events rather than polling them at regular intervals. With an emphasis on reliability, it prevents data loss by tracking undelivered messages until they are acknowledged by outputs. The plugin allows for configurations such as specifying NSQLookupd endpoints, topics, and channels, and it supports multiple data formats for flexibility in data handling.</p>
AWS Redshift
<p>This configuration uses the Telegraf PostgreSQL plugin to send metrics to Amazon Redshift, AWS’s fully managed cloud data warehouse that supports SQL-based analytics at scale. Although Redshift is based on PostgreSQL 8.0.2, it does not support all standard PostgreSQL features such as full JSONB, stored procedures, or upserts. Therefore, care must be taken to predefine compatible tables and schema when using Telegraf for Redshift integration. This setup is ideal for use cases that benefit from long-term, high-volume metric storage and integration with AWS analytics tools like QuickSight or Redshift Spectrum. Metrics stored in Redshift can be joined with business datasets for rich observability and BI analysis.</p>
Configuration
NSQ
AWS Redshift
Input and output integration examples
NSQ
<ol> <li> <p><strong>Real-Time Analytics Dashboard</strong>: Integrate this plugin with a visualization tool to create a dashboard that displays real-time metrics from various topics in NSQ. By subscribing to specific topics, users can monitor system health and application performance dynamically, allowing for immediate insights and timely responses to any anomalies.</p> </li> <li> <p><strong>Event-Driven Automation</strong>: Combine NSQ with a serverless architecture to trigger automated workflows based on incoming messages. This use case could involve processing data for machine learning models or responding to user actions in applications, thus streamlining operations and enhancing user experience through rapid processing.</p> </li> <li> <p><strong>Multi-Service Communication Hub</strong>: Use the NSQ plugin to act as a centralized messaging hub among different microservices in a distributed architecture. By enabling services to communicate through NSQ, developers can ensure reliable message delivery while maintaining decoupled service interactions, significantly improving scalability and resilience.</p> </li> <li> <p><strong>Metrics Aggregation for Enhanced Monitoring</strong>: Implement the NSQ plugin to aggregate metrics from multiple sources before sending them to an analytics tool. This setup enables businesses to consolidate data from various applications and services, creating a unified view for better decision-making and strategic planning.</p> </li> </ol>
AWS Redshift
<ol> <li> <p><strong>Business-Aware Infrastructure Monitoring</strong>: Store infrastructure metrics from Telegraf in Redshift alongside sales, marketing, or customer engagement data. Analysts can correlate system performance with business KPIs using SQL joins and window functions.</p> </li> <li> <p><strong>Historical Trend Analysis for Cloud Resources</strong>: Use Telegraf to continuously log CPU, memory, and I/O metrics to Redshift. Combine with time-series SQL queries and visualization tools like Amazon QuickSight to spot trends and forecast resource demand.</p> </li> <li> <p><strong>Security Auditing of System Behavior</strong>: Send metrics related to system logins, file changes, or resource spikes into Redshift. Analysts can build dashboards or reports for compliance auditing using SQL queries across multi-year data sets.</p> </li> <li> <p><strong>Cross-Environment SLA Reporting</strong>: Aggregate SLA metrics from multiple cloud accounts and regions using Telegraf, and push them to a central Redshift warehouse. Enable unified SLA compliance dashboards and executive reporting via a single SQL interface.</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.
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
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 IntegrationKafka 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 IntegrationKinesis 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