To reproduce this behaviour I added two dummy notifiers in the sink, and a third one(tcp) which actually works, like this
~~~
publishers:
- notifier://172.17.1.121:5666/?driver=amqp&topic=cloud1-metering
- notifier://172.17.1.122:5667/?driver=amqp&topic=cloud1-metering
- tcp://127.0.0.1:3060
~~~
Even though the first 2 weren't reachable, metrics were being sent to the tcp publisher. Does such a behaviour blocks messaging publisher only ? It would be helpful if you could provide some more details to reproduce it.
Could you also try out using "max_retry" parameter like
~~~
- notifier://[notifier_ip]:[notifier_port]?topic=[topic]&driver=driver&max_retry=100
~~~
To reproduce this behaviour I added two dummy notifiers in the sink, and a third one(tcp) which actually works, like this //172.17. 1.121:5666/ ?driver= amqp&topic= cloud1- metering //172.17. 1.122:5667/ ?driver= amqp&topic= cloud1- metering 0.0.1:3060
~~~
publishers:
- notifier:
- notifier:
- tcp://127.
~~~
Even though the first 2 weren't reachable, metrics were being sent to the tcp publisher. Does such a behaviour blocks messaging publisher only ? It would be helpful if you could provide some more details to reproduce it.
Could you also try out using "max_retry" parameter like //[notifier_ ip]:[notifier_ port]?topic= [topic] &driver= driver& max_retry= 100
~~~
- notifier:
~~~