Docker and Apache Hudi Integration

Input and output integration overview

<p>The Docker input plugin allows you to collect metrics from your Docker containers using the Docker Engine API, facilitating enhanced visibility and monitoring of containerized applications.</p>

<p>Writes metrics to Parquet files via Telegraf’s Parquet output plugin, preparing them for ingestion into Apache Hudi’s lakehouse architecture.</p>

Integration details

Docker

<p>The Docker input plugin for Telegraf gathers valuable metrics from the Docker Engine API, providing insights into running containers. This plugin utilizes the Official Docker Client to interface with the Engine API, allowing users to monitor various container states, resource allocations, and performance metrics. With options for filtering containers by names and states, along with customizable tags and labels, this plugin supports flexibility in monitoring containerized applications in diverse environments, whether on local systems or within orchestration platforms like Kubernetes. Additionally, it addresses security considerations by requiring permissions for accessing Docker’s daemon and emphasizes proper configuration when deploying within containerized environments.</p>

Apache Hudi

<p>This configuration leverages Telegraf’s Parquet plugin to serialize metrics into columnar Parquet files suitable for downstream ingestion by Apache Hudi. The plugin writes metrics grouped by metric name into files in a specified directory, buffering writes for efficiency and optionally rotating files on timers. It considers schema compatibility—metrics with incompatible schemas are dropped—ensuring consistency. Apache Hudi can then consume these Parquet files via tools like DeltaStreamer or Spark jobs, enabling transactional ingestion, time-travel queries, and upserts on your time series data.</p>

Configuration

Docker

Apache Hudi

Input and output integration examples

Docker

<ol> <li> <p><strong>Monitoring the Performance of Containerized Applications</strong>: Use the Docker input plugin in order to track the CPU, memory, disk I/O, and network activity of applications running in Docker containers. By collecting these metrics, DevOps teams can proactively manage resource allocation, troubleshoot performance bottlenecks, and ensure optimal application performance across different environments.</p> </li> <li> <p><strong>Integrating with Kubernetes</strong>: Leverage this plugin to gather metrics from Docker containers orchestrated by Kubernetes. By filtering out unnecessary Kubernetes labels and focusing on key metrics, teams can streamline their monitoring solutions and create dashboards that provide insights into the overall health of microservices running within the Kubernetes cluster.</p> </li> <li> <p><strong>Capacity Planning and Resource Optimization</strong>: Use the metrics collected by the Docker input plugin to perform capacity planning for Docker deployments. Analyzing usage patterns helps identify underutilized resources and over-provisioned containers, guiding decisions on scaling up or down based on actual usage trends.</p> </li> <li> <p><strong>Automated Alerting for Container Anomalies</strong>: Set up alerting rules based on the metrics collected through the Docker plugin to notify teams of unusual spikes in resource usage or service disruptions. This proactive monitoring approach helps maintain service reliability and optimize the performance of containerized applications.</p> </li> </ol>

Apache Hudi

<ol> <li> <p><strong>Transactional Lakehouse Metrics</strong>: Buffer and write Web service metrics as Parquet files for DeltaStreamer to ingest into Hudi, enabling upserts, ACID compliance, and time-travel on historical performance data.</p> </li> <li> <p><strong>Edge Device Batch Analytics</strong>: Telegraf running on IoT gateways writes metrics to Parquet locally, where periodic Spark jobs ingest them into Hudi for long-term analytics and traceability.</p> </li> <li> <p><strong>Schema-Enforced Abnormal Metric Handling</strong>: Use Parquet plugin’s strict schema-dropping behavior to prevent malformed or unexpected metric changes. Hudi ingestion then guarantees consistent schema and data quality in downstream datasets.</p> </li> <li> <p><strong>Data Platform Integration</strong>: Store Telegraf metrics as Parquet files in an S3/ADLS landing zone. Hudi’s Spark-based ingestion pipeline then loads them into a unified, queryable lakehouse with business events and logs.</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.