Minor fixes, stdout to print scope info for logs

.cspell.json

@@ -26,6 +26,7 @@
     // workspace dictionary.
     "words": [
         "actix",
+        "anyvalue",
         "appender",
         "appenders",
         "Bhasin",

opentelemetry-stdout/src/logs/exporter.rs

@@ -75,7 +75,10 @@
 fn print_logs(batch: LogBatch<'_>) {
     for (i, log) in batch.iter().enumerate() {
         println!("Log #{}", i);
-        let (record, _library) = log;
+        let (record, library) = log;
+
+        println!("\t Instrumentation Scope: {:?}", library);
+
         if let Some(event_name) = record.event_name() {
             println!("\t EventName: {:?}", event_name);
         }

opentelemetry/Cargo.toml

@@ -34,10 +34,9 @@ js-sys = "0.3.63"
 default = ["trace", "metrics", "logs", "internal-logs"]
 trace = ["pin-project-lite", "futures-sink", "futures-core", "thiserror"]
 metrics = []
-testing = ["trace", "metrics"]
+testing = ["trace"]
 logs = []
 spec_unstable_logs_enabled = ["logs"]
-otel_unstable = []
 internal-logs = ["tracing"]
 
 [dev-dependencies]

opentelemetry/src/global/internal_logging.rs

@@ -1,7 +1,7 @@
 #![allow(unused_macros)]
 ///
 /// **Note**: These macros (`otel_info!`, `otel_warn!`, `otel_debug!`, and `otel_error!`) are intended to be used
-/// **internally within OpenTelemetry code** or for **custom exporters and processors**. They are not designed
+/// **internally within OpenTelemetry code** or for **custom exporters, processors and other plugins**. They are not designed
 /// for general application logging and should not be used for that purpose.
 ///
 /// Macro for logging informational messages in OpenTelemetry.

opentelemetry/src/global/metrics.rs

@@ -15,6 +15,7 @@ fn global_meter_provider() -> &'static RwLock<GlobalMeterProvider> {
 
 /// Sets the given [`MeterProvider`] instance as the current global meter
 /// provider.
+/// Libraries should NOT call this function. It is intended for applications/executables.
 ///
 /// **NOTE:** This function should be called before getting [`Meter`] instances via [`meter()`] or [`meter_with_scope()`]. Otherwise, you could get no-op [`Meter`] instances.
 pub fn set_meter_provider<P>(new_provider: P)

opentelemetry/src/global/trace.rs

@@ -422,6 +422,7 @@ pub fn tracer_with_scope(scope: InstrumentationScope) -> BoxedTracer {
 /// It returns the [`TracerProvider`] instance that was previously mounted as global provider
 /// (e.g. [`NoopTracerProvider`] if a provider had not been set before).
 ///
+/// Libraries should NOT call this function. It is intended for applications/executables.
 /// [`TracerProvider`]: crate::trace::TracerProvider
 pub fn set_tracer_provider<P, T, S>(new_provider: P) -> GlobalTracerProvider
 where