by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Leighton Chen
    @lzchen
    also seems like new release of botocore is causing some test failures
    Daniel
    @ffe4

    another testament to why we should move instrumentations to the contrib repo

    That repo seems kind of dead. What are the plans for the contrib repo? The PR with the CONTRIBUTING.md was never merged; are contributions even welcome at this point?

    5 replies
    alrex
    @codeboten
    Heads up folks, the link for tomorrow's SIG meeting is updated to a new zoom to deal with the numerous SIGs meeting around the same time. The link in the sig notes and the calendar invite are the correct ones: https://zoom.us/j/8287234601
    Still same time, Thursday morning at 9am PST
    Mateusz "mat" Rumian
    @mat-rumian
    Hi everyone,
    could you please tell me since which Python version OT-Python is supported?
    5 replies
    harini0597
    @harini0597
    Hi everyone, Can you please tell me which exporter I should use to export traces to opentelemetry collector?
    4 replies
    Mateusz 'mat' Rumian
    @rydzykje
    Hey guys,
    could you please take a look open-telemetry/opentelemetry-python#1114 :)
    Mateusz 'mat' Rumian
    @rydzykje
    I have one more question about setting service_name for JaegerSpanExporter - in current implementation it's possible only by direct changes in the code. I would say it's not user friendly. I didn't find any issue about this kind of functionality. Maybe it's worth to create one and use OTEL_RESOURCE_ATTRIBUTES variable to set it?
    Wilbert Guo
    @wilguo

    Hey guys,

    Just joined and working on my first issue (open-telemetry/opentelemetry-python#1111).
    I was wondering if anybody got this error when trying to do pip install opentelemetry-exporter-zipkin to run the tests.

    ERROR: Could not find a version that satisfies the requirement opentelemetry-exporter-zipkin (from versions: none)
    ERROR: No matching distribution found for opentelemetry-exporter-zipkin

    7 replies
    Amos Law
    @ahlaw
    Hi everyone, working on my first issue (open-telemetry/opentelemetry-python#1009). I was wondering if anyone actually had a sane way of running mypy on exporter code, it appears tox is only configured to check the api.
    Owais Lone
    @owais

    Hi eveyone, is the opentelemetry-exporter-otlppython package supposed to ship both the trace and metric exporters? I just tried installing it from pypi and looks like it only includes the trace exporter.

    pip install opentelemetry-exporter-otlp
    ls venv/lib/python3.7/site-packages/opentelemetry/exporter/otlp/
    __init__.py     __pycache__/    trace_exporter/ version.py

    Is this expected?

    3 replies
    Wilbert Guo
    @wilguo
    image.png
    2 replies
    Hi everyone, just ran the tests for the zipkin exporter. Should there be failing tests in test_zipkin_exporter.py?
    alrex
    @codeboten
    hey folks, im planning on releasing the new version of opentelemetry python today. if you have any PRs you'd like to have in the release, please post them here for folks to review this morning. The following PRs need a second approver
    open-telemetry/opentelemetry-python#1018
    open-telemetry/opentelemetry-python#1096
    Leighton Chen
    @lzchen
    Hi would like feedback on this PR: open-telemetry/opentelemetry-python#1116
    Amos Law
    @ahlaw
    Hi, would like a review on this: open-telemetry/opentelemetry-python#1121
    2 replies
    Owais Lone
    @owais

    I’d like this to go in but I think it’s already on your radar. open-telemetry/opentelemetry-python#1018

    CI started failing after I updated it to latest master. I assume it’s a known issue in master?

    1 reply
    Owais Lone
    @owais
    Not my PR but I’d also like this to go in if possible. open-telemetry/opentelemetry-python#957
    5 replies
    Happy to adopt the PR if original author cannot anymore.
    Owais Lone
    @owais
    Tornado PR is now green (rebasing resulted in lint issues after being green for almost a month :) ). Would really appreciate if we could include it in the release. open-telemetry/opentelemetry-python#1018
    alrex
    @codeboten
    pr for the new release is up: open-telemetry/opentelemetry-python#1129
    Leighton Chen
    @lzchen
    Need another approver for: open-telemetry/opentelemetry-python#1122
    Jason Liu
    @JasonXZLiu
    Hi! I was wondering if this issue is free to pick up? I would love to work on it! open-telemetry/opentelemetry-python#1002 cc - @alolita
    2 replies
    alrex
    @codeboten
    This message was deleted
    reminder the zoom is: https://zoom.us/j/8287234601
    Wilbert Guo
    @wilguo
    Hi everyone, could someone review my PR (open-telemetry/opentelemetry-python#1124) thank you!
    AzfaarQureshi
    @AzfaarQureshi
    Hey I had a quick question about issue open-telemetry/opentelemetry-python#1001. Im a little new to Python so apologies if the ans is obvious but in Span.py here I don't see any Span attributes being directly exposed. Which Attributes is the issue referring to? Span.Attributes or the Span class's attributes like Span name, Start/End timestamp, Status etc? Thank for the help! :D
    Amos Law
    @ahlaw
    Hi everyone, I was wondering about some of the tracing spec requirement issues that deal with restricting Span instantiation and access such as the above PR and this one: open-telemetry/opentelemetry-python#1000. There aren't any simple ways of enforcing some of these in Python as these sorts of restrictions aren't very Pythonic. What approach should be taken in these cases (i.e. how strictly should these spec requirements be handled)?
    5 replies
    Wilbert Guo
    @wilguo
    Hi, could someone merge my PR (https://github.com/open-telemetry/opentelemetry-python/pull/1124)? It has been approved and the branch has been updated. Thank you!
    3 replies
    Owais Lone
    @owais
    Could someone please take a look at PR for Celery context propagation? open-telemetry/opentelemetry-python#1135
    Jason Liu
    @JasonXZLiu
    Hi! I was wondering if someone could take a quick look at my PR for making SpanContext immutable (open-telemetry/opentelemetry-python#1134). I was just wondering if the approach that I took was correct. Thank you!
    Wilbert Guo
    @wilguo
    Hey, sorry I'm new to this group, can someone point me in the right direction on getting started with this issue (open-telemetry/opentelemetry-python#1107). I have tried to look for compression and encoding with gzip but I don't see it being done anywhere in the project.
    1 reply
    Leighton Chen
    @lzchen
    Hey still need more reviews on open-telemetry/opentelemetry-python#1116
    Aaron Abbott
    @aabmass
    Need one more review on open-telemetry/opentelemetry-python#1096 :slight_smile:
    Amos Law
    @ahlaw
    Would like a review on this: open-telemetry/opentelemetry-python#1136
    Wilbert Guo
    @wilguo
    Would also like a review on open-telemetry/opentelemetry-python#1124 thank you
    Owais Lone
    @owais

    Updated auto-instrumentation PR to confirm to recently merged Otel spec. open-telemetry/opentelemetry-python#1036

    Would love to hear more thoughts on it.

    Leighton Chen
    @lzchen
    Owais Lone
    @owais
    Proposing to split out instrument/bootstrap commands and base instrumentation classes into different packages: open-telemetry/opentelemetry-python#1137
    @codeboten @ocelotl @lzchen ^ would love to hear your thoughts on this
    Leighton Chen
    @lzchen
    Mateusz 'mat' Rumian
    @rydzykje

    Hello everyone,
    could you please help me to understand something. I've very simple script. I'm using auto instrumentation opentelemetry-instrument python test.py

    import requests
    
    from opentelemetry import trace
    from opentelemetry.sdk.trace import TracerProvider
    from opentelemetry.sdk.trace.export import (
        ConsoleSpanExporter,
        SimpleExportSpanProcessor
    
    )
    
    trace.set_tracer_provider(TracerProvider())
    trace.get_tracer(__name__)
    
    trace.get_tracer_provider().add_span_processor(
        SimpleExportSpanProcessor(ConsoleSpanExporter())
    )
    
    
    def main():
        requests.get("http://localhost:8082/do_espresso")
        print("span_id=", trace.get_current_span().get_context().span_id)
    
    main()

    I would like to know whyConsoleExporter is showing properly generated span but when I want to get only span_id by trace.get_current_span().get_context().span_id as result I'm getting 0. Could you please tell me what I'm doing wrong? (in my flask apps I'm doing the same and I'm getting span_id properly)

    5 replies
    alrex
    @codeboten
    Jason Liu
    @JasonXZLiu
    Hi! Would love if someone could review this PR: open-telemetry/opentelemetry-python#1134 Thank you!
    Wilbert Guo
    @wilguo
    Hey everyone! Could someone review my PR (open-telemetry/opentelemetry-python#1141) thank you!
    Leighton Chen
    @lzchen
    Hey guys need reviews on this: open-telemetry/opentelemetry-python#1142
    Mateusz 'mat' Rumian
    @rydzykje
    Hello, could you please take a look open-telemetry/opentelemetry-python#1114 Thanks a lot :)