Redundancy Control
Redundancy Control helps you identify and manage situations where multiple JVMs are sending excessive or duplicate data to Intelligence Cloud. This includes crash loops where JVMs repeatedly restart and send the same data, or scenarios with many similar JVM instances running simultaneously. By controlling this redundant data flow, you can optimize your usage quota and ensure that Intelligence Cloud stores only unique, valuable information.
Based on tags and conditions, Intelligence Cloud can instruct JVMs (via the Forwarder) to only report the data needed for the JVM Inventory reporting.
Configuring Redundancy Control
Administrators can configure Redundancy Control in the WebUI > Settings > Redundancy. By specifying a tag with a frequency limit and time range, JVMs will be instructed to only send Inventory information.
An example:
-
Tag:
AppEnv -
Frequency limit: 60
-
Time range: 1 hour
With this configuration, traffic for the 61st and following JVMs with AppEnv=Value1 will be reduced. JVMs with other tags, e.g. AppEnv=Value2, will not be limited if there are less than 60 of them running so far. You can use any tag key, not only AppEnv, from the dropdown.
If a JVM is started without the configured tag, the value will be considered to be UNDEFINED and will also be taken into account and limited by the configuration when the threshold limit is reached for all UNDEFINED runs.
All redundant JVMs will still be available in the JVM Inventory reporting.
Monitoring Redundancy Control
You can get a summary of JVM runs identified as redundant by configured tags in the WebUI > Explorer > VM Runs Redundancy.
