Someone posted a great how-to on advanced alerts a few days ago but I can't find it when doing searches. I must be blind, hate to ask other people to do searches for me but I guess I'm just not using the right keywords. Help is appriciated. Thanks.
Is this it?
http://www.thwack.com
Try the More serach Options
http://www.thwack.com/search/SearchResults.aspx?q=advanced+alerts+&sd=6%2f1%2f2007&ed=6%2f6%2f2007
That wasn't it, but I ended up going through my browser history and found the link, but it is no longer valid. The link was:
And the title was Advanced Alert 'How To' and Variables List
If person who posted that wouldn't mind, could you PM me with what was in the post?
These will be updated on the OAG very soon-
Advanced Alerts Creation and Management
Alerts are generated for network events, and they may be triggered by the simple occurrence of an event or by the crossing of a threshold value for a monitored Interface, Volume, or Node. Alerts can be set to notify different people on different days, different times of the day, different people for different events, or any combination of times, events, and people. Alerts may be configured to notify the people who need to know about the emergent event by several mediums, including:
Viewing Alerts
The Active Alerts window displays a table view of your alerts log. You can customize the list view by using the following procedure to select your preferred alert grouping criteria.
To view alerts:
1. Click Alerts > Active Alerts.
3. Customize your Active Alerts display as follows:
a. Select from the following options in the Group By list to change your Active Alerts view: Alert Name, Object Type, Object Name, Alert State, Acknowledged, Acknowledged By, or No Grouping.
b. Order your Advanced Alerts list by any of the following criteria by clicking the appropriate column title: Acknowledged, Alert Name, Alert State, Object Name, Triggered Time, Acknowledged By, or Acknowledge Time.
4. Click Refresh at any time to display the most recently triggered alerts that have not yet been reset.
Creating and Configuring Advanced Alerts
A new alerting engine is now included with Orion. This advanced alerting engine allows you to configure alerts using several new features such as:
Multiple condition matching
Automatic alert escalation
Separate actions for triggers and resets
Advanced alerts are configured within the System Manager application or within the Advanced Alert Manager. For more information, see "Using the Advanced Alert Manager" on page 10.
Note: If you want to configure advanced features such as timed alert checking, delayed alert triggering, timed alert resets, or alert suppression, check the Show Advanced Features check box at the lower left of any of the following Advanced Alert windows. For the purposes of this document, Show Advanced Features will always be enabled.
Creating a New Advanced Alert
The following procedure creates a new advanced alert.
To create a new advanced alert;
1. Click Start > SolarWinds Orion > Advanced Features > Advanced Alert Manager.
2. Click View > Configure Alerts.
Naming, Describing and Enabling an Advanced Alert
Use the following steps, after clicking New Alert, Copy Alert, or Edit Alert from the Configure Alerts Window, to name and describe an advanced alert.
To name and describe an advanced alert;
3. Click New Alert or select an alert from the list, and then click Copy Alert or Edit Alert, as appropriate.
5. Enter the name of your alert in the Name of Alert field.
6. Enter a description of your alert in the description field.
7. Check Enable this Alert.
8. If you have checked Show Advanced Features, position the slider to set the checking interval for your alert.
Setting the Monitoring Period for an Advanced Alert
You can select the specific time periods and days that your advanced alert will monitor your network objects with the following procedure.
To set the monitoring time period and days for an advanced alert:
2. Click New Alert or select an alert from the list, and then click Copy Alert or Edit Alert, as appropriate.
3. Click the Time of Day tab.
4. Enter the time period over which you want to monitor your network. Your alerts will only trigger if your trigger condition is met within the time period entered.
Setting a Trigger Condition for an Advanced Alert
You can set the specific conditions for triggering an advanced alert with the following procedure.
To set the trigger conditions for an advanced alert:
3. Click the Trigger Condition tab.
4. Select the network object (Node, Interface, Volume, Custom Node Poller, or Custom Interface Poller) that you want to monitor from the menu.
Note: Generate trigger conditions in the text field by selecting appropriate descriptors from the linked context menus and by clicking the ellipsis on the left of the text field.
5. Click the linked text to select the number of conditions that you want to apply (all, any, none, not all). For more information about linked text conditions, see "Understanding Condition Groups" on page 9.
To generate a condition based on a comparison of network node fields and values, select Add a Complex Condition.
To remove a selected condition, select Delete Current Condition.
8. If you need to delete a condition, select the condition from the condition list and then click Delete.
Notes:
Warning: Imported trigger conditions automatically overwrite any existing trigger conditions.
9. If you have checked Show Advanced Features, you can set a sustained-state condition for your trigger with the slider.
Note: Often, it is appropriate to delay alert trigger actions until a condition has been sustained for a certain amount of time. For example, an alert based on CPU load would not trigger unless the CPU Load of a node has been over 80% for more than 10 minutes.To establish a sustained-state trigger condition, set the slider at the bottom of the Trigger Condition tab to the amount of time the alert engine should wait before any actions are performed. The default setting (slider set all the way to the left) is to trigger the alert immediately, once the trigger condition exists. With the slider set all the way to the right, alert actions will not be performed until the trigger condition has existed for eight hours.
Setting a Reset Condition for an Advanced Alert
You can set the specific conditions for resetting an advanced alert with the following procedure.
To set the conditions for resetting an advanced alert:
2. Click New Alert, Copy Alert, or Edit Alert, as appropriate.
3. Click the Reset Condition tab.
Note: Generate reset conditions in the text field by selecting appropriate descriptors from the linked context menus and by clicking the ellipsis on the left of the text field.
5. Click the ellipsis to view the following condition options:
To further define the application of your conditions, select Add a Condition Group.
6. If you need an additional condition, click Add and then select the type of condition that you want to add.
7. If you need to delete a condition, select the condition from the condition list and then click Delete.
8. If you have checked Show Advanced Features, you can set a sustained-state condition for your alert reset with the slider.
Setting a Suppression for an Advanced Alert
You can set the specific conditions for suppressing an advanced alert with the following procedure.
Note: Alert Suppression is only available if you have checked Show Advanced Features in the lower left of the Edit Advanced Alert window.
To set conditions for advanced alert suppression:
3. Click the Alert Suppression tab.
Note: Generate suppression conditions in the text field by selecting appropriate descriptors from the linked context menus and by clicking the ellipsis on the left of the text field.
4. Click the linked text to select the number of conditions that you want to apply (all, any, none, not all). For more information about linked text conditions, see "Understanding Condition Groups" on page 9.
1. To generate a condition based on a comparison of network node states, select Add a Simple Condition.
Conditions from other alerts may be imported to the current alert by clicking Import Conditions.
Setting a Trigger Action for an Advanced Alert
Select actions that will occur when your advanced alert is triggered with the following procedure.
To set a trigger action for an advanced alert:
3. Click the Trigger Actions tab.
4. If you are adding a new advanced alert action, click Add New Action, and then select the actions that you want to occur in the event that the current alert is triggered.
5. If you are editing an existing advanced alert action, select the existing alert action, and then click Edit Selected Action.
6. Follow the given instructions to configure each action.
Note: Depending on the type of action selected, different options will be displayed to configure the alert action. For more information on the Time of Day tab, see "Setting the Monitoring Period for an Advanced Alert" on page 3. For more information on the Alert Escalation tab, see "Alert Escalation" on page 9.
7. If you need to delete an action, select the action and then click Delete Selected Action.
8. If you are finished configuring your advanced alert, click OK.
Setting a Reset Action for an Advanced Alert
Select actions that will occur when your advanced alert is reset with the following procedure.
To set a reset action for an advanced alert:
3. Click the Reset Actions tab.
7. If you need to delete a selected action, click Delete Selected Action.
Alert Escalation
When editing any trigger or reset action, use the Alert Escalation tab, if it is available, to define additional alert action options. The following options are available on the Alert Escalation tab:
To delay the execution of the alert action, check Delay the execution of this Action and then adjust the slider to set the length of time that the alert engine should wait before executing the alert action.
Understanding Condition Groups
A condition group is a set of user-defined rules that govern alert triggers and resets. By default, the condition group "Trigger Alert when all of the following apply" is added when creating a new alert trigger or reset condition. There are four different logical descriptors that are used to create conditions: "all", "any", "none", and "not all", and they may be changed by clicking the word "all" and selecting a different value. The following is an introduction to these logical descriptors.
"All" Condition Group
In the following example, there are three conditions within the condition group; "Node Status is equal to Up", "Percent Loss is greater than or equal to 75", and "CPU Load is greater than or equal to 85". This alert will not trigger unless the Node is Up, packet loss is greater than or equal to 75%, and CPU load is greater than or equal to 85%.
When setting the condition group to "all", picture every condition as being separated by an "and" statement. So, in this example, the Alert Trigger would read:
Alert when: (Node Status = Up) and (Percent Loss >= 75) and (CPU Load >= 85)
"Any" Condition Group
Changing the condition group to "Trigger Alert when any of the following apply" changes the logic to "or" statements. In this example, changing the condition group to "any" would change the alert trigger to:
Alert when: (Node Status = Up) or (Percent Loss >= 75) or (CPU Load >= 85)
In this situation, if any of the three conditions become true, the alert will trigger.
"None" Condition Group
In this example the alert trigger would read:
Alert when: (Node Status = Down) and (Percent Loss <= 75) and (CPU Load <= 85)
Each condition is separated by an "and" statement just like the "all" condition group; however, the conditions have been inverted (Node Status = Down instead of Node Status = Up).
"Not All" Condition Group
Changing the condition group to "Trigger Alert when not all of the following apply" means that any condition in the group must be false before the alert is triggered. So, in this example the alert trigger would read:
Alert when: (Node Status = Down) or (Percent Loss <= 75) or (CPU Load <= 85)
Each condition is separated by an "or" statement just like the "any" condition group; however, the conditions have been inverted (Node Status = Down instead of Node Status = Up).
Using the Advanced Alert Manager
The Advanced Alert Manager is a new application that is now installed with Orion. This is an additional user interface that is used to view network events and alerts. Advanced Alert Manager is also used to create and manage advanced alerts. The following procedures introduce the main features of the Advanced Alert Manager to show how the Advanced Alert Manager is used to configure and view advanced alerts.
Current Events Window
The Current Events window shows the most recent network events with their descriptions and other information from the events log.
To use the Current Events window to view network events:
2. Click View > Current Events.
3. Select from the Group By list one of the following criteria for grouping events: Event Type, Object Type, Network Node, Acknowledged, or No Grouping.
a. Click the Event View Columns tab.
b. Select column IDs from the All Columns field.
c. Click the right arrow to move your selected column IDs into the Selected Columns field.
d. If there are any column IDs in the Selected Columns field that you do not want to view, select them, and then click the left arrow to move your selected column IDs to the All Columns field.
e. Click the up or down arrows to change the order of your selected columns accordingly.
f. Position the slider to set the Event View refresh rate.
g. Enter the number of events that you want to be able to review in the Display a maximum of XXXX events in the Event View field.
h. If you are finished configuring your Current Events View, click OK.
5. Click Refresh to update the Current Events window with the latest events and column IDs.
6. If you want to acknowledge a network event, click the X next to the event.
Active Alerts Window
The Active Alerts window shows network alerts with their descriptions and other information from the alerts log.
To use the Active Alerts window to view active network alerts:
3. Select from the Group By list one of the following criteria for grouping alerts: Alert Name, Object Type, Object Name, Alert State, Acknowledged, Acknowledged By, or No Grouping.
4. Click Include, and then check the types of alerts that you want to view: Acknowledged, Trigger Pending, Triggered, or Reset Pending.
a. Select column IDs from the All Columns field.
b. Click the right arrow to move your selected column IDs into the Selected Columns field.
c. If there are any column IDs in the Selected Columns field that you do not want to view, select them, and then click the left arrow to move your selected column IDs to the All Columns field.
d. Click the up or down arrows to change the order of your selected columns accordingly.
e. Position the slider to set the Alert View refresh rate.
f. If you are finished configuring your Active Alerts View, click OK.
6. Click Refresh to update the Active Alerts window with the latest alerts and column IDs.
7. Click Configure Alerts to change the settings for individual alerts. For more information, see "Advanced Alerts Creation and Management" on page 1.
8. If you want to acknowledge an active alert, check the alert in the Acknowledged column.
Note: As soon as the alert is acknowledged, the user information and date/time is recorded in the database.
Alert Viewer Settings
Alert views in the Orion NPM Advanced Alert Manager are configured in the Alert Viewer Settings window, as presented in the following procedure..
To configure alert views in the Advanced Alert Manager:
1. Click Start > SolarWinds Orion > Advanced Alert Manager.
2. Click File > Settings.
Note: The Configure Alerts tab of the Alert Viewer Settings window displays all available network alerts, and from this window you can create, copy, edit, and delete alerts. For more information, see "Creating and Configuring Advanced Alerts" on page 2.
4. Select the information titles that you want to see about your alerts from the All Columns list, and then click the right arrow to transfer them to the Selected Columns list.
Note: The Selected Columns list provides a list of all the information that the Alert Viewer will show for each active alert.
5. If you want to remove titles from the Selected Columns list, select titles that you want to remove from the active view in the Selected Columns list, and then click the left arrow.
6. If you want to rearrange the order in which the different pieces of alert information are presented in the Alert Viewer, select titles from the Selected Columns list and use the up and down arrows to arrange the titles accordingly.
7. Position the slider at the bottom of the tab to set the Alert View refresh rate.
8. Click Event View Columns.
9. Select the information titles that you want to see about events from the All Columns list, and then click the right arrow to transfer them to the Selected Columns list.
Note: The Selected Columns list provides a list of all the information that the Alert Viewer will show for each recorded event.
10. If you want to remove titles from the Selected Columns list, select titles that you want to remove from the active view in the Selected Columns list, and then click the left arrow.
11. If you want to rearrange the order in which the different pieces of event information are presented in the Alert Viewer, select titles from the Selected Columns list and use the up and down arrows to arrange the titles accordingly.
12. Position the slider at the bottom of the tab to set the Event View refresh rate.
13. Enter the number of events that you want to see in the Event View.
Adding Alert Actions
Orion Network Performance Monitor provides a variety of actions to signal an alert condition on your network. These alert actions are available for both basic and advanced alerts, and the following procedure assigns actions to the alert conditions that you have defined for your network.
To add an alert action:
1. Click Start > SolarWinds Orion > System Manager.
2. Click Alerts > Active Alerts.
4. Check the alert to which you want to add the action.
5. Click Edit Alert.
6. Click the Actions tab.
7. Select the action that you want to edit.
8. Click Add Alert Action.
The following procedures detail the configuration of each available action type.
Send an E-mail / Page
The Edit E-mail/Page Action window includes several tabs for configuration. The following procedure will configure an email/page alert.
To configure an email/page action:
1. Click the E-mail/Pager Addresses tab.
2. Complete the To, CC, BCC, Name, and Reply Address fields, as appropriate for your alert.
Some pager systems require a valid reply address in order for the page to complete.
3. Click the SMTP Server tab.
4. Enter the Hostname or IP Address of your SMTP Server and the designated SMTP Port Number.
Note: The SMTP server hostname or IP address field is required. You can not send an email/page alert without identifying the SMTP server.
5. If your SMTP server requires authentication, check This SMTP Server requires Authentication.
6. Click the Trigger Message tab.
7. Enter the Subject and Message of your alert trigger email/page.
Trigger messaging will be suppressed if both the Subject and Message fields are left empty.
8. Click the Reset Message tab.
9. Enter the Subject and Message of your alert reset email/page.
• Trigger messaging will be suppressed if both the Subject and Message fields are left empty.
10. If you are finished configuring your email/page alert action, click OK.
Orion Network Performance Monitor alert engines can use variables within the messages that are sent when an alert is triggered or reset. These variables are dynamic, and they parse when the alert is triggered or reset.
Note: In previous versions of Orion Network Performance Monitor Network Performance Monitor, variables were referred to as macros.
Advanced Alert Engine Variables
General
Variable Identifier
Description
${Version}
Version of the SolarWinds software package
${Copyright}
Copyright information
${Release}
Release information
${Application}
SolarWinds application information
${CR}
Line Feed – Carriage Return
${ObjectName}
Description/Name of the object in the alert
${AlertTriggerTime}
Date and time of the last event for this Alert. (Windows control panel defined "Short Date" and "Short Time")
${AlertTriggerCount}
Count of triggers
${Acknowledged}
Acknowledged status
${AcknowledgedBy}
Who the alert was acknowledged by
${AcknowledgedTime}
Time the alert was acknowledged
Custom MIB Poller
${CustomPollers.UniqueName}
Name of the Custom MIB Poller
${CustomPollers.Description}
Description of the Custom MIB Poller
${CustomPollers.OID}
OID
${CustomPollers.MIB}
MIB
${CustomPollerStatus.Total}
Total
${CustomPollerStatus.Rate}
Rate
${CustomPollerStatus.Status}
Status
${CustomPollerStatus.DateTime}
Date/Time
${CustomPollers.Enabled}
Enabled status of the Custom MIB Poller
${DateTime}
Current date and time. (Windows control panel defined "Short Date" and "Short Time" format)
${Date}
Current date. (Short Date format)
${LongDate}
Current date. (Long Date format)
${MediumDate}
Current date. (Medium Date format)
${Time}
Current Time. (Short Time format)
${DayOfWeek}
Current day of the week.
${D}
Current day of the month
${DD}
Current day of the month (two digit number, zero padded)
${AbreviatedDOW}
Current day of the week. Three character abbreviation.
${LocalDOW}
Current day of the week. Localized language format.
${M}
Current month
${MM}
Current month. Two digit number, zero padded.
${MMM}
Current month. Three character abbreviation.
${MMMM}
Full name of the current month
${LocalMonthName}
Current month name in the local language.
${DayOfYear}
Numeric day of the year
${Year2}
Two digit year
${Year}
Four digit year
${H}
Current hour
${HH}
Current hour. Two digit format, zero padded.
Current minute
${Minute}
Current minute. Two digit format, zero padded.
${S}
Current second.
${Second}
Current second. Two digit format, zero padded.
${LastHour}
Last hour
${Last2Hours}
Last two hours
${Last24Hours}
Last 24 hours
${Today}
Today (Short Date format)
${Yesterday}
Yesterday (Short Date format)
${Last7Days}
Last seven days (Short Date format)
${AMPM}
AM/PM indicator
SQL Query
Any value that you can collect from the database can be generated, formatted, or calculated using a SQL query as a variable. To use a SQL query as a variable, use ${SQL:{query}} as follows:
${SQL:Select Count(*) From Nodes}
Node Status Variable
When using the ${Status} variable with a node, numeric values are returned. The following table provides a description for each numeric value.
Numeric Value
${0}
Unknown
${1}
Up
${2}
Down
${3}
Warning
${4}
Shutdown
${5}
Testing
${6}
Dormant
${7}
NotPresent
${8}
LowerLayerDown
${9}
Unmanaged
Custom Interface Poller Variables
The following are valid custom interface poller variables.
Note: At least one of the CustomPollerStatus alerts from the table below must be included in the trigger condition of any and all Custom Interface Poller alerts.
Custom Interface Poller Variable
${Node.NodeID}
${Node.LastSync}
${Node.ObjectSubType}
${Node.IP_Address}
${Node.Caption}
${Node.DNS}
${Node.Community}
${Node.SysName}
${Node.MachineType}
${Node.VendorIcon}
${Node.Vendor}
${Node.LastBoot}
${Node.SysObjectID}
${Node.Description}
${Node.IOSImage}
${Node.IOSVersion}
${Node.GroupStatus}
${Node.StatusDescription}
${Node.Location}
${Node.Contact}
${Node.Status}
${Node.StatusLED}
${Node.Severity}
${Node.ResponseTime}
${Node.PercentLoss}
${Node.AvgResponseTime}
${Node.MinResponseTime}
${Node.MaxResponseTime}
${Node.RediscoveryInterval}
${Node.NextRediscovery}
${Node.PollInterval}
${Node.StatCollection}
${Node.NextPoll}
${Node.EngineID}
${Node.CPULoad}
${Node.TotalMemory}
${Node.MemoryUsed}
${Node.PercentMemoryUsed}
${Node.BufferNoMemThisHour}
${Node.BufferNoMemToday}
${Node.BufferSmMissThisHour}
${Node.BufferSmMissToday}
${Node.BufferMdMissThisHour}
${Node.BufferMdMissToday}
${Node.BufferBgMissThisHour}
${Node.BufferBgMissToday}
${Node.BufferLgMissThisHour}
${Node.BufferLgMissToday}
${Node.BufferHgMissThisHour}
${Node.BufferHgMissToday}
${Node.Allow64BitCounters}
${Node.CMTS}
${Node.MemoryAvailable}
${Node.PercentMemoryAvailable}
${Node.DynamicIP}
${Node.UnManaged}
${Node.UnManageUntil}
${Node.SNMPV2Only}
${Node.SystemUpTime}
${Node.SNMPV3Username}
${Node.SNMPV3Context}
${Node.SNMPV3PrivMethod}
${Node.SNMPV3PrivKey}
${Node.SNMPV3PrivKeyIsPwd}
${Node.SNMPV3AuthMethod}
${Node.SNMPV3AuthKey}
${Node.SNMPV3AuthKeyIsPwd}
${Node.SNMPVersion}
${Node.BlockUntil}
${Node.CustomPollerLastStatisticsPoll}
${Node.AgentPort}
${Interfaces.NodeID}
${Interfaces.InterfaceID}
${Interfaces.LastSync}
${Interfaces.FullName}
${Interfaces.InterfaceName}
${Interfaces.InterfaceAlias}
${Interfaces.InterfaceIndex}
${Interfaces.InterfaceType}
${Interfaces.InterfaceTypeName}
${Interfaces.InterfaceTypeDescription}
${Interfaces.InterfaceSpeed}
${Interfaces.InterfaceMTU}
${Interfaces.InterfaceLastChange}
${Interfaces.PhysicalAddress}
${Interfaces.Status}
${Interfaces.StatusLED}
${Interfaces.AdminStatus}
${Interfaces.OperStatus}
${Interfaces.AdminStatusLED}
${Interfaces.OperStatusLED}
${Interfaces.Severity}
${Interfaces.InterfaceIcon}
${Interfaces.InBandwidth}
${Interfaces.OutBandwidth}
${Interfaces.Outbps}
${Interfaces.Inbps}
${Interfaces.OutPercentUtil}
${Interfaces.InPercentUtil}
${Interfaces.OutPps}
${Interfaces.InPps}
${Interfaces.InPktSize}
${Interfaces.OutPktSize}
${Interfaces.OutUcastPps}
${Interfaces.OutMcastPps}
${Interfaces.InUcastPps}
${Interfaces.InMcastPps}
${Interfaces.InDiscardsThisHour}
${Interfaces.InDiscardsToday}
${Interfaces.InErrorsThisHour}
${Interfaces.InErrorsToday}
${Interfaces.OutDiscardsThisHour}
${Interfaces.OutDiscardsToday}
${Interfaces.OutErrorsThisHour}
${Interfaces.OutErrorsToday}
${Interfaces.MaxInBpsToday}
${Interfaces.MaxInBpsTime}
${Interfaces.MaxOutBpsToday}
${Interfaces.MaxOutBpsTime}
${Interfaces.Caption}
${Interfaces.PollInterval}
${Interfaces.RediscoveryInterval}
${Interfaces.NextRediscovery}
${Interfaces.NextPoll}
${Interfaces.Counter64}
${Interfaces.StatCollection}
${Interfaces.SignalNoise}
${Interfaces.MinSignalNoise}
${Interfaces.MaxSignalNoise}
${Interfaces.AvgSignalNoise}
${Interfaces.TotalCodewords}
${Interfaces.CodewordsUnerrored}
${Interfaces.CodewordsCorrected}
${Interfaces.CodewordsUnCorrectable}
${Interfaces.PercentCodewordsUnerrored}
${Interfaces.PercentCodewordsCorrected}
${Interfaces.PercentCodewordsUnCorrectable}
${Interfaces.IfName}
${Interfaces.XmitRecvBps}
${Interfaces.AvgXmitRecvPercentUtil}
${Interfaces.ObjectSubType}
${Interfaces.PercentCodewordsUncorrectable}
${Interfaces.VirtualInterface}
${Interfaces.CustomPollerLastStatisticsPoll}
${Interfaces.CustomPollerLastStatusPoll}
${CustomPollerAssignment.CustomPollerAssignmentID}
${CustomPollerAssignment.AssignmentName}
${CustomPollerAssignment.PollerID}
${CustomPollerAssignment.NodeID}
${CustomPollerAssignment.InterfaceID}
${CustomPollers.PollerID}
${CustomPollers.SNMPGetType}
${CustomPollers.NetObjectPrefix}
${CustomPollers.GroupID}
${CustomPollers.PollerType}
${CustomPollers.ParserID}
${CustomPollers.Format}
${CustomPollers.IncludeHistoricStatistics}
${CustomPollers.Unit}
${CustomPollers.TimeUnitID}
${CustomPollers.TimeUnitQuantity}
${CustomPollers.DefaultDisplayTimeUnitID}
${CustomPollers.LastChangeUTC}
${CustomPollers.LastChange}
${CustomPollerStatus.CustomPollerAssignmentID}
${CustomPollerStatus.DateTimeUTC}
Custom Node Poller Variables
The following are valid custom node poller variables.
Note: At least one of the CustomPollerStatus alerts from the table below must be included in the trigger condition of any and all Custom Node Poller alerts.
Custom Node Poller Variable
${Node.Username}
${Node.Password}
${Node.EnableLevel}
${Node.EnablePassword}
${CustomPollerStatus.PollerID}
${CustomPollerStatus.NodeID}
${CustomPollerStatus.InterfaceID}
Interface Variables
The following are valid interface variables.
Interface Variable
${Interfaces.IP_Address}
${Interfaces.DNS}
${Interfaces.Community}
${Interfaces.SysName}
${Interfaces.MachineType}
${Interfaces.VendorIcon}
${Interfaces.Vendor}
${Interfaces.LastBoot}
${Interfaces.SysObjectID}
${Interfaces.Description}
${Interfaces.IOSImage}
${Interfaces.IOSVersion}
${Interfaces.GroupStatus}
${Interfaces.StatusDescription}
${Interfaces.Location}
${Interfaces.Contact}
${Interfaces.ResponseTime}
${Interfaces.PercentLoss}
${Interfaces.AvgResponseTime}
${Interfaces.MinResponseTime}
${Interfaces.MaxResponseTime}
${Interfaces.EngineID}
${Interfaces.CPULoad}
${Interfaces.TotalMemory}
${Interfaces.MemoryUsed}
${Interfaces.PercentMemoryUsed}
${Interfaces.BufferNoMemThisHour}
${Interfaces.BufferNoMemToday}
${Interfaces.BufferSmMissThisHour}
${Interfaces.BufferSmMissToday}
${Interfaces.BufferMdMissThisHour}
${Interfaces.BufferMdMissToday}
${Interfaces.BufferBgMissThisHour}
${Interfaces.BufferBgMissToday}
${Interfaces.BufferLgMissThisHour}
${Interfaces.BufferLgMissToday}
${Interfaces.BufferHgMissThisHour}
${Interfaces.BufferHgMissToday}
${Interfaces.Allow64BitCounters}
${Interfaces.CMTS}
${Interfaces.CMTSPoll}
${Interfaces.CMTSImport}
${Interfaces.CMTSPollStatus}
${Interfaces.CMTSImportStatus}
${Interfaces.CMTSImportPending}
${Interfaces.MemoryAvailable}
${Interfaces.PercentMemoryAvailable}
${Interfaces.Username}
${Interfaces.Password}
${Interfaces.EnableLevel}
${Interfaces.EnablePassword}
${Interfaces.DynamicIP}
${Interfaces.UnManaged}
${Interfaces.UnManageUntil}
${Interfaces.SNMPV2Only}
${Interfaces.Department}
${Interfaces.Home}
${Interfaces.Web}
${Interfaces.Telnet}
${Interfaces.DeviceType}
${Interfaces.SystemUpTime}
${Interfaces.WirelessAP}
${Interfaces.WirelessLastStatPoll}
${Interfaces.WirelessStatBlockUntil}
${Interfaces.WirelessPollInterval}
${Interfaces.WebView}
${Interfaces.Manager}
${Interfaces.SubInterface}
${Interfaces.Frequency}
${Interfaces.ChannelWidth}
${Interfaces.Modulation}
${Interfaces.SymbolRate}
${Interfaces.TotalModems}
${Interfaces.ActiveModems}
${Interfaces.RegisteredModems}
${Interfaces.Carrier}
${Interfaces.SLA}
${Interfaces.Bps}
${Interfaces.Comments}
${Interfaces.CircuitID}
${Interfaces.ModulationProfileID}
Node Variables
The following are valid node variables.
Node Variable
${Node.NodeID }
Volume Variables
The following are valid volume variables.
Volume Variable
${Node.CMTSPoll}
${Node.CMTSImport}
${Node.CMTSPollStatus}
${Node.CMTSImportStatus}
${Node.CMTSImportPending}
${Node.Department}
${Node.Home}
${Node.Web}
${Node.Telnet}
${Node.DeviceType}
${Node.WirelessAP}
${Node.WirelessLastStatPoll}
${Node.WirelessStatBlockUntil}
${Node.WirelessPollInterval}
${Node.WebView}
${Node.Manager}
${Volumes.NodeID}
${Volumes.VolumeID}
${Volumes.LastSync}
${Volumes.VolumeIndex}
${Volumes.Caption}
${Volumes.PollInterval}
${Volumes.StatCollection}
${Volumes.RediscoveryInterval}
${Volumes.VolumeDescription}
${Volumes.VolumeType}
${Volumes.VolumeTypeIcon}
${Volumes.VolumePercentUsed}
${Volumes.VolumeSpaceUsed}
${Volumes.VolumeSize}
${Volumes.Status}
${Volumes.StatusLED}
${Volumes.VolumeResponding}
${Volumes.VolumeAllocationFailuresThisHour}
${Volumes.VolumeAllocationFailuresToday}
${Volumes.NextPoll}
${Volumes.NextRediscovery}
${Volumes.FullName}
${Volumes.VolumePercentAvailable}
${Volumes.VolumeSpaceAvailable}
That was the post, thanks!
Ok, stupid question... what is OAG?
The only thing I can think of is On-line Administrators Guide
Orion Administrator Guide
