Merge django-guid into Django core

[andrew-cybsafe]

Code of Conduct

• I agree to follow Django's Code of Conduct

Package Information

snok/django-guid

Problem

The django-guid package ensures that each request has a unique ID associated with it, either generated or retrieved from a header provided by an upstream load balancer, API gateway, etc.. It then adds the ID to all log outputs making debugging a lot easier. This is especially useful if the system is part of a larger set of services where further internal API calls may be required to service the incoming request from the client.

Rationale

I would argue that all production systems need request IDs to facilitate debugging, and that it would be beneficial to new Django projects to have this functionality wired in by default. It saves the hassle of configuring it, adding the request IDs into the logging config, and adding it to various error pages.

Additional Details

No response

Implementation Details

No response

[github-actions]

Thank you andrew-cybsafe for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win

[nanuxbe]

@andrew-cybsafe It looks like you have inverted the problem and rationale in this issue

[nanuxbe]

Thank you for the thoughtful idea shared here! While we're closing this issue for now due to limited community interest, we'd be happy to revisit it if interest grows (via emoji reactions). We're always listening and ready to reopen based on community feedback