Skip to content

Commit 44cc8e4

Browse files
authored
Merge pull request #221639 from MicrosoftDocs/main
12/15 AM Publish
2 parents 99e02f3 + a0184f7 commit 44cc8e4

File tree

83 files changed

+1228
-410
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

83 files changed

+1228
-410
lines changed

articles/active-directory/app-provisioning/functions-for-customizing-application-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -294,7 +294,7 @@ The **interval** string must have one of the following values:
294294
| Get a date ten days prior to hire date | "d" | -10 | 2012-03-16-07:00 | 3/6/2012 7:00:00 AM |
295295
| Add two weeks to hire date | "ww" | 2 | 2012-03-16-07:00 | 3/30/2012 7:00:00 AM |
296296
| Add ten months to hire date | "m" | 10 | 2012-03-16-07:00 | 1/16/2013 7:00:00 AM |
297-
| Add two years to hire date | "yyyy" | 10 | 2012-03-16-07:00 | 3/16/2014 7:00:00 AM |
297+
| Add two years to hire date | "yyyy" | 2 | 2012-03-16-07:00 | 3/16/2014 7:00:00 AM |
298298

299299
---
300300
### DateDiff

articles/active-directory/app-provisioning/how-provisioning-works.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,6 @@ The provisioning service continues running back-to-back incremental cycles indef
138138
- The service is manually stopped using the Azure portal, or using the appropriate Microsoft Graph API command.
139139
- A new initial cycle is triggered using the **Restart provisioning** option in the Azure portal, or using the appropriate Microsoft Graph API command. This action clears any stored watermark and causes all source objects to be evaluated again. This will not break the links between source and target objects. To break the links use [Restart synchronizationJob](https://learn.microsoft.com/graph/api/synchronization-synchronizationjob-restart?view=graph-rest-beta&tabs=http) with the following request:
140140

141-
# [HTTP](#tab/http)
142141
<!-- {
143142
"blockType": "request",
144143
"name": "synchronizationjob_restart"

articles/active-directory/conditional-access/concept-conditional-access-users-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ A workload identity is an identity that allows an application or service princip
103103

104104
Organizations can target specific workload identities to be included or excluded from policy.
105105

106-
For more information, see the article [Conditional Access for workload identities preview](workload-identity.md).
106+
For more information, see the article [Conditional Access for workload identities](workload-identity.md).
107107

108108
## Next steps
109109

articles/active-directory/reports-monitoring/howto-download-logs.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,10 @@ Azure AD stores activity logs for a specific period. For more information, see [
4747
- Timestamps in the downloaded files are based on UTC.
4848
- For large data sets (> 250,000 records), you should use the [reporting API](/graph/api/resources/azure-ad-auditlog-overview?view=graph-rest-1.0) to download the data.
4949

50+
> [!NOTE]
51+
> **Issues downloading large data sets**
52+
> The Azure Portal downloader will time out if you attempt to download large data sets. Generally, data sets smaller than 250,000 records work well with the browser download feature. If you face issues completing large downloads in the browser, you should use the [reporting API](/graph/api/resources/azure-ad-auditlog-overview?view=graph-rest-1.0) to download the data.
53+
5054
## How to download activity logs
5155

5256
You can access the activity logs from the **Monitoring** section of Azure AD or from the **Users** page of Azure AD. If you view the audit logs from the **Users** page, the filter category will be set to **UserManagement**. Similarly, if you view the audit logs from the **Groups** page, the filter category will be set to **GroupManagement**. Regardless of how you access the activity logs, your download is based on the filter you've set.
@@ -72,4 +76,4 @@ If your tenant has enabled the [sign-in logs preview](concept-all-sign-ins.md),
7276
## Next steps
7377

7478
- [Integrate Azure AD logs with Azure Monitor](howto-integrate-activity-logs-with-log-analytics.md)
75-
- [Access Azure AD logs using the Graph API](quickstart-access-log-with-graph-api.md)
79+
- [Access Azure AD logs using the Graph API](quickstart-access-log-with-graph-api.md)

articles/aks/azure-files-volume.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
44
description: Learn how to manually create a volume with Azure Files for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
55
services: container-service
66
ms.topic: article
7-
ms.date: 05/09/2022
7+
ms.date: 12/12/2022
88

99

1010
#Customer intent: As a developer, I want to learn how to manually create and attach storage using Azure Files to a pod in AKS.
@@ -113,6 +113,8 @@ kubectl apply -f azure-files-pod.yaml
113113
You now have a running pod with an Azure Files share mounted at */mnt/azure*. You can use `kubectl describe pod mypod` to verify the share is mounted successfully.
114114

115115
## Mount file share as a persistent volume
116+
> [!NOTE]
117+
> For SMB mount, if `nodeStageSecretRef` field is not provided in PV config, azure file driver would try to get `azure-storage-account-{accountname}-secret` in the pod namespace, if that secret does not exist, it would get account key by Azure storage account API directly using kubelet identity (make sure kubelet identity has reader access to the storage account).
116118
- Mount options
117119
> The default value for *fileMode* and *dirMode* is *0777*.
118120

articles/app-service/tutorial-dotnetcore-sqldb-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alexwolfmsft
77
ms.author: alexwolf
88
ms.devlang: csharp
99
ms.service: app-service
10-
ms.custom: "devx-track-csharp, mvc, cli-validate, seodec18, devx-track-azurecli, devdivchpfy22"
10+
ms.custom: devx-track-csharp, mvc, cli-validate, seodec18, devx-track-azurecli, devdivchpfy22, service-connector
1111
---
1212

1313
# Tutorial: Deploy an ASP.NET Core and Azure SQL Database app to Azure App Service

articles/app-service/tutorial-java-tomcat-connect-managed-identity-postgresql-database.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.topic: tutorial
66
ms.date: 09/26/2022
77
author: KarlErickson
88
ms.author: karler
9-
ms.custom: passwordless-java
9+
ms.custom: passwordless-java, service-connector
1010
---
1111

1212
# Tutorial: Connect to a PostgreSQL Database from Java Tomcat App Service without secrets using a managed identity

articles/azure-monitor/alerts/alerts-common-schema-definitions.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -627,6 +627,30 @@ The following fields describe the cause of an alert.
627627
}
628628
```
629629

630+
#### `monitoringService` = `Prometheus`
631+
632+
**Sample values**
633+
634+
```json
635+
{
636+
"alertContext": {
637+
"interval": "PT1M",
638+
"expression": "sql_up > 0",
639+
"expressionValue": "0",
640+
"for": "PT2M",
641+
"labels": {
642+
"Environment": "Prod",
643+
"cluster": "myCluster1"
644+
},
645+
"annotations": {
646+
"summary": "alert on SQL availability"
647+
},
648+
"ruleGroup": "/subscriptions/<subscription ID>/resourceGroups/myResourceGroup/providers/Microsoft.AlertsManagement/prometheusRuleGroups/myRuleGroup"
649+
}
650+
}
651+
```
652+
653+
630654
## Next steps
631655

632656
- Learn more about the [common alert schema](./alerts-common-schema.md).

articles/azure-monitor/app/asp-net-dependencies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ A list of the latest [currently supported modules](https://github.com/microsoft/
269269
* [Exceptions](./asp-net-exceptions.md)
270270
* [User and page data](./javascript.md)
271271
* [Availability](./monitor-web-app-availability.md)
272-
* Set up custom dependency tracking for [Java](java-in-process-agent.md#add-spans).
272+
* Set up custom dependency tracking for [Java](java-in-process-agent.md#add-spans-using-the-opentelemetry-annotation).
273273
* Set up custom dependency tracking for [OpenCensus Python](./opencensus-python-dependency.md).
274274
* [Write custom dependency telemetry](./api-custom-events-metrics.md#trackdependency)
275275
* See [data model](./data-model.md) for Application Insights types and data model.

articles/azure-monitor/app/java-in-process-agent.md

Lines changed: 56 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -233,29 +233,29 @@ Telemetry emitted by these Azure SDKs is automatically collected by default:
233233

234234
This section explains how to modify telemetry.
235235

236-
### Add spans
236+
### Add spans using the OpenTelemetry annotation
237237

238-
The easiest way to add your own spans is using OpenTelemetry's `@WithSpan` annotation.
238+
The simplest way to add your own spans is using OpenTelemetry's `@WithSpan` annotation.
239239

240240
Spans populate the `requests` and `dependencies` tables in Application Insights.
241241

242242
> [!NOTE]
243243
> This feature is only in 3.2.0 and later.
244244

245-
1. Add `opentelemetry-extension-annotations-1.16.0.jar` to your application:
245+
1. Add `opentelemetry-instrumentation-annotations-1.21.0.jar` (or later) to your application:
246246

247247
```xml
248248
<dependency>
249249
<groupId>io.opentelemetry</groupId>
250-
<artifactId>opentelemetry-extension-annotations</artifactId>
251-
<version>1.16.0</version>
250+
<artifactId>opentelemetry-instrumentation-annotations</artifactId>
251+
<version>1.21.0</version>
252252
</dependency>
253253
```
254254

255255
1. Use the `@WithSpan` annotation to emit a span each time your method is executed:
256256

257257
```java
258-
import io.opentelemetry.extension.annotations.WithSpan;
258+
import io.opentelemetry.instrumentation.annotations.WithSpan;
259259

260260
@WithSpan(value = "your span name")
261261
public void yourMethod() {
@@ -268,20 +268,60 @@ If your method represents a background job that is not already captured by auto-
268268
it is recommended to apply the attribute `kind = SpanKind.SERVER` to the `@WithSpan` annotation
269269
so that it will end up in the Application Insights `requests` table.
270270

271+
### Add spans using the OpenTelemetry API
272+
273+
If the OpenTelemetry `@WithSpan` annotation above doesn't meet your needs,
274+
then you can add your spans using the OpenTelemetry API.
275+
276+
> [!NOTE]
277+
> This feature is only in 3.2.0 and later.
278+
279+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
280+
281+
```xml
282+
<dependency>
283+
<groupId>io.opentelemetry</groupId>
284+
<artifactId>opentelemetry-api</artifactId>
285+
<version>1.0.0</version>
286+
</dependency>
287+
```
288+
289+
1. Use the `GlobalOpenTelemetry` class to create a `Tracer`
290+
291+
```java
292+
import io.opentelemetry.api.GlobalOpenTelemetry;
293+
import io.opentelemetry.api.trace.Tracer;
294+
295+
static final Tracer tracer = GlobalOpenTelemetry.getTracer("com.example");
296+
```
297+
298+
1. Create a span, make it current, and then end it:
299+
300+
```java
301+
Span span = tracer.spanBuilder("my first span").startSpan();
302+
try (Scope ignored = span.makeCurrent()) {
303+
// do stuff within the context of this
304+
} catch (Throwable t) {
305+
span.recordException(t);
306+
} finally {
307+
span.end();
308+
}
309+
```
310+
271311
### Add span events
272312

273313
You can use `opentelemetry-api` to create span events, which populate the traces table in Application Insights. The string passed in to `addEvent()` is saved to the _message_ field within the trace.
274314

275315
> [!NOTE]
276316
> This feature is only in 3.2.0 and later.
277317
278-
1. Add `opentelemetry-api-1.6.0.jar` to your application:
318+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
279319

280320
```xml
281321
<dependency>
282322
<groupId>io.opentelemetry</groupId>
283323
<artifactId>opentelemetry-api</artifactId>
284-
<version>1.6.0</version>
324+
<version>1.0.0</version>
285325
</dependency>
286326
```
287327

@@ -302,13 +342,13 @@ Adding one or more span attributes populates the _customDimensions_ field in the
302342
> [!NOTE]
303343
> This feature is only in 3.2.0 and later.
304344
305-
1. Add `opentelemetry-api-1.6.0.jar` to your application:
345+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
306346

307347
```xml
308348
<dependency>
309349
<groupId>io.opentelemetry</groupId>
310350
<artifactId>opentelemetry-api</artifactId>
311-
<version>1.6.0</version>
351+
<version>1.0.0</version>
312352
</dependency>
313353
```
314354

@@ -329,13 +369,13 @@ You can use `opentelemetry-api` to update the status of a span and record except
329369
> [!NOTE]
330370
> This feature is only in 3.2.0 and later.
331371
332-
1. Add `opentelemetry-api-1.6.0.jar` to your application:
372+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
333373

334374
```xml
335375
<dependency>
336376
<groupId>io.opentelemetry</groupId>
337377
<artifactId>opentelemetry-api</artifactId>
338-
<version>1.6.0</version>
378+
<version>1.0.0</version>
339379
</dependency>
340380
```
341381

@@ -360,13 +400,13 @@ Populate the _user ID_ field in the requests, dependencies, or exceptions table.
360400
> [!NOTE]
361401
> This feature is only in 3.2.0 and later.
362402
363-
1. Add `opentelemetry-api-1.6.0.jar` to your application:
403+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
364404

365405
```xml
366406
<dependency>
367407
<groupId>io.opentelemetry</groupId>
368408
<artifactId>opentelemetry-api</artifactId>
369-
<version>1.6.0</version>
409+
<version>1.0.0</version>
370410
</dependency>
371411
```
372412

@@ -385,13 +425,13 @@ You can use `opentelemetry-api` to get the trace ID or span ID. This action can
385425
> [!NOTE]
386426
> This feature is only in 3.2.0 and later.
387427
388-
1. Add `opentelemetry-api-1.6.0.jar` to your application:
428+
1. Add `opentelemetry-api-1.0.0.jar` (or later) to your application:
389429

390430
```xml
391431
<dependency>
392432
<groupId>io.opentelemetry</groupId>
393433
<artifactId>opentelemetry-api</artifactId>
394-
<version>1.6.0</version>
434+
<version>1.0.0</version>
395435
</dependency>
396436
```
397437

0 commit comments

Comments
 (0)