org.rhq.enterprise.server.alert.engine
Interface AlertConditionCacheManagerLocal

All Known Implementing Classes:

AlertConditionCacheManagerBean

public interface AlertConditionCacheManagerLocal

This is the SLSB interface for interacting with the clustered cache that stores and computes whether AlertDefinition conditions have become true for which Resources in the system. It consequently calls the condition listener MDB, which stores the fired conditions to the backing store. A separate process later comes along and decides - depending on the recovery property, enablement actions, and enablement filtering options that were set on the AlertDefinition this condition was triggered against - whether an alert should fire or not.

Method Summary

AlertConditionCacheStats	checkConditions(org.rhq.core.domain.measurement.Availability... availability) Since Availability is no longer a measurement, it must be checked differently.
AlertConditionCacheStats	checkConditions(org.rhq.core.domain.measurement.calltime.CallTimeData... callTimeData) A MeasurementReport is full of CallTimeData objects.
AlertConditionCacheStats	checkConditions(DriftChangeSetSummary driftChangeSetSummary) Drift changes that an agent reported.
AlertConditionCacheStats	checkConditions(org.rhq.core.domain.event.EventSource source, org.rhq.core.domain.event.Event... events) An EventReport is full of Event objects.
AlertConditionCacheStats	checkConditions(org.rhq.core.domain.measurement.MeasurementData... measurementData) A MeasurementReport is full of MeasurementData objects.
AlertConditionCacheStats	checkConditions(org.rhq.core.domain.operation.OperationHistory operationHistory) Operation history occurs in two distinct phases.
AlertConditionCacheStats	checkConditions(org.rhq.core.domain.configuration.ResourceConfigurationUpdate update) ResourceConfiguration changes can be made through the UI or on the managed resource.
void	reloadAllCaches()
void	reloadCachesForAgent(int agentId)
void	reloadGlobalCache()

Method Detail

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.measurement.MeasurementData... measurementData)

A MeasurementReport is full of MeasurementData objects. Each of these could potentially match against one of the cache's conditions. So, each must be checked against it, to see whether it fires against any of the conditions.

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.measurement.calltime.CallTimeData... callTimeData)

A MeasurementReport is full of CallTimeData objects. Each of these could potentially match against one of the cache's conditions. So, each must be checked against it, to see whether it fires against any of the conditions.

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.operation.OperationHistory operationHistory)

Operation history occurs in two distinct phases. The first is when the operation is first triggered. An OperationHistory element gets persisted whose status is INPROGRESS. The request is sent down to some agent that carries out the requested work. Each agent will send a response back out-of-band and update the operation accordingly. This method needs to be called in BOTH circumstances. Since the current implementation of the alerts subsystem allows you to generate an alert based on ANY of the valid states an operation can be in, we must check the conditions when the OperationHistory is in the only INPROGRESS state as well as any of the various 'resultant' states.

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.measurement.Availability... availability)

Since Availability is no longer a measurement, it must be checked differently. As a side note, since Availability is RLE users can ONLY be notified when the Availability changes. If the Availability for a resource doesn't change between two consecutive reports, this method can be safely called, but it will not trigger an event.

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.event.EventSource source,
                                         org.rhq.core.domain.event.Event... events)

An EventReport is full of Event objects. Each of these could potentially match against one of the cache's conditions. So, each must be checked against it, to see whether it fires against any of the conditions.

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(org.rhq.core.domain.configuration.ResourceConfigurationUpdate update)

ResourceConfiguration changes can be made through the UI or on the managed resource. Whenever a new ResourceConfigurationUpdate is created, it should be passed to this method

Returns:

the number of conditions that were true against this argument

checkConditions

AlertConditionCacheStats checkConditions(DriftChangeSetSummary driftChangeSetSummary)

Drift changes that an agent reported.

Parameters:

driftChangeSetSummary - data on the change set that is to be checked

Returns:

the number of conditions that were true against this argument

reloadCachesForAgent

void reloadCachesForAgent(int agentId)

reloadGlobalCache

void reloadGlobalCache()

reloadAllCaches

void reloadAllCaches()