Change Details

== Description Because of {T382173}, any instrument/experiment should be able to disable collecting user-agent data if its stream is configured accordingly. But `EventLogging` is filling directly the `http.request_headers.user-agent` attribute that is added to every event. == Acceptance criteria [] We have investigated if we can remove the code where `EventLogging` is filling that attribute (other usages could be affected) [] The code where `EventLogging` fills that attribute has been removed or, if not doable, there is a workaround to avoid adding it when appropriate

== Description Because of {T382173}, any instrument/experiment should be able to disable collecting user-agent data if its stream is configured accordingly. But the PHP implementation of `EventLogging` is filling directly the `http.request_headers.user-agent` attribute that is added to every event. == Acceptance criteria [] We have investigated if we can remove the code where `EventLogging` is filling that attribute (other usages could be affected) [] The code where `EventLogging` fills that attribute has been removed or, if not doable, there is a workaround to avoid adding it when appropriate

== Description Because of {T382173}, any instrument/experiment should be able to disable collecting user-agent data if its stream is configured accordingly. But the PHP implementation of `EventLogging` is filling directly the `http.request_headers.user-agent` attribute that is added to every event. == Acceptance criteria [] We have investigated if we can remove the code where `EventLogging` is filling that attribute (other usages could be affected) [] The code where `EventLogging` fills that attribute has been removed or, if not doable, there is a workaround to avoid adding it when appropriate