Skip to content
Discussion options

You must be logged in to vote

Thanks for the screenshots. That confirms what I expected - the pulse-host-agent is using 0% CPU (as shown in Task Manager), and the ~19% you see in Pulse is your Windows system's actual CPU utilization being reported.

This is correct behavior. The agent just reads the CPU usage from the OS and reports it to Pulse - it's not causing the 19% itself.

If you want to reduce how often the agent reports metrics (and slightly reduce network overhead), you can use the --interval flag as mentioned earlier. But the CPU reading itself is accurate.

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@tismofied
Comment options

Comment options

You must be logged in to vote
1 reply
@tismofied
Comment options

Answer selected by tismofied
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants