Skip to content

Update to opentelemetry-configuration v1.1.0#8451

Open
jack-berg wants to merge 6 commits into
open-telemetry:mainfrom
jack-berg:declarative-config-1.1
Open

Update to opentelemetry-configuration v1.1.0#8451
jack-berg wants to merge 6 commits into
open-telemetry:mainfrom
jack-berg:declarative-config-1.1

Conversation

@jack-berg

@jack-berg jack-berg commented Jun 4, 2026

Copy link
Copy Markdown
Member

@codecov

codecov Bot commented Jun 4, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 49.26108% with 103 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.13%. Comparing base (a5cd87f) to head (abac96b).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...EventToSpanEventBridgeLogRecordProcessorModel.java 5.55% 17 Missing ⚠️
...gure/declarativeconfig/model/IdGeneratorModel.java 60.00% 14 Missing and 2 partials ⚠️
...clarativeconfig/model/LogRecordProcessorModel.java 16.66% 15 Missing ⚠️
...larativeconfig/model/IdGeneratorPropertyModel.java 54.83% 12 Missing and 2 partials ⚠️
...del/ExperimentalPrometheusMetricExporterModel.java 54.16% 11 Missing ⚠️
...arativeconfig/model/PeriodicMetricReaderModel.java 50.00% 10 Missing ⚠️
...eclarativeconfig/model/RandomIdGeneratorModel.java 44.44% 9 Missing and 1 partial ⚠️
...e/declarativeconfig/model/TracerProviderModel.java 9.09% 7 Missing and 3 partials ⚠️

❌ Your patch check has failed because the patch coverage (49.26%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #8451      +/-   ##
============================================
+ Coverage     78.54%   79.13%   +0.59%     
- Complexity     8468     8518      +50     
============================================
  Files          1008     1012       +4     
  Lines         28824    28979     +155     
  Branches       3569     3601      +32     
============================================
+ Hits          22639    22932     +293     
+ Misses         5342     5161     -181     
- Partials        843      886      +43     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jack-berg jack-berg changed the title Update to opentelemetry-configuration latest ref Update to opentelemetry-configuration v1.1.0 Jun 5, 2026
@jack-berg jack-berg marked this pull request as ready for review June 5, 2026 17:16
@jack-berg jack-berg requested a review from a team as a code owner June 5, 2026 17:16
/** Reflectively set the max export batch size for the {@link SdkMeterProviderBuilder}. */
public static SdkMeterProviderBuilder setMaxExportBatchSize(
SdkMeterProviderBuilder sdkMeterProviderBuilder, int maxExportBatchSize) {
public static PeriodicMetricReaderBuilder setMaxExportBatchSize(

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was wrong. Had to fix to add support for the new declarative config property for configuring batch size.


@Override
public String getName() {
return "event_to_span_event_bridge/development";

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that event_to_span_event_bridge is formally supported in declarative config, we can directly reference instance of using SPI.

* The attribute value. The type of value must match .type. Property is required and must be
* non-null.
* The attribute value. The type of value must match .type. Property must be present, but if null
* the entry is ignored.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With POJOs checked into VCS now, its cool /useful to see these diffs as we update to the new version of the schema

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant