[incubator-skywalking] branch oap-languages updated: Replace ingress back to endpoint

[wu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch oap-languages
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git


The following commit(s) were added to refs/heads/oap-languages by this push:
     new 9e53dec  Replace ingress back to endpoint
9e53dec is described below

commit 9e53dec6b9d8e9b69d0b0479124f7bc87bdb5b1f
Author: Wu Sheng <wu...@foxmail.com>
AuthorDate: Thu Jul 5 11:04:59 2018 -0700

    Replace ingress back to endpoint
---
 docs/en/OAP/README.md | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/docs/en/OAP/README.md b/docs/en/OAP/README.md
index fbcb77b..9f3c1cc 100644
--- a/docs/en/OAP/README.md
+++ b/docs/en/OAP/README.md
@@ -34,7 +34,7 @@ which provides the easy way to do aggregation and analysis in script style.
 ### Observability Analysis Language
 Provide OAL(Observability Analysis Language) to analysis incoming data in streaming mode. 
 
-OAL focuses on metric in Service, Service Instance and Ingress. Because of that, the language is easy to 
+OAL focuses on metric in Service, Service Instance and Endpoint. Because of that, the language is easy to 
 learn and use.
 
 Considering performance, reading and debugging, OAL is defined as a compile language. 
@@ -50,7 +50,7 @@ METRIC_NAME = from(SCOPE.(* | [FIELD][,FIELD ...]))
 ```
 
 #### Scope
-**SCOPE** in (`All`, `Service`, `ServiceInst`, `Ingress`, `ServiceRelation`, `ServiceInstRelation`, `IngressRelation`).
+**SCOPE** in (`All`, `Service`, `ServiceInst`, `Endpoint`, `ServiceRelation`, `ServiceInstRelation`, `EndpointRelation`).
 
 #### Field
 TODO
@@ -73,34 +73,34 @@ The metric name for storage implementor, alarm and query modules. The type infer
 #### Group
 All metric data will be grouped by Scope.ID and min-level TimeBucket. 
 
-- In `Ingress` scope, the Scope.ID = Ingress id (the unique id based on service and its ingress)
+- In `Endpoint` scope, the Scope.ID = Endpoint id (the unique id based on service and its Endpoint)
 
 #### Examples
 ```
-// Caculate p99 of both Ingress1 and Ingress2
-Ingress_p99 = from(Ingress.latency).filter(name in ("Ingress1", "Ingress2")).summary(0.99)
+// Caculate p99 of both Endpoint1 and Endpoint2
+Endpoint_p99 = from(Endpoint.latency).filter(name in ("Endpoint1", "Endpoint2")).summary(0.99)
 
-// Caculate p99 of Ingress name started with `serv`
-serv_Ingress_p99 = from(Ingress.latency).filter(name like ("serv%")).summary(0.99)
+// Caculate p99 of Endpoint name started with `serv`
+serv_Endpoint_p99 = from(Endpoint.latency).filter(name like ("serv%")).summary(0.99)
 
-// Caculate the avg response time of each Ingress
-Ingress_avg = from(Ingress.latency).avg()
+// Caculate the avg response time of each Endpoint
+Endpoint_avg = from(Endpoint.latency).avg()
 
-// Caculate the histogram of each Ingress by 50 ms steps.
+// Caculate the histogram of each Endpoint by 50 ms steps.
 // Always thermodynamic diagram in UI matches this metric. 
-Ingress_histogram = from(Ingress.latency).histogram(50)
+Endpoint_histogram = from(Endpoint.latency).histogram(50)
 
 // Caculate the percent of response status is true, for each service.
-Ingress_success = from(Ingress.*).filter(status = "true").percent()
+Endpoint_success = from(Endpoint.*).filter(status = "true").percent()
 
 // Caculate the percent of response code in [200, 299], for each service.
-Ingress_200 = from(Ingress.*).filter(responseCode like "2%").percent()
+Endpoint_200 = from(Endpoint.*).filter(responseCode like "2%").percent()
 
 // Caculate the percent of response code in [500, 599], for each service.
-Ingress_500 = from(Ingress.*).filter(responseCode like "5%").percent()
+Endpoint_500 = from(Endpoint.*).filter(responseCode like "5%").percent()
 
 // Caculate the sum of calls for each service.
-IngressCalls = from(Ingress.*).sum()
+EndpointCalls = from(Endpoint.*).sum()
 ```
 
 ## Query in OAP
@@ -130,10 +130,10 @@ Metric.Scope(SCOPE).Func(METRIC_NAME [, PARAM ...])
 ```
 
 #### Scope
-**SCOPE** in (`All`, `Service`, `ServiceInst`, `Ingress`, `ServiceRelation`, `ServiceInstRelation`, `IngressRelation`).
+**SCOPE** in (`All`, `Service`, `ServiceInst`, `Endpoint`, `ServiceRelation`, `ServiceInstRelation`, `EndpointRelation`).
 
 #### Metric name
-Metric name is defined in oal script. Such as **IngressCalls** is the name defined by `IngressCalls = from(Ingress.*).sum()`.
+Metric name is defined in oal script. Such as **EndpointCalls** is the name defined by `EndpointCalls = from(Endpoint.*).sum()`.
 
 #### Metric Query Function
 Metric Query Functions match the Aggregation Function in most cases, but include some order or filter features.