Standardize on zap for logging

[adambkaplan]

Feature request

We should use the same logging framework for the watcher and apiserver so we have consistent configuration and contributor experience.

Use case

• Customizing log levels on the apiserver and watcher.

[alan-ghelardi]

+1 I was going to open exactly the same feature request. Structured logs are quite helpful for debugging with tools like Splunk and others. Any ongoing work on that?

[adambkaplan]

I think #247 is related here. We also recently merged #268 which introduced some logging with zap.

[sayan-biswas]

/assign

[sayan-biswas]

/assign enarha

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[adambkaplan]

/lifecycle frozen

We should ensure we have consistent configuration settings for logging