Add a way for processors to run code after the line is logged
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
Research direction
Start by reading the processor and logger flow in structlog to see where the rendered line is emitted and how processor results are passed along. The issue proposes a post-log hook that can access the logger call's result, but does not name files or tests. Done means a processor can emit content after the log line, including multiline request or response bodies.
Written by the indexing model from the issue text.
Description
From IRC:
[14:08:07] <underyx> @hynek would it somehow be possible for a processor to print something after the rendered line is printed?
[14:08:19] <underyx> it seems impossible to me right now but maybe you know of a way
[14:08:44] <underyx> specifically I'd like to print multiline request/response bodies after the actually log line
[14:09:46] <hynek> underyx: yeah sadly it’s impossible because loggers run last. we'd need some kind of post-log hook
[14:10:05] <underyx> can I open an issue for that or do you consider it out of scope?
[14:50:21] <hynek> I think that would be useful. Maybe it should also get the result of the logger call
- Dominant language
- Python
- Stars
- 5k
- Forks
- 302
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hynek/structlog
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Transform examples in docs into included source filesPossibly taken @alexchen-sys claimed this 97 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
waiting for feedback
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yunaremaia/proto-drift#22 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yunaremaia/memwatch#96 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 91/100
yunaremaia/ci-gate-watch#34 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
yunaremaia/agent-capability-attestation#64 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 86/100
yunaremaia/agent-call-graph#43 ·
Maintainers usually reply within 1 day