Manage agent hours volume

AppMon supports usage-based licensing. Instead of a static number of Agents that are allowed to connect usage-based licensing offers a more flexible model. In times with high load a usage-based volume can be used to connect extra Agents in addition to a static baseline. The unit used to count the consumption is Agent Hour and can be consumed by any technology. Agent hours for z/OS based Agents on Java, CICS & IMS are only provided for trials. Usage based licensing (agent hours) for productive use is not available for z/OS.

Agent hours

An Agent running for a 60 minute period, counted from the beginning to the end of the hour (AppMon server time) is measured as one agent hour. Partial hours are counted as a full hour, but only to the maximum of concurrently attached Agents of the same technology type:

  • Two Java Agents operating in sequence during an hour counts as one Java Agent hour.
  • Five Java Agents operating concurrently for 10 minutes within one hour counts as five Java Agent hours.

Usage-based volume vouchers

To use usage-based licensing a volume voucher needs to be added to the license. It contains a number of agent hours as purchased, where the unit volume is usually Agent Years. One agent year is the equivalent of 9,000 agent hours (~ 24h * 365). Each usage-based volume has a start and an end date. Multiple volumes are treated separately by the AppMon server. The volume that expires first is used first. Incidents are created when the total used agent hours volume reaches certain thresholds (75%, 90%, 95% and 100%). Volume is not used if the volume start date is not reached.

Usage-based volume consumption

Usage-based volume is used whenever there aren't enough perpetual Agent licenses to satisfy the current demand. For example, if there are five perpetual Java Agents in the license but six are connected, the 6th consumes one agent hour per hour of the usage-based volume. License Assignments can be used for limiting consumption of usage-based volume and for configuring the usage of agent hours.

For the consumption of usage-based volume the maximum number of concurrently connected Agents per technology type and per hour is taken into consideration. This value is multiplied with a technology-dependent weight to get the number of agent hours deducted from the usage-based volume. The calculation is performed every full hour.

Agent technology types Unit volume Weight
Java Agent (JVM) - Windows, Unix, Linux, z/OS1 Per JVM
.NET Windows OS Instance (WOSI) Per WOSI
PHP Agent  Per parent process ID (PID)
Node.js Agent  Per process 0.1
IBM integration bus Agent Per process 0.2
Native Agent (ADK) Per process
Database Agent Per instance (8 Cores)
WebServer Agent Per Agent 0.6
NoSQL Agent Per JVM 0.6
Host Monitoring Agent Per host 0.04
z/OS CICS & IMS1 Per region 10

1 z/OS Agents (Java, IMS and CICS) are able to consume agent hours, which is only allowed for PoCs or trials.

For example, 20 Java Agents plus five WebServer Agents monitoring for one hour = (20 Java agent hours * 1) + (5 WebServer agent hours * 0.6) = 23 agent hours consumed from the usage-based volume.

The License Overview dashboard provides information about the agent hours volume usage. The Current Usage column lists the total count of Agents, the OK column shows Agents covered by the perpetual license, and the Consumption Based column lists how many Agents are currently consuming agent hours.

How to manage your usage-based volume

Use the AppMon Client to manage your usage-based volume. The Client must have an Internet connection to access the eServices website. This is the recommended way to manage usage-based volume because it simplifies the process for adding and deactivating consumption volume from your license.

If you are unable to connect to eServices from the Client, you may need to configure a proxy server. For more details, see Configuring a Proxy Server to Connect to eServices.

For instructions on upgrading usage-based volume, see License Upgrade.

Once activated, create License Assignments to precisely manage usage-based volume across multiple System Profiles and Agent Groups.

Add usage-based volume

The online method for adding usage-based volume is initiated in the Client and includes logging into eServices and activating the volume. See below for step-by-step instructions.

Manually add usage-based volume using a file

To manually add usage-based volume, you must download a volume file from eServices and import the file in the Client. The license must be activated to enable the Redeem button in eServices.

Deactivate usage-based volume

Use the AppMon Client to deactivate usage-based volume. This includes logging into eServices and deactivating the volume.

Manually deactivate usage-based volume

Deactivating Consumption volume requires generating a volume deactivation key in the Client, and then accessing eServices and manually entering the key. See below for step-by-step instructions.