5 hours ago, Tisch said:In my opinion, that is a terrible limitation as it works against the concept of using ABCGs.
Agreed.
5 hours ago, Tisch said:have all Collectors ingest traps and assign them to the proper resource/collector via some back-end mechanism
This is how syslog works with LM Logs. It can be done, but LM is pretty anti-traps, so they might not do it for traps any time soon (even though they likely could). Have you thought about samplicator? It could be a single point that your infrastructure can send to, and you can configure it to forward to one/all/specific collectors.
That said, I'll echo LM: what are you getting from traps that you aren't getting from polling? Seriously. If the answer is non-zero, in most cases, you can identify the values bound into the traps and poll them, eliminating the need for a trap. Not to mention EventSources don't have a concept of one trap to open the alert and a corresponding alert to close the trap.
