SNMP 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
The SNMP plugin allows you to collect a variety of metrics from SNMP (Simple Network Management Protocol) agents. It provides flexibility in how data is retrieved, whether collecting single metrics or entire tables.
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.
Integration details
SNMP
This plugin uses polling to gather metrics from SNMP agents, supporting retrieval of individual OIDs and complete SNMP tables. It can be configured to handle multiple SNMP versions, authentication, and other features.
AWS Redshift
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.
Configuration
SNMP
[[inputs.snmp]]
agents = ["udp://127.0.0.1:161"]
[[inputs.snmp.field]]
oid = "RFC1213-MIB::sysUpTime.0"
name = "sysUptime"
conversion = "float(2)"
[[inputs.snmp.field]]
oid = "RFC1213-MIB::sysName.0"
name = "sysName"
is_tag = true
[[inputs.snmp.table]]
oid = "IF-MIB::ifTable"
name = "interface"
inherit_tags = ["sysName"]
[[inputs.snmp.table.field]]
oid = "IF-MIB::ifDescr"
name = "ifDescr"
is_tag = true
AWS Redshift
[[outputs.postgresql]]
## Redshift connection settings
host = "redshift-cluster.example.us-west-2.redshift.amazonaws.com"
port = 5439
user = "telegraf"
password = "YourRedshiftPassword"
database = "metrics"
sslmode = "require"
## Optional: specify a dynamic table template for inserting metrics
table_template = "telegraf_metrics"
## Note: Redshift does not support all PostgreSQL features; ensure your table exists and is compatible
Input and output integration examples
SNMP
- Basic SNMP Configuration: Collect metrics from a local SNMP agent using typical SNMP community string settings. This setup is ideal for local monitoring of device performance.
- Advanced SNMPv3 Setup: Securely collect metrics using SNMPv3 with authentication and encryption to enhance security. This configuration is recommended for production environments.
- Collect Interface Metrics: Configure the plugin to collect interface metrics from the device’s SNMP table. Utilize fields to capture specific data points for traffic analysis.
- Join Two SNMP Tables: By using translation fields, join data from two SNMP tables for a comprehensive view of correlated performance metrics.
AWS Redshift
-
Business-Aware Infrastructure Monitoring: 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.
-
Historical Trend Analysis for Cloud Resources: 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.
-
Security Auditing of System Behavior: 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.
-
Cross-Environment SLA Reporting: 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.
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