You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Apache mod_unique_id module is installed and enabled for Wikimedia's deployment, however the MediaWiki application prefers X-Request-Id if it is set (which internal routing always sets now).
We're not quite yet ready to turn this module off, and we've already added logging of a reqId throgh our own processor.
It is currently confusing to developers that our Logstash messages contain both unique_id and reqId which are similar but only one is "correct".
As I understand it, the WebProcessor has a constructor option to control which fields are used, but unique_id currently bypasses this. Would you be option to a pach for making that work the same way?
The text was updated successfully, but these errors were encountered:
The Apache
mod_unique_idmodule is installed and enabled for Wikimedia's deployment, however the MediaWiki application prefersX-Request-Idif it is set (which internal routing always sets now).We're not quite yet ready to turn this module off, and we've already added logging of a
reqIdthrogh our own processor.It is currently confusing to developers that our Logstash messages contain both
unique_idandreqIdwhich are similar but only one is "correct".As I understand it, the WebProcessor has a constructor option to control which fields are used, but
unique_idcurrently bypasses this. Would you be option to a pach for making that work the same way?The text was updated successfully, but these errors were encountered: