Comments
-
I believe you are looking for the variable 'NeighborIP' when you are sending your trigger action. If you want the interface and its description it looks like its variable: ${N=SwisEntity;M=Router.Nodes.SwitchPortEntriesAsSource.MappedInterfaces.Caption}
-
Do you have SAM or any servers in SolarWinds? I came up with a quick query but as I have NPM and several thousand servers in SAM the report is not clean unless I exclude them. SELECT N.NodeName, N.NCMLicenseStatus.LicensedByNCM FROM Orion.Nodes N WHERE N.NCMLicenseStatus.LicensedByNCM != 'yes' Without servers if needed,…
-
What kind of accounts are you using? Orion or AD/SAML? If your using AD/SAML you would not see records until the user actually logs in. You would have to pull the AD group in compair against who is missing from Orion DB. If your using Orion accounts you can reference the last login date. The default date is '1900-01-01…
-
Which Trap product are you using? New Syslog and Trap Viewers (part of Log Analyzer) - Orion Log Viewer the New and Improved Version of the Syslog and Trap Viewers Or legacy Orion trap/syslog viewer?
-
Thanks for sharing! I was fortunate enough to attend one of the SWUG's last year and would highly recommend it. It was great to speak to yourself, the other SolarWinds employees, and THWACK MVP's.
-
To more directly answer your question. You will want to look into SWQL. Here is a link to get you started. SWQL studio can be downloaded here.
-
Try building out a similar alert with the alert builder UI. Once you have something close you can click on the arrow and expand to show the alert in SWQL. This section of the WebUI With some more context I would wrote up something close: Comes out in SQWL like this: SELECT E0.[Uri], E0.[DisplayName] FROM Orion.Nodes AS E0…
-
What is your use case for groups? I would avoid trying to avoid alerting on groups directly. The main use case for groups (that I use) is for setting up dependencies and 'down stream suppression'. Example: remote site group, with a dependency on the WAN routers. If WAN router goes down, so will everything behind it.…
-
Try setting the alert type ('I want to alert on:') to 'Group' to expose those variables. I know its not 100% what you want, but it will get you going. What kind of alert are you trying to make? I would highly recommend custom properties for classification if possible. I only use groups for condition roll-ups and down…
-
What kind of report are you trying to write? Is there a use case or answer you are trying to achieve?
-
Good question. I don't see an obvious way but I am digging in database to see if SW keeps tracks of the process lifetime on the PID. Whats your use case on the service restart?
-
Is your alert working after you added the null/'is empty' value? I have a few alerts that we had to include "does not contain" on the trigger action. We have custom properties we only populate when we want to 'override' the default alert behavior, or like your example, for specific environments/teams.
-
almogn5 Can you explain the variables you are expecting / looking for? Maybe post a screen capture of what you have so far and pencil in what you expect? I started a test alert and see variables from node and component when I setup advanced > complex conditions.
-
My DBA's told me the same thing. I posed the question to Support (DPA) and they confirmed it should be avoided.
-
Go into the alert and edit its 'Trigger Action'. I would highly recommend checking out the online live training sessions offered by SolarWinds (they are free / assuming you have maintenance). 1. 2. 3.
-
Check out the 'Hardware Sensor (Node)' alert (under 'I want to alert on:'). I do 'hardware Sensor (Node)', 'Status Description', 'is equal to'. I do both 'warning' and 'Critical'. Make sure to set your scope to the devices you want. In your case router/switch. I have a bunch of servers as well so I leave it fairly open. I…
-
I am not familiar with agents as we are going entirely agentless, but what about monitoring on metric collection? SWQL in text for easier copy/paste: WHERE Nodes.UnManaged = 0 --Node has not been unmanaged AND Nodes.Status != '2' --Node is not down. AND Nodes.LastSystemUpTimePollUtc < ADDDATE('Minute', -30, GETUTCDATE())
-
Are you using the legacy trap viewer or the new LA (Orion Log Analyzer)? Log Analyzer does not break out the message like legacy viewer did. Check out these posts From Alert Lab: How can you use old snmp trap varbinds variables in the new OLV? Feature request: Log Analyzer - Allow searching for varbind name / value pair
-
I ran into this issue. From this post:AppInsight for SQL - The process was not found. Check: "local security policy, local policies, user rights assignment and added my monitoring account to the "debug programs" policy."
