Fixing broken links

Author: kainawroth

articles/azure-monitor/app/app-insights-overview.md

@@ -100,7 +100,7 @@ This section lists all supported platforms and frameworks.
 #### Logging frameworks
 * [`ILogger`](./ilogger.md)
 * [Log4Net, NLog, or System.Diagnostics.Trace](./asp-net-trace-logs.md)
-* [`Log4J`, Logback, or java.util.logging](./opentelemetry-add-modify.md?tabs=java#logs)
+* [`Log4J`, Logback, or java.util.logging](./opentelemetry-add-modify.md?tabs=java#send-custom-telemetry-using-the-application-insights-classic-api)
 * [LogStash plug-in](https://github.com/Azure/azure-diagnostics-tools/tree/master/Logstash/logstash-output-applicationinsights)
 * [Azure Monitor](/archive/blogs/msoms/application-insights-connector-in-oms)
 

articles/azure-monitor/app/data-model-complete.md

@@ -440,7 +440,7 @@ To learn more:
 - Check out [platforms](./app-insights-overview.md#supported-languages) supported by Application Insights.
 - Check out standard context properties collection [configuration](./configuration-with-applicationinsights-config.md#telemetry-initializers-aspnet).
 - Explore [.NET trace logs in Application Insights](./asp-net-trace-logs.md).
-- Explore [Java trace logs in Application Insights](./opentelemetry-add-modify.md?tabs=java#logs).
+- Explore [Java trace logs in Application Insights](./opentelemetry-add-modify.md?tabs=java##send-custom-telemetry-using-the-application-insights-classic-api).
 - Learn about the [Azure Functions built-in integration with Application Insights](../../azure-functions/functions-monitoring.md?toc=/azure/azure-monitor/toc.json) to monitor functions executions.
 - Learn how to [configure an ASP.NET Core](./asp-net.md) application with Application Insights.
 - Learn how to [diagnose exceptions in your web apps with Application Insights](./asp-net-exceptions.md).

articles/azure-monitor/app/opentelemetry-add-modify.md

@@ -1688,13 +1688,19 @@ telemetryClient.TrackEvent("testEvent");
     ```java
     telemetryClient.trackEvent("WinGame");
     ```
+
+    **Logs**
 
+    ```java
+    telemetryClient.trackTrace(message, SeverityLevel.Warning, properties);
+    ```
+
     **Metrics**
 
     ```java
     telemetryClient.trackMetric("queueLength", 42.0);
     ```
-    
+
     **Dependencies**
 
     ```java
@@ -1711,13 +1717,7 @@ telemetryClient.TrackEvent("testEvent");
         telemetryClient.trackDependency(telemetry);
     }
     ```
-    
-    **Logs**
-    
-    ```java
-    telemetryClient.trackTrace(message, SeverityLevel.Warning, properties);
-    ```
-    
+
     **Exceptions**
 
     ```java
@@ -1726,8 +1726,8 @@ telemetryClient.TrackEvent("testEvent");
     } catch (Exception e) {
         telemetryClient.trackException(e);
     }
- 
-   
+
+
 #### [Java native](#tab/java-native)
 
 It's not possible to send custom telemetry using the Application Insights Classic API in Java native.
@@ -1965,13 +1965,13 @@ Adding one or more span attributes populates the `customDimensions` field in the
 
 Add custom dimensions in your code:
 
-    ```java
-    import io.opentelemetry.api.trace.Span;
-    import io.opentelemetry.api.common.AttributeKey;
-    
-    AttributeKey attributeKey = AttributeKey.stringKey("mycustomdimension");
-    Span.current().setAttribute(attributeKey, "myvalue1");
-    ```
+```java
+import io.opentelemetry.api.trace.Span;
+import io.opentelemetry.api.common.AttributeKey;
+
+AttributeKey attributeKey = AttributeKey.stringKey("mycustomdimension");
+Span.current().setAttribute(attributeKey, "myvalue1");
+```
 
 ##### [Node.js](#tab/nodejs)
 
@@ -2217,7 +2217,7 @@ Attaching custom dimensions to logs can be accomplished using a [message templat
 
 #### [Java](#tab/java)
 
-Logback, Log4j, and java.util.logging are [autoinstrumented](#logs). Attaching custom dimensions to your logs can be accomplished in these ways:
+Logback, Log4j, and java.util.logging are [autoinstrumented](#send-custom-telemetry-using-the-application-insights-classic-api). Attaching custom dimensions to your logs can be accomplished in these ways:
 
 * [Log4j 2.0 MapMessage](https://logging.apache.org/log4j/2.0/javadoc/log4j-api/org/apache/logging/log4j/message/MapMessage.html) (a `MapMessage` key of `"message"` is captured as the log message)
 * [Log4j 2.0 Thread Context](https://logging.apache.org/log4j/2.x/manual/thread-context.html)

articles/azure-monitor/app/opentelemetry-configuration.md

@@ -408,7 +408,7 @@ export OTEL_TRACES_SAMPLER_ARG=0.1
 ---
 
 > [!TIP]
-> When using fixed-rate/percentage sampling and you aren't sure what to set the sampling rate as, start at 5% (i.e., 0.05 sampling ratio) and adjust the rate based on the accuracy of the operations shown in the failures and performance blades. A higher rate generally results in higher accuracy. However, ANY sampling will affect accuracy so we recommend alerting on [OpenTelemetry metrics](opentelemetry-add-modify.md#metrics), which are unaffected by sampling.
+> When using fixed-rate/percentage sampling and you aren't sure what to set the sampling rate as, start at 5% (i.e., 0.05 sampling ratio) and adjust the rate based on the accuracy of the operations shown in the failures and performance panes. A higher rate generally results in higher accuracy. However, ANY sampling will affect accuracy so we recommend alerting on [OpenTelemetry metrics](opentelemetry-add-modify.md#add-custom-metrics), which are unaffected by sampling.
 
 <a name='enable-entra-id-formerly-azure-ad-authentication'></a>
 

articles/azure-monitor/app/pre-aggregated-metrics-log-metrics.md

@@ -54,7 +54,7 @@ The collection endpoint preaggregates events before ingestion sampling. For this
 |-------------------------|--------------------------|-------------------------------------------|-----------------------------------------|
 | ASP.NET                 | Supported <sup>1<sup>    | Not supported                             | Not supported                           |
 | ASP.NET Core            | Supported <sup>2<sup>    | Not supported                             | Not supported                           |
-| Java                    | Not supported            | Not supported                             | [Supported](opentelemetry-add-modify.md?tabs=java#metrics) |
+| Java                    | Not supported            | Not supported                             | [Supported](opentelemetry-add-modify.md?tabs=java#send-custom-telemetry-using-the-application-insights-classic-api) |
 | Node.js                 | Not supported            | Not supported                             | Not supported                           |
 
 1. [ASP.NET autoinstrumentation on virtual machines/virtual machine scale sets](./azure-vm-vmss-apps.md) and [on-premises](./application-insights-asp-net-agent.md) emits standard metrics without dimensions. The same is true for Azure App Service, but the collection level must be set to recommended. The SDK is required for all dimensions.

articles/azure-monitor/app/transaction-search-and-diagnostics.md

@@ -132,7 +132,7 @@ The first time you do this step, you're asked to configure a link to your Azure
 
 In addition to the out-of-the-box telemetry sent by Application Insights SDK, you can:
 
-* Capture log traces from your favorite logging framework in [.NET](./asp-net-trace-logs.md) or [Java](./opentelemetry-add-modify.md?tabs=java#logs). This means you can search through your log traces and correlate them with page views, exceptions, and other events.
+* Capture log traces from your favorite logging framework in [.NET](./asp-net-trace-logs.md) or [Java](./opentelemetry-add-modify.md?tabs=java#send-custom-telemetry-using-the-application-insights-classic-api). This means you can search through your log traces and correlate them with page views, exceptions, and other events.
 
 * [Write code](./api-custom-events-metrics.md) to send custom events, page views, and exceptions.