Skip to content

Commit 138dc43

Browse files
author
gitName
committed
add other articles
1 parent 14b4c3d commit 138dc43

File tree

5 files changed

+25
-29
lines changed

5 files changed

+25
-29
lines changed

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: 21 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,7 @@
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
86
ms.topic: conceptual
97
ms.date: 03/20/2024
@@ -44,48 +42,46 @@ To complete this tutorial:
4442

4543
## <a name="caching-policies"> </a>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
8076
## <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.
82-
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**.
77+
To see the caching in action, call an operation from the portal.
78+
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 **Send**.
8985

9086
## <a name="next-steps"> </a>Next steps
9187
* For more information about caching policies, see [Caching policies][Caching policies] in the [API Management policy reference][API Management policy reference].

articles/api-management/front-door-api-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ We recommend updating the default route that's associated with the API Managemen
7979

8080
### Test the configuration
8181

82-
Test the Front Door profile configuration by calling an API hosted by API Management, for example, the Demo Conference API. First, call the API directly through the API Management gateway to ensure that the API is reachable. Then, call the API through Front Door.
82+
Test the Front Door profile configuration by calling an API hosted by API Management, for example, the Swagger Petstore API. First, call the API directly through the API Management gateway to ensure that the API is reachable. Then, call the API through Front Door.
8383

8484
### Call an API directly through API Management
8585

-6.3 KB
Loading
44.6 KB
Loading

0 commit comments

Comments
 (0)