I'm running a private build from the git repo circa Jan 27. I'm lousy with git so I'm not sure if there's a better way to identify the version of the code we used. I just did a "git log" on the local repo i used for the build and the last commit was from Jan 26.
We are using a private build because we need the process username which has been added to the output since the most recent release.
I also have to make a correction to my previous statements; the high CPU is only periodic when I set the polling interval to a long time (like 5 mins). I wasn't seeing the expected behavior because i failed to save the config file before restarting the service.
Other troubleshooting ideas I had:
- Spin up a vanilla VM in Azure to eliminate any issues associated with our image or tools installed in our environment.
- Compare with a released build, or a build from the latest source in github.
We can also deal with the issue by adding cores to the servers, but it feels "wrong" that the monitoring software is using more resources than the actual workload of the server.