Request logger

[thetutlage]

[github-actions]

This issue has been marked as stale because it has been inactive for more than 21 days. Please reopen if you still need help on this issue

[Huaian666]

someone on our team pointed me to core the API design is really well thought out. method names make sense, parameters are intuitive, and the return types are consistent. sounds basic but so many libraries get this wrong the TypeScript types are comprehensive and actually helpful, not just 'any' everywhere. generic usage is tasteful the web integration is seamless. request/response handling feels natural and the middleware system is powerful without being confusing the attention to detail throughout this project is remarkable. from the code to the docs to the issue templates - everything is top tier.

[Huaian666]

+1 this would be huge for our use case. currently doing a really ugly workaround

[mcky]

+1 on this, I'm unhappy with my hand-rolled request_logging_middleware

I'm using the otel package to send my logs and I'm guessing built in request logging would work out the box with that

Request: re-use the HttpUrlFilter that's applied to the tracing, and/or allow passing our own filter similar to how it can be configured

    '@opentelemetry/instrumentation-http': {
      ignoredUrls: ['/internal/*', '/api/ping'],
      mergeIgnoredUrls: true,
    },