Update index.mdx

Author: lcian

docs/platforms/rust/common/logs/index.mdx

@@ -19,22 +19,13 @@ sentry = { version = "{{@inject packages.version('sentry.rust') }}", features =
 
 ## Setup
 
-To enable logging, you need to initialize the SDK with the `enable_logs` option set to `true`.
-
-```rust
-let _guard = sentry::init((
-    "___PUBLIC_DSN___",
-    sentry::ClientOptions {
-        release: sentry::release_name!(),
-        enable_logs: true,
-        ..Default::default()
-    }
-));
-```
+To enable logging, just add the `sentry` dependency with the `logs` feature flag.
+This will set `enable_logs: true` by default in your `sentry::ClientOptions`.
+You can opt-out from sending logs even while using the `logs` feature flag by explicitly initializing the SDK with `enable_logs: false`.
 
 ## Usage
 
-Once the feature is enabled on the SDK and the SDK is initialized, you can send logs by using the logging macros.
+Once the feature is enabled and the SDK is initialized, you can send logs by using the logging macros.
 The `sentry` crate exposes macros that support six different log levels:
 `logger_trace`, `logger_debug`, `logger_info`, `logger_warn`, `logger_error` and `logger_fatal`.
 The macros support logging a simple message, or a message with parameters, with `format` syntax:
@@ -81,7 +72,6 @@ tracing = "0.1.41"
 tracing-subscriber = "0.3.19"
 ```
 
-Initialize the SDK with `enable_logs` set to `true`.
 Then, use standard `tracing` macros to capture logs.
 
 ```rust {filename:main.rs}
@@ -119,7 +109,7 @@ fn main() {
 
 The fields of `tracing` events are automatically captured as attributes in Sentry logs.
 
-By default, `tracing` events at info level or above are captured as Sentry logs.
+By default, `tracing` events at or above info level are captured as Sentry logs.
 
 This behavior can be customized by applying a custom `event_filter` when creating the layer.
 The following snippet shows the default `event_filter` that's applied when using the `sentry` crate with the `logs` feature flag.
@@ -136,6 +126,7 @@ let sentry_layer =
         // Capture everything else as both a breadcrumb and a log
         _ => EventFilter::Breadcrumb | EventFilter::Log,
     });
+```
 
 ### `log` Integration
 
@@ -149,7 +140,6 @@ log = "0.4"
 env_logger = "0.11"
 ```
 
-Initialize the SDK with `enable_logs` set to `true`, and configure the `log` integration to map `log` records to logs based on metadata such as severity.
 Then, use standard `log` macros to capture logs.
 
 ```rust {filename:main.rs}
@@ -168,17 +158,7 @@ fn main() {
 
     let logger = sentry::integrations::log::SentryLogger::with_dest(
         env_logger::Builder::from_default_env().build(),
-    )
-    .filter(|md| match md.level() {
-        // Capture error records as Sentry events
-        // These are grouped into issues, representing high-severity errors to act upon
-        log::Level::Error => LogFilter::Event,
-        // Ignore trace level records, as they're too verbose
-        log::Level::Trace => LogFilter::Ignore,
-        // Capture everything else as a log
-        _ => LogFilter::Log,
-    });
-
+    );
     log::set_boxed_logger(Box::new(logger)).unwrap();
     log::set_max_level(log::LevelFilter::Trace);