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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

[48h Knative] Improved Logging #1896

Open
1 of 4 tasks
rhuss opened this issue Nov 17, 2023 · 3 comments
Open
1 of 4 tasks

[48h Knative] Improved Logging #1896

rhuss opened this issue Nov 17, 2023 · 3 comments
Assignees
@dsimansk @sreeram-venkitesh
Labels
kind/resurface-suggestion Suggest renaming or rearranging args for something knative48h Issue selected for the "48h Knative" hackathon

Comments

@rhuss
Copy link
Contributor

rhuss commented Nov 17, 2023 •
edited by dsimansk

馃憢 Hello, awesome contributor!

Are you excited about Knative and open-source development? You're in the right place! This is a mini-project for the upcoming 48h Knative event鈥攁 48-hour hackathon designed to boost contributions to the Knative Client project. For more details, check out Issue #1842.

馃幆 Project Description

This project is about implementing #1587 . More details can be found there.k

馃専 Benefits

A consistent and fine-granular logging capability is key to a good user experience. Logging should be at least as powerful as logging with kubectl

馃洜 Difficulty Level

Easy

馃懃 Recommended Team Size

1

馃帀 Expected Outcome

Logging should be improved and a plan / issue for a concrete improvement of the logging subsystem should be worked out.

馃 Mentor

@dsimansk

馃摑 Additional Information

tbd

馃寪 Entrypoints

tbd

馃搵 Organizer Checklist

  • Added to Project Board
  • Proposal Reviewed
  • Assigned a Mentor
  • Expected Outcome define
@rhuss rhuss added kind/resurface-suggestion Suggest renaming or rearranging args for something knative48h Issue selected for the "48h Knative" hackathon labels Nov 17, 2023
@sreeram-venkitesh
Copy link

/assign sreeram-venkitesh

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2024
@rhuss
Copy link
Contributor Author

rhuss commented Mar 4, 2024

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dsimansk dsimansk

@sreeram-venkitesh sreeram-venkitesh

Labels
kind/resurface-suggestion Suggest renaming or rearranging args for something knative48h Issue selected for the "48h Knative" hackathon
Projects
48h Knative
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rhuss @dsimansk @sreeram-venkitesh