close

Filter

loading table of contents...

Operations Basics / Version 2101

Table Of Contents

5.3.5 Proactive Engine Sub Component

The Proactive Engine is a sub component of the CAE Feeder. The attributes and metrics mentioned in Table 5.5, “Proactive Engine JMX Monitoring” are suggested for monitoring.

For a complete overview of available attributes and metrics have a look at Section 6.3, “CAE Feeder JMX Managed Beans” in Search Manual and com.coremedia.cap.persistentcache.proactive.ProactiveEngineManagement.

ProactiveEngine.KeysCount
Type Gauge
Value Type int
Description

The total number of "keys" that need to be kept up-to-date by the CAE Feeder.

The value may go down when destroying content or moving content outside the path configured for feeding.

Should be monitored together with ValuesCount. See description of ValuesCount for details.

ProactiveEngine.ValuesCount
Type Gauge
Value Type int
Description

The number of "keys" whose latest evaluation is still up-to-date. This is a subset of the total number of keys returned by attribute KeysCount and thus ValuesCount is always less than or equal to KeysCount.

The value may go down on invalidations.

Monitoring typically observes the difference of KeysCount versus ValuesCount: A stable state is reached, when KeysCount is equal to ValuesCount. Otherwise, so if ValuesCount is less than KeysCount, the value of ValuesCount should increase over time. If it does not increase within a given amount of time, you should raise an alarm.

Table 5.5. Proactive Engine JMX Monitoring


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.