fix(deps): update dependency io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha to v2.16.0-alpha (#1886)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Lauri Tulmin <ltulmin@splunk.com>
This commit is contained in:
renovate[bot] 2025-05-16 07:36:50 -07:00 committed by GitHub
parent 60ffcf2b9c
commit 5a3c5f6cd1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
6 changed files with 12 additions and 7 deletions

View File

@ -20,7 +20,12 @@ class AwsComponentProviderTest {
@Test
void endToEnd() {
String yaml = "file_format: 0.3\n" + "propagator:\n" + " composite: [xray, xray-lambda]\n";
String yaml =
"file_format: 0.4\n"
+ "propagator:\n"
+ " composite:\n"
+ " - xray:\n"
+ " - xray-lambda:\n";
OpenTelemetrySdk openTelemetrySdk =
DeclarativeConfiguration.parseAndCreate(

View File

@ -17,7 +17,7 @@ This variable contains a JSON structure, which is parsed to fill the following a
| cloudfoundry.space.id | space_id |
| cloudfoundry.space.name | space_name |
The resource attributes follow the [CloudFoundry semantic convention.](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/attributes-registry/cloudfoundry.md).
The resource attributes follow the [CloudFoundry semantic convention.](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/registry/attributes/cloudfoundry.md).
A description of `VCAP_APPLICATION` is available in the [CloudFoundry documentation](https://docs.cloudfoundry.org/devguide/deploy-apps/environment-variable.html#VCAP-APPLICATION).
## Component owners

View File

@ -2,7 +2,7 @@ plugins {
`java-platform`
}
val otelInstrumentationVersion = "2.15.0-alpha"
val otelInstrumentationVersion = "2.16.0-alpha"
val semconvVersion = "1.32.0"
javaPlatform {

View File

@ -32,12 +32,12 @@ public class JvmIntegrationTest extends TargetSystemIntegrationTest {
JmxScraperContainer scraper, GenericContainer<?> target, Path tempDir) {
return scraper
.withTargetSystem("jvm")
// TODO when JVM metrics will be added to instrumentation, the default "auto" source
// Since JVM metrics were be added to instrumentation, the default "auto" source
// means that the definitions in instrumentation will be used, and thus this test will fail
// due to metrics differences, adding an explicit "legacy" source is required to continue
// testing the JVM metrics defined in this project.
// https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13392
// .withTargetSystem("legacy")
.withTargetSystemSource("legacy")
// also testing custom yaml
.withCustomYaml("custom-metrics.yaml");
}

View File

@ -18,7 +18,7 @@ class EventToSpanBridgeComponentProviderTest {
@Test
void endToEnd() {
String yaml =
"file_format: 0.3\n"
"file_format: 0.4\n"
+ "logger_provider:\n"
+ " processors:\n"
+ " - event_to_span_event_bridge:\n";

View File

@ -38,7 +38,7 @@ class RuleBasedRoutingSamplerComponentProviderTest {
@Test
void endToEnd() {
String yaml =
"file_format: 0.3\n"
"file_format: 0.4\n"
+ "tracer_provider:\n"
+ " sampler:\n"
+ " parent_based:\n"