-
Notifications
You must be signed in to change notification settings - Fork 275
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(telemetry): add ability to set span attributes on connector span #6125
Conversation
Signed-off-by: Benjamin <[email protected]>
✅ Docs Preview ReadyNo new or changed pages found. |
@@ -124,6 +124,9 @@ impl tower::Service<ConnectRequest> for ConnectorService { | |||
"apollo.connector.source.detail" = tracing::field::Empty, | |||
"apollo_private.sent_time_offset" = fetch_time_offset, | |||
); | |||
// TODO: I think we should get rid of these attributes by default and only add it from custom telemetry. We just need to double check it's not required for Studio. |
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.
cc @timbotnik I need your knowledge here
apollo-router/src/plugins/telemetry/config_new/connector/events.rs
Outdated
Show resolved
Hide resolved
…graphql/router into bnjjj/connectors/spans
Signed-off-by: Benjamin <[email protected]>
Signed-off-by: Benjamin <[email protected]>
Signed-off-by: Benjamin <[email protected]>
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.
This looks really good! Just a couple minor comments. It enables some nice things:
telemetry:
instrumentation:
spans:
connector:
attributes:
connector.url.template: true
connector.http.method: true
"rate_limit":
connector_http_response_header: "x-ratelimit-remaining"
Signed-off-by: Benjamin <[email protected]>
Signed-off-by: Benjamin <[email protected]>
Give the ability to use custom telemetry with spans for connectors.
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. ↩