bobmarley ✭✭✭✭✭

Mine stops when the volume of messages gets too high. Here are a couple of things to try. In the Kiwi Console go to 'Email' Then set this up: This will give you a daily log of whats going on. Also set up these: There is also the 'View Syslog Statistics under the 'View' menu

Here is the equivalent SWSQL. This is pulling all nodes that have the name 'Cisco' and a custom property called Team that contains 'Telecommunications' Select IP_Address, Caption, NodeID, _Group FROM Orion.NodesCustomProperties cp INNER JOIN Orion.nodes nd on cp.NodeID = nd.NodeID Where Caption Like '%Cisco%'AND Team Like…

One workaround I used was fronting NPM with Kiwi and converting the traps to syslogs and then forwarding on to NPM's sylsog engine. Not a great solution but it worked.

You should be able to do that (Router, switches,wlc.... etc) by using the 'Filters'. Look at the dropdown box and see if any of the other options will work in your environment.

Launch the Kiwi Syslog Console from the icon or from the start menu Choose File and then Setup Right Click on Rules then Add Rules Right Click on the New Rule and then Add Filter Create a rule for the IP address(s) you want to forward by selecting the IP Address Field from the Pulldown Boxes. You can use multiple as long…

You can create a rule to forward the messages to additional hosts.

I was able to get this done as an alert action using the thread below. Unmanage/remanage or mute/resume an item or all items in a group

Thanks for the post Leon

We have done it a number if ways. 1. Have a second smaller implementation of Solarwinds that is monitoring the main one from a second data center. It also has all of our very important nodes in it as ICMP only so it is doing a subset of monitoring. This server is mainly there to be used during upgrades, disaster recovery…