Kubernetes and AWS Timestream 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>This plugin captures metrics for Kubernetes pods and containers by communicating with the Kubelet API.</p>
<p>The AWS Timestream Telegraf plugin enables users to send metrics directly to Amazon’s Timestream service, which is designed for time series data management. This plugin offers a variety of configuration options for authentication, data organization, and retention settings.</p> <p>With the coming End of Life of AWS Timestream for LiveAnalytics, you can easily switch to AWS Timestream for InfluxDB or other verions of InfluxDB hosted on AWS by using the <a href="https://www.influxdata.com/integrations/influxdb/">InfluxDB Telegraf plugin</a>. Learn more about <a href="https://www.influxdata.com/influxdb-cloud-on-aws/">AWS and InfluxDB</a></p>
Integration details
Kubernetes
<p>The Kubernetes input plugin interfaces with the Kubelet API to gather metrics for running pods and containers on a single host, ideally as part of a daemonset in a Kubernetes installation. By operating on each node within the cluster, it collects metrics from the locally running kubelet, ensuring that the data reflects the real-time state of the environment. Being a rapidly evolving project, Kubernetes sees frequent updates, and this plugin adheres to the major cloud providers’ supported versions, maintaining compatibility across multiple releases within a limited time span. Significant consideration is given to the potential high series cardinality, which can burden the database; thus, users are advised to implement filtering techniques and retention policies to manage this load effectively. Configuration options provide flexible customization of the plugin’s behavior to integrate seamlessly into different setups, enhancing its utility in monitoring Kubernetes environments.</p>
AWS Timestream
<p>This plugin is designed to efficiently write metrics to Amazon’s Timestream for LiveAnalytics service. With AWS no longer accepting new users for their LiveAnalytics service, consider using the <a href="https://www.influxdata.com/integrations/influxdb/">InfluxDB plugin</a> with AWS Timestream for InfluxDB or other <a href="https://www.influxdata.com/influxdb-cloud-on-aws/">InfluxDB options available on AWS</a>. This plugin Telegraf can send data collected from various sources and supports a flexible configuration for authentication, data organization, and retention management. It utilizes a credential chain for authentication, allowing various methods such as web identity, assumed roles, and shared profiles. Users can define how metrics are organized in Timestream—whether to use a single table or multiple tables, alongside control over aspect such as retention periods for both magnetic and memory stores. A key feature is its ability to handle multi-measure records, enabling efficient data ingestion and helping to reduce the overhead of multiple writes. In terms of error handling, the plugin includes mechanisms for addressing common issues related to AWS errors during data writes, such as retry logic for throttling and the ability to create tables as needed.</p>
Configuration
Kubernetes
AWS Timestream
Input and output integration examples
Kubernetes
<ol> <li> <p><strong>Dynamic Resource Allocation Monitoring</strong>: By utilizing the Kubernetes plugin, teams can set up alerts for resource usage patterns across various pods and containers. This proactive monitoring approach enables automatic scaling of resources in response to specific thresholds—helping to optimize performance while minimizing costs during peak usage.</p> </li> <li> <p><strong>Multi-tenancy Resource Isolation Analysis</strong>: Organizations using Kubernetes can leverage this plugin to track resource consumption per namespace. In a multi-tenant scenario, understanding the resource allocations and usages across different teams becomes critical for ensuring fair access and performance guarantees, leading to better resource management strategies.</p> </li> <li> <p><strong>Real-time Health Dashboards</strong>: Integrate the data captured by the Kubernetes plugin into visualization tools like Grafana to create real-time dashboards. These dashboards provide insights into the overall health and performance of the Kubernetes environment, allowing teams to quickly identify and rectify issues across clusters, pods, and containers.</p> </li> <li> <p><strong>Automated Incident Response Workflows</strong>: By combining the Kubernetes plugin with alert management systems, teams can automate incident response procedures based on real-time metrics. If a pod’s resource usage exceeds predefined limits, an automated workflow can trigger remediation actions, such as restarting the pod or reallocating resources—all of which can help improve system resilience.</p> </li> </ol>
AWS Timestream
<ol> <li> <p><strong>IoT Data Metrics</strong>: Use the Timestream plugin to send real-time metrics from IoT devices to Timestream, allowing for quick analysis and visualization of sensor data. By organizing device readings into a time series format, users can track trends, identify anomalies, and streamline operational decisions based on device performance.</p> </li> <li> <p><strong>Application Performance Monitoring</strong>: Leverage Timestream alongside application monitoring tools to send metrics about service performance over time. This integration enables engineers to perform historical analysis of application performance, correlate it with business metrics, and optimize resource allocation based on usage patterns viewed over time.</p> </li> <li> <p><strong>Automated Data Archiving</strong>: Configure the Timestream plugin to write data to Timestream while simultaneously managing retention periods. This setup can automate archiving strategies, ensuring that older data is preserved according to predefined criteria. This is especially useful for compliance and historical analysis, allowing businesses to maintain their data lifecycle with minimal manual intervention.</p> </li> <li> <p><strong>Multi-Application Metrics Aggregation</strong>: Utilize the Timestream plugin to aggregate metrics from multiple applications into Timestream. By creating a unified database of performance metrics, organizations can gain holistic insights across various services, improving visibility into system-wide performance and facilitating cross-application troubleshooting.</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