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

fix: default to not generate ftv1 traces #370

Merged
merged 2 commits into from
Jan 21, 2024
Merged

fix: default to not generate ftv1 traces #370

merged 2 commits into from
Jan 21, 2024

Conversation

dariuszkuc
Copy link
Member

@dariuszkuc dariuszkuc commented Jan 21, 2024

Federation tracing should only be enabled if the Router/Gateway sends the proper ftv1 header and value. Currently trace data is generated even if the header is not specified which leads to unnecessary computations of data that will ultimately be discarded by the Router/Gateway.... If header is not specified, we should default to false to avoid those unnecessary computations.

See: https://www.apollographql.com/docs/federation/metrics/

Supersedes: #368

Federation tracing should only be enabled if the Router/Gateway sends the proper ftv1 header and value. We want to default to false so we are not wasting CPU cycles tracking resolvers and building the extensions if it not going to be used

https://www.apollographql.com/docs/federation/metrics/

Supersedes: #368
Copy link

Apollo Federation Subgraph Compatibility Results

Federation 1 SupportFederation 2 Support
_service🟢
@key (single)🟢
@key (multi)🟢
@key (composite)🟢
repeatable @key🟢
@requires🟢
@provides🟢
federated tracing🟢
@link🟢
@shareable🟢
@tag🟢
@override🟢
@inaccessible🟢
@composeDirective🟢
@interfaceObject🟢

Learn more:

@dariuszkuc dariuszkuc merged commit ce19e68 into main Jan 21, 2024
5 checks passed
@dariuszkuc dariuszkuc deleted the ftv1 branch January 21, 2024 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change: patch Bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant