Trask Stalnaker

URL query string values should be redacted by default

25

Fixes #860 ## Changes Query string values are now redacted by default due to concerns around leaking sensitive data. This is not considered a breaking change because the [OTel semantic...

Similar to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/migration-guide.md

Decide on which `db.system` values to mark stable as part of initial db semconv stability

4

Tracking / blocking issue for initial database semconv stability.

Create an ARM64 GitHub Actions Runner that repositories can use to build / test on ARM64

9

Opening as a public tracking issue, it looks like I have access to create it.

In particular, is it ok for instrumentation to populate span status ERROR description with `exception.message` or `exception.type`? This is the current specification text: > When the status is set to...

Add metric advice to capture only a specific set of values for a given attribute, and normalize the rest to a value which represents "other"

5

This would be needed if we go with [Limit HTTP request method cardinality: use one attribute (option C/E)](https://github.com/open-telemetry/semantic-conventions/pull/35) as the solution for https://github.com/open-telemetry/opentelemetry-specification/issues/3470. The metric advice could take something like...

Should we bump 1.x minor versions when bumping SDK minor versions?

1

Currently we are only bumping 1.x patch versions when bumping SDK minor versions, e.g. https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11879 @brunobat recently reported a breaking change when updating 1.x patch versions. He didn't recall the...

Instead of adding it to each stable module. Check out how this is done in core (SDK) repo: https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-java%20otel.japicmp-conventions&type=code _Originally posted by @trask in https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11763#pullrequestreview-2167969814_

#11528 introduced a new version of japicmp which includes the version numbers in the diffs to make the automation work with this new version, need to * [prepare-release-branch.yml](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/.github/workflows/prepare-release-branch.yml) - need...