BUG: Cannot enable Azure Monitor for a API despite I have already set up Diagnostic settings

Question

---

Hello,

As shown in the above pictures, I have already set up the "Diagnostic Settings" under my API Management Service. However, I can not enable "Azure Monitor" for my API, it keeps asking me to enable diagnostic settings despite I already did so. We are on a developer tier at the meoment.

To me, this looks like a bug. All I want to do is to log the frontend request body so I can see the payload.

Thanks,

Henry

Answer 1

@HenryZhang-6712,
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer.

Issue:

Customer was able to setup the "Diagnostic Settings" under the API Management Service. However, they could not enable "Azure Monitor" for their API, it keeps
asking them to enable diagnostic settings despite already having done so.

Solution:

Customer was able to resolve the issue by renaming the "Diagnostic Setting" and successfully enabled Azure Monitor Diagnostic logs.

Thank you again for your time and patience throughout this issue.

----------

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Thanks,
Carlos V.

Answer 2

Rename the Diagnost Setting name seems solve the problem. In my case, I'm using "HenryTest" for both Setting's name and the log anyasltic resource name, which caused a bug that the setting is not being recognized.