Skip to content

Commit b8fb63c

Browse files
author
Mateusz Rzeszutek
authored
v1.6.0 pre release changes (#560)
1 parent a7fe564 commit b8fb63c

File tree

4 files changed

+32
-14
lines changed

4 files changed

+32
-14
lines changed

CHANGELOG.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,27 @@ and this repository adheres to [Semantic Versioning](https://semver.org/spec/v2.
88

99
## Unreleased
1010

11+
## v1.6.0 - 2021-12-01
12+
13+
### General
14+
15+
- OpenTelemetry Java SDK and OpenTelemetry Instrumentation for Java dependencies have been updated to version 1.9.1.
16+
- Micrometer dependency has been updated to version 1.8.0.
17+
18+
### Bugfixes
19+
20+
- Fix Tomcat thread pool metrics in Tomcat 10.
21+
- Disabled correlation by span links in messaging instrumentations. Now the `PRODUCER`-`CONSUMER` spans will always have
22+
parent-child relationship.
23+
24+
### Enhancements
25+
26+
- The [Micrometer bridge instrumentation](docs/metrics.md#manual-instrumentation) now supports versions starting from
27+
1.3.0.
28+
- A new [Oracle Universal Connection Pool](https://docs.oracle.com/database/121/JJUCP/intro.htm#JJUCP8109)
29+
instrumentation has been added. The agent now collects and exports metrics for Oracle UCP connection pools.
30+
- Profiling: changed the default thread dump rate to 10 seconds (previously 1 second).
31+
1132
## v1.5.0 - 2021-10-20
1233

1334
### General

README.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@
1212

1313
<p align="center">
1414
<img alt="Stable" src="https://img.shields.io/badge/status-stable-informational?style=for-the-badge">
15-
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.7.0">
16-
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.7.0-blueviolet?style=for-the-badge">
15+
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.9.1">
16+
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.9.1-blueviolet?style=for-the-badge">
1717
</a>
1818
<a href="https://github.com/signalfx/gdi-specification/releases/tag/v1.2.0">
1919
<img alt="Splunk GDI specification" src="https://img.shields.io/badge/GDI-1.2.0-blueviolet?style=for-the-badge">
@@ -78,11 +78,6 @@ see [Migrate from the SignalFx Java Agent](https://docs.splunk.com/Observability
7878

7979
<!-- Comments, spacing, empty and new lines in the section below are intentional, please do not modify them! -->
8080
<!--DEV_DOCS_WARNING-->
81-
<!--DEV_DOCS_WARNING_START-->
82-
The documentation below refers to the in development version of this package. Docs for the latest version ([v1.5.0](https://github.com/signalfx/splunk-otel-java/releases/latest)) can be found [here](https://github.com/signalfx/splunk-otel-java/blob/v1.5.0/README.md).
83-
84-
---
85-
<!--DEV_DOCS_WARNING_END-->
8681

8782
## Requirements
8883

@@ -164,12 +159,12 @@ To extend the instrumentation with the OpenTelemetry Instrumentation for Java,
164159
you have to use a compatible API version.
165160

166161
<!-- IMPORTANT: do not change comments or break those lines below -->
167-
The Splunk Distribution of OpenTelemetry Java version <!--SPLUNK_VERSION-->1.5.0<!--SPLUNK_VERSION--> is compatible
162+
The Splunk Distribution of OpenTelemetry Java version <!--SPLUNK_VERSION-->1.6.0<!--SPLUNK_VERSION--> is compatible
168163
with:
169164

170-
* OpenTelemetry API version <!--OTEL_VERSION-->1.7.0<!--OTEL_VERSION-->
171-
* OpenTelemetry Instrumentation for Java version <!--OTEL_INSTRUMENTATION_VERSION-->1.7.0<!--OTEL_INSTRUMENTATION_VERSION-->
172-
* Micrometer version 1.7.5
165+
* OpenTelemetry API version <!--OTEL_VERSION-->1.9.1<!--OTEL_VERSION-->
166+
* OpenTelemetry Instrumentation for Java version <!--OTEL_INSTRUMENTATION_VERSION-->1.9.1<!--OTEL_INSTRUMENTATION_VERSION-->
167+
* Micrometer version 1.8.0
173168

174169
## Snapshot builds
175170

deployments/cloudfoundry/buildpack/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ If you want to use a specific version of the Java agent in your application, you
4040
environment variable before application deployment, either using `cf set-env` or the `manifest.yml` file:
4141

4242
```sh
43-
$ cf set-env SPLUNK_OTEL_JAVA_VERSION 1.5.0
43+
$ cf set-env SPLUNK_OTEL_JAVA_VERSION 1.6.0
4444
```
4545

4646
By default, the [latest](https://github.com/signalfx/splunk-otel-java/releases/latest) available agent version is used.

docs/metrics.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,16 +39,18 @@ For Maven users:
3939
<dependency>
4040
<groupId>io.micrometer</groupId>
4141
<artifactId>micrometer-core</artifactId>
42-
<version>1.7.3</version>
42+
<version>1.8.0</version>
4343
</dependency>
4444
```
4545

4646
For Gradle users:
4747

4848
```kotlin
49-
implementation("io.micrometer:micrometer-core:1.7.3")
49+
implementation("io.micrometer:micrometer-core:1.8.0")
5050
```
5151

52+
The agent supports all micrometer versions starting from 1.3.
53+
5254
### Adding custom metrics
5355

5456
You can use one of meter factory methods provided by the `Metrics` class, or use meter builders and refer to

0 commit comments

Comments
 (0)