In the one of the previous post I presented you the basics of using Analytics in Application Insights. Just to remind you - it's a tool, which allows you to get much more detailed information regarding how your application perform and behaves. In this post I'll try to encourage you to use this tool on daily basis, especially when something is clearly wrong and you don't want to click through all those tabs in Azure Portal.
Quickly finding an exception
Let's consider following example - you're informed by your client, that he or she got an error saying Object reference not set to an instance of an object. You know the time and assume, that we're facing NullReferenceException here. What could you do to quickly find more details regarding this exception? Let's consider following query:
| where timestamp >= ago(24h)
and type == "System.NullReferenceException"
| project method, details, timestamp
This query will project a simple result containing a method in which an exception was thrown, details(like inner stack) and the exact time when it occurred. You can modify it and use different timestamp to get results, which will satisfy you the most.
Finding pages which are loading too slow
This is another example - you have a SPA and you'd like to know, which pages are loading longer, that a fixed threshold. Fortunately we can use a really simple query, which can help us here:
| where duration > 500
Yes, this is really it. Of course you can extend this query and use other metrics to further filter the data like:
| where duration > 50
and operation_Name == "some_operation"
and timestamp > ago(1h)
Or even visualize your data to be aware which slower requests are really the slowest ones:
| where duration >= 250
| render piechart
You can use predefined metrics to gather some information about your application, but where this tool really shines is the possibility to query custom metric. This allows you to easily build your own reports and really focus on what you're interested in.
For example I'd like to know how many times given method is called so I can be aware of all potential hot-paths and focus my optimization efforts on it. To do this I need two things:
- a tool, which will decorate methods calls with a custom metrics logging(AOP/assembly weaving will help here)
- custom query in Application Insights Analytics
Let's say, that this decorator will log one thing - a method name. Now in Analytics we could create a query, which would use this custom metric to show us which method is called the most.