|
7 | 7 | <parent> |
8 | 8 | <groupId>io.last9</groupId> |
9 | 9 | <artifactId>vertx-otel-autoconfigure</artifactId> |
10 | | - <version>2.2.2-beta.2</version> |
| 10 | + <version>2.2.2-beta.3</version> |
11 | 11 | </parent> |
12 | 12 |
|
13 | 13 | <artifactId>vertx-otel-core</artifactId> |
|
87 | 87 | <version>${opentelemetry-instrumentation.version}-alpha</version> |
88 | 88 | </dependency> |
89 | 89 |
|
90 | | - <!-- AWS resource detectors: EC2, ECS, EKS, Lambda, Elastic Beanstalk. |
91 | | - Registered via SPI — autoconfigure picks them up automatically. |
92 | | - Makes short HTTP calls to IMDS at startup; silently skips if not on AWS. --> |
93 | | - <dependency> |
94 | | - <groupId>io.opentelemetry.contrib</groupId> |
95 | | - <artifactId>opentelemetry-aws-resources</artifactId> |
96 | | - <version>${opentelemetry-contrib.version}</version> |
97 | | - </dependency> |
98 | | - |
99 | | - <!-- Kotlin stdlib: okhttp 4.x is written in Kotlin, kotlin-stdlib is required at runtime. |
100 | | - Bundled here so customers don't need to add it separately. --> |
101 | | - <dependency> |
102 | | - <groupId>org.jetbrains.kotlin</groupId> |
103 | | - <artifactId>kotlin-stdlib</artifactId> |
104 | | - <version>1.9.22</version> |
105 | | - </dependency> |
106 | | - |
107 | | - <!-- OkHttp: required by opentelemetry-aws-resources (Ec2Resource calls EC2 IMDS via |
108 | | - OkHttpClient). This is bundled into the fat JAR so the AWS detector works on EC2 |
109 | | - without requiring customers to add okhttp as a dependency. |
110 | | - NOTE: opentelemetry-exporter-sender-okhttp is excluded from the shade; only the |
111 | | - okhttp library itself (not its OTel sender SPI) is bundled here. --> |
112 | | - <dependency> |
113 | | - <groupId>com.squareup.okhttp3</groupId> |
114 | | - <artifactId>okhttp</artifactId> |
115 | | - <version>4.12.0</version> |
116 | | - </dependency> |
117 | | - |
118 | | - <!-- GCP resource detectors: GCE, GKE, Cloud Run, App Engine. |
119 | | - Registered via SPI — autoconfigure picks them up automatically. |
120 | | - Makes short HTTP calls to GCP metadata server at startup; silently skips if not on GCP. --> |
121 | | - <dependency> |
122 | | - <groupId>io.opentelemetry.contrib</groupId> |
123 | | - <artifactId>opentelemetry-gcp-resources</artifactId> |
124 | | - <version>${opentelemetry-contrib.version}</version> |
125 | | - </dependency> |
| 90 | + <!-- Cloud resource detectors (AWS EC2/ECS/EKS, GCP GCE/GKE) REMOVED. |
| 91 | + Their IMDS/metadata HTTP calls during SDK init use OkHttp, whose orphaned |
| 92 | + thread pools interfere with the JDK HttpClient used by the OTLP trace |
| 93 | + exporter — causing traces to silently fail while metrics continue working. |
| 94 | + Cloud attributes should be added by the OTel Collector's resourcedetection |
| 95 | + processor instead (resourcedetection/ec2, resourcedetection/gcp). |
| 96 | + See: https://github.com/open-telemetry/opentelemetry-java-contrib/issues/1351 --> |
126 | 97 |
|
127 | 98 | <!-- Logging --> |
128 | 99 | <dependency> |
|
0 commit comments