Pre-Implementation Query re: Scaling & Limiting Monitoring Metrics

[Adam Yaqub]

We have a project that has about 5000 OpenWrt Routers that are used as hotspots in 1 town, mainly used by displaced refugees living in camps. We need to know whether particular routers are being used or not & if therefore whether they can be decomissioned - so Uptime & traffic needs to be monitored.

I wanted to know whether Openwisp can monitor this amount of devices practically & what kind of specifications the server requires. 

I have seen this post: https://groups.google.com/g/openwisp/c/RabNNnF7Aqk/m/yd7du7zFAAAJ

but tbh - I'm not experienced enough to know about specific horizontal scaling requirements. Can anyone help with some rough idea of what would be needed.

I would also like to know how to limit the metrics monitored to only uptime & specific interface traffic - I'm presuming that this would help in scaling? 

[Federico Capoano]

Hi Adam,

Regarding horizontal scaling, I don't have much to add in respect to what I wrote in https://groups.google.com/g/openwisp/c/RabNNnF7Aqk/m/yd7du7zFAAAJ:

You need to have the DBs on one VM (or cloud system) and the application deployed on multiple VMs. Vertical scaling of each VM is an easy solution to reach support for several thousands of devices easily.

This work is highly dependent on the use case and requirements. There's no "one fit all" solution yet.

Containerized applications can be used too, the challenge there is to configure the management tunnels in a way that the containerized cluster can talk to the management tunnels, VMs are definitely easier to handle in this regard.

The following docs should clarify and reply to the rest of your questions, I highly recommend to read everything:

- Monitoring Overview https://openwisp.io/docs/user/monitoring.html

- List of available monitoring features in current stable release: https://github.com/openwisp/openwisp-monitoring/tree/1.0#available-features

- Limiting monitored interfaces, see "monitored_interfaces" here: https://github.com/openwisp/openwrt-openwisp-monitoring/#configuration-options

If you want to put less stress on the system I also advise to bring down the interval of openwisp-config to 5 or 10 minutes instead of 2 minutes, ensure you have SSH push and management tunnel configured correctly to ensure speedy updates.

Best regards

Federico Capoano

OpenWISP OÜ

Harjumaa, Tallinn, Sepapaja tn 6, 15551

VAT: EE101989729

openwisp.io

--
You received this message because you are subscribed to the Google Groups "OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/f3ea67fd-8704-46b3-9b0a-ea75e8712863n%40googlegroups.com.