Try OpenEdge Now
skip to main content
Alerts Guide and Reference
Introduction : Alert types : Polled alerts : Factors associated with assessing threshold values
Factors associated with assessing threshold values
OpenEdge Management can trigger an alert when a monitored resource performs outside the currently defined value for a threshold rule. However, the defined polling interval could be set such that x number of polling cycles (as defined in the Throw alert after polled field in the Rule definition section of a monitoring plan) must be complete before the alert is triggered.
For example, a CPU resource can be polled hourly to see if the CPU usage exceeds 90%. If the percentage does exceed 90%, an alert is generated. However, the alert will not trigger until the number of polling cycles as defined in the Throw alert after polled field is also exceeded.
Alerts that gather data through this polling process allow you to assess data polled over time to determine if your thresholds are too high or too low. You can adjust these threshold values, and the frequency with which the polling cycles are set to occur, at any time to refine your data collection.
The interpretation of a threshold value can vary from resource type to resource type. Differences in these interpretations can also affect what an alert display means for these various resource types. For an explanation of these resource-specific calculations, see the appropriate resource-specific rule details in the system, network, or file resource rule calculations in OpenEdge Management: Resource Monitoring. For details about database rule details, see OpenEdge Management: Database Management. For details about OpenEdge Management rules related to the OpenEdge server products, see OpenEdge Management: Servers, DataServers, Messengers, and Adapters.