stripet

@"william.evans" you are right: To get rid of a feature (an important one at that!) and not provide a Tool to convert to the new way is unacceptable! We have hundreds of ReportWriter reports that have to be manually converted. That is a LOT of work that should not have to be done! Also, the Web-based reports are not…

I see this as a requirement, mainly due to the fact that Microsoft will be getting rid of the SNMP Agent after Windows Server 2012 and we would then need the alternative WMI as an option when adding Windows nodes to SolarWinds.

I have also had the wish for this feature. I have to try and remember to go and edit the Template later and have caught myself forgetting to back and edit it right away, causing false Advanced Alert emails to go out to the teams, which is never a good thing.

I was referring to "Node Rebooted" Events, not Advanced Alerts. I want to change the text message of the reboot event, which appears to be some sort of default event which appears which I would either want to turn off altogether or change the message text.

Please, pretty please! Yes, we really need this! There appears to be some sort of bug when a node gets Re-Managed some of the SAM Apps stay in Unknown status saying "Initial Polling in progress" and they won't go green until somebody manually does a "Poll Now". That is a lot of work! This requested feature would really…

To Disable EventType 14 (Node Rebooted) events run the following SQL Query: UPDATE EventTypes SET Record=0 WHERE EventType = 14 I tested this and the above query does indeed stop the pesky alerts which are confusing my end users because it says the node rebooted but the node did not reboot, it was just that the SNMP Agent…

We use Remedy as well. I also cannot Resolve Remedy Tickets on RESET because of the issue with not having a unique AlertID field. Without that, it becomes difficult to handle and requires customized coding which I hesitate to do. I am holding out for an AlertID field in the Advanced Alerts.

Jfrazier‌ Can you please divulge the DB Table to modify or the SQL query to modify the event message? I want to change the wording to say "server xyz SNMP Agent cycled" instead of "server xyz rebooted". Thanks

I have a big problem with SolarWinds reporting reboots for servers when in fact all that happened was that the SNMP Agent was cycled on the server. May of our users are confused about this. Please either change the text to state what really happened (SNMP Agent cycled) or stop reporting it as a reboot when it is not. We…

We could really make use of this! We also only check the fixed disks.

@karthik, I agree that Reporting is so very important to the organization but focus does not seem to be put on it. I am excited to start using the new SolarWinds Web based Reporting but we are not yet upgraded to the new version. Have you had a chance to use the new SolarWinds web based reporting tool and if so what are…

I like that idea!

I too have wished I could manage SAM Templates from the Manage Nodes screen. 

Actually, I do not see the AlertID field in the Advanced Alerts table AlertStatus. So, the AlertID field does not exist for Advanced Alerts but should. Please add AlertID (unique identifier for the alert) field to the AlertStatus table in the database for Advanced Alerts. We really need this feature. Also, this field…

cebep37 Yes! I am struggling with this as my users are confused as to why they have to go to a Tab called "Network" for instance when that page for them actually shows a SAM Summary for their application. It does get confusing for users and it seems like it would be quite simple to allow some more flexibility here. I agree…

I see this as a huge issue. We do not run Scheduled Network Sonar Discoveries, so we have an issue where new Volumes and Interfaces do not get checked int he List Resources area. This is more of a problem for Volumes for us than for Interfaces, but in both cases, we would like a Reporter or some way to identify Volumes and…

Yes indeed, we need a fix for this! We also had issues of Linux Filesystems filling up before SolarWinds would alert us due to this issue so we now use a SAM Template with a UNIX bash script monitor which uses df output instead, becasue it is much more accurate! Now the users are a bit confused becasue the Node Details…

The variables available to you depend on the value of the "Type of Property to Monitor" value at the top of the Trigger Condition tab. So, since, in this case, your says "APM:Component" that is why it only presents the APM Component variables. I agree that if the Property to Monitor is set to APM:Component then the…

rick.harwood We would also like the ability to configure Advanced Alerts to alert based on group membership. For Example, only alert when the node belongs to a certain Group.

Yes, I agree. We REALLY need this feature!

And it would be nice to search Alerts by date or date range.

We would also agree to this.

Not only was this lesson fun, but it was also informative, and I got 500 points! It does not take too much time and you can learn about thwack along the way

Thanks so much for adding the Audit feaure! It was much needed. Now I just have to wait until we upgrade our NPM as we are stll at v10.3.1

You can modify or disable the Alert called "Alert me when a node Lastboot changes" AND Disable EventType 14 (Node Rebooted) events by running the following SQL Query: UPDATE EventTypes SET Record=0 WHERE EventType = 14 I tested this and the above query does indeed stop the pesky alerts which are confusing my end users…

So, perhaps we should switch back to using our OpenView environment again? See, this is the reason we moved from OpenView to SolarWinds in the first place: so there would not be an agent to contend with and maintain. I vote No.

You can modify or disable the Alert called "Alert me when a node Lastboot changes" AND Disable EventType 14 (Node Rebooted) events by running the following SQL Query: UPDATE EventTypes SET Record=0 WHERE EventType = 14 I tested this and the above query does indeed stop the pesky alerts which are confusing my end users…

We use the "99" on the last two digits of the year method for the UnManage Until value. All nodes with an UnManageUntil value in the year 2099 are considered to be "permanently" UnManaged.

We need to be able to audit who UnManged and Managed Node and SAM Application Templates

Regarding Windows Eventlog Monitor Enhancements to Display Event Message Details: This is defintiely a MUCH NEEDED feature! We will wait for it to be released as a feature in APM, and hope the wait is not too long. Perhaps if enough of us send comments, they might move it up in the priority list?