Merge branch 'release/3.11' into DOC-11764--docker-otel-prometheus

Author: RichardSmedley

modules/howtos/pages/collecting-information-and-logging.adoc

@@ -275,6 +275,8 @@ And the Prometheus-format metrics fetched with:
 curl --user Administrator:password http://172.17.0.2:8091/metrics
 ----
 
+Further details can be found in the xref:{version-server}@server:rest-api:application-telemetry.adoc[] page.
+
 There may be advantages to collecting information this way,
 but note that metrics are collected per node,
 and a central Prometheus instance should be set to collect all metrics so that information is not lost in case of a sudden failover.

modules/howtos/pages/observability-tracing.adoc

@@ -14,15 +14,34 @@ To give insight into a request/response flow, the SDK provides a `RequestTracer`
 By default, the SDK will emit information about requests that are over a configurable threshold every 10 seconds. 
 Note that if no requests are over the threshold no event / log will be emitted.
 
-It is possible to customize this behavior by modifying the configuration:
+It is possible to customize this behavior by modifying the configuration.
+The recommended way to configure the environment is via a callback when connecting to the cluster:
 
 [source,java]
 ----
-include::devguide:example$java/Tracing.java[tag=tracing-configure,indent=0]
+var cluster = Cluster.connect(
+  connectionString,
+  clusterOptions(username, password)
+    .environment(env -> env
+      .thresholdLoggingTracerConfig(config -> config
+        .enabled(true)  // it's enabled by default, so this line is not strictly necessary
+        .emitInterval(Duration.ofMinutes(1))
+        .kvThreshold(Duration.ofSeconds(2))
+      )
+    )
+);
 ----
 
 In this case the emit interval is one minute and Key/Value requests will only be considered if their latency is greater or equal than two seconds.
 
+// Don't think we'll need to call this out explicitly, but it's here if we need to uncomment it:
+//
+// TIP:
+// Using the `ClusterOptions.environment()`, as in the above snippet, ensures that the SDK manages the environment --
+// shutting down after disconnecting from the cluster.
+// If you create your own `own ClusterEnvironent` or `ClusterEnvironment.Builder` then you will need to manage the environment yourself.
+
+
 The JSON blob emitted looks similar to the following (prettified here for readability):
 
 [source,json]

modules/howtos/pages/slow-operations-logging.adoc

@@ -16,7 +16,7 @@ Threshold logging is the recording of slow operations -- useful for diagnosing w
 
 === Configuring Threshold Logging
 
-To configure threshold logging, adjust the xref:ref:client-settings.adoc#general-options[ThresholdRequestTracer].
+To configure threshold logging, adjust the xref:observability-tracing.adoc#the-default-thresholdloggingtracer[ThresholdRequestTracer].
 You should expect to see output in JSON format in the logs for the services encountering problems:
 
 [source,json]
@@ -54,4 +54,4 @@ Each entry looks like this, with all fields populated:
 }
 ----
 
-If a field is not present (because for example dispatch did not happen), it will not be included. 
+If a field is not present (because for example dispatch did not happen), it will not be included.