Zipkin 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>The Zipkin Input Plugin allows for the collection of tracing information and timing data from microservices. This capability is essential for diagnosing latency troubles within complex service-oriented environments.</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
Zipkin
<p>This plugin implements the Zipkin HTTP server to gather trace and timing data necessary for troubleshooting latency issues in microservice architectures. Zipkin is a distributed tracing system that helps gather timing data across various microservices, allowing teams to visualize the flow of requests and identify bottlenecks in performance. The plugin offers support for input traces in JSON or thrift formats based on the specified Content-Type. Additionally, it utilizes span metadata to track the timing of requests, enhancing the observability of applications that adhere to the OpenTracing standard. As an experimental feature, its configuration and schema may evolve over time to better align with user requirements and advancements in distributed tracing methodologies.</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
Zipkin
AWS Timestream
Input and output integration examples
Zipkin
<ol> <li> <p><strong>Latency Monitoring in Microservices</strong>: Use the Zipkin Input Plugin to capture and analyze tracing data from a microservices architecture. By visualizing the request flow and pinpointing latency sources, development teams can optimize service interactions, improve response times, and ensure a smoother user experience across services.</p> </li> <li> <p><strong>Performance Optimization in Essential Services</strong>: Integrate the plugin within critical services to monitor not only the response times but also track specific annotations that could highlight performance issues. The ability to gather span data can help prioritize areas needing performance enhancements, leading to targeted improvements.</p> </li> <li> <p><strong>Dynamic Service Dependency Mapping</strong>: With the collected trace data, automatically map service dependencies and visualize them in dashboards. This helps teams understand how different services interact and the impact of failures or slowdowns, ultimately leading to better architectural decisions and faster resolutions of issues.</p> </li> <li> <p><strong>Anomaly Detection in Service Latency</strong>: Combine Zipkin data with machine learning models to detect unusual patterns in service latencies and request processing times. By automatically identifying anomalies, operations teams can respond proactively to emerging issues before they escalate into critical failures.</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