Skip to content
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

Monitoring LibreQOS #6

Closed
convergedmw opened this issue Jan 10, 2022 · 12 comments
Closed

Monitoring LibreQOS #6

convergedmw opened this issue Jan 10, 2022 · 12 comments
Milestone

Comments

@convergedmw
Copy link

Please advise if there is a way to monitor LibreQOS via a tool like LibreNMS or CheckMK? We have it nicely running inside our network and now I'd like to get our NOC to keep an eye on it...

@rchac
Copy link
Member

rchac commented Jan 22, 2022

Hello. I can definitely try my hand at it. Perhaps an SNMP interface so LibreNMS can graph it? What stats would you like to see on the monitoring? Thanks, Robert

@convergedmw
Copy link
Author

convergedmw commented Jan 22, 2022 via email

@syadnom
Copy link

syadnom commented Feb 26, 2022

What would be great is to extract the latency details (direct blow at preseem's measurements) to see TCP stats for customers.

throughput per site, per AP, per customer, per customer IP.

I would rather see this exported to a time series db like influx or promethius than via SNMP. That would expose the data to native and existing integrations with grafana and chart.js etc.

@rchac
Copy link
Member

rchac commented Feb 26, 2022

What would be great is to extract the latency details (direct blow at preseem's measurements) to see TCP stats for customers.

throughput per site, per AP, per customer, per customer IP.

I would rather see this exported to a time series db like influx or promethius than via SNMP. That would expose the data to native and existing integrations with grafana and chart.js etc.

Here is a sneak preview of v1.1.

@syadnom
Copy link

syadnom commented Feb 26, 2022

wha?!?!?!?! dude, this is incredible.

@syadnom
Copy link

syadnom commented Feb 26, 2022

my other comment brought this to mind. having throughput broken out into sites and APs would be fantastic

If we're overselling the peak speeds out, what matters to us is seeing mountains not plateaus and this really matters down to the AP level, but the site level would tell us if our backhaul setup was underperforming.

@rchac
Copy link
Member

rchac commented Feb 26, 2022

Thank you for the suggestion. Right now it breaks it down by AP (lowest level parent node) but I will think up how to display graphs by sites so tracking backhaul utilization is easier.

@syadnom
Copy link

syadnom commented Feb 26, 2022

since you're using influx, you could just put the AP name as an attribute so it could be grouped by in grafana.

@syadnom
Copy link

syadnom commented Feb 26, 2022

excuse me... SITE NAME...

@interduo
Copy link
Collaborator

#75 <--- I didn't find this issue earlier so I made duplicate and I describe there how I see this case.

@dtaht dtaht added this to the v1.3 milestone Nov 13, 2022
@dtaht
Copy link
Collaborator

dtaht commented Nov 13, 2022

I would like us to use this quote in the press release:

"wha?!?!?!?! dude, this is incredible."

@dtaht
Copy link
Collaborator

dtaht commented Nov 13, 2022

otherwise, closing.

@dtaht dtaht closed this as completed Nov 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants