Host not appearing in Dynatrace after fresh OneAgent install

[ryan_korteway]

Summary

There are times when you may deploy the OneAgent to a host and see the installation complete successfully, generate some logs for the OneAgent host monitoring process named ruxitagent_host_<PID>.0.log, and yet still not see said host in the Dynatrace UI. 

Problem

If you have a successful install and OneAgent host monitoring logs, ruxitagent_host_<PID>.0.log files, then your first step should be to open the log files and search for a string of several equal signs ===== in a row as this is a distinct sign of OneAgent deactivation for numerous reasons within the logs.

A few examples:

<Timestamp and thread number> info    [native] ============================== Agent inactivated ============================== (no more data will be sent by this agent, except heartbeats and config requests.)

or

<Timestamp and thread number> info    [native] ============================== Agent DEACTIVATED ============================== (it means the agent has been rejected by the server. no more data will be sent by this agent, except heartbeats.)
<Timestamp and thread number> info    [native] Exception handling periodic task heartbeat: received message with error code: REQUEST_REJECTED - sender's message: TokenFilter: Tenant token is invalid

Troubleshooting steps

Firstly it would be best to navigate to the oneagent log file location for your particular Deployment OS and OneAgent style.
Linux: https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/oneagent-configura... 

Or with as many OneAgent logs as you can provide for validating the state of the OA install and its current state when it comes to configuration and cluster communication.

Please provide only the first few characters of the --get-tenant-token outputs so that we can validate the token value against what we can see in the Dynatrace Support Backend, sharing the entire token would reduce its security and is not recommended.

[salumkalshahul]

Thanks for sharing this, Ryan :). Just to add - while building the usable dynatrace link using the OSI ID from the logs, I noticed that the letters in the OSI id appear in lowercase. However, when constructing the url, the letters in the OSI id need to be in uppercase. If not, it leads to a 404 error page.

[AntonioSousa]

@ryan_korteway ,

It's not the first time I have had a installation fail in a host that had been deactivated in the UI in the past 😅