Repository navigation
Add support for debug logging #1255
Copy link
Copy link
Closed
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Description
Activity
- addedpriority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
on Jul 1, 2022 I'd also like to see a way to change log level down (e..g ignore accepted/closed levels)
@trajan0x Have you checked out the v2 proxy? It's much more terse about what it logs. I'd be interested if you'd want to adjust still further.
That's pretty chatty. Seems like a
--quietflag that just logged errors would be in order.See #1452.
We will wait until slog lands in the standard library and then add this.
Going to close this for now.
Metadata
Metadata
Assignees
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.

Sometimes it helps to know more than what the proxy logs (certificate expiration times, for example). This is a feature request to add support for debug logging, as enabled by a
--debugflag or similar. When callers supplied this flag, the proxy would be much more chatty about its internal state, the certificates, the connection data, etc.