Update to 3.4.0

Author: trask

articles/azure-monitor/app/java-standalone-config.md

@@ -140,10 +140,12 @@ Furthermore, sampling is trace ID based, to help ensure consistent sampling deci
 
 ### Rate-Limited Sampling
 
-Starting from 3.4.0-BETA, rate-limited sampling is available, and is now the default.
+Starting from 3.4.0, rate-limited sampling is available, and is now the default.
 
 If no sampling has been configured, the default is now rate-limited sampling configured to capture at most
-(approximately) 5 requests per second. This replaces the prior default which was to capture all requests.
+(approximately) 5 requests per second, along with all the dependencies and logs on those requests.
+
+This replaces the prior default which was to capture all requests.
 If you still wish to capture all requests, use [fixed-percentage sampling](#fixed-percentage-sampling) and set the
 sampling percentage to 100.
 
@@ -158,15 +160,15 @@ Here is an example how to set the sampling to capture at most (approximately) 1
 ```json
 {
   "sampling": {
-    "limitPerSecond": 1.0
+    "requestsPerSecond": 1.0
   }
 }
 ```
 
-Note that `limitPerSecond` can be a decimal, so you can configure it to capture less than one request per second if you
-wish.
+Note that `requestsPerSecond` can be a decimal, so you can configure it to capture less than one request per second if you wish.
+For example, a value of `0.5` means capture at most 1 request every 2 seconds.
 
-You can also set the sampling percentage using the environment variable `APPLICATIONINSIGHTS_SAMPLING_LIMIT_PER_SECOND`
+You can also set the sampling percentage using the environment variable `APPLICATIONINSIGHTS_SAMPLING_REQUESTS_PER_SECOND`
 (which will then take precedence over rate limit specified in the json configuration).
 
 ### Fixed-Percentage Sampling
@@ -266,7 +268,7 @@ Starting from version 3.2.0, if you want to set a custom dimension programmatica
 
 ## Connection string overrides (preview)
 
-This feature is in preview, starting from 3.4.0-BETA.
+This feature is in preview, starting from 3.4.0.
 
 Connection string overrides allow you to override the [default connection string](#connection-string), for example:
 * Set one connection string for one http path prefix `/myapp1`.
@@ -462,7 +464,7 @@ To disable auto-collection of Micrometer metrics (including Spring Boot Actuator
 
 Literal values in JDBC queries are masked by default in order to avoid accidentally capturing sensitive data.
 
-Starting from 3.4.0-BETA, this behavior can be disabled if desired, e.g.
+Starting from 3.4.0, this behavior can be disabled if desired, e.g.
 
 ```json
 {
@@ -476,6 +478,24 @@ Starting from 3.4.0-BETA, this behavior can be disabled if desired, e.g.
 }
 ```
 
+## Mongo query masking
+
+Literal values in Mongo queries are masked by default in order to avoid accidentally capturing sensitive data.
+
+Starting from 3.4.0, this behavior can be disabled if desired, e.g.
+
+```json
+{
+  "instrumentation": {
+    "mongo": {
+      "masking": {
+        "enabled": false
+      }
+    }
+  }
+}
+```
+
 ## HTTP headers
 
 Starting from version 3.3.0, you can capture request and response headers on your server (request) telemetry:

articles/azure-monitor/app/java-standalone-sampling-overrides.md

@@ -48,12 +48,14 @@ To begin, create a configuration file named *applicationinsights.json*. Save it
     "sampling": {
       "overrides": [
         {
+          "telemetryKind": "request",
           "attributes": [
             ...
           ],
           "percentage": 0
         },
         {
+          "telemetryKind": "request",
           "attributes": [
             ...
           ],
@@ -65,41 +67,11 @@ To begin, create a configuration file named *applicationinsights.json*. Save it
 }
 ```
 
-> [!NOTE]
-> Starting from 3.4.0-BETA, `telemetryKind` of `request`, `dependency`, `trace` (log), or `exception` is supported
-> (and should be set) on all sampling overrides, e.g.
-> ```json
-> {
->   "connectionString": "...",
->   "sampling": {
->     "percentage": 10
->   },
->   "preview": {
->     "sampling": {
->       "overrides": [
->         {
->           "telemetryKind": "request",
->           "attributes": [
->             ...
->           ],
->           "percentage": 0
->         },
->         {
->           "telemetryKind": "request",
->           "attributes": [
->             ...
->           ],
->           "percentage": 100
->         }
->       ]
->     }
->   }
-> }
-> ```
-
 ## How it works
 
-When a span is started, the attributes present on the span at that time are used to check if any of the sampling
+`telemetryKind` must be one of `request`, `dependency`, `trace` (log), or `exception`.
+
+When a span is started, the type of span and the attributes present on it at that time are used to check if any of the sampling
 overrides match.
 
 Matches can be either `strict` or `regexp`. Regular expression matches are performed against the entire attribute value,
@@ -118,31 +90,6 @@ If no sampling overrides match:
   [top-level sampling configuration](./java-standalone-config.md#sampling) is used.
 * If this is not the first span in the trace, then the parent sampling decision is used.
 
-> [!NOTE]
-> Starting from 3.4.0-BETA, sampling overrides do not apply to "standalone" telemetry by default. Standalone telemetry
-> is any telemetry that is not associated with a request, e.g. startup logs.
-> You can make a sampling override apply to standalone telemetry by including the attribute
-> `includingStandaloneTelemetry` in the sampling override, e.g.
-> ```json
-> {
->   "connectionString": "...",
->   "preview": {
->     "sampling": {
->       "overrides": [
->         {
->           "telemetryKind": "dependency",
->           "includingStandaloneTelemetry": true,
->           "attributes": [
->             ...
->           ],
->           "percentage": 0
->         }
->       ]
->     }
->   }
-> }
-> ```
-
 ## Example: Suppress collecting telemetry for health checks
 
 This will suppress collecting telemetry for all requests to `/health-checks`.
@@ -157,6 +104,7 @@ This will also suppress collecting any downstream spans (dependencies) that woul
     "sampling": {
       "overrides": [
         {
+          "telemetryKind": "request",
           "attributes": [
             {
               "key": "http.url",
@@ -183,6 +131,7 @@ This will suppress collecting telemetry for all `GET my-noisy-key` redis calls.
     "sampling": {
       "overrides": [
         {
+          "telemetryKind": "dependency",
           "attributes": [
             {
               "key": "db.system",
@@ -203,9 +152,6 @@ This will suppress collecting telemetry for all `GET my-noisy-key` redis calls.
 }
 ```
 
-> [!NOTE]
-> Starting from 3.4.0-BETA, `telemetryKind` is supported (and recommended) on all sampling overrides, e.g.
-
 ## Example: Collect 100% of telemetry for an important request type
 
 This will collect 100% of telemetry for `/login`.
@@ -224,6 +170,7 @@ those will also be collected for all '/login' requests.
     "sampling": {
       "overrides": [
         {
+          "telemetryKind": "request",
           "attributes": [
             {
               "key": "http.url",