What is a one sentence summary of your feature request?
Built-in Automation for Monitoring Plans and Subscriptions
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Are there any plans to introduce built-in automation in Netwrix for routine tasks such as:
Cleanup of disabled monitoring plans
Creation or modification of monitoring plans and subscriptions
Basic error resolution actions
Having automation for these tasks would help reduce manual effort, minimize human error, and improve efficiency in day-to-day operations.
It would be great if the product team could consider this for future releases.
How do you currently solve the challenges you have by not having this feature?
Yes, we are able to manage these tasks manually, but it consumes a significant amount of time. After creating or modifying a plan, replication often takes some time and can sometimes result in errors, which adds to the delay and manual troubleshooting effort.
This is a great idea — working with monitoring plan configurations and subscriptions can definitely be time-consuming. Could you clarify what exactly you would like to automate for subscriptions? For example, do you mainly need to create, modify, and delete them, or do you have a standard set of subscriptions that should be automatically created during each installation? Also, would an API-based approach for managing these tasks be sufficient for your needs, or are you looking for built-in automation directly in the product UI?
For monitoring plans, we mainly need to create, modify, and later delete them (after disabling and keeping them for ~6 months). Even with correct permissions, new plans often throw errors and require manual troubleshooting.
For subscriptions, most tasks involve changing frequency, adding recipients, adding new OUs, and applying filters. In report-based subscriptions, the lack of filter options blocks us, and we often see delays or blank reports.
Our main goal is to reduce this manual work. Ideally, end users should be able to create their own subscriptions in the SSRS portal with limited input, while we have a central place to track all monitoring plans and subscriptions.
Between API or UI automation, we would prefer a UI-based solution built into the product. But both are okay.
For reference, here are some tickets where we faced significant challenges and spent considerable time, which also highlights our need for automation: 00454586, 00448739, 00450238.
For monitoring plans, this area is fairly non-trivial, and at the moment it will most likely remain a feature request. Once the PM team prioritizes it, a proper solution will be provided.
For subscriptions, there are options you can use via API (Early Access Feature):
GET configuration/subscriptions
Returns the full list of subscriptions of all four types with all parameters (SubscriptionsList.xml/json).
GET configuration/subscriptions/{id}
Returns details of a specific subscription by ID or name (SubscriptionsList.xml/json).
GET configuration/subscriptions/{id}/recipients
Returns all recipients of the specified subscription (SubscriptionRecipients.xml/json).
GET configuration/subscriptions/{id}/filters
Returns all filters of the specified subscription (format depends on subscription type, see SubscriptionsList.xml/json).
POST configuration/subscriptions
Adds new subscriptions. Accepts SubscriptionsList.xml/json or individual elements.
Collisions (duplicate IDs or names, both within the list and with existing subscriptions) are considered errors.
The response returns the IDs of created subscriptions along with their status (Added successfully / Already exists / Error).
POST configuration/subscriptions/{id}
Updates only the provided fields of an existing subscription.
If the subscription does not exist, an error is returned.
Provided filters or recipients replace the existing ones.
Fields not provided remain unchanged.
Creation of new subscriptions through this endpoint is not supported.
PUT configuration/subscriptions – Not supported.
PUT configuration/subscriptions/{id}
Fully replaces the content of an existing subscription, including type, recipients, and filters.
The specified ID/name must exist and must not conflict with another subscription.
The request must include all mandatory fields (Enabled, Name, Schedule, Filters, and type-specific tags).
PUT configuration/subscriptions/{id}/recipients
Replaces all recipients with the provided list (SubscriptionRecipients.xml/json).
Adding/removing/changing individual recipients is not currently supported.
PUT configuration/subscriptions/{id}/filters
Replaces all filters with the provided ones (format depends on subscription type).
DELETE configuration/subscriptions – Not supported.
DELETE configuration/subscriptions/{id}
Deletes the subscription specified by ID or name.
Thank you for the response. My intent was more towards having built-in automation within Netwrix itself rather than relying on API scripts. I would like to request this as a feature — the ability to automate monitoring plans and subscriptions directly in the product (e.g., through SSRS), so users can create and manage them without needing to involve the app owner.