-
Notifications
You must be signed in to change notification settings - Fork 267
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
Would like to see old logs at least for 24 hours past #232
Comments
tektoncd/pipeline#107 is tracking a proposal that may be of interest for persistence of logs |
It seems like solid approach, thanks |
Hi @alhazred thank you for raising this. The dashboard currently shows logs for as long as the associated PipelineRun and TaskRun objects exist. Deleting those objects deletes the logs. If tektoncd/pipeline#107 leads to a general persistence mechanism then we'll have to decide whether or not dashboard should use it. |
Seems like the linked ticket has been closed in favor of standard pod log collection practices. Given that centralized log collection can vary from implementation to implementation, what recourse would the dashboard have as far as being able to present historical data? |
This could be an interesting one to watch: https://github.com/tektoncd/experimental/tree/master/results |
Why not add something like |
/assign |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Logs can be persisted externally and displayed in the dashboard after the pods have been deleted by following https://github.com/tektoncd/dashboard/blob/master/docs/walkthrough/walkthrough-logs.md |
Expected Behavior
Possibility to view all pipelines/logs at least for the current day and the previous one
Actual Behavior
only when related pods are live
Steps to Reproduce the Problem
Additional Info
I understand that pods has a short live time but would be nice to keep their logs at least for last 24 hours
The text was updated successfully, but these errors were encountered: