Skip to content

Commit

Permalink
v1.13.0 pre-release changes (#821)
Browse files Browse the repository at this point in the history
  • Loading branch information
laurit authored Jun 17, 2022
1 parent ccd9309 commit 1035fed
Show file tree
Hide file tree
Showing 5 changed files with 28 additions and 17 deletions.
21 changes: 19 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,36 @@ and this repository adheres to [Semantic Versioning](https://semver.org/spec/v2.

## Unreleased

## v1.13.0 - 2022-06-17

### General

- OpenTelemetry Java SDK and OpenTelemetry Instrumentation for Java dependencies have been updated to version 1.15.0.
- Micrometer dependency has been updated to version 1.9.1.

### Breaking Changes

- Deprecated configuration property `splunk.profiler.period.{eventName}` has been removed. You can use
`splunk.profiler.call.stack.interval` instead.

## v1.12.0 - 2022-06-09

### General

- Compliance with [GDI spec version 1.3.0](https://github.com/signalfx/gdi-specification/releases/tag/v1.3.0)
- Bug fix for `OTEL_EXPORTER_OTLP_ENDPOINT` not overriding the `splunk.realm` property (#795)
- Profiling stack trace data defaults to pprof format (#799)
- Change metric names used by memory profiling:
- `jvm.experimental.memory.allocated` -> `process.runtime.jvm.memory.allocated`
- `jvm.experimental.memory.reclaimed` -> `process.runtime.jvm.memory.reclaimed`
(these two have also been migrated from Gauge to Counter)

### Bugfixes

- Fixed `OTEL_EXPORTER_OTLP_ENDPOINT` not overriding the `splunk.realm` property (#795)

### Enhancements

- Profiling stack trace data defaults to pprof format (#799)

## v1.11.0 - 2022-05-18

### General
Expand Down
15 changes: 5 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@

<p align="center">
<img alt="Stable" src="https://img.shields.io/badge/status-stable-informational?style=for-the-badge">
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.14.0">
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.14.0-blueviolet?style=for-the-badge">
<a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v1.15.0">
<img alt="OpenTelemetry Instrumentation for Java Version" src="https://img.shields.io/badge/otel-1.15.0-blueviolet?style=for-the-badge">
</a>
<a href="https://github.com/signalfx/gdi-specification/releases/tag/v1.3.0">
<img alt="Splunk GDI specification" src="https://img.shields.io/badge/GDI-1.3.0-blueviolet?style=for-the-badge">
Expand Down Expand Up @@ -78,11 +78,6 @@ see [Migrate from the SignalFx Java Agent](https://docs.splunk.com/Observability

<!-- Comments, spacing, empty and new lines in the section below are intentional, please do not modify them! -->
<!--DEV_DOCS_WARNING-->
<!--DEV_DOCS_WARNING_START-->
The following documentation refers to the in-development version of `splunk-otel-java`. Docs for the latest version ([v1.12.0](https://github.com/signalfx/splunk-otel-java/releases/latest)) can be found [here](https://github.com/signalfx/splunk-otel-java/blob/v1.12.0/README.md).

---
<!--DEV_DOCS_WARNING_END-->

## Requirements

Expand Down Expand Up @@ -165,11 +160,11 @@ To extend the instrumentation with the OpenTelemetry Instrumentation for Java,
you have to use a compatible API version.

<!-- IMPORTANT: do not change comments or break those lines below -->
The Splunk Distribution of OpenTelemetry Java version <!--SPLUNK_VERSION-->1.12.0<!--SPLUNK_VERSION--> is compatible
The Splunk Distribution of OpenTelemetry Java version <!--SPLUNK_VERSION-->1.13.0<!--SPLUNK_VERSION--> is compatible
with:

* OpenTelemetry API version <!--OTEL_VERSION-->1.14.0<!--OTEL_VERSION-->
* OpenTelemetry Instrumentation for Java version <!--OTEL_INSTRUMENTATION_VERSION-->1.14.0<!--OTEL_INSTRUMENTATION_VERSION-->
* OpenTelemetry API version <!--OTEL_VERSION-->1.15.0<!--OTEL_VERSION-->
* OpenTelemetry Instrumentation for Java version <!--OTEL_INSTRUMENTATION_VERSION-->1.15.0<!--OTEL_INSTRUMENTATION_VERSION-->
* Micrometer version 1.9.1

## Snapshot builds
Expand Down
3 changes: 1 addition & 2 deletions buildSrc/build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,7 @@ dependencies {
implementation(gradleApi())

implementation("com.diffplug.spotless:spotless-plugin-gradle:6.4.2")
// TODO: remove the snapshot version once 1.15 is released
implementation("io.opentelemetry.instrumentation:gradle-plugins:1.15.0-alpha-SNAPSHOT")
implementation("io.opentelemetry.instrumentation:gradle-plugins:1.15.0-alpha")
implementation("io.spring.gradle:dependency-management-plugin:1.0.11.RELEASE")

// keep these versions in sync with settings.gradle.kts
Expand Down
4 changes: 2 additions & 2 deletions buildSrc/src/main/kotlin/splunk.java-conventions.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@ repositories {
val otelVersion = "1.15.0"
val otelAlphaVersion = "1.15.0-alpha"
val otelContribAlphaVersion = "1.14.0-alpha"
val otelInstrumentationVersion = "1.15.0-SNAPSHOT"
val otelInstrumentationAlphaVersion = "1.15.0-alpha-SNAPSHOT"
val otelInstrumentationVersion = "1.15.0"
val otelInstrumentationAlphaVersion = "1.15.0-alpha"
val micrometerVersion = "1.9.1"

// instrumentation version is used to compute Implementation-Version manifest attribute
Expand Down
2 changes: 1 addition & 1 deletion deployments/cloudfoundry/buildpack/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ If you want to use a specific version of the Java agent in your application, you
environment variable before application deployment, either using `cf set-env` or the `manifest.yml` file:

```sh
$ cf set-env SPLUNK_OTEL_JAVA_VERSION 1.12.0
$ cf set-env SPLUNK_OTEL_JAVA_VERSION 1.13.0
```

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

0 comments on commit 1035fed

Please sign in to comment.