-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
VNFRQTS Sprint 33
In version 7.1 of the VES Event Listener Specification, there was language that implied an operator may deploy multiple collector listener endpoints, and specific domains may be sent to specific endpoints.
In 7.1.1, this language was updated to clarify that while there are 2 VES endpoints (primary and secondary), all events regardless of the domain go to which ever VES endpoint is active.
A concern was raised that the language may still be ambiguous and the following recommendations were made:
_A single VES Event Listener may handle more than one type of VES event (different domains); i.e. same VES Event Listener can receive and process heartbeat, fault, measurement, syslog, etc. events.
Somehow, this indirectly suggests with “…may handle…”, that there are other options - that a number of domains can be handled by 1 instance of VES collector, and another group – by another collector instance. If we could adapt this sentence to sth like: “A single VES Event Listener handles all types of VES events (all domains defined in VES Common Event Schema); i.e. the NF is expected to configure a single VES Event Listener destination pair (active and standby) for all types of events.”, then it would be a little bit more straight-forward.
_