OPS agent on an e2-micro instance ends up borking within a 24 hour period.
And then it ends up prompting me to install it again, even though if I restart the instance, the agent starts back up and works again.
Hello ~ Can you verify on OPS agent logs if you see something related to `failed to start subagents: failed to start` ? If yes, make sure to install the OPS agent by following this documentation [1] and choosing the latest version [2]. On previous version of the OPS agent, it was reported that sometimes the installation fails silently.
[1] https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/installation
[2] https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/installation#list-versions
Systmctl says that the agent is running. Yes.
Is it possible that you are using a preemptible VM instance ?
Hard to say without prior investigation, any hints from the logs that can help to understand this behavior?