Trace is not available because response does not contain Apim-Trace-Id header.

Dave Willard 41

Observing when I select Test-> Trace: "Trace is not available because response does not contain Apim-Trace-Id header."

JananiRamesh-MSFT 27,911 Reputation points

2024-07-29T05:44:42.0333333+00:00

@Dave Willard Just a follow up to my previous comment and see if you have any other questions. Feel free to add a comment and if the below answer helped with your question, please accept as answer. That would really help others in the community with similar interests. Thanks again for posting it in Q&A
RUBIANO Armando [PD75423A] 0 Reputation points

2024-08-29T03:54:21.2466667+00:00

I have exactly the same issue.... I am unable to see tracing while testing an API operation from the Azure Console with a subscription that has the "Allow Tracing" enable..... The references in that answer Just don't work!
MOHAMED KAMIL HUSSAIN 0 Reputation points

2024-08-29T04:42:16.97+00:00

I am facing the same issue. There is no option for Enabling Trace on API level as mentioned in the comment.

Accepted answer

JananiRamesh-MSFT 27,911 Reputation points

2024-07-26T07:17:12.5333333+00:00

@Dave Willard Thanks for reaching out. The process of enabling tracing has been now changed due to security reasons, previously we were adding OCP-APIM-Trace = true.

Please refer the setps in the below document to enable tracing for an api https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-api-inspector#enable-tracing-for-an-api.

https://learn.microsoft.com/en-us/rest/api/apimanagement/gateway/list-trace?view=rest-apimanagement-2023-09-01-preview&tabs=HTTP#code-try-0 this rest api will return the trace similar to the trace you can see by tracing a call in the portal's test console.

To see the trace in azure portal click on Trace button you will get a warning but still you will be able to see the trace as shown below

do let me know incase of further queries, I would be happy to assist you.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Please sign in to rate this answer.

1 person found this answer helpful.
JananiRamesh-MSFT 27,911 Reputation points

2024-07-30T06:17:08.25+00:00

@Dave Willard Just checking if you had a chance to look at my above comment. if so, can you please update it? Please accept this as an answer and upvote if this answers your query.

Lawrence Malloy 0 Reputation points

2024-07-31T16:43:22.42+00:00

@JananiRamesh-MSFT I have the same issue and have followed the documentation here: https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-api-inspector#enable-tracing-for-an-api I have successfully completed step 3. When running step 4 I get the error in the picture. I think this is because I do not see anywhere to pass the trace ID obtained in the previous steps. Can you break down exactly what needs to be done after step 3? This new process is confusing a lot of people and I haven't found anyone who knows how to do it yet based off the documentation.

Thank you,
Screenshot 2024-07-31 124015.png

Dave Willard 41 Reputation points

2024-07-31T16:58:01.8466667+00:00

It seems that this issue is not related to the trace in the API Test Trace, but is related to testing a client app trying to implement a trace. My trace is now working also I do not select bypass CORS proxy.

Lawrence Malloy 0 Reputation points

2024-07-31T21:16:02.32+00:00

Hey Dave,

What did you do after Step 3? Where did you put the Trace ID as I cannot find the Request Body in the portal.

Thank you,

NGANDU-BISEBA Gabriel 40 Reputation points

2024-08-30T06:03:58.3466667+00:00

If you want a workaround as a last option, you can apply the following outbound policy in the APIM:

<outbound> <set-variable name="SubscriptionKeyName" value="@(context.Subscription?.Name)" /> <choose> <when condition="@(context.Variables.GetValueOrDefault<string>("SubscriptionKeyName") != null && context.Variables.GetValueOrDefault<string>("SubscriptionKeyName") == "Built-in all-access subscription")"> <set-header name="Apim-Trace-Id" exists-action="override"> <value>@{ return Guid.NewGuid().ToString(); }</value> </set-header> </when> <otherwise /> </choose> </outbound>

It will automatically add the necessary header when using the master subscription key (which you should only ever use for tracing) and remove the error message.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

2 additional answers

NGANDU-BISEBA Gabriel 40 Reputation points

2024-09-13T08:21:05.0333333+00:00

This is a bug the APIM team is aware of. For now, the proposed workaround is to use this link when accessing the portal for a tracing session https://portal.azure.com/?microsoft_azure_apimanagement_newTracing=false
Please sign in to rate this answer.

4 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
hossein jalilian 8,080 Reputation points

2024-07-25T21:57:30.3133333+00:00
Thanks for posting your question in the Microsoft Q&A forum.

It can be resolved by following these steps:

Ensure tracing is enabled for your API, navigate to your API Management instance in the Azure portal and select the API you want to trace then go to the "Settings" tab , under "Diagnostics", make sure "Enable tracing" is turned on.

Add the Ocp-Apim-Trace header and set it to true and include the "Ocp-Apim-Subscription-Key" header with a valid subscription key

Traces are only generated for requests using admin subscription keys ,to get the admin key, go to the Developer Portal -> Profile -> find your target API and copy the key

Make sure Allow tracing is enabled for the subscription whose key you're using

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful
Please sign in to rate this answer.

1 person found this answer helpful.
Dave Willard 41 Reputation points

2024-07-25T23:21:25.52+00:00

Ensure tracing is enabled for your API, navigate to your API Management instance in the Azure portal and select the API you want to trace then go to the "Settings" tab , under "Diagnostics", make sure "Enable tracing" is turned on.

Answer: I see No "Enable tracing available under "Settings" tab , under "Diagnostics"

I do observe:

Diagnostics Logs Application Insights Azure Monitor Local Under Each Enable box

Subscription is checked: Allow tracing

I observe Warning:

Only allow tracing on subscriptions intended for debugging purposes. Sharing subscription keys with tracing allowed with unauthorized users could lead to disclosure of sensitive information contained in tracing logs such as keys, access tokens, passwords, internal hostnames, and IP addresses. Tracing will be enabled for 1 hour.

Dave Willard 41 Reputation points

2024-07-25T23:22:24.7233333+00:00

Subscription

Dave Willard 41 Reputation points

2024-07-25T23:23:51.5533333+00:00

Subscription

RUBIANO Armando [PD75423A] 0 Reputation points

2024-08-30T02:42:49.6533333+00:00

I followed ALL steps shown in Hossein Jalilian (Jul26, 2024) and I received this error while trying to see a Trace ... "Trace is not available because response does not contain Apim-Trace-Id header."...

Lorenzo Righini 0 Reputation points

2024-09-13T07:59:49.5366667+00:00

Same happening to me, it says "Trace is not available because response does not contain Apim-Trace-Id header."

Did anyone find a solution?

Lorenzo Righini 0 Reputation points

2024-09-13T08:03:41.3966667+00:00

Same happening to me, it says "Trace is not available because response does not contain Apim-Trace-Id header."

Did anyone find a solution?

Abhishek 5 Reputation points

2024-09-13T16:32:43.96+00:00

I've verified with the proposed workaround by @NGANDU-BISEBA Gabriel and it is working for me . Thank you !

Max Pawlikowski 0 Reputation points

2024-09-20T20:43:34.0666667+00:00

@Ngandu-Biseba Gabriel You are the best, worked for me as well!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Trace is not available because response does not contain Apim-Trace-Id header.

2 additional answers

Your answer