Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CPU metrics mismatch
See original GitHub issueDescribe the bug APM agent often pushes 0% process and system CPU usage, it should have at least some value greater than zero as the process is still running. Even comparing the stats on the container itself does not match the CPU usage provided by APM.
To Reproduce Steps to reproduce the behavior:
- Deploy APM enabled node application to a container (Linux).
- Compare container stats to APM data
- Compare process metrics within the container to APM data
- Screenshot of this comparison attached.
Expected behavior APM agent should push correct CPU metrics instead of 0%
Environment (please complete the following information)
- OS: Linux
- Node.js version: 8.10.0
- APM Server version: 6.7.0
- Agent version: 2.6.0, 2.11.1
How are you starting the agent? (please tick one of the boxes)
- Calling
agent.start()directly (e.g.require('elastic-apm-node').start(...)) - Requiring
elastic-apm-node/startfrom within the source code - Starting node with
-r elastic-apm-node/start
Additional context Add any other context about the problem here.
- Screenshot
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for reporting this bug. I’m able to reproduce it and we’ll look into what’s going on.
Thank you @watson for fixing it. 👍