[Discussion] -3dBFS messages and more graphs1090 stuff maybe

[SaturnusDJ]

Current dashboard compared to graphs1090 is missing some graphs. I am pretty sure to get them it just requires some calculations with the metrics. So this is not really an issue, just a discussion.

So, for example the most important one missing now is -3dBFS messages percentage.

I looked up the metrics and thought it would be this: dump1090_stats_local_strong_signals{job="dump1090", time_period="last1min"} / dump1090_stats_messages_total{time_period="last1min"} *100. However compared to graphs1090 it looks a bit high every now and then.

(Note due to Docker timezone issue Graphs1090 time is 2 hours behind.)

See for example how 16:00 Graphs1090 / 18:00 Grafana, they report about 3% and 5% respectively.
Or 11:00 Graphs1090 / 13:00 Grafana, 5% and 8%.
Or 03:40 Graphs 1090 / 05:40 Grafana, 2% and 6-8%.

So I am doubting here. Wrong calculation, or just they way the metrics are rendered?

[claws]

Your proposed calculation seems right to me. I'm not familiar with graphs1090, maybe the metrics being compared are not identical.

[SaturnusDJ]

Thanks.

For people interested, here are some average lines:

Average aircrafts last week, same day, 2 hours average: avg_over_time(dump1090_recent_aircraft_observed{job="dump1090", time_period="latest"}[2h] offset 167h)

Average messages last week, same day, 2 hours average: avg_over_time(dump1090_stats_messages_total{job="dump1090", time_period="last1min"}[2h] offset 167h) / 60

Average range last week, same day, 12 hours average: avg_over_time(dump1090_recent_aircraft_max_range{job="dump1090", time_period="latest"}[12h] offset 162h)

(I found that offset (24*7)-(avg-value/2) lines out the graph the best.)

I disabled rate(dump1090_messages_total{job="dump1090", time_period="latest"}[1m]) because it gives strange results. The green line here:

In some weeks I hope to add some other useful queries and publish the full dashboard here.