flaviostutz / flaviostutz/perfstat

low-cpu-idle is fixed at "1" in Prometheus metrics but checking the interface locally this is not true

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
36
Forks
2
PR merge metrics
No merged PRs in 30d

Description

![image](https://user-images.githubusercontent.com/7790172/90153929-eca3a280-dd5f-11ea-9a72-78e1cb2ab98e.png)

![image](https://user-images.githubusercontent.com/7790172/90154112-1f4d9b00-dd60-11ea-9de8-c1769b2f6297.png)

![image](https://user-images.githubusercontent.com/7790172/90154157-2b395d00-dd60-11ea-8f4b-f57e226e78aa.png)

it is not even being recognized as a danger type:
![image](https://user-images.githubusercontent.com/7790172/90154222-3f7d5a00-dd60-11ea-9f93-4e881c6946b8.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating where the low-cpu-idle Prometheus metric is generated and where metrics are classified as danger types. Reproduce the discrepancy against the local CPU interface and compare the exported value and classification with the observed value; done means the metric reflects the interface and is recognized correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux, prometheus
Domain
observability, performance
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.