close
Skip to content

Document hpack logger configuration#292

Closed
Mirochill wants to merge 1 commit into
python-hyper:masterfrom
Mirochill:use-trace-log-level
Closed

Document hpack logger configuration#292
Mirochill wants to merge 1 commit into
python-hyper:masterfrom
Mirochill:use-trace-log-level

Conversation

@Mirochill
Copy link
Copy Markdown

@Mirochill Mirochill commented May 25, 2026

Summary

  • document that hpack emits its verbose encoder, decoder, and table diagnostics through named loggers
  • show how applications can keep global DEBUG logging while raising the hpack logger level
  • add the logging configuration page to the docs toctree

Refs #273

Tests

  • git diff --check
  • git diff --check origin/master..HEAD
  • git show --check --stat --oneline HEAD
  • Not run locally

@Kriechi
Copy link
Copy Markdown
Member

Kriechi commented May 25, 2026

I think the best practice is to use the approach outlined in https://stackoverflow.com/a/35326281 instead of introducing a new log level in hpack itself.

Signed-off-by: Miro <200482516+Mirochill@users.noreply.github.com>
@Mirochill Mirochill force-pushed the use-trace-log-level branch from 7325250 to 6c9c93b Compare May 25, 2026 20:01
@Mirochill Mirochill changed the title Use trace level for verbose HPACK logs Document hpack logger configuration May 25, 2026
@Mirochill
Copy link
Copy Markdown
Author

Thanks, adjusted in that direction.

I removed the custom TRACE level and code/test changes, and rewrote this as a docs-only update showing how to configure the named hpack loggers independently from an application's root logger. The PR title/body now reflect that it documents the recommended logger configuration rather than changing hpack's log levels.

Static checks run:

  • git diff --check
  • git diff --check origin/master..HEAD
  • git show --check --stat --oneline HEAD

@Kriechi Kriechi closed this May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants