OpenTelemetry

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

Bug description

When the backend API responds with 500 error code then the loader on charts section loads infinitely

Expected behavior

Charts should show No Data like in trace table.

Version information

I think I've had about a 10% success rate with markdownlint since it seems to get throttled by GitHub. I've heard this was an issue that should have improved, but it doesn't seem to have been and I can't find any context for that in this repo.

Perhaps switching markdownlint to a GitHub Action would work around the throttling "for free" (actions automatically have GitHub creds for the repo). Jus

Since we upgraded to latest gaurav-nelson/github-action-markdown-link-check@1.0.14 (from 1.0.13) every time we change something in a md file with links we fail the link check, see:
https://github.com/open-telemetry/opentelemetry-collector/runs/5755269731?check_suite_focus=true

Something that may be related open-telemetry/opentelemetry-specification#2426.

open-telemetry/opentelemetry-dotnet#3112 As a follow up to this, we can now modify the instrumentation libraries to leverage the new Status field on Activity.

In the doc page https://opentelemetry.io/docs/java/manual_instrumentation/, it would be nice if a layer could be added, using the latests dependencies, bom and inner project dependencies(api, sdk, and opentelemetry-exporters-otlp) to use the provided code.

It would be nice if the sample could provide the gradle/maven, etc. dependencies as a block to copy/paste int the https://opentelemetry.io/

Intake API

Extend transaction Intake API to accept transaction.dropped_spans_stats.service_target_type and transaction.dropped_spans_stats.service_target_name.

Aggregated Metrics Calculation

Extend transaction.DroppedSpanStats to contain the service_target_* fields. For calculating related span m

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

There is a good amount of docstring/API documentation missing from our sphinx builds. For example opentelemetry.propagate classes/functions and docstrings are not available on ReadTheDocs. The same is tru

Schema should be defined as part of resource in metadata.yaml. The filed should be required

schema_version: v1.8.0

Doing that makes wrapBySchemaURLSetterConsumer function redundant, but it cannot be removed until processes scraper is migrated to the new metrics builder open-telemetry/opentelemetry-collector-contrib#7140.

See the spec change for details open-telemetry/opentelemetry-specification#1269

Minimal reproduce step

1.Using Kafka to create a topic
2.Create a loggie to consume this topic by disable auto-commit
3.Create a another one loggie using same config.

Suggest

using franz-go to consume Kafka consumerGroup. When rebalance happen, loggie can using kgo.OnPartitionsRevoked to handle event of new client join/lost the group.

For example, using `CommitUncommittedO

Setting the maxReplicas: 2 crashes the Otel Operator. also tried explicitly set Replicas: null, still same result.

Operator starts successfully but crashes after few minutes with the following error from the log. Removing the maxReplicas solves problem

Operator Log:

{"level":"info","ts":1648778190.841319,"logger":"collector-upgrade","msg":"skipping upgrade for OpenTelemetry C

The method formatStackTrace should be moved from Span into a dedicated Util/Formatter class in the SDK\Common namespace since formatting stack traces is not the responsibility of a Span.

• Move logic in formatStackTrace from Span into a dedicated Util/Formatter class
• Add Backward compatib

This would be eventually required for

• To support async interface between span/log processor and exporters.
• Async IO while exporting the spans.
• Timers to poll for Spans in BatchSpanProcessor, and metrics in PeriodicMetricReader.
• Asynchronously collect metrics for all the instruments across all the meters ( this would be a costly operation sequentially or even using threads).

Re

Currently (as of 0.7.0) NEOS tutorial that is opening up next to Cloud Shell window has 9 pages. 6 of them look similar but shorter versions of what's available in the user guide.
We want to shorten the NEOS tutorial and move details into the user guide. (Hugo static website under /website folder)

Our Rack instrumentation allows configuration of a URL quantization function https://github.com/open-telemetry/opentelemetry-ruby/blob/1c37b00dc82d490dace1f92739977aa4674d7039/instrumentation/rack/lib/opentelemetry/instrumentation/rack/middlewares/tracer_middleware.rb#L122-L137

We should add the same functionality to the Sinatra instrumentation. @genebean reported this requirement in Gitter:

Use Case

• Provide a sample application to test DBs, messaging systems and HTTP, GRPC backend resolution and call view.

Proposal

• A simple app where backend can be swapped or we can use multiple backends.

During the release process the script bump-version-and-create-release-note is used to generate a new version doc which release notes are generated from. Currently this generates notes for ALL closed issues including stale ones and closed PRs. An audit should be done on how t

This line does not work for me in Powershell:
./bin/otelcorecol_* --config ./examples/local/otel-config.yaml

Error message: "./bin/otelcorecol_* : The term './bin/otelcorecol_*' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

• .