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

Research separation of patchers and exporters #333

Closed
ocelotl opened this issue Dec 12, 2019 · 1 comment
Closed

Research separation of patchers and exporters #333

ocelotl opened this issue Dec 12, 2019 · 1 comment

Comments

@ocelotl
Copy link
Contributor

ocelotl commented Dec 12, 2019

Right now, the ext directory contains code that implements functionality for automatic patching of several third-party projects that integrate with this project. Inside this directory it can also be found exporters that integrate in a similar way.

It would be convenient to have a uniform interface for these components and to make them integrate with this project through like standard entry points instead of having them imported statically.

This is closely related to #300 since the separation proposed here can benefit the auto-instrumentation efforts by allowing this project to dynamically load the patchers that do auto-instrumentation instead of having them all hard coded in the sitecustomize.py file.

ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Dec 13, 2019
@ocelotl ocelotl mentioned this issue Dec 13, 2019
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Dec 18, 2019
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Dec 18, 2019
@ocelotl
Copy link
Contributor Author

ocelotl commented Dec 18, 2019

Is getting a bit complicated to keep this issue separated from #300. I'll be merging the PR branch that corresponds to this issue into the PR branch of #300.

@ocelotl ocelotl closed this as completed Dec 18, 2019
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Jan 3, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Jan 7, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Jan 7, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Jan 27, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 3, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 5, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 17, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 19, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 20, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 24, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Feb 28, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Mar 2, 2020
ocelotl added a commit to ocelotl/opentelemetry-python that referenced this issue Mar 16, 2020
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this issue Nov 1, 2020
open-telemetry#333)

* fix(exporter-zipkin): use hrTimeToMicroseconds for zipkin timestamp and duration

* fix: review comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant