Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add detailed information (pod restarts, resourses, env) #1929

Open
feym78 opened this issue Apr 25, 2024 · 5 comments
Open

Add detailed information (pod restarts, resourses, env) #1929

feym78 opened this issue Apr 25, 2024 · 5 comments

Comments

@feym78
Copy link

feym78 commented Apr 25, 2024

Hello.
Just tried this software, it looks nice, but it would be great to get some additional detalization:

  1. with prometheus plugin it is not possible to chose timeline for metrics. there is only last 10 minutes displayed and looks like it is hardcoded in plugin, it would be cool to have a control for this like 10 min. 30 min, 1h and etc or even custom range (like grafana does)
  2. there is no information about resource requests and limits, I saw several issues about this but still no feature yet
    for example Getting real time mertrics on Pod level for CPU/Memory requests and Limits? #1380 Pods: Add resource metrics to the list view #1
    It would be useful to see requests and limits at least in text and very useful also in graphical chart from prometheus plugin
  3. it also be useful to see exit code if pod was restarted, not just restarts count, also would be useful to see exact time of last restart
  4. there is env variables in pod details, but there is no values of these variables, it would be cool to get these values in pod description (except the ones mapped to secrets, it should be masked and not be accessible if token does not have permissions to get secrets), other software like Lens have this feature to show env values.
    upd 26.04
  5. extra useful feature - to have some switch for parsing json formatted logs in pods
@SquupS
Copy link

SquupS commented Apr 26, 2024

Fully agree and support especially points 1-3. Having those things present would make headlamp the go to tool for all things cluster related (on our side of things). As off now, we still have to jiggle with various tools to get all info needed in some cases.

@joaquimrocha
Copy link
Collaborator

@feym78 , @SquupS , I think those make a lot of sense. I will open issues for them so we get to them.
About point 3, I thought we were displaying the exit code. Maybe we only have this in the container?

@feym78
Copy link
Author

feym78 commented May 2, 2024

@joaquimrocha Hi! Thanks for your reply.

About point 3, I thought we were displaying the exit code. Maybe we only have this in the container?

Just checked windows desktop version - in containers section of pod's details there is only resatart count, no time or restart reason available.
Can't check it with in-cluster installation right now, but I think it's the same.

@SquupS
Copy link

SquupS commented May 2, 2024

Same for in-cluster deployment. Not available there

@feym78
Copy link
Author

feym78 commented Sep 2, 2024

@joaquimrocha Hi
I see that in last version there is already exit codes for restarted pods - great job, thanks headlamp team.
Also I see mention about json parsing in other opened issue, it's good to be heard.

For 1 point I created separated issue in plugins repo - headlamp-k8s/plugins#82

Can you please give some updates on points 2 and 4?
I find it very useful for a team to see actual pod limits to get understanding of given resources for their apps.
For 4 point I have some update: I noticed that if env variables in pod entered directly, then is shows in headlamp, but if it is mapped from configmap, then it doesn't. Is it a bug? If variable mapped to a secret, then its value omitted as expected (shows secrets field name?).
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants