[elastic_agent]: CPU Usage Inconsistency Based on Kibana Time Picker Selection #13321
Labels
bug
Something isn't working, use only for issues
impact: medium
Integration:elastic_agent
Elastic Agent
needs:triage
Team:Elastic-Agent-Control-Plane
Label for the Agent Control Plane team
Comments
Danouchka
added
needs:triage
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
cc @cmacknz |
andrewkroh
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Integration Name
Elastic Agent [elastic_agent]
Dataset Name
system.process.cpu
Integration Version
latest
Agent Version
8.17.1
Agent Output Type
elasticsearch
Elasticsearch Version
ECH 8.17.2 on GCP Belgium
OS Version and Architecture
Windows Server 2022 for elastic agent
Software/API Version
No response
Error Message
None
Event Original
The elastic agent cpu usage percentage is not the same depending on the kibana time picker selection.
See video below
As a result, customer cannot know really how much cpu the elastic agent consumes in avg
Enregistrement.de.l.ecran.2025-03-25.a.10.58.32.mov
What did you do?
Nothing
What did you see?
See attached video
What did you expect to see?
an avg cpu % that does not vary whatever the duration over which we are looking
Anything else?
No response
The text was updated successfully, but these errors were encountered: