Usage of notification-watchers REST APIs

[RagsRachamadugu]

I'm using NSX-T 2.4 and my goal is to sync DFW group membership information from NSX-T. For this I registered a watcher using API "POST /api/v1/notification-watchers". After this it looks like I also need to add URI filters using "POST /api/v1/notification-watchers/<watcher_id>/notifications?action=add_uri_filters", which requires specifying of notification_id. The information about permitted values for notification_id is not present in the API documentation, which simply states

A string identifying feature_name.notification_name to indicate a notification watcher is interested in receiving notifications for the URI identified by the feature_name.notification_name.

I'm looking for a bit more documentation on the overall notification watcher including possible notification_id values. Highly appreciate any input in this regard.

Thanks Rags

[SRoland]

Hi,

Yeah, indeed there's not too much documentation in regards this, but be aware that this is currently experimental. It may be there in the next release as a fully exposed feature or will be removed. Not known yet.  Please note this as well!

So, as you may already know these parameters officially are defined as follows:

Name	Description	Type	Notes
notification_id	A string identifying feature_name.notification_name A string identifying feature_name.notification_name to indicate a notification watcher is interested in receiving notifications for the URI identified by the feature_name.notification_name.	string
uri_filters	Optional list of URIs	array of string

There might be a list for the "notification_id", but it is not currently exposed (I cannot find anything public yet).

Since notification feature is available for Service Insertion so I assume you work for a partner trying to utilize it. In that case it would be more advisable to engage through partner support channels to get the currently available list of parameters officially from our developers.

Having said that can you please elaborate a bit more on your request :

... my goal is to sync DFW group membership information from NSX-T...

What is the reason behind this? Cannot you sync from AD or LDAP directly? Maybe there are other ways to achieve what you want knowing the "big picture".

Thanks!

//Roland

Note: even though I work for VMware the notes here are mine and must not be treated as an official response from VMware.

[ReSTNSX]

Something that might help you out is ReSTNSX's policy sync tool - ReSTNSX-Policy Sync Tool - YouTube