<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Application Insights on Isaac Levin</title><link>https://example.com/tags/application-insights/</link><description>Recent content in Application Insights on Isaac Levin</description><generator>Hugo</generator><language>en</language><managingEditor>isaac@isaaclevin.com (Isaac Levin)</managingEditor><webMaster>isaac@isaaclevin.com (Isaac Levin)</webMaster><lastBuildDate>Thu, 01 Mar 2018 11:00:59 -0400</lastBuildDate><atom:link href="https://example.com/tags/application-insights/index.xml" rel="self" type="application/rss+xml"/><item><title>Extensions to Application Insights Telemetry Collection</title><link>https://example.com/2018/application-insights-extensions/</link><pubDate>Thu, 01 Mar 2018 11:00:59 -0400</pubDate><author>isaac@isaaclevin.com (Isaac Levin)</author><guid>https://example.com/2018/application-insights-extensions/</guid><description>&lt;h2 id="extending-the-greatness-of-application-insights"&gt;Extending the Greatness of Application Insights&lt;/h2&gt;
&lt;br /&gt;
&lt;p&gt;I will start off by saying I love Application Insights. I have been using it for a long time, and am delighted at the new roll-out of features for it. I have even been giving a talk on Application Insights and how easy it is to instrument your application, so check that out if you are interested. One thing that is great about Application Insights is how extendable it is. The nature of how the data is structured allows a developer to add custom metadata to the telemetry, as well as add filter out telemetry based on specific criteria. Whenever I spin up a new app, I always notice that I add a handful of extensions to the telemetry collection process and thought it would be helpful to share.&lt;/p&gt;</description></item></channel></rss>