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

extensions deprecation #330

Closed
dorinsimionescu opened this issue Jul 21, 2020 · 10 comments
Closed

extensions deprecation #330

dorinsimionescu opened this issue Jul 21, 2020 · 10 comments
Labels
help wanted Extra attention is needed

Comments

@dorinsimionescu
Copy link

Hi,

The new apollo version will favor the new plugin api and extensions will be deprecated.

[deprecated] A "OpentracingExtension" was defined within the "extensions" configuration for Apollo Server. The API on which this extension is built ("graphql-extensions") is being deprecated in the next major version of Apollo Server in favor of the new plugin API. See https://go.apollo.dev/s/plugins for the documentation on how these plugins are to be defined and used.

Are there any plans to migrate the this project to use the new extensions api?

Thank you,
Dorin

@DanielMSchmidt
Copy link
Owner

Hi, I think we should make it a plugin as well. I haven't looked deeply into the plugin docs, but it seems like besides a bit of the interface not much changed, would you like to give it a try?

@robross0606
Copy link

Apollo has become pretty heavy-handed with their notifications on this one. You get one of those messages on your application for each extension that is registered against Apollo. No way to quiet them down.

@Multiply
Copy link

Multiply commented Sep 8, 2020

I'm going to be implementing OpenTracing in our next apollo project, so might pick this up if anyone still needs it

@robross0606
Copy link

We definitely need it, but I have not had time to work on a PR.

@oliversalzburg
Copy link

I'm also interested in this subject and would be willing to invest some time to work on porting this to a proper plugin.

We are currently using our own Apollo Server plugin in our stack. This plugin will simply export the existing Apollo traces into an external tracer (Jaeger in our case). But the additional features in this module seem interesting enough to revisit this.

Also note that there is apparently work in this area in the opentelemetry space: open-telemetry/opentelemetry-js-contrib#14

@Multiply
Copy link

@oliversalzburg thanks for the link.
I think a generic implementation is preferred, and not something bound to apollo-server specifically.

I'll follow the developments in opentelemetry-js-contrib more closely over the next two weeks, and if good progress is being made, I'll stick with their implementation.

@stale
Copy link

stale bot commented Dec 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 4, 2020
@robross0606
Copy link

Bump

@stale stale bot removed the stale label Dec 4, 2020
@oliversalzburg
Copy link

@robross0606 Did you have a look at open-telemetry/opentelemetry-js-contrib#226 by any chance?

I just wrote my own Apollo plugins for tracing. You can easily convert the internally collected spans or collect your own. The tracing plugin in Apollo can be used as a base to work off.

However, the above PR looks most promising and I might try to convert to that approach.

@DanielMSchmidt
Copy link
Owner

Forgot to close the issue, it was resolved in #356 👍 Thanks all for the patience, took me longer than expected to find the time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants