Cijo Thomas

Fix stdout traceexporter to show scope attributes

1

Fixes # Design discussion issue (if applicable) # ## Changes Please provide a brief description of the changes here. ## Merge requirement checklist * [ ] [CONTRIBUTING](https://github.com/open-telemetry/opentelemetry-rust/blob/main/CONTRIBUTING.md) guidelines followed *...

Prepare v0.23 release

1

Preparing the next release. No change in overall [status](https://github.com/open-telemetry/opentelemetry-rust/tree/main?tab=readme-ov-file#project-status) and breaking changes are still expected in next release. The next release, which is planned for June 30 2024, is expected...

Remove global shutdown from metrics and doc fixes

2

Fixes https://github.com/open-telemetry/opentelemetry-rust/issues/1679

[Metrics SDK] Shutdown false alarm

1

Originally discussed here: https://github.com/open-telemetry/opentelemetry-rust/pull/1623/files#r1527013980 ``` #[test] fn test_shutdown_false_alarm() { let reader = TestMetricReader::new(); let provider = super::SdkMeterProvider::builder() .with_reader(reader.clone()) .build(); // Initially, shutdown should not be called assert!(!reader.is_shutdown()); // Shutdown the...

Metrics SDK improvements

1

Opening a parent issue to track Metrics SDK improvements for [Stable release](https://github.com/open-telemetry/opentelemetry-rust/issues/1719). **Background** The primary function of the Metrics SDK is to accept a number `` along with a slice...

Appender-tracing and target

2

OpenTelemetry-Appender-Tracing is currently ignoring the `target` from the Metadata. It is stored as an [attribute "log.target"](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-appender-tracing/src/layer.rs#L52) when using experimental feature flag. `target` from `tracing` is what OTel calls [instrumentation scope's...

Metrics beta/rc/stable release timelines

2

Extracting from [parent issue](https://github.com/open-telemetry/opentelemetry-rust/issues/1678) to own issue to gather explicit feedbacks, as details are hard to notice, when embedded inside the parent issue, especially the breaking changes. ### Background: Re-emphasizing...

Signal feature flag name is not consistent

1

https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/Cargo.toml#L35 We use "trace", "logs", "metrics". Proposing to make it consistent and rename "trace" to "traces". https://opentelemetry.io/docs/concepts/signals/

[Default ](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/Cargo.toml#L34) is only Trace today. This issue is to track adding Metrics to the default. (Whether to add Logs or not is separately tracked)

[Metric API] Instrument validation error handling

10

Noticed an inconsistency in the Metric API regarding the `init` and `try_init` methods for instrument initialization. The documentation for [init](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/src/metrics/instruments/mod.rs#L80) says that it would panic when validation fails, while [try_init](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry/src/metrics/instruments/mod.rs#L68)...