ekis

SW Orion DB on Linux?

You are missing close parenthesis before: as [CI_Owner] & before : as [CI_Key_Functions]

Alternatively, a workaround that will span it vertically is possible if you will use a Custom Table resource, & use a custom SQL query that uses UNPIVOT.

Looks like this bug is still not yet fixed, I also see it in my NPM 12.0 + SAM 6.2.4 environment. A workaround is to : Edit the Node Details view Add a 'custom table' resource to this view, hit SUBMIT. Configure the Custom table resource by clicking either the EDIT button or the CONFIGURE THIS RESOURCE link. Keep the check…

Actually I don't know what the notify option is for. I've just thought of setting that to zero (off) as well. Maybe other Thwack members have some inputs about the notify option.

The "Message" output from a Powershell Script Monitor cannot be assigned to a custom property since there's no such thing as a "Custom Properties for Component Monitors".

Here's the SQL code. **NOTES** * The varchar(50) conversion (shown with the blue arrow in the pic below) may or may not work for you. It will depend on the length of characters for the custom property in question. If 50 is not enough, just replace it for a value acceptable to you. * The section with the red curly brace…

The PowerOrion from the Orion SDK may be a possible workaround. Configure an custom alert that looks for the old volumes that qualifies for removal. Then have an alert action that will run a PowerOrion-based script that will remove the volume object(s) in question. Just a thought. Maybe PowerOrion experts can chime in?

This one is cool : web report + sql = awesome!

Well, yes you can put the SSL cert's Subject can be put in as a value for custom property, but even that cannot be used in dynamically putting in the subject as the component name. Therefore, you really have to rename the component name or application and manually key in the SSL cert's Subject.

Try editing the logon account of the JobEngine and JobEnginev2 services to use Network Service or perhaps have it use the same credential used by the monitor.

I got the same concern. I provide support for the SolarWinds monitoring app but the SysAdmins have node management powers on their own machines. They disabled hardware sensors for stuff they don't want. But all those disabled hardware sensors eat up a lot in the Hardware Health Overview pie chart in our dashboard as they…

try this: * login to SW using a user account that has admin privileges * launch this URL : http:// or https://yourOrionserverFqdnOrIPAddress/orion/admin/swis.aspx * that page will launch the Orion SWIS query page

Try updating the EventTypes table and set it to not record and not notify for events about 'Thin AP Disappeared'. UPDATE EventTypes SET Record = 0 ,Notify = 0 WHERE Name = 'Thin AP Disappeared' Hope this helps.

Yes, you are correct. Alert on other objects besides "Node" will still have access to the nodes custom properties in the alert actions. However, the full format of the alert variable will be dependent on the option you chose on the I WANT TO ALERT on field in the trigger condition tab. For instance, a node object has a…

A workaround that will span it vertically is to use a Custom Table resource, & use a custom SQL query that uses UNPIVOT.

If you've already turned off whatever you can turn off within SolarWinds itself, try checking if there's anything else within the Windows OS that hosts SolarWinds that's sending out reverse dns lookups. Remote in to the polling engine, and try using Netmon from Microsoft to run a packet capture (I'm more familiar with…

The NPM_RoutingNeighbor table will have unique NeighborID's that are related to each NodeID. The NPM_VRFs table will have a list of all the VRF names that are related to each NodeID. If my analysis of the two tables you mentioned is accurate, then,it looks like that there's no way to trace which specific NeighborID is…

Yup powershell cmdlet can be used like Invoke-WebRequest or Invoke-RestMethod. Then, you need to compose a custom-built Powershell script specific for your needs and then put that into SAM's Windows Powershell Monitor component.

It looks like SolarWinds is using an RFC as its basis for the down status of HTTP(s) monitors. And it looks like 4xx and 5xx are the ones that are considered errors. ------ part of Hypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. Informational 1xx This class of status code indicates a provisional response,…

Error 50X also appears to get a down status for the component monitor

The component name cannot be dynamically populated with whatever Subject the SSL cert has. You have to manually key it in.

any updates about this? is it compatible with NPM 12.0 onwards?

Yes it is possible. Our company recently created a new domain that's currently working and existing along side the old domain. I became flooded with requests to give the new domain users permissions to login to the Orion Web Console. I went ahead and tried to add them into SolarWinds via the Manage Accounts page:…

Have you already tried remoting in directly to the SolarWinds server, launching Powershell from there and running your script? Does it run successfully? If it does not run successfully when you try it directly in a Powershell console, large possibility is that it will not run in SAM as well.

Look at each of your node object alerts and check the trigger condition statements declared in it. If you'll add new nodes, keep a tab in your mind that you have to make sure that that new node will be within the alerting scope of the node object alert you have. Say you have a SW alert that fires when CPU load is greater…

In the Node Details page of the device in question, does it display the correct, actual, real, LAST BOOT date/time stamp? Check the NEXT POLL time stamp : is it stuck in a date/time in the past? Try loading a fresh from scratch run of the LIST RESOURCES page of the node in question : is it able to load or does it error out?

Try adding a custom table resource and configure the datasource with a custom SQL query like the one below: then add columns don't forget to edit the advanced section for ICMPSTATUS ; ensure that you click add display settings > choose generic icon & replace its contents with: /Orion/images/StatusIcons/Small-{0} Hit SUBMIT…

Without use of dependencies, you'll get both alert emails if the interface down alert's trigger condition is NOT configured to exclude nodes with down status. But if you've explicitly inserted and defined within the interface down alert a line like "Node status IS NOT EQUAL TO DOWN", even if the node goes down first, you…

You can try to look into another related Thwack post -> status LED in a custom report