add zipkin's local picture
diff --git a/_posts/cn/2019-01-23-customized-tracing-with-servicecomb.md b/_posts/cn/2019-01-23-customized-tracing-with-servicecomb.md
old mode 100644
new mode 100755
index 9f8702b..d37e0a5
--- a/_posts/cn/2019-01-23-customized-tracing-with-servicecomb.md
+++ b/_posts/cn/2019-01-23-customized-tracing-with-servicecomb.md
@@ -66,8 +66,8 @@
 ## 快速演示
 下面使用java-chassis/samples/bmi 程序演示,如何使用自定义追踪功能定位应用程序中的问题?
 1. 正常运行bmi程序,结果如下
-    ![正常结果](https://img-blog.csdnimg.cn/20190122101706113.png)
-    ![zipkin追踪正常情况](https://img-blog.csdnimg.cn/20190122101505915.png)
+    ![正常结果](../../assets/images/zipkin/demo-bmi-run.png)
+	![zipkin正常追踪结果](../../assets/images/zipkin/zipkin-track-bmi.png)
 2. 在bmi程序的calculator服务的calculate方法处,增加一块进程休眠代码(模拟实际工作中调用当前线程处理其他业务的情景),如下
 	```java
 	public double calculate(double height, double weight) {
@@ -88,12 +88,12 @@
 
 	```
 3. 运行bmi程序,出现如下异常结果。查看zipkin追踪情况和程序报错信息,可以初步确定问题由 bmi/calculator 服务超时未响应导致
-    ![异常结果](https://img-blog.csdnimg.cn/20190121193215681.png)     	
-    ![zipkin追踪情况](https://img-blog.csdnimg.cn/20190121195130561.png)
-    ![程序报错信息](https://img-blog.csdnimg.cn/20190122093001881.png)
+    ![异常结果](../../assets/images/zipkin/demo-bmi-run-error.png)     	
+    ![zipkin追踪情况](../../assets/images/zipkin/zipkin-track-bmi-error.png)
+    ![程序报错信息](../../assets/images/zipkin/error-message.png)
 4. 使用自定义追踪功能,定位问题具体位置
 	在calculator服务中配置自定义追踪功能,添加注解 `@Span`在calculator服务的方法上 。运行bmi程序,zipkin追踪耗时情况如下。根据span占用的时间戳,可以确定延时问题出现在calculate方法处,点击span,可查看call.path 获取calculate方法的具体位置。
-	![zipkin追踪异常情况](https://img-blog.csdnimg.cn/20190121200305278.png)
-	![span信息信息](https://img-blog.csdnimg.cn/20190121200411404.png)
+	![zipkin追踪异常情况](../../assets/images/zipkin/zipkin-customized-track-bmi.png)
+	![span信息信息](../../assets/images/zipkin/zipkin-track-span.png)
 ## 总结
 从上面的示例可以看出,通过配置ServiceComb的自定义追踪功能,可以实现对服务中调用方法、接口的追踪,实现更细力度化的追踪。这对于我们监控服务内部调用、定位服务中的延时问题等非常有帮助。
diff --git a/assets/images/zipkin/demo-bmi-run-error.png b/assets/images/zipkin/demo-bmi-run-error.png
new file mode 100755
index 0000000..3055c90
--- /dev/null
+++ b/assets/images/zipkin/demo-bmi-run-error.png
Binary files differ
diff --git a/assets/images/zipkin/demo-bmi-run.png b/assets/images/zipkin/demo-bmi-run.png
new file mode 100755
index 0000000..9a5ef2a
--- /dev/null
+++ b/assets/images/zipkin/demo-bmi-run.png
Binary files differ
diff --git a/assets/images/zipkin/error-message.png b/assets/images/zipkin/error-message.png
new file mode 100755
index 0000000..3d8c5bb
--- /dev/null
+++ b/assets/images/zipkin/error-message.png
Binary files differ
diff --git a/assets/images/zipkin/zipkin-customized-track-bmi.png b/assets/images/zipkin/zipkin-customized-track-bmi.png
new file mode 100755
index 0000000..ca9c09a
--- /dev/null
+++ b/assets/images/zipkin/zipkin-customized-track-bmi.png
Binary files differ
diff --git a/assets/images/zipkin/zipkin-track-bmi-error.png b/assets/images/zipkin/zipkin-track-bmi-error.png
new file mode 100755
index 0000000..56d7dc9
--- /dev/null
+++ b/assets/images/zipkin/zipkin-track-bmi-error.png
Binary files differ
diff --git a/assets/images/zipkin/zipkin-track-bmi.png b/assets/images/zipkin/zipkin-track-bmi.png
new file mode 100755
index 0000000..2d57945
--- /dev/null
+++ b/assets/images/zipkin/zipkin-track-bmi.png
Binary files differ
diff --git a/assets/images/zipkin/zipkin-track-span.png b/assets/images/zipkin/zipkin-track-span.png
new file mode 100755
index 0000000..30038f5
--- /dev/null
+++ b/assets/images/zipkin/zipkin-track-span.png
Binary files differ