When I had initially configured my Azure APIM Logging to an Azure Event Hub, I thought viewing my logs would be very straightforward. Turns out there were a few things I had to go through. Find your Azure Event Hubs Your Azure Event Hubs are located within your Azure Event Hub Namespace. Validate that Messages are being logged to the Event Hub On the Overview pane, you will see three graphs, the Messages Graph identifies…
A while back I had to integrate logging for my Azure APIM Integration that enabled logging outside of APIM (to be picked up by different groups) and logged information to separate locations. To accomplish this task, I leveraged Azure Event Hubs for storing the logs and have outlined the steps below. The high-level steps for this implementation are available here – https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-log-event-hubs – but there are some pieces I had to figure out to make…
I have a similar picture from when my children were young, we had bought new chairs and had all these boxes so we made this weird box fort in the basement that they could draw on, hang out in, eat, have snacks, etc, etc. It’s where creativity is born.
I’ve held off on adding new categories to my posts for a while now as I generally think what you do comes down to behaviors of work that you do, but I know I’ve been writing about different areas of work that I’d like to bring more to the forefront and I’m also looking to change some of the content that I’ll be writing about. You’ll start seeing new categories such as Team (for remote,…
Logs are the lifeblood of any application you create. If your logs are garbage and make no sense, debugging issues when they arise (because they will arise), will be near impossible. Generic Error Codes, readable information, and elevated error states allow you to filter out what you need and diagnose information quickly. If you’re spending hours and hours to find out what went wrong, you missed something in your initial build.