Ronny Trommer

:+1: yes agree, one of the main features to allow discussion about code or configuration via IRC.

@dino2gnt yes it would make sense to disable telemetryd by default, cause we have external dependencies which need to be installed and deployed first before we can enable telemetryd.

> > @dino2gnt yes it would make sense to disable telemetryd by default, cause we have external dependencies which need to be installed and deployed first before we can enable...

The problem is someone can push your OpenNMS into unpredictable behavior by just enabling flows and sending it to OpenNMS. This happens pretty easily, especially if you have OpenNMS running...

> The problem is someone can push your OpenNMS into unpredictable behavior by just enabling flows and sending it to OpenNMS. This happens pretty easily, especially if you have OpenNMS...

> To solve this problem as @j-white would like to see it, we would need a neutral NOOP strategy for our non-existing external dependencies. I would vote -0 for this...

An example of unwanted behavior if you have unused open ports: https://www.youtube.com/watch?v=qFR8weCbMTM

> > Does this problem not occur when flows are configured with the external dependencies in place, or is this a bug in the listener/parser/adapter that should be addressed separately?...

Hello, @ssuman-opennms can you please spend a little bit more love when you create PR`s? See here: 

It seems like still an issue in Alpine 3.14.0 right? Here is what I've tested running Alpine in Docker with a simple Makefile: ```bash .PHONY: test test: @echo "Hello World"...