{"id":1183,"date":"2014-05-23T15:13:00","date_gmt":"2014-05-23T15:13:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/05\/23\/quick-intellitrace-file-open-from-app-insights\/"},"modified":"2022-07-15T03:53:58","modified_gmt":"2022-07-15T11:53:58","slug":"quick-intellitrace-file-open-from-app-insights","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/quick-intellitrace-file-open-from-app-insights\/","title":{"rendered":"Quick IntelliTrace File Open from App Insights"},"content":{"rendered":"<p>As was introduced in the <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2013\/09\/20\/performance-details-in-intellitrace.aspx\">Details Page Feature Blog<\/a>, the IntelliTrace Performance Details Page\u00a0provides to the user thorough information as well as enhanced functionalities for previewing code and debugging.\u00a0This post will focus on specific IntelliTrace files that are opened from\u00a0<a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2013\/11\/13\/announcing-application-insights-preview.aspx\">Application Insights<\/a>\u00a0portal\u00a0and the user experience when single performance events are analyzed within Visual Studio.<\/p>\n<h2>Start at Details Page for Single Performance Event<\/h2>\n<p>When analyzing performance events through Application Insights online, the user has\u00a0the option of downloading data into a .itrace file to open in Visual Studio locally (for more information on logs, check out <a href=\"http:\/\/blogs.msdn.com\/b\/zainnab\/archive\/2013\/03\/05\/understanding-intellitrace-part-vi-working-with-intellitrace-logs.aspx\">Working with IntelliTrace Logs<\/a>).<\/p>\n<p>Prior to VS2013 Update 3, if the data analyzed in this way contains only 1 single performance event or violation &#8211; and no other exception\/test data, the\u00a0log would still show a summary page where the only option was for you to select that single event.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/8473.old20summary.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>The summary page above is now skipped when only 1 performance violation exists and no other data has been collected.\u00a0 Note that for all other logs which have more than 1 event,\u00a0the summary page default has not changed.<\/p>\n<p>With VS2013 Update 3, opening a log file with a single performance event takes you directly to the Details Page instead of the Summary Page. \u00a0This provides a more streamlined workflow and easier navigation.<\/p>\n<p>Below, we see the Details Page which is now the default page for analyzing single performance events:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/0488.new20landing.png\" alt=\"\" border=\"0\" \/><\/p>\n<h2>Details Page Functionality<\/h2>\n<p>On this enhanced Details page you will see all of the previous features and information as described in the <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2013\/09\/20\/performance-details-in-intellitrace.aspx\">Details Page Feature Blog<\/a>\u00a0post\u00a0but also some new aspects which you&#8217;d expect to see on a\u00a0summary page if there was one:<\/p>\n<ul>\n<li><strong>System**** Information<\/strong> \u2013 the system information previously available only on the summary page is now included in the Details subsection.<\/li>\n<li><strong>Single Event Indication<\/strong> \u2013\u201cThis is the only event in the IntelliTrace file\u201d specifies the default action.****<\/li>\n<li><strong>Information Bar<\/strong> \u2013 the yellow or \u201cgold bar\u201d that displays useful information to the user previously available only on the summary page now has the same functionality on the Details Page.\u00a0 This is mostly used for opening the corresponding solution when the .itrace file contains build information.<\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/7522.new20details20page.png\" alt=\"\" border=\"0\" \/><\/p>\n<p><strong>Other Features<\/strong> &#8211; all of the features that we have come to enjoy on our Details Page are available to us as well, including <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/02\/12\/intellitrace-mvc-navigation.aspx\">MVC Navigation<\/a>, <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/02\/10\/jump-to-sql-with-intellitrace.aspx\">Jump to SQL<\/a>, <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2014\/02\/11\/ui-enhancements-for-intellitrace-with-visual-studio-2013-update-2.aspx\">Performance Event Hot Path<\/a>, and of course the &#8216;Debug This Call&#8217; action.<\/p>\n<p>MVC Navigation:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/5125.mvc20navi.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>Jump to SQL and\u00a0Performance Event Hot Path:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/8244.j2sql.png\" alt=\"\" border=\"0\" \/><\/p>\n<h2>Showing Log and Opening Solution<\/h2>\n<p>Navigating in and out of the log file has also become easier.\u00a0 Going to the top toolbar and choosing <strong>Debug >****\u00a0IntelliTrace >****\u00a0\u201cShow Log File\u201d **will take the user to the appropriate summary or details page.\u00a0 If debugging has already started, the user can also click the **\u201cShow Log File\u201d<\/strong> button on the IntelliTrace Event Window.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/3201.show20log20file.png\" alt=\"\" border=\"0\" \/><\/p>\n<p>Lastly, opening a solution from the &#8220;gold bar&#8221; is now page specific &#8211; VS remembers what page you opened it from.\u00a0 The past action flow would always return the user to the summary page after opening the solution, in the process closing any and all detail pages that may have been opened prior.\u00a0 This behavior has now been revamped to return the user to the page that the solution was opened from, whether that was the summary or details page.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2014\/05\/5224.return20220page.png\" alt=\"\" border=\"0\" \/><\/p>\n<h2>In Closing<\/h2>\n<p>For expanded scenarios and usage information refer to <span style=\"text-decoration: underline\"><a title=\"MSDN\" href=\"http:\/\/msdn.microsoft.com\/en-US\/\">MSDN<\/a><\/span><\/p>\n<p>We are always looking for feedback and comments for our features. Please visit the <a href=\"http:\/\/social.msdn.microsoft.com\/Forums\/en-US\/vsdebug\/threads\">MSDN Diagnostics\u00a0forum<\/a><\/p>\n<div>\n  \u00a0\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>As was introduced in the Details Page Feature Blog, the IntelliTrace Performance Details Page\u00a0provides to the user thorough information as well as enhanced functionalities for previewing code and debugging.\u00a0This post will focus on specific IntelliTrace files that are opened from\u00a0Application Insights\u00a0portal\u00a0and the user experience when single performance events are analyzed within Visual Studio. Start at [&hellip;]<\/p>\n","protected":false},"author":148,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[226,1,225],"tags":[],"class_list":["post-1183","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ci","category-devops","category-git"],"acf":[],"blog_post_summary":"<p>As was introduced in the Details Page Feature Blog, the IntelliTrace Performance Details Page\u00a0provides to the user thorough information as well as enhanced functionalities for previewing code and debugging.\u00a0This post will focus on specific IntelliTrace files that are opened from\u00a0Application Insights\u00a0portal\u00a0and the user experience when single performance events are analyzed within Visual Studio. Start at [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/1183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/148"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=1183"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/1183\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=1183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=1183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=1183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}