[48h Knative] Improved Logging

[rhuss]

👋 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—a 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

[sreeram-venkitesh]

/assign sreeram-venkitesh

[github-actions]

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.

[rhuss]

/remove-lifecycle stale

[github-actions]

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.

[sreeram-venkitesh]

/remove-lifecycle stale

@rhuss Got caught up with a bunch of stuff and couldn't reply to your comment in the PR. I will take this up and work with David.

[EraKin575]

@sreeram-venkitesh are you still working on this issue?

[sreeram-venkitesh]

@EraKin575, I'm not actively working on this issue right now. But I do have an open PR: #1904 where I had done some work.

[github-actions]

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.

[sreeram-venkitesh]

/remove-lifecycle stale

[sreeram-venkitesh]

I have the bandwidth for this issue now and I'll be working on it actively now.