As part of getting the API “match fit” prior to deployment I explored the various options for logging, auditing and telemetry to provide feedback in relation to production diagnosis and application usage (API focus here). This is part 1 which covers the enrichment of the deployment pipelines using the Azure Application Insights.
Following on from my adventures in Azure API Management Caching I discovered the following error when updating Azure API Management with a new OpenAPI definition file I received the following error: “Azure API Management Template Parameters Used In The UriTemplate Must Be Defined In The Operation, And Vice-Versa”. A fair bit of head-scratching ensued, due to the error message not giving too much away, (which Operation? I’ve 100s of them!) and also being a bit flippant (“vice-versa” <– sass!). Also, I always check that my OpenAPI document conforms and plays nicely with the online Swagger editor. So what gives?
Carried out a discovery phase recently to look at Azure API Management and the key features gained by layering Azure’s API Manager (APIM) as a proxy/facade layer between your backend APIs. One of the elements of APIM that rather appealed to me was the “out of the box” caching.
Was playing with a POC app recently. I pushed out a web deploy to an Azure App Service. Everything built and deployed without issue. The app fired up and nothing just the vanilla error message returned. I checked the site logs via Kudu and nothing jumped out. Tried another deploy and no dice. So where do we go from here?