Question A
I am unable to find a very basic straight forward comparison between the Legacy OS Cartridge Monitoring and the Infrastructure Remote OS Monitoring. I need something that just shows what features you get and don't get with each one.
Question 1
What is the road map for the Legacy and the Infrastructure Cartridge?
Question 2
If and when do you expect the Infrastructure Cartridge to contain all the features of the Legacy Cartridge?
Question 3
If using the Legacy Cartridge and the network dies between the Legacy Agent and the FMS, how long does the Legacy Cartridge retain metrics before it rolls over if the FMS does not come back right away?
Question 4
Is there any network traffic (performance) differences between the Infrastructure Cartridge collecting metrics from a specific host or the Legacy Cartridge collecting metrics from a specific host?
Answer A
The monitoring style has changed between the OS and IC agents,
different metrics/rules are used in IC than OS.
I have included the user / reference guides for both agent types
as well as the additional information you will need for the IC agent.
This way you can compare the dashboards, rules and metrics collected for each one
OS Agent details
-----------------------------------------
User/Reference guides
IC Infrastructure agent details
-----------------------------------------
User/Reference guide
FglAM Requirements for Remote Monitoring
Agent Manager Guide
Credentials/lockboxes for remote host monitoring
Admin and Configuration Guide
Answer 1
Part A - Road map for Legacy
There is no road map, this cartridge is out of support
Part B - Road map for IC
The OS portion of the IC agent is considered completed.
All utility agents (WebMonitor, LogFilter, etc) except for
Terminal Server will be rewritten at some point and moved to a
utilities cartridge separate from the IC and OS cartridge.
Most of the utility agents are already being coded/tested and
should start to be released this year
Answer 2
Same as part B for the answer to Question 1
Part B - Road map for IC
The OS portion of the IC agent is considered completed.
All utility agents (WebMonitor, LogFilter, etc) except for
Terminal Server will be rewritten at some point and moved to a
utilities cartridge separate from the IC and OS cartridge.
Most of the utility agents are already being coded/tested and
should start to be released this year
******* If you currently require LogFilter / AppMonitor,
you will still have to deploy a local FglAM
WebMonitor you can do remotely, as long as
you can properly get to the target URL
Answer 3
This item does not depend on the Agent, but the FglAM itself.
It is the FglAM itself that caches data on the FglAM host
(as long as the memory of the FglAM holds out) while there
is an outage to the FMS.
If the FglAM memory cache gets full, the FglAM starts dumping
the agent data out of the cache until such a time when the
connection is restored and the data can be sent to the FMS.
This issue depends on the number of agents deployed, the
amount of data collection, the FglAM memory and the length
of the outage. There may be gaps in data collection for
the agents after the connection to the FMS is restored
because it was too much data for the FglAM to hold.
Answer 4
The gain in performance is not over the network for the IC agent.
All agents (local or remote) will have their data transported
over the network by the FglAM. The IC/OS agents are comparable
in data sizes.
The performance gain is that if you monitor remotely you do not
have the overhead of a FglAM and agents running on your target server
