Add unique ID without impacting wildcard functionality
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- observability
Research direction
Start by reviewing the library's extend behavior and wildcard matching, then trace how names are formatted and filtered. Define how a unique transaction ID should appear in log output while preserving patterns such as DEBUG=debug:app*:other_extend_call; done means both identification and wildcard filtering work together.
Written by the indexing model from the issue text.
Description
If a lot of different users interact with your application at the same time and calling async calls, you get log output that is a combination of all these actions and it's not easy to determine which log line is for which user/action/transaction/call_it_however_you_like.
I thought about using the extend function and add something like ":trans(transaction_id)" so the output would be:
debug:app(transaction_id) Some log output
But the problem here is that wildcards for enabling other extend calls would be an issue. For example DEBUG=debug:app*:other_extend_call which will not work.
Is there a way to add a transactionid to this without breaking the wildcard functionality? For example by just removing (transaction_id) using a replace somewhere in the library?
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 992
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 debug-js/debug
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Debug as JSON Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·