A receiver can look healthy in a browser while still showing a problem over a longer period. dump1090-exporter bridges compatible decoder JSON and Prometheus, making receiver behavior available to time-series dashboards and alert rules alongside the rest of your infrastructure.
Translate the data carefully
The exporter reads aircraft, receiver, and statistics endpoints. Missing observations should not silently become invented zeroes, and a decoder restart should not make a counter appear to run backward. Handling those details helps keep the resulting graphs interpretable when the source changes or temporarily disappears.
Keep labels under control
The metrics avoid turning every aircraft address into a label. That choice limits cardinality and keeps an observation tool from creating an unbounded collection of series. Receiver-level and aggregate measurements are a better fit for monitoring the health and broad behavior of a station.
Use metrics with context
A health endpoint supports service checks, while Prometheus can retain the measurements for later analysis. Pair the exporter with dashboards and alerts that reflect your own receiver's baseline. A low aircraft count may be normal at one location or hour and unusual at another.
Explore dump1090-exporter → · Source and documentation ↗