-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elastic Synthetic Identifier In UA String #232
Labels
Comments
30 tasks
andrewvc
added a commit
to andrewvc/synthetics-1
that referenced
this issue
May 26, 2022
When we originally implemented elastic#232 it appears we didn't implement the third AC, allowing users to override our custom UA string "Elastic/Synthetics" which is appended. Some users need to fully replace the UA, this allows them to do that. Rather than adding a boolean, this assumes that if you're overriding the UA you want full control, which is more in line with the principle of least surprise.
vigneshshanmugam
pushed a commit
to andrewvc/synthetics-1
that referenced
this issue
Jun 3, 2022
When we originally implemented elastic#232 it appears we didn't implement the third AC, allowing users to override our custom UA string "Elastic/Synthetics" which is appended. Some users need to fully replace the UA, this allows them to do that. Rather than adding a boolean, this assumes that if you're overriding the UA you want full control, which is more in line with the principle of least surprise.
vigneshshanmugam
added a commit
that referenced
this issue
Jun 3, 2022
* Only append 'Elastic/Synthetics' to default UA When we originally implemented #232 it appears we didn't implement the third AC, allowing users to override our custom UA string "Elastic/Synthetics" which is appended. Some users need to fully replace the UA, this allows them to do that. Rather than adding a boolean, this assumes that if you're overriding the UA you want full control, which is more in line with the principle of least surprise. * fix tests and rebase Co-authored-by: vigneshshanmugam <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a Synthetics user
I want to be able to easily identify Elastic Synthetic traffic in my analytics
So that I can exclude such traffic from my visitor volumes as this monitoring skews real customer figures
ACs:
Elastic/Synthetics
to the actual UA string)Referencing somewhat related tickets:
The text was updated successfully, but these errors were encountered: