profile
viewpoint
alrex codeboten Lightstep Vancouver

codeboten/ochoneycomb 3

OpenCensus Python exporter for Honeycomb

codeboten/hnylambda 1

Contains packages used to wrap AWS Lambda functions with Honeycomb tracing

codeboten/nginx-auth-proxy 1

nginx auth proxy container

codeboten/o11y 1

Repo to play with aws, serverless, terraform & observability

codeboten/about 0

Sourcegraph blog, feature announcements, and website (about.sourcegraph.com)

codeboten/all-apis 0

Repo to test building APIs in various languages

codeboten/ameliora 0

App to record your bike ride

codeboten/autoscaler 0

Autoscaling components for Kubernetes

create barnchlightstep/opentelemetry-examples

branch : migrating-launcher-code

created branch time in 7 hours

pull request commentopen-telemetry/opentelemetry-python

Span name updated to follow semantic conventions to reduce cardinality

It looks like aiohttp-client already does the right thing unless the configuration overrides the span_name method, did I miss any other http client libraries @lzchen?

codeboten

comment created time in 8 hours

issue commentlightstep/lightstep-tracer-go

Problematic tracer metrics defaults

This change how now been released with v0.21.0

ahayworth

comment created time in 8 hours

created taglightstep/lightstep-tracer-go

tagv0.21.0

The LightStep distributed tracing library for Go

created time in 8 hours

push eventcodeboten/opentelemetry-python

Alex Boten

commit sha fcb61244eb4819b7833e6769d2013e71c84146a8

wrap exception formatting for py34

view details

push time in 8 hours

push eventlightstep/lightstep-tracer-go

alrex

commit sha 84f34eb5822382c57b8b028cc623c3e32ffa4db0

chore: prepare 0.21.0 release (#260)

view details

push time in 9 hours

PR merged lightstep/lightstep-tracer-go

chore: prepare 0.21.0 release

Updated changelog and version number

+4 -2

0 comment

3 changed files

codeboten

pr closed time in 9 hours

push eventcodeboten/opentelemetry-python

alrex

commit sha b3c2a0372e27eff4594891db8ad04c438e9fdf4c

fix: update default OTLP port to 55680 (#977)

view details

alrex

commit sha 76b1ed0d6f4d41df0075953dcfbece72dd4bb344

Renaming OTEL_RESOURCE env var (#973)

view details

alrex

commit sha ab580c9a65f658c7c690721aa0169dfb67112659

Merge branch 'master' into reduce-cardinality-requests

view details

push time in 12 hours

PR opened lightstep/lightstep-tracer-go

chore: prepare 0.21.0 release

Updated changelog and version number

+4 -2

0 comment

3 changed files

pr created time in 12 hours

create barnchlightstep/lightstep-tracer-go

branch : codeboten/0.21.0

created branch time in 12 hours

push eventlightstep/lightstep-tracer-go

alrex

commit sha 05ceb821439633ecd131e1af4af1959cb6fd26c4

feature: Support env var to disable metrics (#259) Adding the ability to disable metrics via the `LS_METRICS_ENABLED` env var. Setting this variable to `LS_METRICS_ENABLED=false` will disable system metrics. Fixes https://github.com/lightstep/lightstep-tracer-go/issues/256

view details

push time in 12 hours

PR merged lightstep/lightstep-tracer-go

feature: Support environment variable to disable metrics

Adding the ability to disable metrics via the LS_METRICS_ENABLED environment variable. Setting this variable to LS_METRICS_ENABLED=false will disable system metrics.

Fixes https://github.com/lightstep/lightstep-tracer-go/issues/256

+6 -1

0 comment

2 changed files

codeboten

pr closed time in 12 hours

issue closedlightstep/lightstep-tracer-go

Problematic tracer metrics defaults

👋

Hello, LightStep friends -

It seems that #249 turned metrics reporting on globally, and also bypassed any collector hosts that were configured.

This is causing something of a headache at GitHub, because now our go services are trying to report metrics directly to lightstep-managed ingest points, rather than our own endpoints. Worse still; they're often failing to connect and are now spamming our internal error tracking system.

Was it intentional to enable this by default, and to specifically bypass configured collectors? It seems like this was brought up in the PR review but was not addressed before it was merged.

If possible, could you please push a new version that:

  • does not enable the feature by default
  • respects the globally-configured collector host, if enabled

We'd appreciate it if you could do that. It'd save us quite a bit of work internally, re-configuring and re-deploying everything.

Some things to consider when deciding if this should be enabled or not, and what hosts should be used:

  • We don't want to report metrics outside of known and vetted infrastructure. That poses a security and compliance risk for us, so now this is something of an emergency on my end.
  • My team prefers to support one standard metrics configuration internally, and this being enabled by default raises the possibility that teams might begin to use it without our approval and/or knowledge - and that means it's an increased workload on our team that we didn't sign up for and makes our own policy-setting somewhat pointless.
  • We specifically configured internal collector pools to absorb the tracing load for our services, and because ingest.lightstep.com isn't keeping up, it's now causing a knock-on problem in our exception tracking system every time the metrics reporter fails to report and raises an exception.
  • Even if we did want to use this feature, we haven't necessarily sized our collector pool to handle even more load - so defaulting to the global collector host is not sufficient. We should be able to opt-in, not opt-out.

Thanks!

cc @marwan-at-work

closed time in 12 hours

ahayworth

Pull request review commentlightstep/otel-launcher-python

Update README

 configure_opentelemetry(  ``` +### Usage with Auto Instrumentation++OpenTelemetry Python includes a command that allows the user to automatically instrument+certain third party libraries. Here is an example that shows how to use this launcher+with auto instrumentation.++First, create a new virtual environment:++```bash+cd ~+mkdir auto_instrumentation+virtualenv auto_instrumentation+source auto_instrumentation/bin/activate+pip install opentelemetry-api+pip install opentelemetry-sdk+pip install opentelemetry-instrumentation+pip install opentelemetry-ext-flask

could this be replaced by using opentelemetry-bootstrap -a install?

ocelotl

comment created time in 13 hours

Pull request review commentlightstep/otel-launcher-python

Update README

 configure_opentelemetry(  ``` +### Usage with Auto Instrumentation++OpenTelemetry Python includes a command that allows the user to automatically instrument+certain third party libraries. Here is an example that shows how to use this launcher+with auto instrumentation.++First, create a new virtual environment:++```bash+cd ~+mkdir auto_instrumentation+virtualenv auto_instrumentation+source auto_instrumentation/bin/activate+pip install opentelemetry-api+pip install opentelemetry-sdk+pip install opentelemetry-instrumentation+pip install opentelemetry-ext-flask+pip install requests

why is requests installed, but opentelemetry-ext-flask installed?

ocelotl

comment created time in 13 hours

Pull request review commentlightstep/otel-launcher-python

Update README

 configure_opentelemetry(  ``` +### Usage with Auto Instrumentation++OpenTelemetry Python includes a command that allows the user to automatically instrument+certain third party libraries. Here is an example that shows how to use this launcher+with auto instrumentation.++First, create a new virtual environment:++```bash+cd ~+mkdir auto_instrumentation+virtualenv auto_instrumentation+source auto_instrumentation/bin/activate+pip install opentelemetry-api+pip install opentelemetry-sdk+pip install opentelemetry-instrumentation

these are not needed if opentelemetry-launcher is installed first (as it will install all of those as dependencies)

ocelotl

comment created time in 13 hours

pull request commentopen-telemetry/opentelemetry-specification

Adding OTLP Exporter

For the sake of making progress I am happy if this PR gets merged as is provided that we create an issue to address this concern before GA. @codeboten if you are OK with this approach please create the issue.

@tigrannajaryan I've opened follow up issues regarding the OTLP exporter, happy to tackle #790 right away. @fbogsany can you open an issue to address the capturing metrics in the span processors?

codeboten

comment created time in 13 hours

issue openedopen-telemetry/opentelemetry-specification

OTLP Exporter must send client side metrics

A follow-up issue to discussions in #699

As per @fbogsany's comment https://github.com/open-telemetry/opentelemetry-specification/pull/699#issuecomment-668739433:

It would also be valuable to specify metrics here. When monitoring a tracing pipeline in production, it is useful to have
consistent metrics across different SDKs.

The following metrics are suggested in open-telemetry/opentelemetry-ruby#309

  • export.failure - counts failed export requests
  • export.success - counts successful export requests
  • export.spans - counts spans successfully exported

created time in 13 hours

issue openedopen-telemetry/opentelemetry-specification

OTLP Exporter must support single configuration for all signals

A follow-up issue to discussions in https://github.com/open-telemetry/opentelemetry-specification/pull/699

The OTLP exporter must allow the same configuration for metrics/traces (and in the future logs) to support the most common use-case of sending all telemetry to the same collector and multiplexing the data from the collector.

created time in 14 hours

push eventcodeboten/opentelemetry-python

alrex

commit sha b3c2a0372e27eff4594891db8ad04c438e9fdf4c

fix: update default OTLP port to 55680 (#977)

view details

alrex

commit sha cc2749f20aaf15fb6684cb59e884eb97ae0db7d7

Merge branch 'master' into rename-resource-labels

view details

push time in 14 hours

PublicEvent
PublicEvent

push eventopen-telemetry/opentelemetry-python

alrex

commit sha b3c2a0372e27eff4594891db8ad04c438e9fdf4c

fix: update default OTLP port to 55680 (#977)

view details

push time in 5 days

PR merged open-telemetry/opentelemetry-python

fix: update default OTLP port to 55680

Description

Updating default OTLP port.

Fixes #968

Type of change

  • [x] Bug fix (non-breaking change which fixes an issue)

Checklist:

  • [x] Followed the style guidelines of this project
  • [x] Changelogs have been updated
  • [x] Unit tests have been updated
+5 -3

0 comment

4 changed files

codeboten

pr closed time in 5 days

issue closedopen-telemetry/opentelemetry-python

Change default port for OTLP exporter

By default the collector OTLP receiver is configured on port 55680, the current default port in the OTLP exporter is still using the old OpenCensus receiver port. This should be changed.

closed time in 5 days

codeboten

push eventcodeboten/gh-test-b

alrex

commit sha f61e7837e705f4b4911e366978c5c93ce9bfe403

Update watch-upstream.yml

view details

push time in 5 days

push eventcodeboten/gh-test-b

Alex Boten

commit sha 6fca6529768871d21f216d2997ed1818c5f693eb

add upstream file

view details

push time in 5 days

push eventcodeboten/gh-test-b

alrex

commit sha a940c81db6f60f183fe4672592e4375e891c726a

Update watch-upstream.yml

view details

push time in 5 days

push eventlightstep/lightstep-tracer-go

Robert-André Mauchin

commit sha 33b45638f0ca0ad0cb935fd7577cfe6688d79083

Convert id to string using strconv.Itoa See https://github.com/golang/go/issues/32479 Fix #257. Signed-off-by: Robert-André Mauchin <zebob.m@gmail.com>

view details

alrex

commit sha 883058a95344d0fb69f0f713289d6104172cbf3f

Merge branch 'master' into codeboten/issue-256

view details

push time in 5 days

issue commentopen-telemetry/opentelemetry-python

Review spec for tracing

  • [ ] is_valid is currently a method on the SpanContext, the spec defines it as a bool flag https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/api.md#spancontext
codeboten

comment created time in 5 days

issue commentopen-telemetry/opentelemetry-python

Review semantic conventions specifications

Not sure about the other attributes, but at least in the telemetry.sdk.* case they could be set in the OTelResourceDetector to

telemetry.sdk.name=opentelemetry
telemetry.sdk.language=python
telemetry.sdk.name=pkg_resources.get_distribution(
    "opentelemetry-sdk"
).version
codeboten

comment created time in 5 days

push eventcodeboten/opentelemetry-python

Alex Boten

commit sha 0979424b152a554b2bf6f73b5e710026caa69639

update changelog

view details

push time in 5 days

PR opened open-telemetry/opentelemetry-python

Reviewers
fix: update default OTLP port to 55680

Description

Updating default OTLP port.

Fixes #968

Type of change

  • [x] Bug fix (non-breaking change which fixes an issue)

Checklist:

  • [x] Followed the style guidelines of this project
  • [x] Changelogs have been updated
  • [x] Unit tests have been updated
+3 -3

0 comment

3 changed files

pr created time in 5 days

create barnchcodeboten/opentelemetry-python

branch : update-otlp-port

created branch time in 5 days

issue commentopen-telemetry/opentelemetry-python

Review semantic conventions specifications

* [ ]  There is no default resource detector to populate [standard resource names](https://github.com/open-telemetry/opentelemetry-specification/tree/master/specification/resource/semantic_conventions) (not sure if this is in scope)

Any thoughts on whether the telemetry.sdk.* values should be set in the Resource itself or via a ResourceDetector?

codeboten

comment created time in 5 days

push eventlightstep/lightstep-tracer-go

Robert-André Mauchin

commit sha 33b45638f0ca0ad0cb935fd7577cfe6688d79083

Convert id to string using strconv.Itoa See https://github.com/golang/go/issues/32479 Fix #257. Signed-off-by: Robert-André Mauchin <zebob.m@gmail.com>

view details

push time in 5 days

PR merged lightstep/lightstep-tracer-go

Convert id to string using strconv.Itoa

See https://github.com/golang/go/issues/32479

Fix #257.

Signed-off-by: Robert-André Mauchin zebob.m@gmail.com

+2 -1

0 comment

1 changed file

eclipseo

pr closed time in 5 days

issue closedlightstep/lightstep-tracer-go

Go 1.15: conversion from int to string yields a string of one rune

Go 1.15 rc1 on Fedora Rawhide:

Testing    in: /builddir/build/BUILD/lightstep-tracer-go-0.20.0/_build/src
         PATH: /builddir/build/BUILD/lightstep-tracer-go-0.20.0/_build/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin
       GOPATH: /builddir/build/BUILD/lightstep-tracer-go-0.20.0/_build:/usr/share/gocode
  GO111MODULE: off
      command: go test -buildmode pie -compiler gc -ldflags "-X github.com/lightstep/lightstep-tracer-go/version=0.20.0 -extldflags '-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld '"
      testing: github.com/lightstep/lightstep-tracer-go
github.com/lightstep/lightstep-tracer-go
# github.com/lightstep/lightstep-tracer-go_test
./test_utils_test.go:27:20: conversion from int to string yields a string of one rune, not a string of digits (did you mean fmt.Sprint(x)?)
FAIL	github.com/lightstep/lightstep-tracer-go [build failed]

See https://github.com/golang/go/issues/32479

closed time in 5 days

eclipseo

PR opened lightstep/lightstep-tracer-go

feature: Support environment variable to disable metrics

Adding the ability to disable metrics via the LS_METRICS_ENABLED environment variable. Setting this variable to LS_METRICS_ENABLED=false will disable system metrics.

Fixes https://github.com/lightstep/lightstep-tracer-go/issues/256

+6 -1

0 comment

2 changed files

pr created time in 5 days

create barnchlightstep/lightstep-tracer-go

branch : codeboten/issue-256

created branch time in 5 days

issue commentopen-telemetry/opentelemetry-python

Incorrect package name for "OpenTelemetry aiopg instrumentation"

Thanks for reporting the issue! It's been fixed in this change https://github.com/open-telemetry/opentelemetry-python/commit/28d0cdf9316830e2b1a35b96b59c62bfe2a233ab#diff-3c7226bf569c295f9bdf1fded3ad1e59R16

The new package will be released in the next release.

hawkaa

comment created time in 6 days

delete branch codeboten/opentelemetry-specification

delete branch : main2

delete time in 6 days

delete branch codeboten/opentelemetry-specification

delete branch : main3

delete time in 6 days

delete branch codeboten/opentelemetry-specification

delete branch : main4

delete time in 6 days

push eventcodeboten/opentelemetry-specification

Alex Boten

commit sha 95a19f630ef8b585c1c16aa82e3e6f268814c568

fix broken link

view details

push time in 6 days

push eventcodeboten/opentelemetry-specification

push time in 6 days

pull request commentopen-telemetry/opentelemetry-specification

Adding OTLP Exporter

@andrewhsu sounds good. i'll sort out the git mess i just got myself into and get the CI passing.

codeboten

comment created time in 6 days

push eventcodeboten/opentelemetry-specification

Yusuke Tsutsumi

commit sha 4daee3af756be75edbd17085f6d382d963027bc8

Clarify semantic conventions around span start and end time (#592) * Adding http semantic conventions for span start and end times. * Corrected send to end, further clarified timings. * Moving span operation clarification to api Feedback states that the clarification around the meaning of the span start and end times could be more generic. Starting a proposal around by adding an example to the API. * Addressing feedback Rewording recommendation to use a more generic RPC Adding a small blurb clarifying sub operations can be instrumented. * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Expanding on child spans Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

view details

Anuraag Agrawal

commit sha b70565d5a8a13d26c91fb692879dc874d22c3ac8

Add peer.service semantic convention to indicate the name of a target… (#652) * Add peer.service semantic convention to indicate the name of a target remote service. * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Simplify * Remove fallback wording * Needs to be configured using instrumentation * CHANGELOG * Clarify relationship with rpc.service and peer.service and some examples * Clarify example * Move peer.service / rpc.service relationship explanation to rpc doc. * Apply suggestions from code review Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Update specification/trace/semantic_conventions/span-general.md Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Cleanup * Tweak * Update specification/trace/semantic_conventions/rpc.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Update CHANGELOG.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Update specification/trace/semantic_conventions/span-general.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * TOC * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

view details

Armin Ruech

commit sha 0c6f484d073124dde2526d66291bc6a2cfb5e020

Exclude github.com from markdown-link-check (#675)

view details

Carlos Alberto Cortez

commit sha b338f9f63dbf02ff8ebd100e8a847e7bf43e2682

Do not write a value in Context upon failed extraction. (#671)

view details

Armin Ruech

commit sha 6c86748a63e9e7194f414b8175356a35e75b9400

Revise and extend semantic conventions for databases (#575)

view details

Armin Ruech

commit sha c8554d862597a346830121010d4290113b31d905

Remove ZPagesProcessor mentioned in SDK spec (#683)

view details

Carlos Alberto Cortez

commit sha 8b2542091e2c99850f3c80d90b4f25b07dff6057

Update CHANGELOG with 0.6.0 changes. (#685)

view details

Janet Vu

commit sha 4ea4d27c37ad8230aedf5e50e9d3f3e47f6d46c0

Fix links that weren't working (#688)

view details

shrapx

commit sha e69bde658bf014d77d85742bfd6e58a397846f3e

typos (#687)

view details

Armin Ruech

commit sha 709293fe132709705f0e0dd4252992e87a6ec899

Fix Redis sample (db.redis.database_index was missing) (#692)

view details

Tyler Yahn

commit sha f4e6d6ef2e52da61061d0f6f54b50b7cf83d94d8

Update resource `process.*` descriptions (#695) Not all Unix based OSs have `procfs` (Darwin) or have it enabled by default (FreeBSD). Update the description to be specific to Linux systems.

view details

Anuraag Agrawal

commit sha 0434a7b41b9de3bf2a90385f7fbb5e3119d0ddf4

Add mapping for nginx 499 http status (#677)

view details

Carlos Alberto Cortez

commit sha 3e34565066251b1d1777f599ceb5d0f674467bfb

Use OTel as the official acronym in the README. (#700)

view details

Reiley Yang

commit sha c5b1dfd1a89ba9669aaeea8687d4877d4459490a

Add issue/PR templates (#701) * add issue/pr templates * fix tag

view details

Armin Ruech

commit sha 27010e53d47c62986893a18cd48b3f9f6f392c74

Add resource semantic conventions for operating systems (#693)

view details

Reiley Yang

commit sha b610b076f99eb5072e6128d2f5a59ed72096efb0

Fix typo (#702) * fix typo * rephrase

view details

Armin Ruech

commit sha 363e339e83ec08688172f76da7b70a32819288fa

Adapt semantic conventions for the span name of messaging systems (#690) * Adapt messaging semantic conventions to include the operation in the span name * Specify that the operation name must match the respective attribute if the suggested span name format is used * Update span names in examples * Consolidate definition of operation names into a separate section * Consolidate capitalization * Reference Conversation ID definition * Consolidate MD syntax * Organize definitions * Organize definitions * Reference definitions * Allow artificial destinations as span name if neither destination name nor conversation ID are suitable * Do not use conversation IDs for span name * Wording Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com> * Fix typo * Add more links and guidance on messaging.operation * Fix changelog Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com>

view details

Tyler Yahn

commit sha bd98664ae9b7750b38284817013bd9c33d086a90

Unify the batch span processor parameters (#708) The parameter `maxExportBatchSize` refers to "export", but `exporterTimeoutMillis` refers to the "exporter." This unifies on "export" since they are both in reference to the same process.

view details

John Watson

commit sha 15c41b15da0761c2a2d5cf17a1c34b79f93d9463

Add an addendum for allowing async/callback export return results. (#707)

view details

Daniel Dyla

commit sha 587bebac6ef773cf2540907b335b8478245ef836

specify how probability sampler is used with ParentOrElse (#704)

view details

push time in 6 days

create barnchcodeboten/opentelemetry-specification

branch : main4

created branch time in 6 days

create barnchcodeboten/opentelemetry-specification

branch : main3

created branch time in 6 days

push eventcodeboten/opentelemetry-specification

Yusuke Tsutsumi

commit sha 4daee3af756be75edbd17085f6d382d963027bc8

Clarify semantic conventions around span start and end time (#592) * Adding http semantic conventions for span start and end times. * Corrected send to end, further clarified timings. * Moving span operation clarification to api Feedback states that the clarification around the meaning of the span start and end times could be more generic. Starting a proposal around by adding an example to the API. * Addressing feedback Rewording recommendation to use a more generic RPC Adding a small blurb clarifying sub operations can be instrumented. * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Expanding on child spans Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

view details

Anuraag Agrawal

commit sha b70565d5a8a13d26c91fb692879dc874d22c3ac8

Add peer.service semantic convention to indicate the name of a target… (#652) * Add peer.service semantic convention to indicate the name of a target remote service. * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Simplify * Remove fallback wording * Needs to be configured using instrumentation * CHANGELOG * Clarify relationship with rpc.service and peer.service and some examples * Clarify example * Move peer.service / rpc.service relationship explanation to rpc doc. * Apply suggestions from code review Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Update specification/trace/semantic_conventions/span-general.md Co-authored-by: Christian Neumüller <christian+github@neumueller.me> * Cleanup * Tweak * Update specification/trace/semantic_conventions/rpc.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Update CHANGELOG.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * Update specification/trace/semantic_conventions/span-general.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> * TOC * Apply suggestions from code review Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com> Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

view details

Armin Ruech

commit sha 0c6f484d073124dde2526d66291bc6a2cfb5e020

Exclude github.com from markdown-link-check (#675)

view details

Carlos Alberto Cortez

commit sha b338f9f63dbf02ff8ebd100e8a847e7bf43e2682

Do not write a value in Context upon failed extraction. (#671)

view details

Armin Ruech

commit sha 6c86748a63e9e7194f414b8175356a35e75b9400

Revise and extend semantic conventions for databases (#575)

view details

Armin Ruech

commit sha c8554d862597a346830121010d4290113b31d905

Remove ZPagesProcessor mentioned in SDK spec (#683)

view details

Carlos Alberto Cortez

commit sha 8b2542091e2c99850f3c80d90b4f25b07dff6057

Update CHANGELOG with 0.6.0 changes. (#685)

view details

Janet Vu

commit sha 4ea4d27c37ad8230aedf5e50e9d3f3e47f6d46c0

Fix links that weren't working (#688)

view details

shrapx

commit sha e69bde658bf014d77d85742bfd6e58a397846f3e

typos (#687)

view details

Armin Ruech

commit sha 709293fe132709705f0e0dd4252992e87a6ec899

Fix Redis sample (db.redis.database_index was missing) (#692)

view details

Tyler Yahn

commit sha f4e6d6ef2e52da61061d0f6f54b50b7cf83d94d8

Update resource `process.*` descriptions (#695) Not all Unix based OSs have `procfs` (Darwin) or have it enabled by default (FreeBSD). Update the description to be specific to Linux systems.

view details

Anuraag Agrawal

commit sha 0434a7b41b9de3bf2a90385f7fbb5e3119d0ddf4

Add mapping for nginx 499 http status (#677)

view details

Carlos Alberto Cortez

commit sha 3e34565066251b1d1777f599ceb5d0f674467bfb

Use OTel as the official acronym in the README. (#700)

view details

Reiley Yang

commit sha c5b1dfd1a89ba9669aaeea8687d4877d4459490a

Add issue/PR templates (#701) * add issue/pr templates * fix tag

view details

Armin Ruech

commit sha 27010e53d47c62986893a18cd48b3f9f6f392c74

Add resource semantic conventions for operating systems (#693)

view details

Reiley Yang

commit sha b610b076f99eb5072e6128d2f5a59ed72096efb0

Fix typo (#702) * fix typo * rephrase

view details

Armin Ruech

commit sha 363e339e83ec08688172f76da7b70a32819288fa

Adapt semantic conventions for the span name of messaging systems (#690) * Adapt messaging semantic conventions to include the operation in the span name * Specify that the operation name must match the respective attribute if the suggested span name format is used * Update span names in examples * Consolidate definition of operation names into a separate section * Consolidate capitalization * Reference Conversation ID definition * Consolidate MD syntax * Organize definitions * Organize definitions * Reference definitions * Allow artificial destinations as span name if neither destination name nor conversation ID are suitable * Do not use conversation IDs for span name * Wording Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com> * Fix typo * Add more links and guidance on messaging.operation * Fix changelog Co-authored-by: Christian Neumüller <christian.neumueller@dynatrace.com>

view details

Tyler Yahn

commit sha bd98664ae9b7750b38284817013bd9c33d086a90

Unify the batch span processor parameters (#708) The parameter `maxExportBatchSize` refers to "export", but `exporterTimeoutMillis` refers to the "exporter." This unifies on "export" since they are both in reference to the same process.

view details

John Watson

commit sha 15c41b15da0761c2a2d5cf17a1c34b79f93d9463

Add an addendum for allowing async/callback export return results. (#707)

view details

Daniel Dyla

commit sha 587bebac6ef773cf2540907b335b8478245ef836

specify how probability sampler is used with ParentOrElse (#704)

view details

push time in 6 days

Pull request review commentopen-telemetry/opentelemetry-specification

Adding OTLP Exporter

+# OpenTelemetry Protocol Collector Exporter++This document specifies the configuration options available to the OpenTelemetry Protocol ([OTLP](https://github.com/open-telemetry/oteps/blob/master/text/0035-opentelemetry-protocol.md)) [Collector](https://github.com/open-telemetry/opentelemetry-collector) `SpanExporter` and `MetricsExporter` as well as the retry behavior.

While I agree that it would greatly simplify configuration, we would also be losing the flexibility of sending different types of telemetry data (traces/logs/metrics) to different backends by combining the configuration into a single one.

Though I suppose a user would still be able to accomplish this in code (by instantiating separate exporters for instance), they just wouldn't be able to do this via environment variable configuration.

codeboten

comment created time in 6 days

pull request commentopen-telemetry/opentelemetry-specification

Adding OTLP Exporter

I agree that consistency metrics should be reported. I would expect the metrics to be defined across all exporters and not specifically to the OTLP exporter. Any thoughts around creating a separate issue to track this @fbogsany? Sounds like it could be 2 separate issues:

  1. Exporters must report failure/success/spans metrics
  2. Processor must report dropped_spans
codeboten

comment created time in 6 days

push eventcodeboten/opentelemetry-python

Diego Hurtado

commit sha c42c5f3b4ba0bcc46269a803239de344f8ba91be

Fix grpc version to previous version (#975)

view details

alrex

commit sha 5878b4815325dbd2657b539b4a8af2f2dbb978ac

Merge branch 'master' into reduce-cardinality-requests

view details

push time in 6 days

push eventcodeboten/opentelemetry-python

Diego Hurtado

commit sha c42c5f3b4ba0bcc46269a803239de344f8ba91be

Fix grpc version to previous version (#975)

view details

alrex

commit sha 328729f5273bd81889878517b82529e4e618b836

Merge branch 'master' into rename-resource-labels

view details

push time in 6 days

pull request commentopen-telemetry/opentelemetry-go

Renaming OTEL_RESOURCE_LABELS env var

@MrAlias changelog updated

codeboten

comment created time in 6 days

push eventcodeboten/opentelemetry-go

Alex Boten

commit sha ee049a4d150ffcefcd3513e01959e3f673df4176

update changelog

view details

push time in 6 days

push eventocelotl/opentelemetry-python

Diego Hurtado

commit sha c42c5f3b4ba0bcc46269a803239de344f8ba91be

Fix grpc version to previous version (#975)

view details

alrex

commit sha 26fdc1f7689de97315cf08241e45bcd329682e03

Merge branch 'master' into issue_797

view details

push time in 6 days

issue commentopen-telemetry/opentelemetry-python

Align Sampling API with specs + is_recording_events

@aravinsiva are you still interested in taking this on? Just checking that you'll have enough time to work on it.

lzchen

comment created time in 6 days

push eventlightstep/otel-launcher-go

alrex

commit sha d92804197630762889fde15a0682ffb540e2a916

rename labels to attributes (#12)

view details

push time in 6 days

Pull request review commentlightstep/otel-launcher-go

rename labels to attributes

 func configurePropagators(c *LauncherConfig) error { }  func newResource(c *LauncherConfig) *resource.Resource {+	// workaround until the following change is released+	// https://github.com/open-telemetry/opentelemetry-go/pull/1042+	reset := false+	if len(os.Getenv("OTEL_RESOURCE_LABELS")) == 0 {

i thought about it, but figured the code will be removed shortly anyways

codeboten

comment created time in 6 days

created taglightstep/otel-launcher-python

tagv0.11b0

Launcher, an OpenTelemetry Configuration Layer for Python 🚀

created time in 6 days

push eventlightstep/otel-launcher-python

alrex

commit sha 1ad1e349a6533558b4899e6163a1d2551604ddc6

update dependencies (#30)

view details

push time in 6 days

create barnchlightstep/otel-launcher-python

branch : bump-dependency-11b0

created branch time in 6 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha 04c93ebafdd66258f51bcaa869974bb041a67ff4

add test for WithResourceAttributes

view details

push time in 6 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha 0d78eec9fbe5f83e91b564c71cc90473b904abb4

reset the variable if not set initially

view details

push time in 6 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha d1ce6be0d77144a90842a282829bc88b39c51a43

bump version

view details

push time in 6 days

create barnchlightstep/otel-launcher-go

branch : rename-labels-attrs

created branch time in 6 days

create barnchlightstep/otel-launcher-python

branch : rename-resource-labels

created branch time in 6 days

PR opened open-telemetry/opentelemetry-python

Renaming OTEL_RESOURCE env var

Description

The environment variable OTEL_RESOURCE has been renamed to OTEL_RESOURCE_ATTRIBUTES as per the specification open-telemetry/opentelemetry-specification#758

Type of change

  • [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

  • [x] Unit tests have been run

Checklist:

  • [x] Followed the style guidelines of this project
  • [x] Changelogs have been updated
  • [x] Unit tests have been updated
+10 -8

0 comment

3 changed files

pr created time in 6 days

create barnchcodeboten/opentelemetry-python

branch : rename-resource-labels

created branch time in 6 days

PR opened open-telemetry/opentelemetry-go

Reviewers
Renaming OTEL_RESOURCE_LABELS env var

The environment variable OTEL_RESOURCE_LABELS has been renamed to OTEL_RESOURCE_ATTRIBUTES as per the specification https://github.com/open-telemetry/opentelemetry-specification/pull/758

+2 -2

0 comment

2 changed files

pr created time in 6 days

create barnchcodeboten/opentelemetry-go

branch : rename-resource-labels

created branch time in 6 days

created taglightstep/otel-launcher-go

tagv0.10.0

Launcher, an OpenTelemetry Configuration Layer for Golang 🚀

created time in 7 days

push eventlightstep/otel-launcher-go

alrex

commit sha 71c44dcd8dc77dbe952e6bb2298ec67953636730

update dependencies to 0.10.0, fix release tooling (#11)

view details

push time in 7 days

PR merged lightstep/otel-launcher-go

update dependencies to 0.10.0, fix release tooling
  • updating OpenTelemetry dependencies to 0.10.0
  • adding changelog
  • updating tooling to simplify release process
+625 -607

1 comment

8 changed files

codeboten

pr closed time in 7 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha 01d6c78e42dc7a99f0651bec96160208fbe3eb80

fix go.sum

view details

push time in 7 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha 3719e57598bf5f216158d193a3eb1e60d84d4abb

fix test

view details

push time in 7 days

push eventcodeboten/opentelemetry-python

Alex Boten

commit sha dcf20797e95e85e6ef8ec54be1508a34b5e7d54a

fix test, commit forgotten changelog

view details

push time in 7 days

PR opened lightstep/otel-launcher-go

update dependencies to 0.10.0, fix release tooling
  • updating OpenTelemetry dependencies to 0.10.0
  • adding changelog
  • updating tooling to simplify release process
+616 -604

0 comment

7 changed files

pr created time in 7 days

push eventlightstep/otel-launcher-go

Alex Boten

commit sha 108da2f3ae713bb7895e5fcac22b3835006c69e0

update dependencies to 0.10.0, fix release tooling

view details

push time in 7 days

create barnchlightstep/otel-launcher-go

branch : update-dependencies

created branch time in 7 days

PR opened open-telemetry/opentelemetry-python

Span name updated to follow semantic conventions to reduce cardinality

Description

Using the path for span names in the requests instrumentation led to high cardinality in the reported data. This changes updates the name to use the method instead as defined in the semantic conventions

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • [x] Tested locally
  • [x] Ran unit tests

Checklist:

  • [x] Followed the style guidelines of this project
  • [x] Changelogs have been updated
  • [x] Unit tests have been updated
+4 -7

0 comment

2 changed files

pr created time in 7 days

create barnchcodeboten/opentelemetry-python

branch : reduce-cardinality-requests

created branch time in 7 days

push eventocelotl/opentelemetry-python

Diego Hurtado

commit sha 590c32cffc61762894e2ea782cfc2d00889478e3

Handle B3 trace_id and span_id correctly (#934)

view details

Diego Hurtado

commit sha 85a2f435c0d1344210c38196ed43bc1a4aba984c

Stop TracerProvider from being overridden (#959) Co-authored-by: Leighton Chen <lechen@microsoft.com>

view details

alrex

commit sha 50e7b0822b4527ae26446bdd3ea7f3c8e09014df

Merge branch 'master' into issue_305

view details

push time in 7 days

push eventopen-telemetry/opentelemetry-python

Diego Hurtado

commit sha 85a2f435c0d1344210c38196ed43bc1a4aba984c

Stop TracerProvider from being overridden (#959) Co-authored-by: Leighton Chen <lechen@microsoft.com>

view details

push time in 7 days

PR merged open-telemetry/opentelemetry-python

Stop TracerProvider from being overridden

Description

The actual behavior allows overriding of the current TracerProvider. Setting of TracerProvider can happen in the auto instrumentation steps and later it can be overridden in application code, causing span processors to be lost.

Fixes #958

Type of change

Please delete options that are not relevant.

  • [x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

This PR introduces a change in the following test that asserts that the appropriate warning is raised and that the tracer provider is not overridden even after calling set_tracer_provider twice.

  • [x] opentelemetry-api/tests/trace/test_globals.py:test_tracer_provider_override_warning

Checklist:

  • [x] Followed the style guidelines of this project
  • [x] Changelogs have been updated
  • [x] Unit tests have been added
  • [x] Documentation has been updated
+61 -38

1 comment

6 changed files

ocelotl

pr closed time in 7 days

issue closedopen-telemetry/opentelemetry-python

TracerProvider can be overridden

When TracerProvider is overridden we raise a warning. This is good but actually we should also stop it from being overridden. If a TracerProvider is set in any step of auto instrumentation, then it may be easily overridden in application code causing unexpected side effects like span processors being lost.

closed time in 7 days

ocelotl

push eventlightstep/opentelemetry-examples

Alex Boten

commit sha 4080f8d445754ce76363ccb6d8485c7a3700d84a

update separator for sed

view details

Alex Boten

commit sha cee6655e0150b9a272a7aa8806fe62ca9f5cf893

fix script

view details

push time in 7 days

push eventlightstep/opentelemetry-examples

alrex

commit sha 973806daa0a97f8193ea58ab17d28b71cfac0bcc

Update run.yml

view details

push time in 7 days

push eventlightstep/opentelemetry-examples

alrex

commit sha 0eb446a2a788d7ae52500eb21184c6bca572a067

Update run.yml

view details

push time in 7 days

push eventlightstep/opentelemetry-examples

alrex

commit sha 94fb9f8fd5fbbc3daab8c694b043bf2c508288b2

Update run.yml

view details

push time in 7 days

push eventlightstep/opentelemetry-examples

Alex Boten

commit sha f9b1b7dd9caa5e3f52cf9d9603428fe161dcf02b

fix specialagent builds

view details

push time in 7 days

push eventlightstep/opentelemetry-examples

Alex Boten

commit sha b0a998c969a1ccc0bd22a8e78153f9a26c4a8a86

fix script

view details

push time in 7 days

more