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

Plugin discovery #275

Closed
c24t opened this issue Nov 7, 2019 · 1 comment
Closed

Plugin discovery #275

c24t opened this issue Nov 7, 2019 · 1 comment
Labels
build & infra Issues related to build & infrastructure.

Comments

@c24t
Copy link
Member

c24t commented Nov 7, 2019

As discussed in today's SIG meeting, we need to settle on conventions for naming and discovering plugins, i.e. exporters and integrations.

Right now we're using the opentelemetry.ext namespace, and each plugin is a namespace package. One option is to use importlib to discover matching namespace packages.

We may be able to write generic tests to be run by plugin developers. For example, an exporter test that loads each registered exporter and exports one or more spans. Exporter plugins could run this test from the latest version of the core library. Note that this would mean packaging core library tests such that others can run them, and distinguishing exporters from plugins.

This is motivated by #272, the first exporter to graduate from ext/ and get its own separate repo.

@c24t c24t added build & infra Issues related to build & infrastructure. ext labels Nov 7, 2019
@codeboten
Copy link
Contributor

This will be addressed by #760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build & infra Issues related to build & infrastructure.
Projects
None yet
Development

No branches or pull requests

2 participants