I have developed an Alert to trigger on Nodes which are unmanaged for more than 30 days.
It's a Custom Query Alert which is written based on Audit Events as unmanaged objects can't trigger an alert unless we update/check the box under Polling Settings to trigger actions on unmanaged objects.
This alert will work even without enabling trigger action on unmanaged objects under polling settings.
Trigger Condition :
I have developed an Alert to trigger on Nodes which are muted for more than 3 days.
It's a Custom Query Alert which is written based on Audit Events as once node is in Muted state it can't trigger an alert.
Trigger Condition :
The Process Monitors for components have out of the box thresholds for:
CPU
Physical Memory
Virtual Memory
I/O Read
I/O Write
I/O Total
But one we're missing is for process count. This is an effort to implement a workaround to alert when a count is over a certain threshold.
Type: Custom SWQL
This is the basis of the alert in SWQL from the alert (but there are additional notes in the alert)
SELECT TOP 1000 [Component].Uri
, [Component].DisplayName
FROM Orion.APM.Component...
This alert is triggered when a new version of the Synology DSM software is detected. This detection is made by the Device Poller also available for download ( Synology Network Attached Storage - Device Pollers - Network Performance Monitor ).
Hi there, I've been working on this today and I think I finally worked up a solution. Basically this alert uses a custom SQL query which will check if the status value of the UnDP has changed, if so it will get triggered.
I've searched in the forums for this solution but I couldn't find it so I though I might share it in case someone finds it helpful.
Here is the query:
SELECT CustomPollerAssignmentView.AssignmentName
, CustomPollerAssignmentView.CustomPollerAssignmentID
FROM CustomPollerAssignmentView...
Hello there,
The Problem
Custom Properties are a very important tool for organising your SolarWinds platform, and many administrators choose to be very granular when it comes to how they group devices. This becomes even more important when you work in an operations environment where you are looking after multiple sites, across multiple countries and regions.
However, filling in custom properties is often not done, or not done correctly so this automation alert is intended to take some of the...
Occasionally SNMP or the device itself will restart frequently due to an issue. This alert identifies the node, currently set to 4 times in 30 minutes.
I have never been a fan of the out of the box alert for high CPU in Orion. It is a static value and in no installation I have ever worked on, has a single value been appropriate for all devices.
This alert definition uses the Critical threshold value, for which you can specifity at the global level (Settings > Orion Thresholds) or at the Node object level (Edit Node). This gives much greater control over the correct alert condition for each device.
Within the settings, you will see I have a...
This alert looks to see if any polling engines have not updated the database in the last 10 minutes, which is an indication that either the polling function has stopped, or database connectivity has been lost.
