Hi, we are using DUDE to monitor our Network. We are a Network Connectivity Provider and we have several customers. We connect the offices of many customers using sections of our network.
It use to happen that when there is a problem with the provided connectivity service, the customer send us a compliance. But after check the problem, we noted that in many occasions the problem is not in our network, but it is inside the own customer's network.
We'd like to ask Mikrotik, to develope an API to split our Network in several pieces, using DUDE. Each piece of our network will correspond to the network section used to implement a connectivity network for each customer. Each of these pieces will be later loaded into a Customer Web Portal (to be implemented) to allow our customers verify the status of each section of our network used to provided them a connectivity service.
In this way, previous to send us a claim, the customer will be able to verify whether a problem in the service was caused in our network or it was caused inside their own internal network.
The target of this API is to reduce the quantity of claims from the customers to us and help them find a problem in their own network.
The challenge here is to find the way, with DUDE, how to split our network or just how to allow the see just a portion of DUDE: just the portion corresponding to the connectivity network implemented for such a customer.
Is this possible to develop? Many thanks in advance for your kind quick reply. Best regards

This sound like a feature request to implement granular permission in the Dude. Dude is not under active development right now, an Mikrotik plans about it is not so clear.

Related to your case, not sure how complex is your network, but a separate Dude per customer with full access to it should work. But if you have ten's, or even more, customers, that approach is not scalable.