This agent can monitor statistical events created by the user (user defined events) from events, which in turn are being monitored by other agents Osmius. The four types of statistical events can be monitored are:

• The average of an event in a period of time (last hour, last 7d, etc.).
• The accumulate of an event in a period of time (last hour, last 7d, etc.).
• The difference in the last value of one event with the last value of another event, or with respect to a constant value.
• Sum of several events

Statistical Osmius agent has been developed using functionalities and enhancements of Osmius framework and ACE libraries, so it is necessary to install the ACE libraries for the proper deployment and operation of Statistical Osmius agent. See chapter: installation.

Statistical agent does not provide any events to be monitored, it is the user who creates them and active in any instance of this agent.

This agent connects to the Osmius MySql database installed in the Osmius server to monitor events that are capturing the other agents, so it is essential that Statistical agent is able to connect to the Osmius server.

All events are remote, so not intrusive, and multiplatform. Statistical Osmius Agent is ready to reuse connections to the database and try to reconnect only when one event doesn't work.

As a general rule each Osmius agent can monitor one instance type. If you are not familiar with these concepts check out the glossary. Each instance is individually defined in the configuration file (if you want further information go to agents and instances); depending on agent type is the instance type and depending on instance is the connection info.

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info

For Statistical Osmius agent the connection_info prototype would be:

CONNECTION_INFO= -u USER -p PASSWORD -d BD_NAME -h BD_SERVER -l PORT

It should be noted that in the creation of an instance of type Statistical, the user will not be asked for this information. This data is automatically filled with data connection to the Osmius MySql database server:

• USER: User with access to the MYSQL database of the Osmius Server.
• PASSWORD: User password of the Osmius Mysql database Server.
• BD_NAME: Name of the MySQL database of the Osmius Server.
• BD_SERVER: Target IP (or host name if your DNS is able to resolve it) of the Osmius MYSQL database server.
• PORT: Port number of the MYSQL database of the Osmius Server.

Examples:

CONNECTION_INFO = -u osmius -p osmius -d osmius -h localhost -l 3306

The type defines the instance type to be monitored. Every declared instance must be associated with a type as you can see here

For Statistical agent:

TYPE= TRANSFER

Here's briefly the capabilities of this agent, further down on this page each event is described in more detail.

This UTEXAMP1 event returns the load cpu average of the server OSM_Host in the last hour.

Return values:

Recommended parameters:

Parameter setting example:

UTEXAMP1 = -t 86400 -c 0 -w 80 -a 90 -T ""  -s 0 -R "(ABS LINUX001.OSPRCCPU AV LH)" -A LINUX001 -B OSM_Host

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

Make sure you have an updated network map and clear in order to plan adequately monitoring.

• Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.

• In the particular case of Osmius Statistical agent you can easily generate Makefile as follows:

From the agent directory using console or terminal.

Linux:

$ACE_ROOT/bin/mpc.pl -type make osm_ag_transfer.mpc

HP-UX / Solaris:

$ACE_ROOT/bin/mpc.pl -type gnuace osm_ag_transfer.mpc

Windows and Visual C 8:

%ACE_ROOT%\bin\mpc.pl -type vc8 osm_ag_transfer.mpc

• Now that you have created the Makefile, agent compiling is extremely simple.

Linux:

make -f GNUmakefile.Osm_Ag_Transfer_Osmius

HP-UX:

gmake -f GNUmakefile.Osm_Ag_Transfer_Osmius

Windows:

Double click on Osm_Ag_Transfer_Osmius.vcproj and the project will be opened with Visual C. \\ Select the Rebuild option to compile.

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

Statistical agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

To run Statistical agent without Osmius web console:

Statistical agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests.

Basically you have to add a new value, called SNDCMD, to Osmius agent configuration file (osm_ag_TRANSFER.ini) as shown here.

Then you must run the Osmius agent for IP setting Master Agent communications port to zero, for example:

Performed test for Osmius Statistical agent.