Application insigth intergrated to API management to get apim logs

Nolan Le 5

User's image

I encountered an error while integrating Application Insight into APIM. I have reviewed APIM's network status and believe that this error is preventing Application Insight from receiving data. My APIM is binding to vnet and it's external. Could everyone please support me in solving this problem?

Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-04-05T10:04:01.7+00:00

Hi - do you have an NSG on the subnet, if so what outbound rules are defined ? I can see other dependencies are green, but just to double check there's no traffic being forced to a firewall (a user defined route collecting all traffic?). Finally, are you/your organisation using AMPLS (Az monitor private link service) to control access to Az monitor endpoints?
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-04-05T10:06:51.0866667+00:00

Sorry for all the questions - it sounds like you're using APIM Premium or development (so STV2) which is vnet attach but "external" , is that correct? So , you are not using Standard V2 SKU with VNET Integration?
Nolan Le 5 Reputation points

2024-04-08T01:40:54.6533333+00:00

Hi Ben Gimblett, yup I'm using APIM development STV2 which vnet attached but using external.
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-04-08T08:23:16.19+00:00

Do you have NSG, or UDR? If so can you provide the details?
Nolan Le 5 Reputation points

2024-04-08T08:42:55.2566667+00:00

Here are APIM routetb and NSG. However, I have run the APIM network diagnose, the result that the NSG is ok just only issue with the connectivity to the Optional Dependencies
Nolan Le 5 Reputation points

2024-04-08T08:45:22.25+00:00

Here is my APIM NSG, but I have run the APIM network diagnose seems this is ok, only the issue with the optional dependencies.
Nolan Le 5 Reputation points

2024-04-08T09:00:11.6566667+00:00

Because my backend in the private network and the same vnet with the APIM, therefore, I need to use the APIM virtual network external. When I changed APIM virtual network to none, this error is resolved but the APIM cannot connect to the private backend.
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-04-08T09:22:19.8866667+00:00

Yes if you want to reach the private backend with STV2 you need to use dev/premium and network attach.
The custom routes you should not need , they dont seem to serve a purpose - APIM + default routing is configured out of the box to reach vnet (when vnet attach as is the case here) and to reach PaaS and Internet.
Did you try removing the NSG association and trying (to rule in or out the NSG) ?
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-04-08T09:23:06.97+00:00

Note: The recommended NSG rules for APIM STV2 are as follows https://learn.microsoft.com/en-us/azure/api-management/api-management-using-with-vnet?tabs=stv2#configure-nsg-rules what you have is close but not following the advice exactly
Nolan Le 5 Reputation points

2024-04-08T10:01:57.5766667+00:00

yah, I have tried this but nothing happens, because the same config that I setup for dev env is working, but for UAT I got this error when intergrate the app insights to APIM. :(

Share via

Application insigth intergrated to API management to get apim logs

Your answer