-
Notifications
You must be signed in to change notification settings - Fork 192
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
Port Statistics Dashboard Not Working #4229
Comments
I tried the latest port stats dashboard from this repo and am not having any issues, however it could just be something different with my setup. If you query Is I'm not a maintainer, so perhaps someone else can chime in, but it may be helpful to see your modified faucet and gauge config files. |
Could you elaborate on what the test using the grafana explorer looks like? Not really sure what I would have to do to test this. I'm using the docker-compose file from this repository that sets up all services so I see gauge running in docker. The gauge.yaml file is the one from the /etc/ folder in this repository. https://github.com/faucetsdn/faucet/blob/master/etc/faucet/gauge.yaml I can also see that the faucet and gauge controller are both connected to the ovs bridge so not really sure what the issue is.
|
In your Prometheus database you should have an |
I had the issue that after a fresh install the of_port_rx_bytes was missing in grafana. |
The port statistics dashboard appears to be broken. I have cloned a clean copy of this repo, changed the faucet.yml config to match my setup, configured grafana to talk to the prometheus data service and setup all dashboards accordingly. The other two dashboards show information as expected but the port statistics do not show any datapath names. I can manually enter them and it resolves the port list but no data is ever resolved.
I am running this via docker-compose so all the versions there are the versions being used. Is this a broken dashboard? Prometheus version issue? Some other compatibility issue with the dashboard itself?
The text was updated successfully, but these errors were encountered: