Skip to content

Commit f7993fd

Browse files
author
Jill Grant
authored
Merge pull request #278945 from dlepow/patch-297
Update api-management-tracing-alert.md
2 parents dccb717 + 44049bd commit f7993fd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

includes/api-management-tracing-alert.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,6 @@ ms.date: 05/05/2024
66
ms.author: danlep
77
---
88
> [!IMPORTANT]
9-
> * API Management request tracing can no longer be enabled by setting the **Ocp-Apim-Trace** header in a request and using the value of the **Ocp-Apim-Trace-Location** header in the response to retrieve the trace.
10-
> * To improve security, tracing is now enabled at the level of an individual API by obtaining a time-limited token using the API Management REST API, and passing the token in a request to the gateway. For details, see later in this tutorial.
9+
> * API Management request tracing using the **Ocp-Apim-Trace** header in a request and using the value of the **Ocp-Apim-Trace-Location** response header is being deprecated.
10+
> * To improve security, tracing can now be enabled at the level of an individual API by obtaining a time-limited token using the API Management REST API, and passing the token in a request to the gateway. For details, see [Enable tracing of an API](../articles/api-management/api-management-howto-api-inspector.md#enable-tracing-for-an-api).
1111
> * Take care when enabling tracing, as it can expose sensitive information in the trace data. Ensure that you have appropriate security measures in place to protect the trace data.

0 commit comments

Comments
 (0)