After the alert disapear from this page:
https://orion.rtss.qc.ca/Orion/NetPerfMon/Alerts.aspx
1)Where do they go ? Are they archive or deleted ?
2)In wich database table do alert are coming from ?
After the alert disapear from this page:
https://orion.rtss.qc.ca/Orion/NetPerfMon/Alerts.aspx
1)Where do they go ? Are they archive or deleted ?
2)In wich database table do alert are coming from ?
Hi deathunt,
after disappearing from this page (by acknowledging or run out from number of displayed alerts) the alerts are still present in AlertStatus table and can be viewed also via Advanced/Basic alert manager, where you are still able to view them, clear and acknowledge/unacknowledge.
AlertStatus only contain ~10 alerts.
After they are clean from AlertStatus, do they go into another table ?
I ask because I have to make a SQL / report that show error for node, volume and application with more than those label (show on https://orion.rtss.qc.ca/Orion/NetPerfMon/Alerts.aspx): TIME OF ALERT, ALERT NAME, ALERT TYPE, NETWORK OBJECT, ACKNOWLEDGED BY, ACKNOWLEDGED TIME.
Also, any way to join table AlertStatus and Nodes ? They have no common ID....
ActiveObject and ObjectType are what you should join on
Somethng like this:
Select Top 1000 *
From AlertStatus A
left outer join Nodes N
on N.nodeid=A.ActiveObject and A.ObjectType='Node'
left outer join Interfaces I
on I.InterfaceID=A.ActiveObject and A.ObjectType='Interface'
left outer join NPM_NV_WL_APS W
on W.ID=A.ActiveObject and A.ObjectType='Wireless Access Point'
(there maye be other tables that you need to join, for example if you have UDT alerts, IPAM alerts, SAM alerts, etc....)
fx: shrug. you're right.
Solarwinds seems to lack a metadata manager who blesses their database structure and names.
Notice we have nodeid, interfaceid, but wireless access points are 'ID'. ObjectType has this longish string value, but in the pollers table we have 'N', and 'I'
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.