What to do when an agent is offline?
When installed/restarted an agent first performs a web post to
api.opsramp.com on port 443 to get the server to connect.
- Verify if DNS resolution is working.
- Telnet to port 443 on
- In the browser, enter
https://api.opsramp.comand verify the redirect to OpsRamp .
What if the agent cannot reach api.opsramp.com?
api.opsramp.com is not reachable, the agent falls back to
cn01-sjc.opsramp.com after six (6) checks to get the server URL to connect.
After getting the first response from
api.opsramp.com, the agent connects to the servers based on which node the client is connected to. An agent log file is displayed and provides information about the agent connected to DNS.
How do I validate the agent if it is displayed offline?
- Make sure DNS resolution is working.
- Telnet to port 443 on above URLs based on what URL agent is connected to.
- In the browser, type
https://Above URL/stats. It displays a page with Agent count text.
- If above validations are successful and agent remains offline, create a support ticket with the AgentLog file attached. Mention if the agent is a proxy agent or direct agent.
What are that steps that the agent shield uses for direct agent and proxy agent?
|Agent process does not run||Agent Shield restarts the agent.|
|Agent process does not run|
|Agent process consumes more than 250 MB memory||Agent Shield restarts the agent.|
|Agent process consumes more than 2500 handle count of resources||Agent Shield restarts the agent.|
|Agent process consumes more than 250 thread count of execution||Agent Shield restarts the agent.|