TerryHarding ✭✭✭✭✭

DateTime > ADDWEEK(-1,getdate())DateTime > ADDMONTH(-1,getdate())github.com/.../SWQL-Functions

Or maybe create groups for the port channels and use the Group Status root cause variable in your alert?

EMailTo is a Custom Property for the Node. If the Node has that Custom Property Set to Network Support Group then it will send to the recipients listed in the To field. It's just to ensure only Down Nodes supported by the Network Support Team receive the e-mail alert.

The actual error is reported in C:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log

I think the report is the best option. Not sure how you can use an alert for this. If you use a Custom SWQL resource, something like the following: SELECT n.Caption as Node ,i.Caption as Interface, InTotalBytes, OutTotalBytes FROM Orion.NPM.InterfaceTraffic t JOIN Orion.Nodes n ON t.NodeID = n.NodeID JOIN…

Hi Cal, I passed the SAM SCP on the 4th of April and did not receive a polo - has this been discontinued? Terry

If it's on a per account basis you can disable session timeout by editing the account in question in the All Settings, Manage Accounts page:

In Orion, the session timeout setting is in Settings, All Settings, Product Specific Settings, Web Console Settings:

It works if you remove the ORDER BY aa from the script

Create your own - it will be one SAM component for each server it’s deployed to.

The Custom Query only allows one search box so filtering also on group is only attainable by entering the extra ' AND GroupName LIKE '%eMAIL% in the search box.

Expand the node in Manage Nodes and delete the volume. List resources shows active resources only.

C:\ProgramData\SolarWinds\Logs\Orion

Try this: Select N.NodeID, N.Caption, IP_Address, Status, COUNT(DISTINCT CPUIndex) As "Number Of CPU", NumberOfCores as "Number of Cores" FROM CPUMultiLoad_Detail CPU WITH(NOLOCK) JOIN Nodes N ON CPU.NodeID = N.NodeID JOIN AssetInventory_Processor A ON CPU.NodeID = A.NodeID GROUP BY N.NodeID, N.Caption, IP_Address, Status,…

Worth checking this thread from a while back... Server Rack Diagram for SAM

As below using Response Time History Timestamp:

Get the sql query of web based report.

SELECT n.NodeID ,n.Caption FROM Nodes n JOIN NodesStatistics s on n.NodeID = s.NodeID WHERE s.LastSystemUpTimePollUTC <DATEADD(DAY,-10,GetDate()) AND n.ToBeDeleted<>'1'

ICMP doesn't use a TCP port as such. You will need to target a system on the remote end of your MPLS which responds to a specific application port such as 80 or 443 for a Web Site.

Hi Scott, The release notes for NPM 12.1 state there is a fix included for Cisco Switch Stacks not displaying properly. May be worth investigating.

There is a feature request for disabling the session timeout at If you vote it up, they may add this functionality.

Hi, Sounds like you're describing the Orion Settings page rather than Web Help Desk so you may have posted in the wrong forum...? Regards, Terry

Hi Serena, So, if the Component Count under Database Details, Total Element Count is 13,000 plus, would you say that an Additional Polling Engine is required to carry the load even though the Polling Engines Details page shows the SAM polling percentage to be 8% of its maximum rate? Regards, Terry

I opened a Support Case with SolarWinds regarding exactly this. The reply I got was: "The warning you brought to our attention has no impact on your maintenance schedule nor on any product functionality. We advise customers to ignore the warning, as it's generated automatically by one of our internal system routines."

It can be either. Just a non-standard application.

Hi Tony, If using the Orion integration as the primary source for Service Desk tickets, how would we address an issue with alerts being raised if the connection to the Service Desk is not available due to an interruption to internet connectivity? There would be alerts raised but no corresponding incidents. Would it be…

See this post: https://thwack.solarwinds.com/t5/NPM-Documents/ViewExporter-ps1/ta-p/519617

Browse to the node in question and in the Node Details page, in the Current Hardware Health resource, click on Manage Sensors, then disable the power supply sensor.