How does dynatrace identify the state of a process
Hi Team,
Could you please let us know how dynatrace identifies the state of the process( running ,not running & terminated) and its PID. Attached the screenshot for the same.
Regards,
Anusha
We want to monitor the Process State( running ,not running & terminated) if we can get this information its enough we don't need the corresponding PID .We will perform the steps suggested by you above to find the process state .
Thank you Graeme : )
Anusha,
If you have access to a user account with permission to call WMI then possibly you could use the Generic Execution plugin to run a small PowerShell script to retrieve the information you want. The Generic Execution plugin is documented here: https://community.dynatrace.com/community/display/DL/Generic+Execution+Plugin
Is there any reason you need to know the PID? You can check to see if a process is still responding using the URL Monitor plugin: URL Monitor
The reason the agent is able to avoid all this is that it is running inside the process.
-- Graeme
Thanks Graeme.
We actually want to monitor a process of the system .We tried Windows Service Status Monitor Plugin and Windows Process Monitor Plugin ,but we were getting error as logon account configured for the dynaTrace collector needed to have appropriate access to the host(s) which we wanted to monitor (typically Administrator access to the server) as mentioned in Community .But in our case we don't have admin access for the same and also we don't have permission to add a new account which we could give admin access.
Hence we wanted to know how dynatrace gets the state and the PID so that we can get an alternate way to monitor the state of a process .Could you please suggest on this.
Regards,
Anusha
Anusha,
The agent – the Dynatrace library that is loaded into the process – makes calls to the operating system. Part of each agent is specific to the language environment (e.g., the Java agent is different to the .NET agent) and part of the agent is specific to the operating system that the application is running on (so a Windows agent is different to a Linux agent).
This screen is generated by the operating-system-specific part of the agent.
Was there a particular issue you were having with this data?
-- Graeme
