Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
As customer and Acquia Support, having a way to trace an Acquia Search Solr request back to an originating HTTP request to Drupal would help out greatly to debug many issues.
My proposal would be to basically add this ID the same way we already create the unique request_id that goes to the Solr backend.
Comments
Comment #2
janusman CreditAttribution: janusman at Acquia commentedPatch for review.
Comment #3
Nick_vhCan it ever be set but be empty?
Comment #4
janusman CreditAttribution: janusman at Acquia commentedNew patch.
Logic for this patch:
* Adds x-request-id=- to the Solr request path, whenever the X-Request-ID header is not present, or present but has no value.
* Adds x-request-id={actual value of the X-Request-ID}, if present and has some value.
I am not thinking of ever omitting the added x-request-id=... to the Solr request, since that means we will not be able to tell between the X-Request-ID header not being there, or if we are dealing with older versions of the module.
Comment #5
janusman CreditAttribution: janusman at Acquia commentedComment #6
Stanislav Mixnovich CreditAttribution: Stanislav Mixnovich commentedComment #7
Nick_vhGood to go. If nobody objects, I can commit this tomorrow.
Comment #8
Stanislav Mixnovich CreditAttribution: Stanislav Mixnovich commentedComment #9
janusman CreditAttribution: janusman at Acquia commentedNeeds porting to 7.x-3.x.
Here's a patch.
Comment #11
irek02 CreditAttribution: irek02 at Acquia commentedCommitted and pushed.