dashboard icon indicating copy to clipboard operation
dashboard copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Clear logs

Open manuks opened this issue 2 years ago • 6 comments

What would you like to be added?

I will be great to have a clear button in the log viewer to see the logs since the current timestamp

Why is this needed?

We are watching an API call and its logs. In that case, old logs are not important.

manuks avatar Nov 25 '22 07:11 manuks

You can use the auto-refresh option and then go to the end of logs (make sure to actually scroll to the end). It will start following the logs. I don't think we would want to add the option to "clear the logs" since we always download the full log from the API and there is a number of options that allow you to simply go to the end and follow the latest logs.

Zrzut ekranu z 2022-11-25 10-57-14 Zrzut ekranu z 2022-11-25 10-57-35

floreks avatar Nov 25 '22 09:11 floreks

I used Rancher UI to see the logs for one of my projects. And there I found this feature very useful.

manuks avatar Nov 25 '22 10:11 manuks

We will get a particular log after clearing the entire log that's why we need the clear button

jyothisjose avatar Nov 25 '22 10:11 jyothisjose

You basically want to get the latest logs from what I understand. I am not sure I see any benefits of adding the clear button over following the logs. It would probably require changing our API in addition to the frontend.

floreks avatar Nov 25 '22 10:11 floreks

I was using the rancher to view the logs and It had a "clear screen" button functionality. It was conducive. But From Kubernetes version 1.22, we can't view the pod logs using rancher. So I tried many dashboards, like skooner, headlamp but the "clear button" functionality is not available in any of the dashboards. It will be helpful if the Kubernetes dashboard had that functionality.

sebinnsebastian avatar Nov 25 '22 12:11 sebinnsebastian

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Feb 23 '23 12:02 k8s-triage-robot