alibaba / alibaba/Sentinel

Very strange for sentinel monitor operation system load

Open
#1,800 1 comment 0 reactions 0 assignees View on GitHub
kind/discussion
Dominant language
Java
Stars
23.1k
Forks
8.1k
PR merge metrics
No merged PRs in 30d

Description

## Issue Description

Type: *feature request*

### Describe what happened (or what feature you want)

Since we should pay notice to operation system system load,
but in sre sence, we offer just pay notice to the system load of 1 core.
For example , in k8s we may use this metric instance:node_load1_per_cpu:ratio
For developers, we just not want to know which kind node our application runs on.

### Describe what you expected to happen
We just want a new system load pre core for our system rule

### How to reproduce it (as minimally and precisely as possible)

### Tell us your environment

### Anything else we need to know?
![image](https://user-images.githubusercontent.com/2881751/96331107-3759d780-108d-11eb-9fc1-189ef8bda877.png)

Contributor guide

Open the contributing guide

Research direction

No files, tests, or implementation entry points are named. Start by locating Sentinel's system-load monitoring and system-rule handling, then determine how the requested per-core load metric should be obtained without depending on the node type. Done means a system rule can use per-core load consistently, with coverage for the new behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kubernetes
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.