I forgot we even had cnMaestro notifications turned on as gmail had been silently discarding them as spam (mostly) for ever up until the other evening. Now we are being inundated with “Major” notifications when customers power their radio off and on. This happens a lot as we have many customers who are off-grid and are in the habit of shutting things off when not in use.
It seems to me that with the lack of notification configurability maybe the cnMaestro team could re-classify SMs going offline/online less than a major event? Please? An AP going offline is “Major” as is another infrastructure element. Customer radios aren’t important to be notified about.
I’m not a software developer so please forgive me if I get the terminology wrong, but for our use case, cnMaestro has always been too process-driven in how it does things. My frustration in the first post is an example of this. We have to un-select a pre-determined thing to stop notifications that are built in to the system. Or perhaps, I selected those things at some point on accident. My point is, that we should be able to somewhat arbitrarily decide what triggers notifications and what doesn’t. Let me just right-click on a device or click the … next to it and have all options. This has always been the biggest issue I have with cnMaestro. It simply isn’t flexible.
I have to look up scheduling reboots pretty much every time I want to do it as it simply isn’t intuitive.
The process-driven approach is great if you want to update firmware on devices, but not flexible enough for real-world usage as a NMS. For cnMaestro to be truly useful to us, we need to be able to define the events that matter “to us” and also define the thresholds that trigger those notification events.
