Comments
-
Edit: I pulled another example and custom node poller works fine. I'll leave the below as something to try. Would also try pulling the 'custom node poller, unique name' for your scoping. If your pulling row ID you might want to switch to 'custom table poller current status'. Here is one of mine
-
You can you the full installer .ISO and select the 'additional polling engine' during the install process.
-
You can create one from, Settings, SAM settings, Templates, Create new. Here is an example.
-
What exactly did you have to do to get this working? I see a 'reportingclient' user but its on the DB level and cant access other DBs on the instance.
-
Also having the same issue.
-
Also had this issue and this fixed it.
-
You can add a time window on the alert to not process during specified times (or the alert can work but not send out notifications). you can also schedule the nodes to go into maintenance mode, Configure Orion to unmanage items on a scheduled basis
-
You can do ssh script monitors.
-
Which vendor is this? Do the allow any remote management (SNMP/WMI/API)? If so SolarWinds might be the easier system to monitor them. If your other vendor supports any sort of external call you can likely integrate it with your ITSM (webhook/email/SNMP trap/syslog/even if you have to scrap a log to do it), tho I will say I…
-
Stealing almost the exact wording that @"jm_sysadmin" used on a similar post. You will likely need to script it and have the alert call the script. The script connects to the ITSM, opens the INC, returns the number, and then stamps that back into the alert notes.
-
I assume your referring to this post 'QUESTION: Does Solarwinds have a Northbound Interface?'. SolarWinds has a fairly good API to push/pull data. SNMP traps can be received, as well as forward traps to a new destination. Not 100% understanding your use case.
-
I'm sure this is possible but I always prefer to do polling data if you want to clear/reset events when integrating with a ticketing system. I personally find the polled metrics easier to write alert conditions against. Do these devices only support syslog? Does your security policy allow you give us some more details on…
-
Enterprise Operations Console can do this if you.
-
Love content like this, thanks!
-
The offline installer should have a bundle of everything.
-
Done, and thanks.
-
I poked around a little. The alert engine does not make it easy to link between applications and components despite the links being available in SWQL. Hopefully someone more familiar with SAM can help out.
-
Ran into one more post upgrade. * "SAM Database Maintenance Is Overdue" * "ERROR SolarWinds.Data.DatabaseMaintenance.TimeSeriesTableHandler - Retention interval settings not specified" in log files. Per support: "These are known issues in this product version. It will be fixed in the release 2023.3." "The issue seen does…
-
I opened a feature request for tracking. https://thwack.solarwinds.com/product-forums/the-orion-platform/i/feature-requests/remove-platform-connect-icon-from-menu-bar
-
I opened a feature request for tracking. https://thwack.solarwinds.com/product-forums/the-orion-platform/i/feature-requests/remove-platform-connect-icon-from-menu-bar
-
Is this an application or component alert (as configured on 'trigger condition > I want to alert on:"?
-
If your using scripts, try: ${N=SwisEntity;M=MultipleStatisticData.StringData}
-
This is SWQL, just need to add your user WHERE clause, tho I would recommend to make this a query dashboard and let whoever search there to get the user. SELECT AuditEventID, TimeLoggedUtc, AccountID, A.AuditingActionType.ActionType, ActionTypeID, AuditEventMessage FROM Orion.AuditingEvents A WHERE A.TimeLoggedUtc <…
-
#Bump
-
You might need to whitelist your IP with Service-Now (at least most of my clients set it up that way). Which event module are you using? Found the older post on the service-now event integration:…
-
Just an FYI that 2020.2.6 is EOL on May 18, 2023.
-
KB might be out of date, I don't see them named that on 2023.2. @"KMSigma.SWI"can you point us in the right direction of the log (and poke someone internal to update the KB). Ref: [quote userid="60518"…
-
Defect still exists on 2023.2. Support said it will be resolved on 2023.3.
-
I think there is an out of the box SAM template for this "Windows TCP Port Exhaustion". If its not out of the box just ran this command: netstat -ano | find /i "estab" /c Edit: I apply this to all my SW servers as we ran into this issue ourselves. It also also recommend to expand the ephemeral port range, KB: Ephemeral…
-
I made a new post to avoid hijacking this one: Errors During Upgrade to 2023.2
