Discussion Feed

Hi Team,   We are facing the same issue in our environment.    We are facing issue while installing the machine agent service on linux box whose O.S version is as follow:SUSE Linux Enterprise Server 11 (x86_64).   When using the system systemctl command to create the service, it throws up an error that "systemctl" command is not found. Also, I am not sure whether we need to make changes suggested in below step: >>Edit the environment variables and options in the service file as needed:   /etc/systemd/system/appdynamics-machine-agent.service >> /opt/appdynamics/machine-agent/etc/systemd/system/appdynamics-machine-agent.service   MACHINE_AGENT_HOME: Specifies where the Machine Agent files are located.   JAVA_HOME: Specifies the JRE the agent uses. The Machine Agent bundles the JRE that we recommend you use, but you can use an existing JRE. (1.7 or higher)   User: This option in the service file specifies the system user to be used to start the Standalone Machine Agent. By default this is root. AppDynamics recommends that you create a non-root user to run the machine agent. The new user needs to have read-access to controller-info.xml and write access to the log file. See Permissions for Non-Root User to Run the Machine Agent for more details. "MACHINE_AGENT_USER" variable doesn't exist in the systemd service file.   ExecStart: This option in the service file points to a script that starts the agent as a daemon. If you didn't install the machine agent in /opt/appdynamics/machine-agent, then change the path to <machine-agent-home>/scripts/machine-agent-daemon.>> The machine agent is able to start and connect to controller but we are finding challenges in making the service. Please assist.   Regards, Anuranjan Kumar ... View more

Hi Atyuha,   We have already deployed machine agent as well as java agent, and we are getting some data. But we need more deep dive data such as services which are running on the server/host.   Our priority is to get data ralated to services on host.   Please guide us for the same.   Thanks Atyuha !!!   Regards, Anuranjan Kumar ... View more