One server connected to 3 ISP and need to monitor those latency to some ip/websites .
Can heartbeat monitor ip/website via specific network interface ? or run some scripts (for change gateway ) after complete a round of monitoring .
One server connected to 3 ISP and need to monitor those latency to some ip/websites .
Can heartbeat monitor ip/website via specific network interface ? or run some scripts (for change gateway ) after complete a round of monitoring .
Hi @luckyclue,
Currently, there's no option available to specify the origin interface of a monitor. This is where we create a tcp connection for http monitors and since we are not specifying any local address, it is being resolved for us. Do you think this topic can be a possible workaround for your use case?
This is a great idea for a feature. we've opened an issue for it, but it's not a top priority since it's a very rare request. We'd gladly accept a contribution / PR however.
Thanks,
Kyungeun
netns ! I almost forget it . I think it's worth trying . Thx
Thanks!! FYI I've created a ticket in our beats repository if you'd like to track updates on this
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.