Leverage APM Tracing(#2612 (comment)) in order to investigate:
- Elastic Agent API calls towards k8s API
- check memory consumption
Update
Background
get the base line of current resource usage (8.12.x) and the method to measure it, just for the internal understanding
Goals
Understand internally how to get metrics:
Measure:
a) Memory
we are not splitting sub-processes for now, just elastic-agent
b) CPU
c) API calls (from both agent and underlying beats)
Actions
- How to get all the required Measurements
-
are we required to use system integration - yes, we want to get info over time
-
but how to get mem info for the elastic-agent - k8s related providers
-
cluster only with agent with empty policy - check the base line of resource usage + api calls (with audit logs)
-
enable k8s integration - check the mem/cpu change
- The scenarios to measure memory, cpu usage and API calls:
- 1 node cluster:
- elastic-agent with default metrics 1 node cluster and 50 pods
- leave system integration enabled
- elastic-agent with logs 1 node cluster: X rate of logs with 50pods
- Repeat above with 5 node cluster with 50pods
- elastic-agent with default metrics 1 node cluster and 50 pods
- elastic-agent with logs 1 node cluster: X rate of logs with 50pods
Leverage APM Tracing(#2612 (comment)) in order to investigate:
Update
Background
get the base line of current resource usage (8.12.x) and the method to measure it, just for the internal understanding
Goals
Understand internally how to get metrics:
Measure:
a) Memory
we are not splitting sub-processes for now, just elastic-agent
b) CPU
c) API calls (from both agent and underlying beats)
Actions
are we required to use system integration - yes, we want to get info over time
but how to get mem info for the elastic-agent - k8s related providers
cluster only with agent with empty policy - check the base line of resource usage + api calls (with audit logs)
enable k8s integration - check the mem/cpu change