Shipped minion flow listener config does not create a working listener
Description
While deploying a lab environment using minion for flow reception, i noticed the shipped config flow listener config does not create a working listener. However, creating a new config under a different name using the same configuration results in a listener on the specified port.
Makes sense. if traps/syslog are enabled by default, we can enable flows as well.
Dino Yancey February 1, 2021 at 6:52 PM
There may not be default config included in Minion (that I can find at a glance) for the other sinks, but they have enough config out of the box that they are listening:
...which I assume was the point of the `org.opennms.features.telemetry.listeners.flows.cfg` config.
If it's there it should work; if it can't be made to work it should be removed. Personally, i think having the listener configured out of the box would be a benefit. (It would have saved me several hours of head-scratching and tail chasing).
Chandra Gorantla February 1, 2021 at 4:51 PM
Edited
Looks like that is stale config. It has to be org.opennms.features.telemetry.listeners-****.cfg
Since we don't have default config for any of other listeners, I'm not sure if we need this here. I can remove this config so that it avoids confusion. Let me know what do you think.
While deploying a lab environment using minion for flow reception, i noticed the shipped config flow listener config does not create a working listener. However, creating a new config under a different name using the same configuration results in a listener on the specified port.
No listener on port 9999:
https://github.com/OpenNMS/opennms/blob/develop/features/container/minion/src/main/filtered-resources/etc/org.opennms.features.telemetry.listeners.flows.cfg
Listener on port 9999:
https://github.com/dino2gnt/opennms-gcp-playground-ansible/blob/main/roles/minion/files/org.opennms.features.telemetry.listeners-udp-9999.cfg
Also note: `parser` vs `parsers`.