Save processing and data by easily filtering unneeded metrics before shipping with observIQ’s distribution of the OpenTelemetry Collector.
Join the DZone community and get the full member experience.
In this tutorial, we will address the common monitoring use case of filtering metrics within observIQ’s distribution of the OpenTelemetry (OTEL) collector. Whether the metrics are deemed unnecessary, or they are filtered for security concerns, the process is fairly straightforward.
For our sample environment, we will use MySQL on Red Hat Enterprise Linux 8. The destination exporter will be to Google Cloud Operations, but the process is exporter agnostic. We are using this exporter to provide the visual charts showing the metric before and after filtering.
Once configured using the LPU I created, MySQL metrics should be flowing. For our purposes, we will focus on the specific metric mysql.buffer_pool.limit. Currently, our config.yaml MySQL section looks like this:
After waiting for at least five minutes to get a good amount of data, metrics will look something like this in Google’s Metrics Explorer:
Now that metrics are flowing, we can filter them.
