a few more fixes

Author: SergeyKanzhelev

content/posts/2014-12-01-telemetry-initializers.markdown

@@ -4,7 +4,6 @@ title: "Telemetry Initializers"
 date: 2014-12-01 21:07:47 -0800
 comments: true
 aliases: [/blog/2014/12/01/telemetry-initializers/]
-published: true
 categories: 
 ---
 Application Insights .NET SDK has number of extensibility points. One of them is called telemetry initializer. Telemetry initializer is a class implementing ITelemetryInitializer interface. The only method of this interface "Initialize" is called whenever a TraceFoo method is called for one of telemetry data items (Event, Metric, Request, Exception, etc.).

content/posts/2014-12-02-tracking-static-content-with-application-insights-httpmodule.markdown

@@ -4,7 +4,6 @@ title: "tracking static content with Application Insights HttpModule"
 date: 2014-12-02 12:01:01 -0800
 comments: true
 aliases: [/blog/2014/12/02/tracking-static-content-with-application-insights-httpmodule/]
-published: true
 categories: 
 - Application Insights
 ---

content/posts/2015-01-02-integrated-this-blog-with-twitter.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "Integrated this blog with twitter"
 date: 2015-01-02 21:44:37 -0800
 comments: true
-aliases: [/blog/2015-01-02-integrated-this-blog-with-twitter/]
+aliases: [/blog/2015/01/02/integrated-this-blog-with-twitter/]
 categories:
 - setup 
 ---

content/posts/2015-01-05-track-dependencies-in-console-application.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "track dependencies in console application"
 date: 2015-01-05 20:28:50 +0200
 comments: true
-aliases: [/blog/2015-01-05-track-dependencies-in-console-application/]
+aliases: [/blog/2015/01/05/track-dependencies-in-console-application/]
 categories: 
 - Application Insights
 ---

content/posts/2015-02-02-collecting-performance-counters.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "Collecting performance counters"
 date: 2015-02-02 08:18:47 -0800
 comments: true
-aliases: [/blog/2015-02-02-collecting-performance-counters/]
+aliases: [/blog/2015/02/02/collecting-performance-counters/]
 published: false
 categories: 
 ---

content/posts/2015-02-02-developer-mode.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "Developer Mode"
 date: 2015-02-02 08:54:58 -0800
 comments: true
-aliases: [/blog/2015-02-02-developer-mode/]
+aliases: [/blog/2015/02/02/developer-mode/]
 categories: 
 - Application Insights
 - troubleshooting

content/posts/2015-02-06-more-on-applicationinsights-dot-config.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "More on ApplicationInsights.config"
 date: 2015-02-06 09:04:12 -0800
 comments: true
-aliases: [/blog/2015-02-06-more-on-applicationinsights-dot-config/]
+aliases: [/blog/2015/02/06/more-on-applicationinsights-dot-config/]
 categories:
 - Application Insights 
 ---

content/posts/2015-02-23-request-name-and-url.markdown

@@ -3,7 +3,7 @@ layout: post
 title: "Request name and url"
 date: 2015-02-23 09:08:55 -0800
 comments: true
-aliases: [/blog/2015-02-23-request-name-and-url/]
+aliases: [/blog/2015/02/23/request-name-and-url/]
 categories:
 - Application Insights
 ---

content/posts/2018-09-26-filtering-bad-sampling-good.markdown

@@ -150,7 +150,7 @@ about all slow outgoing calls. You may also discover that while browsing Azure
 portal in many cases you will see examples of slow incoming requests with both -
 slow and fast requests collected.
 
-![](../images/2018-09-26-filtering-bad-sampling-good/suggested-slow-request.png)
+![](/images/2018-09-26-filtering-bad-sampling-good/suggested-slow-request.png)
 
 The reason for this is that adaptive sampling is using probability sampling
 algorithm to decide on sampling decision. If sampling score is lower than 20% -
@@ -162,7 +162,7 @@ interesting to analyze. This is why you will get many useful samples
 with all the details. When you scroll down or randomly will open examples - you
 will see many of them with slow dependency only collected.
 
-![](../images/2018-09-26-filtering-bad-sampling-good/other-slow-request.png)
+![](/images/2018-09-26-filtering-bad-sampling-good/other-slow-request.png)
 
 In a given conditions all collected fast requests will have the details on all
 the fast dependency calls. Again, browsing those may be useful.
@@ -185,7 +185,7 @@ calls that used to take 10 ms will start taking 200 ms - this change will be
 visible on chart even on 5% of telemetry. And it will likely be caught by smart
 detectors of Application Insights.
 
-![](../images/2018-09-26-filtering-bad-sampling-good/count-gained-up.png)
+![](/images/2018-09-26-filtering-bad-sampling-good/count-gained-up.png)
 
 Latency problems caused by multiple calls to the fast dependent service will be
 caught - there probably be examples of those in the collected 5%.