[incubator-servicecomb-service-center] branch master updated: Update the description of Service-Center in Readme (#323)

2018-04-07 Thread littlecui
This is an automated email from the ASF dual-hosted git repository.

littlecui pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-service-center.git


The following commit(s) were added to refs/heads/master by this push:
 new d201bd3  Update the description of Service-Center in Readme (#323)
d201bd3 is described below

commit d201bd3c98b91813621f7ddc447801380fb575f5
Author: Mohammad Asif Siddiqui 
AuthorDate: Sun Apr 8 07:48:17 2018 +0530

Update the description of Service-Center in Readme (#323)
---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0db90ca..09315a4 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,8 @@
 # Apache-Incubator-ServiceComb-Service-Center 
 [![Build 
Status](https://www.travis-ci.org/apache/incubator-servicecomb-service-center.svg?branch=master)](https://www.travis-ci.org/apache/incubator-servicecomb-service-center)
  [![Coverage 
Status](https://coveralls.io/repos/github/apache/incubator-servicecomb-service-center/badge.svg?branch=master)](https://coveralls.io/github/apache/incubator-servicecomb-service-center?branch=master)
  [![Go Report 
Card](https://goreportcard.com/badge/github.com/apache/incubator-servicecomb-service-cen
 [...]
 
-Apache ServiceComb (incubating) service-center allows services to register 
their instance information and to discover providers of a given service. 
+Apache ServiceComb (incubating) Service-Center is a Restful based 
service-registry that provides micro-services discovery and micro-service 
management. It is based on Open API format and provides features like 
service-discovery, fault-tolerance, dynamic routing, notify subscription and 
scalable by design. It has high performance cache design and separate entity 
management for micro-services and their instances. It provides out of box 
support for metrics and tracing. It has a web portal t [...]
+
 ## Features
  - **Open API**: API doc(Open API format) management for microservice
  - **Metadata**: Metadata management for both microservice and microservice 
instance

-- 
To stop receiving notification emails like this one, please contact
little...@apache.org.


[incubator-servicecomb-website] branch asf-site updated (2464a75 -> 33072f9)

2018-04-07 Thread ningjiang
This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 2464a75  Publish the website
 add cded6ae  fix style
 add f77cc47  fix style
 new 11372f0  Merge branch 'master' into asf-site
 new 33072f9  Publish the website

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _users/cn/metrics-in-1.0.0-m1.md   | 24 ++-
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  2 +
 _users/edge-in-1.0.0-m1.md |  2 +-
 _users/metrics-in-1.0.0-m1.md  | 24 +++
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  7 +++-
 content/cn/users/metrics-in-1.0.0-m1/index.html| 46 +++--
 .../index.html | 10 +++--
 content/feed.xml   |  2 +-
 content/sitemap.xml|  2 +-
 content/users/edge-in-1.0.0-m1/index.html  |  2 +-
 content/users/metrics-in-1.0.0-m1/index.html   | 48 --
 .../index.html | 15 ---
 12 files changed, 105 insertions(+), 79 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.


[incubator-servicecomb-website] 01/02: Merge branch 'master' into asf-site

2018-04-07 Thread ningjiang
This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 11372f04f577375ebf2b2d790dbf267ffd06
Merge: 2464a75 f77cc47
Author: Willem Jiang 
AuthorDate: Sat Apr 7 22:09:07 2018 +0800

Merge branch 'master' into asf-site

 _users/cn/metrics-in-1.0.0-m1.md   | 24 +-
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  2 ++
 _users/edge-in-1.0.0-m1.md |  2 +-
 _users/metrics-in-1.0.0-m1.md  | 24 ++
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  7 +--
 5 files changed, 37 insertions(+), 22 deletions(-)

diff --cc _users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
index 315ba99,63fc23b..d0fbfef
mode 100755,100644..100755
--- a/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
+++ b/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.


[incubator-servicecomb-website] 02/02: fix style

2018-04-07 Thread ningjiang
This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit f77cc474bd06b77ed8bc419e88b49d0f858c043d
Author: zhengyangyong 
AuthorDate: Wed Apr 4 17:11:15 2018 +0800

fix style

Signed-off-by: zhengyangyong 
---
 _users/cn/metrics-in-1.0.0-m1.md | 4 ++--
 _users/metrics-in-1.0.0-m1.md| 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/_users/cn/metrics-in-1.0.0-m1.md b/_users/cn/metrics-in-1.0.0-m1.md
index 124cf97..dcbbf1e 100644
--- a/_users/cn/metrics-in-1.0.0-m1.md
+++ b/_users/cn/metrics-in-1.0.0-m1.md
@@ -253,7 +253,7 @@ public class OrderController {
 
 注意事项: 
  
-1. 
通过MonitorManager获取Monitor传递name和tag数组,最终输出的ID是它们连接后的字符串,所以请保持唯一性,上面的例子输出的Metrics为:
+1.通过MonitorManager获取Monitor传递name和tag数组,最终输出的ID是它们连接后的字符串,所以请保持唯一性,上面的例子输出的Metrics为:
 
 ```java
 Map metrics = MonitorManager.getInstance().measure();
@@ -265,7 +265,7 @@ Map metrics = 
MonitorManager.getInstance().measure();
 // 生成订单(统计项=最大生成时间,单位=MILLISECONDS)
 ```
 
-2. MonitorManager获取Monitor的方法均为**获取或创建**,因此多次传递相同的name和tag数组返回的是同一个计数器:
+2.MonitorManager获取Monitor的方法均为**获取或创建**,因此多次传递相同的name和tag数组返回的是同一个计数器:
 
 ```java
 Counter counter1 = MonitorManager.getInstance().getCounter("订单数量", "商品名", 
"levis jeans", "型号", "512");
diff --git a/_users/metrics-in-1.0.0-m1.md b/_users/metrics-in-1.0.0-m1.md
index 16af428..f591706 100644
--- a/_users/metrics-in-1.0.0-m1.md
+++ b/_users/metrics-in-1.0.0-m1.md
@@ -254,7 +254,7 @@ public class OrderController {
 
 Notice:
 
-1. Metric ID is join name and all tags that pass to MonitorManager when 
getting monitor,so please keep uniqueness,metrics output of front example are:
+1.Metric ID is join name and all tags that pass to MonitorManager when getting 
monitor,so please keep uniqueness,metrics output of front example are:
 
 ```java
 Map metrics = MonitorManager.getInstance().measure();
@@ -266,7 +266,7 @@ Map metrics = 
MonitorManager.getInstance().measure();
 // orderGenerated(statistic=max,unit=MILLISECONDS)
 ```
 
-2. All get monitor method in MonitorManager act as **get or new**,so use same 
name and tags will return same one monitor:
+2.All get monitor method in MonitorManager act as **get or new**,so use same 
name and tags will return same one monitor:
 
 ```java
 Counter counter1 = MonitorManager.getInstance().getCounter("orderGenerated", 
"product", "levis jeans", "model", "512");

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.


[incubator-servicecomb-website] branch master updated (da90d48 -> f77cc47)

2018-04-07 Thread ningjiang
This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from da90d48  add edge en doc
 new cded6ae  fix style
 new f77cc47  fix style

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _users/cn/metrics-in-1.0.0-m1.md   | 24 +-
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  2 ++
 _users/edge-in-1.0.0-m1.md |  2 +-
 _users/metrics-in-1.0.0-m1.md  | 24 ++
 ...rics-integration-with-prometheus-in-1.0.0-m1.md |  7 +--
 5 files changed, 37 insertions(+), 22 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.


[incubator-servicecomb-website] 01/02: fix style

2018-04-07 Thread ningjiang
This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit cded6aef8bd30c207e66cdf7c33ca831e25d5c6e
Author: zhengyangyong 
AuthorDate: Wed Apr 4 16:14:18 2018 +0800

fix style

Signed-off-by: zhengyangyong 
---
 _users/cn/metrics-in-1.0.0-m1.md | 20 
 ...etrics-integration-with-prometheus-in-1.0.0-m1.md |  2 ++
 _users/edge-in-1.0.0-m1.md   |  2 +-
 _users/metrics-in-1.0.0-m1.md| 20 +---
 ...etrics-integration-with-prometheus-in-1.0.0-m1.md |  7 +--
 5 files changed, 33 insertions(+), 18 deletions(-)

diff --git a/_users/cn/metrics-in-1.0.0-m1.md b/_users/cn/metrics-in-1.0.0-m1.md
index bd08c41..124cf97 100644
--- a/_users/cn/metrics-in-1.0.0-m1.md
+++ b/_users/cn/metrics-in-1.0.0-m1.md
@@ -251,8 +251,10 @@ public class OrderController {
 }
 ```
 
-注意事项:  
+注意事项: 
+ 
 1. 
通过MonitorManager获取Monitor传递name和tag数组,最终输出的ID是它们连接后的字符串,所以请保持唯一性,上面的例子输出的Metrics为:
+
 ```java
 Map metrics = MonitorManager.getInstance().measure();
 
@@ -264,17 +266,19 @@ Map metrics = 
MonitorManager.getInstance().measure();
 ```
 
 2. MonitorManager获取Monitor的方法均为**获取或创建**,因此多次传递相同的name和tag数组返回的是同一个计数器:
+
 ```java
-Counter counter1 = MonitorManager.getInstance().getCounter("订单数量", "商品名", 
"levis jeans", "型号", "512");
-Counter counter2 = MonitorManager.getInstance().getCounter("订单数量", "商品名", 
"levis jeans", "型号", "512");
+Counter counter1 = MonitorManager.getInstance().getCounter("订单数量", "商品名", 
"levis jeans", "型号", "512");
+Counter counter2 = MonitorManager.getInstance().getCounter("订单数量", "商品名", 
"levis jeans", "型号", "512");
 
-counter1.increment();
-counter2.increment();
+counter1.increment();
+counter2.increment();
 
-Assert.assertEquals(2,counter1.getValue());
-Assert.assertEquals(2,counter2.getValue());
-
Assert.assertEquals(2.0,MonitorManager.getInstance().measure().get("订单数量(商品名=levis
 jeans,型号=512)"),0);
+Assert.assertEquals(2,counter1.getValue());
+Assert.assertEquals(2,counter2.getValue());
+Assert.assertEquals(2.0,MonitorManager.getInstance().measure().get("订单数量(商品名=levis
 jeans,型号=512)"),0);
 ```
+
 **获取Monitor的方法性能较低,请在初始化阶段一次获取所需的Monitor,然后将它们缓存起来,请参照前面OrderController的做法。**
 
 **提示:Servo已经被Netflix标记为DEPRECATED,我们将在1.0.0-m2中使用Netflix 
spectator替换,扩展自定义Metrics的方式会有调整**
diff --git a/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md 
b/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
index b5100dc..63fc23b 100644
--- a/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
+++ b/_users/cn/metrics-integration-with-prometheus-in-1.0.0-m1.md
@@ -87,6 +87,7 @@ scrape_configs:
 
 ### 验证输出
 Prometheus Simple HTTP 
Server使用/metrics作为默认URL,metrics-prometheus会使用9696作为默认端口,微服务启动后你可以使用http://localhost:9696/metrics
 访问它。
+
 使用Prometheus Simple HTTP Server接口发布的数据是Prometheus采集的标准格式:
 ```text
 # HELP ServiceComb Metrics ServiceComb Metrics
@@ -114,6 +115,7 @@ 
servicecomb_invocation_calculator_calculatorRestEndpoint_calculate{role="produce
 
如何在Grafana中添加Prometheus作为数据源请参考[这篇文章](https://prometheus.io/docs/visualization/grafana/)。
 ## 运行效果
 配置好Prometheus并启动了微服务之后,就可以打开Prometheus Web界面(默认地址是http://localhost:9090/ 
),在Metrics列表中看到ServiceComb开头的Java Chassis Metrics,如下图所示:
+
 ![MetricsInPrometheus](/assets/images/MetricsInPrometheus.png)  
 
 为了能够达到更好的查询效果,在Grafana中添加Prometheus作为数据源,通过Grafana查询数据如下图示:
diff --git a/_users/edge-in-1.0.0-m1.md b/_users/edge-in-1.0.0-m1.md
index 4bd689a..7429f56 100644
--- a/_users/edge-in-1.0.0-m1.md
+++ b/_users/edge-in-1.0.0-m1.md
@@ -92,7 +92,7 @@ Edge Service use SPI(Service Provider Interface) to load 
custom VertxHttpDispatc
 Edge Service always use to provide monitoring, resiliency, security, and more, 
not only dynamic routing. We recommend extend custom handlers, there is an 
example named AuthHandler in demo-edge.
 
 ## Other Reference
-In demo/demo-edge we had provided a simple demo to show abilities of Edge 
Service:
+In demo/demo-edge we had provided a simple demo to show abilities of Edge 
Service:
 1. edge-service:Edge Service, include AuthHandler;
 2. authentication:Simulate authentication, accept requests from AuthHandler;
 3. business-x.x.x:Simulate multi-version business instances;
diff --git a/_users/metrics-in-1.0.0-m1.md b/_users/metrics-in-1.0.0-m1.md
index f46d845..16af428 100644
--- a/_users/metrics-in-1.0.0-m1.md
+++ b/_users/metrics-in-1.0.0-m1.md
@@ -200,6 +200,7 @@ Metrics data will output as Map,in order to 
let user easier fetch
 //get K3=30 Metric from node
 
node.getChildrenNode("1").getChildrenNode("20").getFirstMatchMetricValue("K3","30");
 ```
+
 *More detail can be found in demo/perf/PerfMetricsFilePublisher.java*
 
 ## How to Extend Custom Metrics
@@