Skip to content

Commit 0d4d85b

Browse files
authored
Merge pull request #291443 from MicrosoftDocs/main
12/4/2024 PM Publish
2 parents feb01bd + 7e19d76 commit 0d4d85b

File tree

118 files changed

+1395
-807
lines changed

Some content is hidden

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

118 files changed

+1395
-807
lines changed

.openpublishing.redirection.json

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,30 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/partner-solutions/split-experimentation/create.md",
5+
"redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/create",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/partner-solutions/split-experimentation/how-to-set-up-data-access.md",
10+
"redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/how-to-set-up-data-access",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/partner-solutions/split-experimentation/manage.md",
15+
"redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/manage",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/partner-solutions/split-experimentation/overview.md",
20+
"redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/overview",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/partner-solutions/split-experimentation/troubleshoot.md",
25+
"redirect_url": "/previous-versions/azure/partner-solutions/split-experimentation/troubleshoot",
26+
"redirect_document_id": false
27+
},
328
{
429
"source_path": "articles/virtual-desktop/virtual-desktop-fall-2019/classic-retirement.md",
530
"redirect_url": "/previous-versions/azure/virtual-desktop-classic/classic-retirement",
@@ -3986,4 +4011,4 @@
39864011
"redirect_document_id": false
39874012
}
39884013
]
3989-
}
4014+
}

articles/api-management/api-management-howto-app-insights.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -293,14 +293,14 @@ If you are configuring the logger for a workspace, create a `Microsoft.ApiManage
293293
Use the following steps to enable Application Insights logging for an API. You can also enable Application Insights logging for all APIs.
294294

295295
1. Navigate to your **Azure API Management service instance** in the **Azure portal**.
296-
1. Select **APIs** from the menu on the left.
297-
1. Click on your API, in this case **Demo Conference API**. If configured, select a version.
296+
1. Select **APIs** > **APIs** from the menu on the left.
297+
1. Select an API, such as **Swagger Petstore**. If configured, select a version.
298298

299299
> [!TIP]
300300
> To enable logging for all APIs, select **All APIs**.
301301
1. Go to the **Settings** tab from the top bar.
302302
1. Scroll down to the **Diagnostics Logs** section.
303-
:::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-api-1.png" alt-text="App Insights logger":::
303+
:::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-api-1.png" alt-text="Screenshot of Diagnostic Logs configuration in the portal.":::
304304
1. Check the **Enable** box.
305305
1. Select your attached logger in the **Destination** dropdown.
306306
1. Input **100** as **Sampling (%)** and select the **Always log errors** checkbox.

articles/api-management/api-management-howto-cache.md

Lines changed: 28 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,9 @@
11
---
2-
title: Add caching to improve performance in Azure API Management | Microsoft Docs
2+
title: Add caching to improve performance in Azure API Management
33
description: Learn how to improve the latency, bandwidth consumption, and web service load for API Management service calls.
44
author: dlepow
5-
manager: erikre
6-
ms.assetid: 740f6a27-8323-474d-ade2-828ae0c75e7a
75
ms.service: azure-api-management
8-
ms.topic: conceptual
6+
ms.topic: how-to
97
ms.date: 03/20/2024
108
ms.author: danlep
119
---
@@ -42,52 +40,53 @@ To complete this tutorial:
4240
+ [Create an Azure API Management instance](get-started-create-service-instance.md)
4341
+ [Import and publish an API](import-and-publish.md)
4442

45-
## <a name="caching-policies"> </a>Add the caching policies
43+
## Add the caching policies
4644

47-
With caching policies shown in this example, the first request to the **GetSpeakers** operation returns a response from the backend service. This response is cached, keyed by the specified headers and query string parameters. Subsequent calls to the operation, with matching parameters, will have the cached response returned, until the cache duration interval has expired.
45+
With caching policies shown in this example, the first request to a test operation returns a response from the backend service. This response is cached, keyed by the specified headers and query string parameters. Subsequent calls to the operation, with matching parameters, will have the cached response returned, until the cache duration interval has expired.
4846

4947
1. Sign in to the [Azure portal](https://portal.azure.com).
50-
2. Browse to your APIM instance.
51-
3. Select the **API** tab.
52-
4. Click **Demo Conference API** from your API list.
53-
5. Select **GetSpeakers**.
54-
6. On the top of the screen, select **Design** tab.
55-
7. In the **Inbound processing** section, click the **</>** icon.
48+
1. Browse to your API Management instance.
49+
1. Select **APIs** > **APIs** from the menu on the left.
50+
1. Select an API for which you want to configure caching.
51+
1. On the top of the screen, select **Design** tab.
52+
1. In the **Inbound processing** section, select the **</>** icon.
53+
:::image type="content" source="media/api-management-howto-cache/code-editor.png" alt-text="Screenshot of the API Management policy editor in the portal.":::
5654

57-
![code editor](media/api-management-howto-cache/code-editor.png)
55+
8. In the `inbound` element, add the following policy:
5856

59-
8. In the **inbound** element, add the following policy:
60-
61-
```
57+
```xml
6258
<cache-lookup vary-by-developer="false" vary-by-developer-groups="false">
6359
<vary-by-header>Accept</vary-by-header>
6460
<vary-by-header>Accept-Charset</vary-by-header>
6561
<vary-by-header>Authorization</vary-by-header>
6662
</cache-lookup>
6763
```
6864

69-
9. In the **outbound** element, add the following policy:
65+
9. In the `outbound` element, add the following policy:
7066

71-
```
67+
```xml
7268
<cache-store duration="20" />
7369
```
7470

75-
**Duration** specifies the expiration interval of the cached responses. In this example, the interval is **20** seconds.
71+
In this policy, **duration** specifies the expiration interval of the cached responses. In this example, the interval is **20** seconds.
7672

7773
> [!TIP]
7874
> If you are using an external cache, as described in [Use an external Azure Cache for Redis in Azure API Management](api-management-howto-cache-external.md), you may want to specify the `caching-type` attribute of the caching policies. See [API Management caching policies](api-management-policies.md#caching) for more details.
7975
80-
## <a name="test-operation"> </a>Call an operation and test the caching
81-
To see the caching in action, call the operation from the developer portal.
76+
## Call an operation and test the caching
77+
To see the caching in action, call an operation from the portal.
8278

83-
1. In the Azure portal, browse to your APIM instance.
84-
2. Select the **APIs** tab.
85-
3. Select the API to which you added caching policies.
86-
4. Select the **GetSpeakers** operation.
87-
5. Click the **Test** tab in the top right menu.
88-
6. Press **Send**.
79+
1. In the Azure portal, browse to your API Management instance.
80+
1. Select **APIs** > **APIs** from the menu on the left.
81+
1. Select the API to which you added caching policies.
82+
1. Select an operation to test.
83+
1. Select the **Test** tab in the top right menu.
84+
1. Select **Trace** two or three times in quick succession.
85+
1. Under **HTTP response**, select the **Trace** tab.
86+
1. Jump to the **Inbound** section and scroll to the `cache-lookup` policy. You should see a message similar to the one in the following screenshot, indicating a cache hit:
87+
:::image type="content" source="media/api-management-howto-cache/test-api-cache-lookup.png" alt-text="Screenshot of cache-lookup when testing an API in the portal.":::
8988

90-
## <a name="next-steps"> </a>Next steps
89+
## Related content
9190
* For more information about caching policies, see [Caching policies][Caching policies] in the [API Management policy reference][API Management policy reference].
9291
* For information on caching items by key using policy expressions, see [Custom caching in Azure API Management](api-management-sample-cache-by-key.md).
9392
* For more information about using external Azure Cache for Redis, see [Use an external Azure Cache for Redis in Azure API Management](api-management-howto-cache-external.md).
@@ -116,7 +115,4 @@ To see the caching in action, call the operation from the developer portal.
116115

117116
[Create an API Management service instance]: get-started-create-service-instance.md
118117

119-
[Configure an operation for caching]: #configure-caching
120-
[Review the caching policies]: #caching-policies
121-
[Call an operation and test the caching]: #test-operation
122-
[Next steps]: #next-steps
118+

0 commit comments

Comments
 (0)