Apache Flink monitoring support is now available in the open-source OpenTelemetry collector. You can check out the OpenTelemetry repo here! You can utilize this receiver in conjunction with any OTel collector: including the OpenTelemetry Collector and other distributions of the collector.

Today we'll use observIQ’s OpenTelemetry distribution, and shipping Apache Flink telemetry to a popular backend: Google Cloud Ops. You can find out more on the GitHub page: https://github.com/observIQ/observiq-otel-collector

What Signals Matter?

Apache Flink is an open-source, unified batch processing and stream processing framework. The Apache Flink collector records 29 unique metrics, so there is a lot of data to pay attention to. Some specific metrics that users find valuable are:

• Uptime and restarts
  • Two different metrics that record the duration a job has continued uninterrupted, and the number of full restarts a job has committed, respectively.
• Checkpoints
  • A number of metrics monitoring checkpoints can tell you the number of active checkpoints, the number of completed and failed checkpoints, and the duration of ongoing and past checkpoints.
• Memory Usage
  • Memory-related metrics are often relevant to monitor. The Apache Flink collector ships metrics that can tell you about total memory usage, both present and over time, mins and maxes, and how the memory is divided between different processes.

All of the above categories can be gathered with the Apache Flink receiver — so let’s get started.

Before You Begin

If you don’t already have an OpenTelemetry collector built with the latest Apache Flink receiver installed, you’ll need to do that first. The Collector distro we're using includes the Apache Flink receiver (and many others) and is simple to install with a one-line installer.

Configuring the Apache Flink Receiver

Navigate to your OpenTelemetry configuration file. If you’re following along, you’ll find it in the following location: 

• /opt/observiq-otel-collector/config.yaml (Linux)

For the Collector, edit the configuration file to include the Apache Flink receiver as shown below:

receivers:
  flinkmetrics:
    endpoint: http://localhost:8081
    collection_interval: 10s

Processors:
  nop:
   # Resourcedetection is used to add a unique (host.name)
  # to the metric resource(s),...  target_key: namespace

exporters:
  nop:
    # Add the exporter for your preferred destination(s)

service:
  pipelines:
    metrics:
      receivers: [flinkmetrics]
      processors: [nop]
      exporters: [nop]

If you’re using the Google Ops Agent instead, you can find the relevant config file here.

Viewing the Metrics Collected

If you followed the steps detailed above, the following Apache Flink metrics will now be delivered to your preferred destination.

This OpenTelemetry collector can help companies looking to implement OpenTelemetry standards.