Resource pool metrics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
I am using performance manager to get resource pool metrics with intervalId=300.
After running the query:
end_time = service_instance.CurrentTime()
start_time = end_time - datetime.timedelta(seconds=300)
query_spec = vim.PerformanceManager.QuerySpec()
query_spec.format = "normal"
query_spec.endTime = end_time
query_spec.startTime = start_time
query_spec.intervalId = 300
query_spec.entity = <resource_pool>
query_specs.append(query_spec)
perf_entity_metrics = performance_manager.QueryPerf(query_specs)
i get some metrics that's are irrelevant for me right now but cpu.usagemhz and memory.active are missing though i see them in vpshere graphs and their interval is 5 minutes.
I can get them only if setting interval for more than 25 minutes.
Any reason why those counters are sent only every 25 minutes?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Python PerformanceManager.QuerySpec and QueryPerf calls shown in the report, using a resource pool and intervalId=300. Reproduce the missing cpu.usagemhz and memory.active counters, then verify the cause of their availability and the interval at which the query returns them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100