-
Notifications
You must be signed in to change notification settings - Fork 0
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
Chore: Align/extend User Agents #61
Milestone
Comments
github-project-automation
bot
moved this to Needs Discussion
in Mobile & Cross Platform SDK
Feb 26, 2024
We'll align across SDK teams what the User Agent should look like |
PHP, Go, Python do send a user agent, format is like |
kahest
changed the title
Project: Make User Agent useful
Project: Align/extend User Agents
Mar 6, 2024
|
somewhat related initiative on Ingest team: https://github.com/getsentry/team-ingest/issues/276 |
stephanie-anderson
changed the title
Project: Align/extend User Agents
Chore: Align/extend User Agents
Jul 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently, some SDKs (e.g. sentry-cocoa) don't set a user agent or just set the SDK name as user agent.
In an effort to make troubleshooting of issues more viable if only the http request headers are available (e.g. looking into LB issues), we want to add more information to the user agent:
Define base and optional/additional format
Ensure SDKs use base format
(Optional) Adopt optional/additional format in SDKs
Why should we be doing this?
To make troubleshooting of issues more viable if only the http request headers are available, e.g. in incidents like INC-648
Why now?
The earlier we add at least the basic info (SDK name+version), the higher the likelihood that we have useful information available during the next incident.
RFC
No response
Slack-Channel
#inc-648
Notion Document(s)
INC-648 doc
Stakeholder(s)
INC-648, SRE
Team(s)
Mobile
Web Backend
Web Frontend (?)
The text was updated successfully, but these errors were encountered: