Possibility to specify custom header name for bounded request_id

[badziyoussef]

The application could be behind aws elb, that use a non customisable trace_id X-Amzn-Trace-Id, if we can specify request header name from settings, we can use same id generated by aws across all logs. What do you think?

[jrobichaud]

can it be achieved using bind_extra_request_metadata signal?

[jrobichaud]

I am not sure if you mean a request header to bind to the logs or return a an ID in a header in the response.

[badziyoussef]

I am not sure if you mean a request header to bind to the logs or return a an ID in a header in the response.

Talking about this part of code

        request_id = get_request_header( 
             request, "x-request-id", "HTTP_X_REQUEST_ID" 
         ) or str(uuid.uuid4())

if the x-request-id could be customized

[badziyoussef]

The idea is to use the traceId generated by the elb as request-id, which sometimes have a custom name, not always named x-request-id

[jrobichaud]

You can technically do this:

from django.contrib.sites.shortcuts import get_current_site
from django.dispatch import receiver
from django_structlog import signals
import structlog

@receiver(signals.bind_extra_request_metadata)
def bind_custom_id(request, logger, **kwargs):
    my_custom_id = "hey"
    structlog.contextvars.bind_contextvars(request_id=my_custom_id)

[badziyoussef]

You can technically do this:

from django.contrib.sites.shortcuts import get_current_site
from django.dispatch import receiver
from django_structlog import signals
import structlog

@receiver(signals.bind_extra_request_metadata)
def bind_custom_id(request, logger, **kwargs):
    my_custom_id = "hey"
    structlog.contextvars.bind_contextvars(request_id=my_custom_id)

Yes I know, ok I will go with that, thank you.

[jrobichaud]

I am considering to add a section "How-To Guides" with these different use-cases I saw over time (#325).