API "industry" standard appears to be moving towards OAUTH and rotating authorization tokens. it would be great if SW could somehow support native alert trigger actions that support OAUTH and having to refresh access_tokens using a static 'refresh_token'.
Would like to be able to view Avery CPU & Memory for every 5 minutes for like the last Month if possible. Seems like I can only do 12 hours currently to get that 5 minute mark. Longer time period is prefered. Here is example from older version of NPM.
Enable user authentication to the web portal from multiple different active directory domains.
We are about to deploy agents in a slow rollout. I want to set up groups for linux and windows [agent] that dynamically assigns an agent process/svc monitor when polling type is agent. no way to do that right now (that I saw). Ultimately, I want to be able to set up an alert that looks for "unable to connect to agent",…
I like that I can go into my nodes and schedule a planned maintenance window in advance. This comes in handy when a service provider tells you there will be a maintenance window in the future and will affect one of your sites. HOWEVER, I'd love to have a place where I can go in and SEE all the maintenance windows that…
Custom Area Chart with scale which can show 100% on "y" axis, at present when we have multiple interfaces to display as a chart the percentage utilization varies on each & the auto scaling of the chart adjusts depending on the usage. It would be useful to with one standard "Y" Axis scaling so that when a manager/CIO looks…
Currently there is an Interface widget for Percent Utilization - Real Time Data This is not very useful for high bandwith interfaces that as a percentage have a low ammount of traffic It would be better if there was a In/Out bits per second - Real Time Data widget
Please can we have a way to organise the alerts by severity order, an not just by alphabetical order of the severity
Me and my team often close a ticket before its even created because we already resolved the issue. However, we found out doing this is messing with certain reports. One report says our average time to close is 7 days which is not true at all. We would still like to close tickets immediately instead of having to…
Currently Hardware sensors are only related to the Node, which is fine for some things like temperature and such. However, for sensors that are directly related to an Interface, such as monitoring SFP's that support DOM for things like Tx/Rx power, temp, bias and such it needs to be associated with the interface and not…
It looks like you're new here. Sign in or register to get started.