You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/02/25 14:34:41 UTC

[GitHub] [skywalking] kezhenxu94 commented on a change in pull request #6446: Polish a log to doc and menu for latest status.

kezhenxu94 commented on a change in pull request #6446:
URL: https://github.com/apache/skywalking/pull/6446#discussion_r582879776



##########
File path: docs/en/concepts-and-designs/backend-overview.md
##########
@@ -1,34 +1,17 @@
 # Observability Analysis Platform
-OAP(Observability Analysis Platform) is a new concept, which starts in SkyWalking 6.x. OAP replaces the 
-old SkyWalking whole backend. The capabilities of the platform are following.
+We define SkyWalking as an Observability Analysis Platform, which provides a full observability to the services running
+either in brown zone, or green zone, even hybrid.
 
-## OAP capabilities
-OAP accepts data from more sources, which belongs two groups: **Tracing** and **Metrics**.
+## Capabilities
+SkyWalking covers all 3 fields of observability, including, **Tracing**, **Metrics** and **logging**.
 
 - **Tracing**. Including, SkyWalking native data formats. Zipkin v1,v2 data formats and Jaeger data formats.
 - **Metrics**. SkyWalking integrates with Service Mesh platforms, such as Istio, Envoy, Linkerd, to provide observability from data panel 
-or control panel. Also, SkyWalking native agents can run in metrics mode, which highly improve the 
-performance.
-
-At the same time by using any integration solution provided, such as SkyWalking log plugin or toolkits, 
-SkyWalking provides visualization integration for binding tracing and logging together by using the 
-trace id and span id.
-
-As usual, all services provided by gRPC and HTTP protocol to make integration easier for unsupported ecosystem.
-
-## Tracing in OAP
-Tracing in OAP has two ways to process.
-1. Traditional way in SkyWalking 5 series. Format tracing data in SkyWalking trace segment and span formats, 
-even for Zipkin data format. The OAP analysis the segments to get metrics, and push the metrics data into
-the streaming aggregation.
-1. Consider tracing as some kinds of logging only. Just provide save and visualization capabilities for trace. 
-
-Also, SkyWalking accepts trace formats from other project, such as Zipkin, Jaeger, OpenCensus.
-These formats could be processed in the two ways too.
-
-## Metrics in OAP
-Metrics in OAP is totally new feature in 6 series. Build observability for a distributed system based on metrics of connected nodes.
-No tracing data is required.
-
-Metrics data are aggregated inside OAP cluster in streaming mode. See about [Observability Analysis Language](oal.md),
-which provides the easy way to do aggregation and analysis in script style. 
\ No newline at end of file
+or control panel. Also, SkyWalking native agents can run in metrics mode, which highly improve the performance.
+- **Logging**. Including the logs collected from disk or through network. Native agent could bind the tracing context with logs automatically,
+or use SkyWalking to bind the trace and log through the text content.
+
+There are 3 powerful and native language engines to focus on analyzing observability data from above fields.
+1. [Observability Analysis Language](oal.md) processes the native traces and service mesh data.
+1. [Meter Analysis Language](mal.md) does metrics calculation for native meter data, and adopts stable and widely used metrics system, such as Prometheus and OpenTelemetry.
+1. [Log Analysis Language](lal.md) focuses on log contents and collaborate with Meter Analysis Language.

Review comment:
       ```suggestion
   1. [Log Analysis Language](lal.md) focuses on log contents and collaborates with Meter Analysis Language.
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org