-
Notifications
You must be signed in to change notification settings - Fork 246
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 support for studio trace id in selectors and document context entry #5189
Conversation
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
CI performance tests
|
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
Co-authored-by: Gary Pennington <gary@apollographql.com>
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.
I'm requesting change for the selectors.mdx change because I don't think that will work properly without escaping the pipe.
Apart from that it looks great and thanks for documenting the Rhai constants.
docs/source/configuration/telemetry/instrumentation/selectors.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Gary Pennington <gary@apollographql.com>
@garypen good catch ! Thanks |
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.
Docs review
...uter/src/configuration/snapshots/apollo_router__configuration__tests__schema_generation.snap
Show resolved
Hide resolved
Co-authored-by: Edward Huang <edward.huang@apollographql.com>
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.
Can we introduce an integration test for this? I think it should jsut work as the apollo key and graph ref is present.
Co-authored-by: Edward Huang <edward.huang@apollographql.com>
Co-authored-by: Edward Huang <edward.huang@apollographql.com>
…studio_trace_id_selector
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
…ographql/router into bnjjj/add_studio_trace_id_selector
@BrynCooke integration test added |
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
…ry (#5189) Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com> Co-authored-by: Gary Pennington <gary@apollographql.com> Co-authored-by: Edward Huang <edward.huang@apollographql.com>
``` | ||
Router.APOLLO_SDL // Context key to access the SDL | ||
Router.APOLLO_START // Constant to calculate durations | ||
Router.APOLLO_AUTHENTICATION_JWT_CLAIMS // Context key to access authentication jwt claims | ||
Router.APOLLO_SUBSCRIPTION_WS_CUSTOM_CONNECTION_PARAMS // Context key to modify or access the custom connection params when using subscriptions in WebSocket to subgraphs (cf subscription docs) | ||
Router.APOLLO_ENTITY_CACHE_KEY // Context key to access the entity cache key | ||
Router.APOLLO_OPERATION_ID // Context key to get the value of apollo operation id (studio trace id) from the context | ||
``` | ||
|
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.
@shorgi Not urgent, but this probably needs some other visual treatment.
I think this whole feature should have been called "operation ID"? We pluck the value from |
Add support for a new trace id selector kind, the apollo trace id which represents the trace id on Apollo Studio.
Example:
Add documentation for available rhai constants.
Fixes #3803
Fixes #5172
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
Footnotes
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. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩