Privileges required for new OS agents in 4.2
Hi,
I'm just taking a look through the new 4.2 documentation and I couldn't seem to find any reference to the permissions required by the new Operating System Agents (I'm not sure if that is the correct name).
I know a few people who absolutely refuse to give out administrative access so I would appreciate if you could provide any insight into this area. I guess I'm coming from a Windows point of view, but any *nix information would also be highly appreciated.
Thanks in advance,
Steve
Hi Stephen
The requirement for our new "Host Monitoring Agent" was to work without requiring specific system privilidges. Check out the section "What is Monitored?" on the following doc page: Host Health Monitoring
Let me know if this is enough information or if you need more details.
Our Host Monitoring Agent uses different Operating System APIs to retrieve this data - these are APIs that should be callable by a standard user with no extra privilidges.
Andi
Andi,
I want to piggy back on this thread to ask a couple of questions about the new Host Agent:
1. Is it separately licensed? If so, why?
2. Can the host agent and Java/.NET agent co-exist? If so, who does what?
3. Is there plan to deprecate Java/.NET agents from collecting JVM/CLR metrics so only host agents can do that?
Thanks.
Manoj
Happy to answer these questions
1. A certain amount of Host Monitoring Agents are FREE when you buy a Production License - I think its 25 Hosts that are free. If you want more than that we sell them in packs of 25. But - remember - every dynaTrace Agent (Java, .NET, Native, Web Server) also collects this new Host Information data. So - for all of your machines where you have a Java/.NET/.. Agent running anyway you DO NOT need an extra Host Agent
2. Yes - they can co-exist. Both agents will send Host Information to the dynaTrace Server but only one set of data will be stored (otherwise it would be redundant information). This supports the scenario where you e.g: have a Windows server that runs ASP.NET. Typcially you would rely on the .NET Agent to send Host Information. When there is no load on the system, IIS will shutdown the ASP.NET Worker Processes and with that our .NET Agent. In case you also want Host Information in these times of no traffic you want to install an additional Host Agent so that you always get Host Information data
3. No plan to deprecate this. The Host Monitoring Agent will monitor Host Information - NOT APP specific information. The Java/.NET Agent on the otherside have direct access to these JVM/CLR metrics and will therefore provide these metrics
Hope this helps
