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

Reorganize examples #482

Closed
mauriciovasquezbernal opened this issue Mar 12, 2020 · 1 comment
Closed

Reorganize examples #482

mauriciovasquezbernal opened this issue Mar 12, 2020 · 1 comment
Assignees
Labels
doc Documentation-related

Comments

@mauriciovasquezbernal
Copy link
Member

I'm proposing to slight reorganize the examples structure by having:

Tracing: show the tracing api. Use console exporter

  • Basic tracer: how to start spans, add events, attributes.
  • http tracer: shows usage of an integration (requests in this case).

Metrics: shows usage of different instruments and different calling conventions.

  • basic: how to use Counter and Measure using direct call convention.
  • observer: how to register an observer instrument.
  • calling_conventions: how to use direct, bound instruments and batch calling conventions.

Exporters: examples showing how to use the different tracing and metrics exporters.

  • jaeger
  • otcollector: with link to the collector (different examples for metrics and tracing)
  • zipkin (if time allows)
  • prometheus
@mauriciovasquezbernal
Copy link
Member Author

Fixed by #483.

srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this issue Nov 1, 2020
* feat: add addExporter to Meter

* chore: remove event emitter from handle

* style: remove nested if
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Documentation-related
Projects
None yet
Development

No branches or pull requests

1 participant