-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway Loss and RTT not showing any values #64
Comments
@alexwmaustin In the dashboard variables, what did you put for the Gateway Variable? I get the same results as your "after", but nothing appears in the dashboard gateway/RTT section |
My gateway variables match the value from above. I would check on InfluxDB GUI that you are getting the values in the database first. That way you can determine whether its a Influx -> Grafana problem or OPNSense -> Influx |
First you have to follow the instructions of bsmithio. Replace the file with this one : Disable Telegraf in OPNSense. Test : sudo telegraf_pfifgw.php Enable Telegraf. This file is needed to get the the _measurement 'gateways' and the fields 'delay' and 'loss'. Edit : works with OPNSense 24.1.6 |
Unfortunately, I'm experiencing exactly the same issue as described above; it doesn't work. As a result, both the Gateway RTT and the interfaces remain empty. As atcbyea described, I get a clean response from 'pluginctl -r return_gateways_status'. However, even with
, no gateways are listed. Maybe someone will find a solution for this. Otherwise, the dashboard is really great. 20.08.2024 Update: In the Influx DB there is no entry for gateway or delay under _mesurment |
The metrics for RTT and loss weren't displaying any values. The
telegraf_pfifgw.php
usesreturn_gateways_status
to query these values.To enable the query properly go into System > Gateways > Configuration in opnsense and uncheck Disable Gateway Monitoring for each gateway.
Using the command
pluginctl -r return_gateways_status
you can view the output from this query.Before
After
The text was updated successfully, but these errors were encountered: