Hi All,I want to know about monitor event Listener : monitorCreateEvent, monitorAttributeValueChangeEvent, monitorStateChangeEvent & monitorDeleteEvent.On which use case I will use these event in TMF 640 (serviceActivationandConfiguration).
Can you provide scenario example it would be a great help.
Hi ShivamThe Monitor pattern was introduced a while back, specifically for Service and Resource Activations, recognizing that the operation of activating or configuring in the network is likely to take time (seconds, minutes?). So as not to block a consumer thread, the API implementation allows definition of a monitor, which will notify the consumer when the activation request (POST/PATCH) is complete.It could be argued that this could be addressed in other ways, e.g. by events, or (in the future) by Async API.
can we use the monitor to query the previous activation or configuration that been done?
I don't think so, I would imagine that once the configuration/activation is complete the Monitor would disappear. However it does depend very strongly on the actual implementation of the API in the network itself (or in a software mediator).
You could interrogate the network directly (GET on Service/Resource in TMF640/TMF702), or the Inventory (TMF638/TMF639) to find the current state of a resource.
Hope it helps