Add scheduling option to alerting
Use Case: Provider I am a provider with a substantial amount of customers being monitored by the platform. A single customer requests monitoring to be suspended for 14 days as they do a physical DC move. The move will be 1:1 so all systems will come back up in same logical location and only move physical locations. Requests are filed, meetings are had and the day comes to move and NOC turns alerting off for customer. Uneventful days go by and on the day that alerting is supposed to be turned back on a regional event happens that the provider NOC is responding to for other customers(You can insert any normal well defined chaos that happens in a NOC here) and alerting does not get re-enabled for the customer with the physical DC move. Enterprise: Oracle team notifies the NOC that a weekend upgrade will be happening on the Oracle customer and the upgrade team does not want to be notified of any alarms as they will have their hands full with the upgrade and they will call back when the upgrade is complete. NOC turns alerting off and upgrade team never calls to say that they are done working. Request: Much like SDT enable calendaring and scheduling as a option for enabling/disabling alerting as a backup option in case of failure in manual processes.2Views0likes0CommentsUser Containers
Use Case: I am a provider with loads of customers using the system. Operators working on MACs must navigate the flat user tree looking for specific users for any number of a myriad of reasons. One of the main use cases for this feature is to avoid mix ups when multiple customers have very similar names only differentiated by domain. Think Jim Smith as an example. Request: Looking for a way to “containerize” users in the User Access -> Users tab. It would be extremely cool and helpful to be able to add groups on this screen to contain customer’s users in a single bucket. I would love for this to occur by adding metadata/tags to a user when it is created. I would then create groups just like we do when we create devices and auto-assign users to them based on the metadata entered for the user. If the auto-assign is robust enough you could really make this interesting by using a standard query of metadata + role to get the structure below: MSP Admin Operator Cst 1 Role 1 Users Role 2 Users Cst 2 Role 4 Cst N Role N Users0Views0likes0Comments