Comments
-
I am getting push back from the AWS admins stating the effort to create accounts in AWS to allow SolarWinds access. They indicated there would need to be numerous accounts needed to access all of the data in AWS based on how we have our security setup. Just wanted to see if you have run across this.
-
I just started using anomaly alerting and I am finding it difficult to apply alerts to groups of nodes i.e. Windows only and by environments. I have custom fields I use for alerting and it does not appear I can use these. Also, where is the select all? How do I add additional nodes later and filter on Nodes not checked?
-
When will this be available? Looking for this on Arista.
-
I assume this is April fools joke?
-
Agree, getting push back from security not allowing WMI access to Domain controllers and SNMP v3 is not supported on Windows.
-
We do emails if groups want them, but incidents are created through integrations with ServiceNow. I would like to offer Teams chat vs. email though.
-
I find them very limiting as I can not custom fields to limit the scope. Also, time consuming having to select each one individually vs select ALL. When I have hundreds of the same type of node this is very time consuming.
-
Add a "Group by" at the end. Order by TimeLoggedUTC
-
Thank you planning on using this for alerting!
-
When will this issue be resolved. I am new to Solarwinds and have just run into this road block. I need to have the traps show on the Home page so that my NOC operators can see and acknowledge the the condition. I placed a feature request last week for this, I hope this makes it in soon.
-
I have not implemented SNMPv3 only SNMPv2. I do have one AIX system that exhibits the same results and I have not been able to resolve this. The configuration files appear to be the same when compared to other systems that are working. Sorry I cannot help.
-
Here is what I found out and did to resolve this issue. With the OS upgrade, IBM switched to SNMPv3 as the default. You need to switch back to SNMPv1. The following is how this is done. Modify SNMPD.CONF file vi /etc/snmpd.conf logging file=/usr/tmp/snmpd.log enabled logging size=0 level=0 community <Community String> trap…
-
I think I have a solution using custom fields and SQL query in an alert. I created an alert with a custom SQL query that triggers when the time is between 11:45 PM and 11:59 PM and then resets after 15 minutes. I created a custom field "PM_muted" and the alert changes it from "No" to "Yes". I updated my alert for high…
