Merge pull request #253324 from AaronMaxwell/aaronmax-java-faq-update

Log processors don't work with TelemetryClient.trackTrace

Author: prmerger-automator[bot]

articles/azure-monitor/app/java-standalone-telemetry-processors-examples.md

@@ -552,3 +552,9 @@ Let's assume the input log message body is `User account with userId 123456xx fa
   }
 }
 ```
+
+## Frequently asked questions
+
+### Why doesn't the log processor process logs using TelemetryClient.trackTrace()?
+
+TelemetryClient.trackTrace() is part of the Application Insights Classic SDK bridge, and the log processors only work with the new [OpenTelemetry-based instrumentation](opentelemetry-enable.md).

articles/azure-monitor/app/java-standalone-telemetry-processors.md

@@ -30,7 +30,7 @@ Some use cases:
 
 Before you learn about telemetry processors, you should understand the terms *span* and *log*.
 
-A span is a type of telemetry that represent one of:
+A span is a type of telemetry that represents one of:
 
 * An incoming request.
 * An outgoing dependency (for example, a remote call to another service).
@@ -479,7 +479,7 @@ The log processor modifies either the log message body or attributes of a log ba
 
 ### Update Log message body
 
-The `body` section requires the `fromAttributes` setting. The values from these attributes are used to create a new body, concatenated in the order that the configuration specifies. The processor will change the log body only if all of these attributes are present on the log.
+The `body` section requires the `fromAttributes` setting. The values from these attributes are used to create a new body, concatenated in the order that the configuration specifies. The processor changes the log body only if all of these attributes are present on the log.
 
 The `separator` setting is optional. This setting is a string. It's specified to split values.
 > [!NOTE]
@@ -604,7 +604,7 @@ For more information, see [Telemetry processor examples](./java-standalone-telem
 
 Metric filter are used to exclude some metrics in order to help control ingestion cost.
 
-Metric filters only support `exclude` criteria. Metrics that match its `exclude` criteria will not be exported.
+Metric filters only support `exclude` criteria. Metrics that match its `exclude` criteria won't be exported.
 
 To configure this option, under `exclude`, specify the `matchType` one or more `metricNames`.
 
@@ -645,3 +645,9 @@ To configure this option, under `exclude`, specify the `matchType` one or more `
 | `\Process(??APP_WIN32_PROC??)\Private Bytes` | default metrics | Sum of [MemoryMXBean.getHeapMemoryUsage()](https://docs.oracle.com/javase/8/docs/api/java/lang/management/MemoryMXBean.html#getHeapMemoryUsage--) and [MemoryMXBean.getNonHeapMemoryUsage()](https://docs.oracle.com/javase/8/docs/api/java/lang/management/MemoryMXBean.html#getNonHeapMemoryUsage--). | no |
 | `\Process(??APP_WIN32_PROC??)\IO Data Bytes/sec` | default metrics | `/proc/[pid]/io` Sum of bytes read and written by the process (diff since last reported). See [proc(5)](https://man7.org/linux/man-pages/man5/proc.5.html). | no |
 | `\Memory\Available Bytes` | default metrics | See [OperatingSystemMXBean.getFreePhysicalMemorySize()](https://docs.oracle.com/javase/7/docs/jre/api/management/extension/com/sun/management/OperatingSystemMXBean.html#getFreePhysicalMemorySize()). | no |
+
+## Frequently asked questions
+
+### Why doesn't the log processor process logs using TelemetryClient.trackTrace()?
+
+TelemetryClient.trackTrace() is part of the Application Insights Classic SDK bridge, and the log processors only work with the new [OpenTelemetry-based instrumentation](opentelemetry-enable.md).