Skip to content
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

Add more observability around WS handshake failures #6771

Conversation

john-markham
Copy link

@john-markham john-markham commented Feb 11, 2025

Description here

Fixes #issue_number


Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

  • Changes are compatible1
  • Documentation2 completed
  • Performance impact assessed and acceptable
  • Tests added and passing3
    • Unit Tests
    • Integration Tests
    • Manual Tests

Exceptions

Note any exceptions here

Notes

Footnotes

  1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.

  2. Configuration is an important part of many changes. Where applicable please try to document configuration examples.

  3. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions.

@apollo-cla
Copy link

@john-markham: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

@svc-apollo-docs
Copy link
Collaborator

svc-apollo-docs commented Feb 11, 2025

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 0affb52a2746780446dba6f8

Comment on lines 676 to 674
tracing::warn!(
error.type = "websocket_connection_failed",
error.details= %error_details,
error.source = %std::any::type_name_of_val(&err),
"WebSocket connection failed"
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good but I don't think this part is needed as we're returning the SubrequestWsError we should be able to display it using custom telemetry configuration. Also might be worth to add the source to SubrequestWsError

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can leave adding additional metadata to SubrequestWsError to a followup

@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch 4 times, most recently from c02b6d3 to c498ae6 Compare February 12, 2025 15:58
@john-markham john-markham marked this pull request as ready for review February 12, 2025 23:37
@john-markham john-markham requested review from a team as code owners February 12, 2025 23:37
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch from c498ae6 to 9d45f12 Compare February 12, 2025 23:38
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch 2 times, most recently from 35e3083 to b62176f Compare February 13, 2025 21:32
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch 4 times, most recently from 2de21a1 to c561dd4 Compare February 13, 2025 22:17
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch 3 times, most recently from 8be1b17 to 7fd6e95 Compare February 13, 2025 22:26
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch 2 times, most recently from 9f9f20f to 22a7368 Compare February 13, 2025 22:56
@john-markham john-markham force-pushed the jm/propose-utf-8-observability branch from 22a7368 to d8c40ab Compare February 13, 2025 23:09
Signed-off-by: Benjamin <5719034+bnjjj@users.noreply.github.com>
@bnjjj
Copy link
Contributor

bnjjj commented Feb 14, 2025

Thanks @john-markham closing this PR in favor of #6798

@bnjjj bnjjj closed this Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants