kubesphere / kubesphere/ks-devops

Still show Jenkins agent pod resource usage footprint after pod down

Open
#86 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

Recently, some users encountered some problems in the pipeline execution, and the pipeline ended soon. We don't have any chance to see the resource usage of Jenkins agent pod. This makes it difficult for us to find out the cause of the problem.

So I request to show Jenkins agent pod resource usage footprint after pod is down.

### Exepcted Jenkins agent pod resource footprint

**Show in Pod monitor**:

![image](https://user-images.githubusercontent.com/16865714/127663282-bea0c0c1-5cd3-40e7-9278-ab836c9c7764.png)

**or show in Custom Monitor Dashboard**
![image](https://user-images.githubusercontent.com/16865714/127672084-cb9040b1-3fc0-410a-8e8c-410220e0837f.png)

Contributor guide

Open the contributing guide

Research direction

The issue identifies Jenkins agent pods and the Pod monitor or Custom Monitor Dashboard as the desired locations, but names no files, tests, or entry points. Start by locating the monitoring implementation for Kubernetes pod resource usage and determine whether usage is retained after a pod terminates. Done means the terminated agent pod's resource footprint remains visible in one of the requested monitoring views.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.