Couldn't find any earlier discussion about this. When registering a new agent from the agent's side (agent-initiated connection), a proxy agent can be defined:
Is there any further documentation regarding this? What does the proxy agent setup entail, is it basically the same as installing a regular agent but with the exception that this one also accepts and forwards measurement data from one or more agents & sends it to the agent manager? Is it then dedicated to be used as a proxy agent, or can it still execute its own monitoring and forward all the data (own + other agents') to the manager? And finally, is the process of adding the proxy agent as a new agent in the Synthetic Console the same as if it was a regular agent?
One way to achieve similar functionality as the agent proxy would be to define a child agent manager, but I'm wondering whether this type of chain is possible:
Manager A = Parent
Manager B = Child to Manager A
Manager C = Child to Manager B?
So then C would send monitoring data to B, and B would forward it to A, and from A it would go to CAS. Is that type of setup possible?
Answer by Carol O. ·
Hi. I have modified the documentation for Adding an Agent with Agent-Initiated Communication; I think it was confusing. I'm not sure what you meant by "proxy agent", but the Agent-initiated registration really refers to defining a proxy that may be required for the Agent to communicate with the Agent Manager. You can use this if you need a proxy. It is similar to configuring a proxy server in the Agent General Tab or in the Agent Manager General Tab. You may also want to refer to the proxy server documentation in Servers Content Pane
I think some customers have used multiple hierarchical Agent Managers. If needed, you should be able to use this type of chain (PAM = Parent Agent Manager; CAM = Child Agent Manager):
PAM A = Parent AM with configuration
PAM B = Parent AM reporting to its Parent AM A
CAM C = Child AM reporting to its Parent AM B.
So then C's Agents would send monitoring data to C; C would send data to B, and B would forward it to A.
Answer by Kalle L. ·
No responses yet, but in the meantime another question: the agents connecting to the proxy need to get their Recorder licensing from somewhere. I suppose you could install DLM on a Proxy Agent and have the agents get their licensing from there, right? So far we've had the DLM running either at CAS or an Agent Manager, but I suppose there's no limitation to put it on a Proxy Agent...