Could you help me in a case that was left to me. My question will be translated which is the following: I would like a script for solarwinds that updates the list of nodes every time a new server is entered until the new server appears as a node, and that

Could you help me in a case that was left to me.
My question will be translated which is the following: I would like a script for solarwinds that updates the list of nodes every time a new server is entered until the new server appears as a node, and that once updated in solarwinds it sends me by email email that this new server has already been correctly registered within the solarwinds system.

  • The first part of your request is largely automatic. Anytime a node is created - any report that lists all nodes will automatically pull the current list of all nodes directly from the database. Same with deletes. 

    I do not have my scripts handy, but the second part is your notification email for new nodes. That is best handled by an alert based on the audit tables that a node was created, then have the audit message added to the alert trigger email notification.

    I do not use the event logs - as they show server updates when they are added to a polling engine, so that scoops up polling engine changes. This is not the same as creating a new node. While better filtering may work with the event logs, the audit logs have been great and I use them to notify me of node adds and removes. 

  • Could you help me with those scripts please. 

  • I just checked, and I dont even have a script for this alert. Create a new Alert set the Alert on to Auditing Event. Set the scope to all objects and for the trigger condition, you can use the following. This will trigger notifications for adds and deletes. You do not need both conditions either. You can just use the Node added.

    Set the reset action to no reset required/trigger every time. For the notification, choose Send an Email. Add any email addresses that you need. The message is simple, One variable is all that you need, but I recommend two (the alert name variable).

  • If you have good visibility of the virtualization layer, and that accounts for everything, a nice report is VMs that do/dont have their detailsURL like '%N:%'