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 multiple ISP lines #11

Open
elekgeek opened this issue Jun 25, 2020 · 1 comment
Open

monitoring multiple ISP lines #11

elekgeek opened this issue Jun 25, 2020 · 1 comment

Comments

@elekgeek
Copy link

elekgeek commented Jun 25, 2020

Hi,

Thank you so much for the work you have done on this, really awesome!

Can you please help on how to monitor multiple ISP lines. The script works perfectly, but I need to be able to monitor multiple lines, is it I have to install linux+zabbix_agent on a different place and allow that machine through the FW on that ISP line in order to be able to monitor that specific line? I am not sure if this is how you planned this excellent piece of art :)
Do you have better ideas? I am all ears to be honest.

thanks a lot

@pschmitt
Copy link
Owner

That's kinda tricky to implement. The underlying Speedtest tool does not have any flag or config option to set the gateway, or the network device to use for the benchmark.

Now, what I would do to effectively monitor the bandwidth of 2 separate WANs on a single host is to setup 2 docker containers on said host. Both will be running zabbix-agent(2).
You should be able to easily create virtual bridges for the containers so that their WAN traffic is routed through the right NIC. Or you could setup static routing for the containers (you'll obviously need static IPS for your containers - which is possible as well). I recommend the former since messing with Docker's routing is generally not recommended.

Then each zabbix-agent container should listen on its own port and you'll need to set them up as 2 separate hosts on your zabbix server. Voilà. That's how I'd do it. Now this obviously only is feasible if your host is capable of running containers...

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

2 participants