-
Notifications
You must be signed in to change notification settings - Fork 373
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
feat: upgrade otel to v1.26 #1585
Conversation
Pull Request Test Coverage Report for Build 9416496963Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me at a first glance. If they end up in Honeycomb and the Prometheus server is serving up pretty-much the same metrics as before, address the comments from @kangmingtay and merge I guess.
nice work! feel free to resolve the comments and merge 👍 |
Will merge in the evening, after some final sanity checks |
Might have to delay this to the morning, having slight issues pulling on the internet connection where I'm at. |
🤖 I have created a release *beep* *boop* --- ## [2.154.0](v2.153.0...v2.154.0) (2024-06-12) ### Features * add max length check for email ([#1508](#1508)) ([f9c13c0](f9c13c0)) * add support for Slack OAuth V2 ([#1591](#1591)) ([bb99251](bb99251)) * encrypt sensitive columns ([#1593](#1593)) ([e4a4758](e4a4758)) * upgrade otel to v1.26 ([#1585](#1585)) ([cdd13ad](cdd13ad)) * use largest avatar from spotify instead ([#1210](#1210)) ([4f9994b](4f9994b)), closes [#1209](#1209) ### Bug Fixes * define search path in auth functions ([#1616](#1616)) ([357bda2](357bda2)) * enable rls & update grants for auth tables ([#1617](#1617)) ([28967aa](28967aa)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## What kind of change does this PR introduce? Spiritual successor to supabase#1305 where we attempt to bump the OTEL version from v1.10.0 to v1.26.0 which has a few breaking changes ## How this was tested We used a local setup with honeycomb with tracing and metrics enabled. We then triggered - a cleanup to test `gotrue_cleanup_affected_rows` - a few password sign ins to test `gotrue_compare_hash_and_password_submitted` - Checked if `gotrue_running` was present - Checked that DB traces were still present DB Trace: <img width="1108" alt="CleanShot 2024-05-23 at 20 46 02@2x" src="https://github.com/supabase/auth/assets/8011761/a365badb-08c3-4184-aef8-83624082d08d"> Metrics: <img width="1064" alt="CleanShot 2024-05-23 at 20 41 51@2x" src="https://github.com/supabase/auth/assets/8011761/1fc7743e-fc87-42a1-bf11-d14c739d5b67">
🤖 I have created a release *beep* *boop* --- ## [2.154.0](supabase/auth@v2.153.0...v2.154.0) (2024-06-12) ### Features * add max length check for email ([supabase#1508](supabase#1508)) ([f9c13c0](supabase@f9c13c0)) * add support for Slack OAuth V2 ([supabase#1591](supabase#1591)) ([bb99251](supabase@bb99251)) * encrypt sensitive columns ([supabase#1593](supabase#1593)) ([e4a4758](supabase@e4a4758)) * upgrade otel to v1.26 ([supabase#1585](supabase#1585)) ([cdd13ad](supabase@cdd13ad)) * use largest avatar from spotify instead ([supabase#1210](supabase#1210)) ([4f9994b](supabase@4f9994b)), closes [supabase#1209](supabase#1209) ### Bug Fixes * define search path in auth functions ([supabase#1616](supabase#1616)) ([357bda2](supabase@357bda2)) * enable rls & update grants for auth tables ([supabase#1617](supabase#1617)) ([28967aa](supabase@28967aa)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## What kind of change does this PR introduce? Spiritual successor to supabase#1305 where we attempt to bump the OTEL version from v1.10.0 to v1.26.0 which has a few breaking changes ## How this was tested We used a local setup with honeycomb with tracing and metrics enabled. We then triggered - a cleanup to test `gotrue_cleanup_affected_rows` - a few password sign ins to test `gotrue_compare_hash_and_password_submitted` - Checked if `gotrue_running` was present - Checked that DB traces were still present DB Trace: <img width="1108" alt="CleanShot 2024-05-23 at 20 46 02@2x" src="https://github.com/supabase/auth/assets/8011761/a365badb-08c3-4184-aef8-83624082d08d"> Metrics: <img width="1064" alt="CleanShot 2024-05-23 at 20 41 51@2x" src="https://github.com/supabase/auth/assets/8011761/1fc7743e-fc87-42a1-bf11-d14c739d5b67">
🤖 I have created a release *beep* *boop* --- ## [2.154.0](supabase/auth@v2.153.0...v2.154.0) (2024-06-12) ### Features * add max length check for email ([supabase#1508](supabase#1508)) ([f9c13c0](supabase@f9c13c0)) * add support for Slack OAuth V2 ([supabase#1591](supabase#1591)) ([bb99251](supabase@bb99251)) * encrypt sensitive columns ([supabase#1593](supabase#1593)) ([e4a4758](supabase@e4a4758)) * upgrade otel to v1.26 ([supabase#1585](supabase#1585)) ([cdd13ad](supabase@cdd13ad)) * use largest avatar from spotify instead ([supabase#1210](supabase#1210)) ([4f9994b](supabase@4f9994b)), closes [supabase#1209](supabase#1209) ### Bug Fixes * define search path in auth functions ([supabase#1616](supabase#1616)) ([357bda2](supabase@357bda2)) * enable rls & update grants for auth tables ([supabase#1617](supabase#1617)) ([28967aa](supabase@28967aa)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
What kind of change does this PR introduce?
Spiritual successor to #1305 where we attempt to bump the OTEL version from v1.10.0 to v1.26.0 which has a few breaking changes
How this was tested
We used a local setup with honeycomb with tracing and metrics enabled. We then triggered
gotrue_cleanup_affected_rows
gotrue_compare_hash_and_password_submitted
gotrue_running
was presentDB Trace:
Metrics: