bobmarley ✭✭✭✭✭

Nice work! 

We use this to get the alerts into Splunk first. SolarWinds Add-on for Splunk | Splunkbase . We log the alerts using this alert action so that we can use the variables within SolarWinds to craft the message to look exactly what we want it to look like then Splunk grabs the alerts out of the above log. Once the data is in…

Great idea! This is also useful for example if you are monitoring locations that are closed during the evening hours and the Engineers can not get physical access into the building during off hours. We use a custom property AlertAfterHours and populate the ones we do not want to alert with a No, The alert re-enables at 7am…

Click the Show Filter Examples and look at the examples shown. Nodes.CustomProperties._Region = 'CHE' works, I tested it.

I do not have the product installed but I think it may be in this table. I would think you could create a custom SWQL alert for this. Would need to see the data myself. SELECT TOP 1000 ScopeId, NodeId, SharedNetworkId, DhcpGroupId, GroupId, SubnetId, LastSeen, FirstSeen, HideIfOrphaned, FoundAddress, FoundAddressN,…

I add this resource on my Node Details page, at least at node level.

Sounds like a powershell script running under a SAM template may be your ticket :)

(+) How to mute node with Powershell - SolarWinds SDK - The SolarWinds Platform - THWACK

I hope this works!

I don't have any to try, but possibly refer to the admin guide on what these specific settings do? 

Manage Nodes - Select a node - Edit Node, scroll to the bottom and choose your connection profile

This was my replacement to the out of the box Node Down resource as I needed the time in it that the node went down, and my exclusion list was getting too long on that resource and it is way easier to work on within the SWQL query. I also included our SNow assignment group so our NOC could see when they went down and what…

Try this, I commented out a custom property SELECT NodeName AS [Node Name], '/Orion/images/StatusIcons/Small-' + StatusIcon AS [_IconFor_Node Name], DetailsUrl AS [_LinkFor_Node Name]--, Nodes.CustomProperties._Group as [Group], ,MAX(tolocal(DOWNEVENT.EVENTTIME)) AS [DOWN TIME] FROM ORION.NODES NODES INNER JOIN…

I can think of a lot of ways to do this, however if you want to use SAM try this. Here is an example. This SAM Template is going to look for an event in the event log on our SQL servers for when it loses connection of it's twin replication server - event ID 1676. You can use any event you wish, this is the closest I have…

On your trigger actions page there is a box where you can insert the variables. Use the ones from there, these will be the new SWQL style ones. 

You may also try plugging the device into a different port on the switch, possible bad port?

We are on SolarWinds Observability Self-Hosted Advanced Enterprise Scale: 2024.4.0 and it is working fine. Thanks for sharing. I will upgrade my test environment and test it.

The software is designed to run on Windows Server 2016 and up. Have you tried setting up a virtual machine on your laptop and installing it on a valid Server OS? If that is not possible, try getting a personal cloud account set up and spinning the server up in the cloud. 

Is the network device getting link down messages in the log? Also, what is the device plugged into the parts warehouse port? Are you sure you don't have an end user messing with something? When I hear warehouse I think of the shenanigans that the warehouse workers would do back when I was on site support. Some of them were…

Just thinking out loud, is there any speed or duplex mismatches between the switch and end device? If it is set to auto try manually putting it at the correct settings? Bad cable?

I read through the admin guide and then installed it. SolarWinds User Device Tracker Getting Started Guide SolarWinds User Device Tracker Administrator Guide

Our setup sounds exactly like what @"stuartd" described. Tickets are typically P2, P3, or P5. We skipped the P1 and P4 altogether as it aligns best with creating tickets in SNOW. So we have a custom property for nodes/interfaces that determines the priority when tickets get generated. That said in many of our alerts we…

When you unmanage a node, all data collection stops. There is another feature Mute a node, that only mutes the alerts for that node and still collects data for it. I would suggest looking into the Mute feature for this. 

SELECT TOP 100 N.Caption AS [NodeName] ,AVG(N.ResponseTimeHistory.Availability) AS [Availability] FROM Orion.Nodes as N WHERE N.ResponseTimeHistory.DateTime>ADDDAY(-7,GETUTCDATE()) GROUP BY N.Caption ORDER BY AVG(N.ResponseTimeHistory.Availability)

You should be able to get something close here: Modern Dashboards - The SolarWinds Platform - THWACK

Tools: openDCIM - Open Source Data Center Infrastructure Management 

@"stuartd" Great suggestion, that is the exact same way we did it as well. Another very nice Custom Property we use is Group, which is the SNOW group to assign the ticket to. All of these can be passed in the alert message using variables.

Possibly check the alerts in the database and compare the time it was generated -vs- the time Netcool received it. Determine if the delay is in the SolarWinds side or the Netcool side.

Please take the next step and make the certification exams available at proctored exam center. 

Here is an example: SELECT tolocal(TimeLoggedUtc) AS [Last Login], CASE WHEN AccountID LIKE 'domain/user1' THEN 'BobMarley' WHEN AccountID LIKE 'domain/user2' THEN 'Fred Flintstone' ELSE AccountID END AS [Name] , AuditEventMessage FROM Orion.AuditingEvents AS AE WHERE daydiff(timeloggedutc ,getutcdate())<1 AND…