')`: Transforms less-based histogram buckets to meter system histogram buckets.
+`le` parameter represents the tag name of the bucket.
+
+**Note** In SkyWalking, the histogram buckets are based on time and will be transformed to the `milliseconds-based`
+histogram buckets in the meter system. (If the metrics from the Prometheus are based on the `seconds-based` histogram
+buckets, will multiply the bucket value by 1000.)
+
+#### histogram_percentile
+`histogram_percentile([])`: Represents the meter-system to calculate the p-percentile (0 ≤ p ≤ 100) from the buckets.
+
+#### time
+`time()`: Returns the number of seconds since January 1, 1970 UTC.
+
+#### foreach
+`forEach([string_array], Closure each)`: Iterates all samples according to the first array argument, and provide two parameters in the second closure argument:
+1. `element`: element in the array.
+2. `tags`: tags in each sample.
+
+## Down Sampling Operation
+MAL should instruct meter-system on how to downsample for metrics. It doesn't only refer to aggregate raw samples to
+`minute` level, but also expresses data from `minute` in higher levels, such as `hour` and `day`.
+
+Down sampling function is called `downsampling` in MAL, and it accepts the following types:
+
+ - AVG
+ - SUM
+ - LATEST
+ - SUM_PER_MIN
+ - MIN
+ - MAX
+ - MEAN (TODO)
+ - COUNT (TODO)
+
+The default type is `AVG`.
+
+If users want to get the latest time from `last_server_state_sync_time_in_seconds`:
+
+```
+last_server_state_sync_time_in_seconds.tagEqual('production', 'catalog').downsampling(LATEST)
+```
+
+## Metric level function
+
+They extract level relevant labels from metric labels, then informs the meter-system the level and [layer](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/Layer.java) to which this metric belongs.
+
+ - `service([svc_label1, svc_label2...], Layer)` extracts service level labels from the array argument, extracts layer from `Layer` argument.
+ - `instance([svc_label1, svc_label2...], [ins_label1, ins_label2...], Layer, Closure> propertiesExtractor)` extracts service level labels from the first array argument,
+ extracts instance level labels from the second array argument, extracts layer from `Layer` argument, `propertiesExtractor` is an optional closure that extracts instance properties from `tags`, e.g. `{ tags -> ['pod': tags.pod, 'namespace': tags.namespace] }`.
+ - `endpoint([svc_label1, svc_label2...], [ep_label1, ep_label2...])` extracts service level labels from the first array argument,
+ extracts endpoint level labels from the second array argument, extracts layer from `Layer` argument.
+ - `process([svc_label1, svc_label2...], [ins_label1, ins_label2...], [ps_label1, ps_label2...], layer_lable)` extracts service level labels from the first array argument,
+ extracts instance level labels from the second array argument, extracts process level labels from the third array argument, extracts layer label from fourse argument.
+ - `serviceRelation(DetectPoint, [source_svc_label1...], [dest_svc_label1...], Layer)` DetectPoint including `DetectPoint.CLIENT` and `DetectPoint.SERVER`,
+ extracts `sourceService` labels from the first array argument, extracts `destService` labels from the second array argument, extracts layer from `Layer` argument.
+ - `processRelation(detect_point_label, [service_label1...], [instance_label1...], source_process_id_label, dest_process_id_label, component_label)` extracts `DetectPoint` labels from first argument, the label value should be `client` or `server`.
+ extracts `Service` labels from the first array argument, extracts `Instance` labels from the second array argument, extracts `ProcessID` labels from the fourth and fifth arguments of the source and destination.
+
+## Decorate function
+`decorate({ me -> me.attr0 = ...})`: Decorate the [MeterEntity](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/meter/MeterEntity.java) with additional attributes.
+The closure takes the MeterEntity as an argument. This function is used to add additional attributes to the metrics. More details, see [Metrics Additional Attributes](metrics-additional-attributes.md).
+
+## Configuration file
+
+The OAP can load the configuration at bootstrap. If the new configuration is not well-formed, the OAP fails to start up. The files
+are located at `$CLASSPATH/otel-rules`, `$CLASSPATH/meter-analyzer-config`, `$CLASSPATH/envoy-metrics-rules` and `$CLASSPATH/zabbix-rules`.
+
+The file is written in YAML format, defined by the scheme described below. Brackets indicate that a parameter is optional.
+
+A full example can be found [here](../../../oap-server/server-starter/src/main/resources/otel-rules/oap.yaml)
+
+Generic placeholders are defined as follows:
+
+* ``: A regular string.
+* ``: A closure with custom logic.
+
+```yaml
+# initExp is the expression that initializes the current configuration file
+initExp:
+# filter the metrics, only those metrics that satisfy this condition will be passed into the `metricsRules` below.
+filter: # example: '{ tags -> tags.job_name == "vm-monitoring" }'
+# expPrefix is executed before the metrics executes other functions.
+expPrefix:
+# expSuffix is appended to all expression in this file.
+expSuffix:
+# insert metricPrefix into metric name: _
+metricPrefix:
+# Metrics rule allow you to recompute queries.
+metricsRules:
+ [ - ]
+```
+
+###
+
+```yaml
+# The name of rule, which combinates with a prefix 'meter_' as the index/table name in storage.
+name:
+# MAL expression.
+exp:
+```
+
+## More Examples
+
+Please refer to [OAP Self-Observability](../../../oap-server/server-starter/src/main/resources/otel-rules/oap.yaml).
diff --git a/docs/en/concepts-and-designs/manual-sdk.md b/docs/en/concepts-and-designs/manual-sdk.md
new file mode 100644
index 000000000000..b9bc16002b78
--- /dev/null
+++ b/docs/en/concepts-and-designs/manual-sdk.md
@@ -0,0 +1,15 @@
+# Manual instrument SDK
+Our incredible community has contributed to the manual instrument SDK.
+- [Rust](https://github.com/apache/skywalking-rust). Rust SDK follows the SkyWalking format.
+- [C++](https://github.com/SkyAPM/cpp2sky). C++ SDK follows the SkyWalking format.
+
+Below is the archived list.
+- [Go2Sky](https://github.com/SkyAPM/go2sky). Since Jun 14, 2023.
+
+## What are the SkyWalking format and the propagation protocols?
+- [Tracing APIs](../api/trace-data-protocol-v3.md)
+- [Meter APIs](../api/meter.md)
+- [Logging APIs](../api/log-data-protocol.md)
+
+## Envoy tracer
+Envoy has its internal tracer implementation for SkyWalking. Read [SkyWalking Tracer doc](https://www.envoyproxy.io/docs/envoy/v1.19.1/api-v3/config/trace/v3/skywalking.proto.html?highlight=skywalking) and [SkyWalking tracing sandbox](https://www.envoyproxy.io/docs/envoy/v1.19.1/start/sandboxes/skywalking_tracing?highlight=skywalking) for more details.
diff --git a/docs/en/concepts-and-designs/metrics-additional-attributes.md b/docs/en/concepts-and-designs/metrics-additional-attributes.md
new file mode 100644
index 000000000000..460d2e6c018e
--- /dev/null
+++ b/docs/en/concepts-and-designs/metrics-additional-attributes.md
@@ -0,0 +1,61 @@
+# Metrics Additional Attributes
+SkyWalking provides [OAL](oal.md) and [MAL](mal.md) to analyze the data source and generate the metrics.
+Generally, the metrics fields in the storage include `name`, `entity_id`, `service_id` `value` and `timebucket` etc.
+In most cases, these fields are enough to query a metric. However, sometimes we need to add more fields to the metrics to make the query more flexible.
+A typical case is the `topN` query, when we query the top N services by the metric value.
+If we want to filter the services by `Layer` or `Group` or other specific conditions, it is impossible to do this with the current metrics fields.
+
+Since 10.2.0, SkyWalking supports the metrics attributes through source decorate.
+SkyWalking provides additional attributes(`attr0...attr5`) fields to the metrics and source.
+By default, these fields are empty, we can fill them by set a specific decorate logic for source.
+According to the difference between the `OAL` and `MAL`, the usage of decorate is different.
+
+**Notice:** For now, the metrics attributes only support the `service metrics` and `non-labeled` metrics.
+
+## OAL Source Decorate
+In the OAL script, you can use the [decorator](oal.md#decorator) function to specify a Java Class to decorate the source,
+and the Java Class must follow the following rules:
+- The Class must implement the [ISourceDecorator](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/ISourceDecorator.java) interface.
+- The Class package must be under the `org.apache.skywalking.*`.
+
+### Default Decorator
+SkyWalking provides some default implementation of decorator:
+
+- [ServiceDecorator](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/source/ServiceDecorator.java) which set the `attr0` to the service `Layer`.
+The following OAL metrics had been decorated by the `ServiceDecorator` by default:
+```text
+// Service scope metrics
+service_resp_time = from(Service.latency).longAvg().decorator("ServiceDecorator");
+service_sla = from(Service.*).percent(status == true).decorator("ServiceDecorator");
+service_cpm = from(Service.*).cpm().decorator("ServiceDecorator");
+service_apdex = from(Service.latency).apdex(name, status).decorator("ServiceDecorator");
+```
+
+- [EndpointDecorator](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/source/EndpointDecorator.java) which set the `attr0` to the endpoint `Layer`.
+The following OAL metrics had been decorated by the `EndpointDecorator` by default:
+```text
+endpoint_cpm = from(Endpoint.*).cpm().decorator("EndpointDecorator");
+endpoint_resp_time = from(Endpoint.latency).longAvg().decorator("EndpointDecorator");
+endpoint_sla = from(Endpoint.*).percent(status == true).decorator("EndpointDecorator");
+```
+
+- [K8SServiceDecorator](../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/source/K8SServiceDecorator.java) which set the `attr0` to the k8s service `Layer`.
+The following OAL metrics had been decorated by the `K8SServiceDecorator` by default:
+```text
+kubernetes_service_http_call_cpm = from(K8SService.*).filter(detectPoint == DetectPoint.SERVER).filter(type == "protocol").filter(protocol.type == "http").cpm().decorator("K8SServiceDecorator");
+kubernetes_service_http_call_time = from(K8SService.protocol.http.latency).filter(detectPoint == DetectPoint.SERVER).filter(type == "protocol").filter(protocol.type == "http").longAvg().decorator("K8SServiceDecorator");
+kubernetes_service_http_call_successful_rate = from(K8SService.*).filter(detectPoint == DetectPoint.SERVER).filter(type == "protocol").filter(protocol.type == "http").percent(protocol.success == true).decorator("K8SServiceDecorator");
+kubernetes_service_apdex = from(K8SService.protocol.http.latency).filter(detectPoint == DetectPoint.SERVER).filter(type == "protocol").filter(protocol.type == "http").apdex(name, protocol.success).decorator("K8SServiceDecorator");
+```
+
+## MAL Source Decorate
+In the MAL script, you can use the [decorate](mal.md#decorate-function) function to decorate the source, and must follow the following rules:
+- The decorate function must after service() function.
+- Not supported for histogram metrics.
+- Not supported for labeled metrics.
+
+SkyWalking does not provide a default script for MAL, you can refer to the following example to set the `attr0` to the service `Layer`:
+```text
+ - name: cpu_load1
+ exp: (node_load1 * 100).service(['node_identifier_host_name'] , Layer.OS_LINUX).decorate({ me -> me.attr0 = me.layer.name()})
+```
diff --git a/docs/en/concepts-and-designs/oal.md b/docs/en/concepts-and-designs/oal.md
new file mode 100644
index 000000000000..13ea3f8d4ce5
--- /dev/null
+++ b/docs/en/concepts-and-designs/oal.md
@@ -0,0 +1,196 @@
+# Analysis Native Streaming Traces and Service Mesh Traffic
+
+The traces in SkyWalking native format and Service Mesh Traffic(Access Log in gRPC) are able to be analyzed by OAL,
+to build metrics of services, service instances and endpoints, and to build topology/dependency of services, service
+instances and endpoints(traces-oriented analysis only).
+
+The spans of traces relative with RPC, such as HTTP, gRPC, Dubbo, RocketMQ, Kafka, would be converted to service input/output
+traffic, like access logs collected from service mesh. Both of those traffic would be cataloged as the defined sources
+in the `Observability Analysis Language` engine.
+
+The metrics are customizable through Observability Analysis Language(OAL) scripts,
+and the topology/dependency is built by the SkyWalking OAP kernel automatically without
+explicit OAL scripts.
+
+# Observability Analysis Language
+OAL(Observability Analysis Language) serves to analyze incoming data in streaming mode.
+
+OAL focuses on metrics in Service, Service Instance and Endpoint. Therefore, the language is easy to
+learn and use.
+
+OAL scripts are now found in the `/config` folder, and users could simply change and reboot the server to run them.
+However, the OAL script is a compiled language, and the OAL Runtime generates java codes dynamically. Don't expect to mount
+the changes of those scripts in the runtime.
+If your OAP servers are running in a cluster mode, these script defined metrics should be aligned.
+
+You can open set `SW_OAL_ENGINE_DEBUG=Y` at system env to see which classes are generated.
+
+## Grammar
+Scripts should be named `*.oal`
+```
+// Declare the metrics.
+METRICS_NAME = from(CAST SCOPE.(* | [FIELD][,FIELD ...]))
+[.filter(CAST FIELD OP [INT | STRING])]
+.FUNCTION([PARAM][, PARAM ...])
+
+// Disable hard code
+disable(METRICS_NAME);
+```
+
+## From
+The **from** statement defines the data source of this OAL expression.
+
+Primary **SCOPE**s are `Service`, `ServiceInstance`, `Endpoint`, `ServiceRelation`, `ServiceInstanceRelation`, and `EndpointRelation`.
+There are also some secondary scopes which belong to a primary scope.
+
+See [Scope Definitions](scope-definitions.md), where you can find all existing Scopes and Fields.
+
+
+## Filter
+Use filter to build conditions for the value of fields by using field name and expression.
+
+The filter expressions run as a chain, generally connected with `logic AND`.
+The OPs support `==`, `!=`, `>`, `<`, `>=`, `<=`, `in [...]` ,`like %...`, `like ...%` , `like %...%` , `contain` and `not contain`, with type detection based on field type. In the event of incompatibility, compile or code generation errors may be triggered.
+
+## Aggregation Function
+The default functions are provided by the SkyWalking OAP core, and it is possible to implement additional functions.
+
+Functions provided
+- `longAvg`. The avg of all input per scope entity. The input field must be a long.
+> instance_jvm_memory_max = from(ServiceInstanceJVMMemory.max).longAvg();
+
+In this case, the input represents the request of each ServiceInstanceJVMMemory scope, and avg is based on field `max`.
+- `doubleAvg`. The avg of all input per scope entity. The input field must be a double.
+> instance_jvm_cpu = from(ServiceInstanceJVMCPU.usePercent).doubleAvg();
+
+In this case, the input represents the request of each ServiceInstanceJVMCPU scope, and avg is based on field `usePercent`.
+- `percent`. The number or ratio is expressed as a fraction of 100, where the input matches with the condition.
+> endpoint_percent = from(Endpoint.*).percent(status == true);
+
+In this case, all input represents requests of each endpoint, and the condition is `endpoint.status == true`.
+- `rate`. The rate expressed is as a fraction of 100, where the input matches with the condition.
+> browser_app_error_rate = from(BrowserAppTraffic.*).rate(trafficCategory == BrowserAppTrafficCategory.FIRST_ERROR, trafficCategory == BrowserAppTrafficCategory.NORMAL);
+
+In this case, all input represents requests of each browser app traffic, the `numerator` condition is `trafficCategory == BrowserAppTrafficCategory.FIRST_ERROR` and `denominator` condition is `trafficCategory == BrowserAppTrafficCategory.NORMAL`.
+Parameter (1) is the `numerator` condition.
+Parameter (2) is the `denominator` condition.
+- `count`. The sum of calls per scope entity.
+> service_calls_sum = from(Service.*).count();
+
+In this case, the number of calls of each service.
+
+- `histogram`. See [Heatmap in WIKI](https://en.wikipedia.org/wiki/Heat_map).
+> service_heatmap = from(Service.latency).histogram(100, 20);
+
+In this case, the thermodynamic heatmap of all incoming requests.
+Parameter (1) is the precision of latency calculation, such as in the above case, where 113ms and 193ms are considered the same in the 101-200ms group.
+Parameter (2) is the group amount. In the above case, 21(param value + 1) groups are 0-100ms, 101-200ms, ... 1901-2000ms, 2000+ms
+
+- `apdex`. See [Apdex in WIKI](https://en.wikipedia.org/wiki/Apdex).
+> service_apdex = from(Service.latency).apdex(name, status);
+
+In this case, the apdex score of each service.
+Parameter (1) is the service name, which reflects the Apdex threshold value loaded from service-apdex-threshold.yml in the config folder.
+Parameter (2) is the status of this request. The status(success/failure) reflects the Apdex calculation.
+
+- `p99`, `p95`, `p90`, `p75`, `p50`. See [percentile in WIKI](https://en.wikipedia.org/wiki/Percentile).
+> service_percentile = from(Service.latency).percentile2(10);
+
+**percentile (deprecated since 10.0.0)** is the first multiple-value metric, which has been introduced since 7.0.0. As a metric with multiple values, it could be queried through the `getMultipleLinearIntValues` GraphQL query.
+**percentile2** Since 10.0.0, the `percentile` function has been instead by `percentile2`. The `percentile2` function is a labeled-value metric with default label name `p` and label values `50`,`75`,`90`,`95`,`99`.
+In this case, see `p99`, `p95`, `p90`, `p75`, and `p50` of all incoming requests. The parameter is precise to a latency at p99, such as in the above case, and 120ms and 124ms are considered to produce the same response time.
+
+In this case, the p99 value of all incoming requests. The parameter is precise to a latency at p99, such as in the above case, and 120ms and 124ms are considered to produce the same response time.
+
+- `labelCount`. The count of the label value.
+> drop_reason_count = from(CiliumService.*).filter(verdict == "dropped").labelCount(dropReason, 100);
+
+In this case, the count of the drop reason of each Cilium service, max support calculate `100` reasons(optional configuration).
+
+- `labelAvg`. The avg of the label value.
+> drop_reason_avg = from(BrowserResourcePerf.*).labelAvg(name, duration, 100);
+
+In this case, the avg of the duration of each browser resource file, max support calculate `100` resource file(optional configuration).
+
+## Metrics name
+The metrics name for storage implementor, alarm and query modules. The type inference is supported by core.
+
+## Group
+All metrics data will be grouped by Scope.ID and min-level TimeBucket.
+
+- In the `Endpoint` scope, the Scope.ID is same as the Endpoint ID (i.e. the unique ID based on service and its endpoint).
+
+## Cast
+Fields of source are static type. In some cases, the type required by the filter expression and aggregation function doesn't
+match the type in the source, such as tag value in the source is String type, most aggregation calculation requires numeric.
+
+Cast expression is provided to do so.
+- `(str->long)` or `(long)`, cast string type into long.
+- `(str->int)` or `(int)`, cast string type into int.
+
+```
+mq_consume_latency = from((str->long)Service.tag["transmission.latency"]).longAvg(); // the value of tag is string type.
+```
+
+Cast statement is supported in
+1. **From statement**. `from((cast)source.attre)`.
+2. **Filter expression**. `.filter((cast)tag["transmission.latency"] > 0)`
+3. **Aggregation function parameter**. `.longAvg((cast)strField1== 1, (cast)strField2)`
+
+## Decorator
+`decorator` is to select a specific decorator to decorate the source for the metrics.
+> service_resp_time = from(Service.latency).longAvg().decorator("ServiceDecorator");
+
+In this case, the `ServiceDecorator` is the `Java Class simple name` which used to decorate the source of `Service` before the aggregation function.
+This function is used to add additional attributes to the metrics. More details, see [Metrics Additional Attributes](metrics-additional-attributes.md).
+
+## Disable
+`Disable` is an advanced statement in OAL, which is only used in certain cases.
+Some of the aggregation and metrics are defined through core hard codes. Examples include `segment` and `top_n_database_statement`.
+This `disable` statement is designed to render them inactive.
+By default, none of them are disabled.
+
+**NOTICE**, all disable statements should be in `oal/disable.oal` script file.
+
+## Examples
+```
+// Calculate p99 of both Endpoint1 and Endpoint2
+endpoint_p99 = from(Endpoint.latency).filter(name in ("Endpoint1", "Endpoint2")).summary(0.99)
+
+// Calculate p99 of Endpoint name started with `serv`
+serv_Endpoint_p99 = from(Endpoint.latency).filter(name like "serv%").summary(0.99)
+
+// Calculate the avg response time of each Endpoint
+endpoint_resp_time = from(Endpoint.latency).avg()
+
+// Calculate the p50, p75, p90, p95 and p99 of each Endpoint by 50 ms steps.
+endpoint_percentile = from(Endpoint.latency).percentile2(10)
+
+// Calculate the percent of response status is true, for each service.
+endpoint_success = from(Endpoint.*).filter(status == true).percent()
+
+// Calculate the sum of response code in [404, 500, 503], for each service.
+endpoint_abnormal = from(Endpoint.*).filter(httpResponseStatusCode in [404, 500, 503]).count()
+
+// Calculate the sum of request type in [RequestType.RPC, RequestType.gRPC], for each service.
+endpoint_rpc_calls_sum = from(Endpoint.*).filter(type in [RequestType.RPC, RequestType.gRPC]).count()
+
+// Calculate the sum of endpoint name in ["/v1", "/v2"], for each service.
+endpoint_url_sum = from(Endpoint.*).filter(name in ["/v1", "/v2"]).count()
+
+// Calculate the sum of calls for each service.
+endpoint_calls = from(Endpoint.*).count()
+
+// Calculate the CPM with the GET method for each service.The value is made up with `tagKey:tagValue`.
+// Option 1, use `tags contain`.
+service_cpm_http_get = from(Service.*).filter(tags contain "http.method:GET").cpm()
+// Option 2, use `tag[key]`.
+service_cpm_http_get = from(Service.*).filter(tag["http.method"] == "GET").cpm();
+
+// Calculate the CPM with the HTTP method except for the GET method for each service.The value is made up with `tagKey:tagValue`.
+service_cpm_http_other = from(Service.*).filter(tags not contain "http.method:GET").cpm()
+
+disable(segment);
+disable(endpoint_relation_server_side);
+disable(top_n_database_statement);
+```
diff --git a/docs/en/concepts-and-designs/overview.md b/docs/en/concepts-and-designs/overview.md
new file mode 100644
index 000000000000..59ba7cee023d
--- /dev/null
+++ b/docs/en/concepts-and-designs/overview.md
@@ -0,0 +1,66 @@
+# Overview
+SkyWalking is an open source observability platform used to collect, analyze, aggregate and visualize data from services and cloud native
+infrastructures. SkyWalking provides an easy way to maintain a clear view of your distributed systems, even across Clouds.
+It is a modern APM, specially designed for cloud native, container based distributed systems.
+
+SkyWalking covers all the observability needs in Cloud Native world, including:
+- **Tracing**. SkyWalking native data formats, and Zipkin traces of v1 and v2 formats are supported.
+- **Metrics**. SkyWalking supports mature metrics formats, including native meter format, OTEL metrics format, and Telegraf format.
+ SkyWalking integrates with Service Mesh platforms, typically Istio and Envoy, to build observability into the data plane
+ or control plane. Also, SkyWalking native agents can run in the metrics mode, which greatly improves performances.
+- **Logging**. Includes logs collected from disk or through network. Native agents could bind the tracing context with logs automatically,
+ or use SkyWalking to bind the trace and log through the text content.
+- **Profiling**. Profiling is a powerful tool to help developers understand the performance of their applications from lines of codes perspective.
+ SkyWalking provides profiling feature bundled in native language agents and independent ebpf agents.
+- **Event**. Event is a special kind of data, which is used to record the important moments in the system, such as version upgrade, configuration change, etc.
+ Linking the events with metrics could help on explain the peaks or valleys in the metrics, and linking the events with traces and logs could help on troubleshooting root cause.
+
+## Why use SkyWalking?
+SkyWalking provides solutions for observing and monitoring distributed systems, in many different scenarios. First of all,
+like traditional approaches, SkyWalking provides auto instrument agents for services, such as Java, C#, Node.js, Go, PHP and Python,
+and manually SDKs for C++, Rust, and Nginx LUA.
+In multi-language, continuously deployed environments, cloud native infrastructures grow more powerful but also more complex.
+SkyWalking's service mesh receiver allows SkyWalking to receive telemetry data from service mesh frameworks
+such as Istio/Envoy, allowing users to understand the entire distributed system. Powered by eBPF stack, SkyWalking provides
+k8s monitoring.
+Also, by adopting OpenTelemetry, Telegraf, Zabbix, Zipkin, Prometheus, SkyWalking can integrate with other distributed tracing, metrics and logging systems
+and build a unified APM system to host all data.
+
+Besides the support of various kinds of telemetry formats, the hierarchy structure of objects in SkyWalking is defined as
+**service**(s), **service instance**(s), **endpoint**(s), **process**(s). The terms Service,
+Instance and Endpoint are used everywhere today, so it is worth defining their specific meanings in the context of SkyWalking:
+
+- **Layer**. A **layer** represents an abstract framework in computer science, such as Operating System(OS_LINUX layer),
+ and Kubernetes(k8s layer). A layer is an abstract collection of services. A service typically only belongs to one layer,
+ but in some scenarios, a service could belong to multiple layers. For example, a service could be deployed in an Istio service mesh,
+ it could belong to mesh and mesh-dp(mesh data plane) layer.
+- **Service**. Represents a set/group of workloads which provide the same behaviours for incoming requests. You can define the service
+ name when you are using instrument agents or SDKs. SkyWalking can also use the name you define in platforms such as Istio.
+- **Service Instance**. Each individual workload in the Service group is known as an instance. Like `pods` in Kubernetes, it
+ doesn't need to be a single OS process, however, if you are using instrument agents, an instance is actually a real OS process.
+- **Endpoint**. A path in a service for incoming requests, such as an HTTP URI path or a gRPC service class + method signature.
+- **Process**. An operating system process. In some scenarios, a Service Instance is
+ not a process, such as a pod Kubernetes could contain multiple processes.
+
+SkyWalking allows users to understand the topology relationship between Services and Endpoints, also detect API dependencies
+in the distributed environment if you use our native agents.,
+
+Besides topology map, SkyWalking provides [**Service Hierarchy Relationship**](service-hierarchy.md) , which defines the relationships of existing
+logically same services in various layers. For example, a service could be deployed in a Kubernetes cluster with Istio mesh,
+services are detected by k8s monitoring and Istio mesh, this hierarchy relationship could connect the services in k8s layer and mesh layer.
+
+## Architecture
+SkyWalking is logically split into four parts: Probes, Platform backend, Storage and UI.
+
+
+
+- **Probe**s collect telemetry data, including metrics, traces, logs and events in various formats(SkyWalking, Zipkin, OpenTelemetry, Prometheus, Zabbix, etc.)
+- **Platform backend** supports data aggregation, analysis and streaming process covers traces, metrics, logs and events. Work as Aggregator Role, Receiver Role or both.
+- **Storage** houses SkyWalking data through an open/plugable interface. You can choose an existing implementation, such as
+ ElasticSearch, H2, MySQL, TiDB, BanyanDB, or implement your own.
+- **UI** is a highly customizable web based interface allowing SkyWalking end users to visualize and manage SkyWalking data.
+
+
+## What is next?
+- Learn SkyWalking's [Project Goals](project-goals.md)
+- FAQ, [Why doesn't SkyWalking involve MQ in the architecture in default?](../FAQ/why_mq_not_involved.md)
diff --git a/docs/en/concepts-and-designs/probe-introduction.md b/docs/en/concepts-and-designs/probe-introduction.md
new file mode 100644
index 000000000000..9407fd909f0d
--- /dev/null
+++ b/docs/en/concepts-and-designs/probe-introduction.md
@@ -0,0 +1,53 @@
+# Probe Introduction
+
+In SkyWalking, probe means an agent or SDK library integrated into a target system that takes charge of collecting
+telemetry data, including tracing and metrics. Depending on the target system tech stack, there are very different ways
+how the probe performs such tasks. But ultimately, they all work towards the same goal — to collect and reformat data,
+and then to send them to the backend.
+
+On a high level, there are four typical categories in all SkyWalking probes.
+
+- **Language based native agent**. These agents run in target service user spaces, such as a part of user codes. For
+ example, the SkyWalking Java agent uses the `-javaagent` command line argument to manipulate codes in runtime,
+ where `manipulate` means to change and inject user's codes. Another example is SkyWalking agent, which leverage Golang
+ compiling mechanism to weaves codes in the compiling time. For some static compilation languages, such as C++, manual
+ library is the only choice.
+ As you can see, these agents are based on languages and libraries, no matter we provide auto instrument or manual agents.
+
+- **Service Mesh probes**. Service Mesh probes collect data from sidecar, control plane in service mesh or proxy. In the
+ old days, proxy is only used as an ingress of the whole cluster, but with the Service Mesh and sidecar, we can now
+ perform observability functions.
+
+- **3rd-party instrument library**. SkyWalking accepts many widely used instrument libraries data formats.
+ SkyWalking community is connected closely with Zipkin community, it could work as an alternative server for both v1 and
+ v2 Zipkin traces. Also, OTEL trace format in gRPC is supported, and converted to Zipkin format inside SkyWalking.
+ As an alternative Zipkin server, Zipkin lens UI could be used to visualize accepted traces when they are in Zipkin format.
+ See [Receiver for Zipkin traces](../setup/backend/zipkin-trace.md) and [Receiver for OTEL traces](../setup/backend/otlp-trace.md) for more information.
+
+- **eBPF agent**. The eBPF agent collects metrics and profiling the target service powered by the eBPF technology of Linux kernel.
+
+You don't have to install all probes to make SkyWalking up and running.
+There are several recommended ways on how to use these probes:
+
+1. Use **Language based native agent** only to build topology and metrics for your business application.
+1. Use **3rd-party instrument library** only, like the Zipkin instrument ecosystem.
+1. Use **Service Mesh probe** if you prefer Service Mesh stack and don't want to use native agents.
+1. Use **Service Mesh probe** with **Language based native agent** or **3rd-party instrument library** in pure tracing
+ status. (Advanced usage)
+1. Use **eBPF agent** only if you only want to profile on demand and/or activating automatic performance analysis.
+1. Use **eBPF agent** with **Language based native agent** collaboratively. Enhance the traces with the eBPF agent to collect extra information.
+
+What is the meaning of **in tracing status**?
+
+By default, **Language based native agent** and **3rd-party instrument library** both send distributed traces to the
+backend, where analyses and aggregation on those traces are performed. **In pure tracing status** means that the backend
+considers these traces as something like logs. In other words, the backend saves them, but doesn't run the metrics analysis from
+traces. As a result, there would not have data of `service/instance/endpoint metrics and relationships`.
+
+## What is next?
+
+- Learn more about the probes supported by SkyWalking in [Service auto instrument agent](service-agent.md)
+ , [Manual instrument SDK](manual-sdk.md) and [Zipkin receiver](../setup/backend/zipkin-trace.md).
+- After understanding how the probe works, see the [backend overview](backend-overview.md) for more on analysis and
+ persistence.
+
diff --git a/docs/en/concepts-and-designs/profiling.md b/docs/en/concepts-and-designs/profiling.md
new file mode 100644
index 000000000000..5c1ae91e9603
--- /dev/null
+++ b/docs/en/concepts-and-designs/profiling.md
@@ -0,0 +1,121 @@
+# Profiling
+
+The profiling is an on-demand diagnosing method to locate bottleneck of the services.
+These typical scenarios usually are suitable for profiling through various profiling tools
+
+1. Some methods slow down the API performance.
+2. Too many threads and/or high-frequency I/O per OS process reduce the CPU efficiency.
+3. Massive RPC requests block the network to cause responding slowly.
+4. Unexpected network requests caused by security issues or codes' bug.
+
+In the SkyWalking landscape, we provided three ways to support profiling within reasonable resource cost.
+
+1. In-process profiling is bundled with auto-instrument agents.
+2. Out-of-process profiling is powered by eBPF agent.
+3. Continuous profiling is powered by eBPF agent.
+
+## In-process profiling
+
+In-process profiling is primarily provided by auto-instrument agents in the VM-based runtime.
+
+### Tracing Profiling
+This feature resolves the issue <1> through capture the snapshot of the thread stacks periodically.
+The OAP would aggregate the thread stack per RPC request, and provide a hierarchy graph to indicate the slow methods
+based
+on continuous snapshot.
+
+The period is usually every 10-100 milliseconds, which is not recommended to be less, due to this capture would usually
+cause classical stop-the-world for the VM, which would impact the whole process performance.
+
+Learn more tech details from the post, [**Use Profiling to Fix the Blind Spot of Distributed
+Tracing**](sdk-profiling.md).
+
+For now, Java and Python agents support this.
+
+### Java App Profiling
+
+Java App Profiling uses the [AsyncProfiler](https://github.com/async-profiler/async-profiler) for sampling
+
+Async Profiler is a low overhead sampling profiler for Java that does not suffer from Safepoint bias problem. It features HotSpot-specific APIs to collect stack traces and to track memory allocations. The profiler works with OpenJDK and other Java runtimes based on the HotSpot JVM.
+
+Async Profiler can trace the following kinds of events:
+
+- CPU cycles
+- Allocations in Java Heap
+- Contented lock attempts, including both Java object monitors and ReentrantLocks
+- and [more](https://github.com/async-profiler/async-profiler/blob/master/docs/ProfilingModes.md)
+
+Only Java agent support this.
+
+## Out-of-process profiling
+
+Out-of-process profiling leverage [eBPF](https://ebpf.io/) technology with origins in the Linux kernel.
+It provides a way to extend the capabilities of the kernel safely and efficiently.
+
+### On-CPU Profiling
+
+On-CPU profiling is suitable for analyzing thread stacks when service CPU usage is high.
+If the stack is dumped more times, it means that the thread stack occupies more CPU resources.
+
+This is pretty similar with in-process profiling to resolve the issue <1>, but it is made out-of-process and based on
+Linux eBPF.
+Meanwhile, this is made for languages without VM mechanism, which caused not supported by in-process agents, such as,
+C/C++, Rust. Golang is a special case, it exposed the metadata of the VM for eBPF, so, it could be profiled.
+
+### Off-CPU Profiling
+
+Off-CPU profiling is suitable for performance issues that are not caused by high CPU usage, but may be on high CPU load.
+This profiling aims to resolve the issue <2>.
+
+For example,
+
+1. When there are too many threads in one service, using off-CPU profiling could reveal which threads spend
+ more time context switching.
+2. Codes heavily rely on disk I/O or remote service performance would slow down the whole process.
+
+Off-CPU profiling provides two perspectives
+
+1. Thread switch count: The number of times a thread switches context. When the thread returns to the CPU, it completes
+ one context switch. A thread stack with a higher switch count spends more time context switching.
+2. Thread switch duration: The time it takes a thread to switch the context. A thread stack with a higher switch
+ duration spends more time off-CPU.
+
+Learn more tech details about ON/OFF CPU profiling from the post, [**Pinpoint Service Mesh Critical Performance Impact
+by using eBPF**](ebpf-cpu-profiling.md)
+
+### Network Profiling
+
+Network profiling captures the network packages to analysis traffic at L4(TCP) and L7(HTTP) to recognize network traffic
+from a specific process or a k8s pod. Through this traffic analysis, locate the root causes of the issues <3> and <4>.
+
+Network profiling provides
+
+1. Network topology and identify processes.
+2. Observe TCP traffic metrics with TLS status.
+3. Observe HTTP traffic metrics.
+4. Sample HTTP request/response raw data within tracing context.
+5. Observe time costs for local I/O costing on the OS. Such as the time of Linux process HTTP request/response.
+
+Learn more tech details from the post, [**Diagnose Service Mesh Network Performance with
+eBPF**](../academy/diagnose-service-mesh-network-performance-with-ebpf.md)
+
+## Continuous Profiling
+
+Continuous Profiling utilizes monitoring of system, processes, and network,
+and automatically initiates profiling tasks when conditions meet the configured thresholds and time windows.
+
+### Monitor type
+
+Continuous profiling periodically collects the following types of performance metrics for processes and systems:
+1. System Load: Monitor current system load value.
+2. Process CPU: Monitor process CPU usage percent, value in [0-100].
+3. Process Thread Count: Monitor process thread count.
+4. HTTP Error Rate: Monitor the process HTTP(/1.x) response error(response status >= 500) percent, value in [0-100].
+5. HTTP Avg Response Time: Monitor the process HTTP(/1.x) response duration(ms).
+
+### Trigger Target
+
+When the collected metric data matches the configured threshold, the following types of profiling tasks could be triggered:
+1. On CPU Profiling: Perform eBPF On CPU Profiling on processes that meet the threshold.
+2. Off CPU Profiling: Perform eBPF Off CPU Profiling on processes that meet the threshold.
+3. Network Profiling: Perform eBPF Network Profiling on all processes within the same instance as the processes that meet the threshold.
diff --git a/docs/en/concepts-and-designs/project-goals.md b/docs/en/concepts-and-designs/project-goals.md
new file mode 100644
index 000000000000..51baa5f55003
--- /dev/null
+++ b/docs/en/concepts-and-designs/project-goals.md
@@ -0,0 +1,36 @@
+# Design Goals
+This document outlines the core design goals for the SkyWalking project.
+
+- **Maintaining Observability**. Regardless of the deployment method of the target system, SkyWalking provides an integration solution for it to maintain observability. Based on this, SkyWalking provides multiple runtime forms and probes.
+
+- **Topology, Metrics and Trace Together**. The first step to understanding a distributed system is the topology map. It visualizes the entire complex system in an easy-to-read layout. Under the topology, the OSS personnel have higher requirements in terms of the metrics for service, instance, endpoint and calls. Traces are in the form of detailed logs to make sense of those metrics.
+For example, when the endpoint latency becomes long, you want to see the slowest the trace to find out why. So you can see,
+they are from big picture to details, they are all needed. SkyWalking integrates and provides a lot of features to
+make this possible and easy understand.
+
+- **Light Weight**. There two parts of light weight are needed. (1) In probe, we just depend on network
+communication framework, prefer gRPC. By that, the probe should be as small as possible, to avoid the library
+conflicts and the payload of VM, such as permsize requirement in JVM.
+(2) As an observability platform, it is secondary and third level system in your project environment.
+So we are using our own light weight framework to build the backend core. Then you don't need to
+deploy big data tech platform and maintain them. SkyWalking should be simple in tech stack.
+
+- **Pluggable**. SkyWalking core team provides many default implementations, but definitely it is not enough,
+and also don't fit every scenario. So, we provide a lot of features for being pluggable.
+
+- **Portability**. SkyWalking can run in multiple environments, including:
+(1) Use traditional register center like eureka.
+(2) Use RPC framework including service discovery, like Spring Cloud, Apache Dubbo.
+(3) Use Service Mesh in modern infrastructure.
+(4) Use cloud services.
+(5) Across cloud deployment.
+SkyWalking should run well in all of these cases.
+
+- **Interoperability**. The observability landscape is so vast that it is virtually impossible for SkyWalking to support all systems, even with the support of its community.
+Currently, it supports interoperability with other OSS systems, especially probes, such as Zipkin, Jaeger, and OpenTelemetry.
+It is very important to end users that SkyWalking has the ability to accept and read these data formats, since the users are not required to switch their libraries.
+
+
+## What is next?
+- See [probe Introduction](probe-introduction.md) to learn about SkyWalking's probe groups.
+- From [backend overview](backend-overview.md), you can understand what the backend does after it receives probe data.
diff --git a/docs/en/concepts-and-designs/scope-definitions.md b/docs/en/concepts-and-designs/scope-definitions.md
new file mode 100644
index 000000000000..a2f269e7110f
--- /dev/null
+++ b/docs/en/concepts-and-designs/scope-definitions.md
@@ -0,0 +1,658 @@
+# Scopes and Fields
+
+Using the Aggregation Function, the requests will be grouped by time and **Group Key(s)** in each scope.
+
+### SCOPE `Service`
+
+This calculates the metrics data from each request of the service.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| name | The name of the service. | | string |
+| layer | Layer represents an abstract framework in the computer science, such as operation system(OS_LINUX layer), Kubernetes(k8s layer) | | enum |
+| serviceInstanceName | The name of the service instance ID. | | string |
+| endpointName | The name of the endpoint, such as a full path of HTTP URI. | | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request. Such as: Database, HTTP, RPC, gRPC. | | enum |
+| tags | The labels of each request. Each value is made up by `TagKey:TagValue` in the segment. | | `List` |
+| tag | The key-value pair of span tags in the segment. | | `Map` |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+
+### SCOPE `TCPService`
+
+This calculates the metrics data from each request of the TCP service.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------|-----------------------|
+| name | The name of the service. | | string |
+| layer | Layer represents an abstract framework in the computer science, such as operation system(OS_LINUX layer), Kubernetes(k8s layer) | | enum |
+| serviceInstanceName | The name of the service instance ID. | | string |
+| tags | The labels of each request. Each value is made up by `TagKey:TagValue` in the segment. | | `List` |
+| tag | The key-value pair of span tags in the segment. | | `Map` |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+| receivedBytes | The received bytes of the TCP traffic. | | long |
+| sentBytes | The sent bytes of the TCP traffic. | | long |
+
+### SCOPE `ServiceInstance`
+
+This calculates the metrics data from each request of the service instance.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| endpointName | The name of the endpoint, such as a full path of the HTTP URI. | | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| tags | The labels of each request. Each value is made up by `TagKey:TagValue` in the segment. | | `List` |
+| tag | The key-value pair of span tags in the segment. | | `Map` |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+
+### SCOPE `TCPServiceInstance`
+
+This calculates the metrics data from each request of the service instance.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------------------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| tags | The labels of each request. Each value is made up by `TagKey:TagValue` in the segment. | | `List` |
+| tag | The key-value pair of span tags in the segment. | | `Map` |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+| receivedBytes | The received bytes of the TCP traffic. | | long |
+| sentBytes | The sent bytes of the TCP traffic. | | long |
+
+#### Secondary scopes of `ServiceInstance`
+
+This calculates the metrics data if the service instance is a JVM and collects through javaagent.
+
+1. SCOPE `ServiceInstanceJVMCPU`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| usePercent | The percentage of CPU time spent. | | double |
+
+2. SCOPE `ServiceInstanceJVMMemory`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| heapStatus | Indicates whether the metric has a heap property or not. | | bool |
+| init | See the JVM documentation. | | long |
+| max | See the JVM documentation. | | long |
+| used | See the JVM documentation. | | long |
+| committed | See the JVM documentation. | | long |
+
+3. SCOPE `ServiceInstanceJVMMemoryPool`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| poolType | The type may be CODE_CACHE_USAGE, NEWGEN_USAGE, OLDGEN_USAGE, SURVIVOR_USAGE, PERMGEN_USAGE, or METASPACE_USAGE based on different versions of JVM. | | enum |
+| init | See the JVM documentation. | | long |
+| max | See the JVM documentation. | | long |
+| used | See the JVM documentation. | | long |
+| committed | See the JVM documentation. | | long |
+
+4. SCOPE `ServiceInstanceJVMGC`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| phase | Includes both NEW and OLD. | | Enum |
+| time | The time spent in GC. | | long |
+| count | The count in GC operations. | | long |
+
+5. SCOPE `ServiceInstanceJVMThread`
+
+| Name | Remarks | Group Key | Type |
+|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| liveCount | The current number of live threads. | | long |
+| daemonCount | The current number of daemon threads. | | long |
+| peakCount | The current number of peak threads. | | long |
+| runnableStateThreadCount | The current number of threads in runnable state. | | long |
+| blockedStateThreadCount | The current number of threads in blocked state. | | long |
+| waitingStateThreadCount | The current number of threads in waiting state. | | long |
+| timedWaitingStateThreadCount | The current number of threads in time-waiting state. | | long |
+
+6. SCOPE `ServiceInstanceJVMClass`
+
+| Name | Remarks | Group Key | Type |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| name | The name of the service instance, such as `ip:port@Service Name`. **Note**: Currently, the native agent uses `uuid@ipv4` as the instance name, which does not assist in setting up a filter in aggregation. | | string |
+| serviceName | The name of the service. | | string |
+| loadedClassCount | The number of classes that are currently loaded in the JVM. | | long |
+| totalUnloadedClassCount | The total number of classes unloaded since the JVM has started execution. | | long |
+| totalLoadedClassCount | The total number of classes that have been loaded since the JVM has started execution. | | long |
+
+### SCOPE `Endpoint`
+
+This calculates the metrics data from each request of the endpoint in the service.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|-----------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| name | The name of the endpoint, such as a full path of the HTTP URI. | | string |
+| serviceName | The name of the service. | | string |
+| serviceNodeType | The type of node to which the Service or Network address belongs, such as Normal, Database, MQ, or Cache. | | enum |
+| serviceInstanceName | The name of the service instance ID. | | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| tags | The labels of each request. Each value is made up by `TagKey:TagValue` in the segment. | | `List` |
+| tag | The key-value pair of span tags in the segment. | | `Map` |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+
+### SCOPE `ServiceRelation`
+
+This calculates the metrics data from each request between services.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| sourceServiceName | The name of the source service. | | string |
+| sourceServiceInstanceName | The name of the source service instance. | | string |
+| sourceLayer | The layer of the source service. | | enum |
+| destServiceName | The name of the destination service. | | string |
+| destServiceInstanceName | The name of the destination service instance. | | string |
+| destLayer | The layer of the destination service. | | enum |
+| endpoint | The endpoint used in this call. | | string |
+| componentId | The ID of component used in this call. | yes | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| detectPoint | Where the relation is detected. The value may be client, server, or proxy. | yes | enum |
+| tlsMode | The TLS mode between source and destination services, such as `service_relation_mtls_cpm = from(ServiceRelation.*).filter(tlsMode == "mTLS").cpm()` | | string |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+
+### SCOPE `TCPServiceRelation`
+
+This calculates the metrics data from each request between services.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| sourceServiceName | The name of the source service. | | string |
+| sourceServiceInstanceName | The name of the source service instance. | | string |
+| sourceLayer | The layer of the source service. | | enum |
+| destServiceName | The name of the destination service. | | string |
+| destServiceInstanceName | The name of the destination service instance. | | string |
+| destLayer | The layer of the destination service. | | enum |
+| endpoint | The endpoint used in this call. | | string |
+| componentId | The ID of component used in this call. | yes | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| detectPoint | Where the relation is detected. The value may be client, server, or proxy. | yes | enum |
+| tlsMode | The TLS mode between source and destination services, such as `service_relation_mtls_cpm = from(ServiceRelation.*).filter(tlsMode == "mTLS").cpm()` | | string |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+| receivedBytes | The received bytes of the TCP traffic. | | long |
+| sentBytes | The sent bytes of the TCP traffic. | | long |
+
+### SCOPE `ServiceInstanceRelation`
+
+This calculates the metrics data from each request between service instances.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| sourceServiceName | The name of the source service. | | string |
+| sourceServiceInstanceName | The name of the source service instance. | | string |
+| sourceServiceLayer | The layer of the source service. | | enum |
+| destServiceName | The name of the destination service. | | |
+| destServiceInstanceName | The name of the destination service instance. | | string |
+| destServiceLayer | The layer of the destination service. | | enum |
+| endpoint | The endpoint used in this call. | | string |
+| componentId | The ID of the component used in this call. | yes | string |
+| latency | The time taken by each request. | | int |
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| detectPoint | Where the relation is detected. The value may be client, server, or proxy. | yes | enum |
+| tlsMode | The TLS mode between source and destination service instances, such as `service_instance_relation_mtls_cpm = from(ServiceInstanceRelation.*).filter(tlsMode == "mTLS").cpm()` | | string |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+
+### SCOPE `TCPServiceInstanceRelation`
+
+This calculates the metrics data from each request between service instances.
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The name of the source service. | | string |
+| sourceServiceInstanceName | The name of the source service instance. | | string |
+| sourceServiceLayer | The layer of the source service. | | enum |
+| destServiceName | The name of the destination service. | | |
+| destServiceInstanceName | The name of the destination service instance. | | string |
+| destServiceLayer | The layer of the destination service. | | enum |
+| componentId | The ID of the component used in this call. | yes | string |
+| detectPoint | Where the relation is detected. The value may be client, server, or proxy. | yes | enum |
+| tlsMode | The TLS mode between source and destination service instances, such as `service_instance_relation_mtls_cpm = from(ServiceInstanceRelation.*).filter(tlsMode == "mTLS").cpm()` | | string |
+| sideCar.internalErrorCode | The sidecar/gateway proxy internal error code. The value is based on the implementation. | | string |
+| receivedBytes | The received bytes of the TCP traffic. | | long |
+| sentBytes | The sent bytes of the TCP traffic. | | long |
+
+### SCOPE `EndpointRelation`
+
+This calculates the metrics data of the dependency between endpoints.
+This relation is hard to detect, and it depends on the tracing library to propagate the previous endpoint.
+Therefore, the `EndpointRelation` scope aggregation comes into effect only in services under tracing by SkyWalking
+native agents,
+including auto instrument agents (like Java and .NET), or other tracing context propagation in SkyWalking specification.
+
+| Name | Remarks | Group Key | Type |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------|
+| endpoint | The parent endpoint in the dependency. | | string |
+| serviceName | The name of the service. | | string |
+| serviceNodeType | The type of node to which the Service or Network address belongs, such as Normal, Database, MQ, or Cache. | | enum |
+| childEndpoint | The endpoint used by the parent endpoint in row(1). | | string |
+| childServiceName | The endpoint used by the parent service in row(1). | | string |
+| childServiceNodeType | The type of node to which the Service or Network address belongs, such as Normal, Database, MQ, or Cache. | | string |
+| childServiceInstanceName | The endpoint used by the parent service instance in row(1). | | string |
+| rpcLatency | The latency of the RPC between the parent endpoint and childEndpoint, excluding the latency caused by the parent endpoint itself.
+| componentId | The ID of the component used in this call. | yes | string
+| status | Indicates the success or failure of the request. | | bool(true for success) |
+| httpResponseStatusCode | The response code of the HTTP response, and if this request is the HTTP call. E.g. 200, 404, 302 | | int |
+| rpcStatusCode | The string value of the rpc response code. | | string |
+| type | The type of each request, such as Database, HTTP, RPC, or gRPC. | | enum |
+| detectPoint | Indicates where the relation is detected. The value may be client, server, or proxy. | yes | enum |
+
+### SCOPE `BrowserAppTraffic`
+
+This calculates the metrics data from each request of the browser application (browser only).
+
+| Name | Remarks | Group Key | Type |
+|-----------------|--------------------------------------------------------------------------------|-----------|--------|
+| name | The browser application name of each request. | | string |
+| count | The number of request, which is fixed at 1. | | int |
+| trafficCategory | The traffic category. The value may be NORMAL, FIRST_ERROR, or ERROR. | | enum |
+| errorCategory | The error category. The value may be AJAX, RESOURCE, VUE, PROMISE, or UNKNOWN. | | enum |
+
+### SCOPE `BrowserAppSingleVersionTraffic`
+
+This calculates the metrics data from each request of a single version in the browser application (browser only).
+
+| Name | Remarks | Group Key | Type |
+|-----------------|--------------------------------------------------------------------------------|-----------|--------|
+| name | The single version name of each request. | | string |
+| serviceName | The name of the browser application. | | string |
+| count | The number of request, which is fixed at 1. | | int |
+| trafficCategory | The traffic category. The value may be NORMAL, FIRST_ERROR, or ERROR. | | enum |
+| errorCategory | The error category. The value may be AJAX, RESOURCE, VUE, PROMISE, or UNKNOWN. | | enum |
+
+### SCOPE `BrowserAppPageTraffic`
+
+This calculates the metrics data from each request of the page in the browser application (browser only).
+
+| Name | Remarks | Group Key | Type |
+|-----------------|--------------------------------------------------------------------------------|-----------|--------|
+| name | The page name of each request. | | string |
+| serviceName | The name of the browser application. | | string |
+| count | The number of request, which is fixed at 1. | | int |
+| trafficCategory | The traffic category. The value may be NORMAL, FIRST_ERROR, or ERROR. | | enum |
+| errorCategory | The error category. The value may be AJAX, RESOURCE, VUE, PROMISE, or UNKNOWN. | | enum |
+
+### SCOPE `BrowserAppPagePerf`
+
+This calculates the metrics data from each request of the page in the browser application (browser only).
+
+| Name | Remarks | Group Key | Type |
+|-----------------|-----------------------------------------|-----------|------------|
+| name | The page name of each request. | | string |
+| serviceName | The name of the browser application. | | string |
+| redirectTime | The time taken to redirect. | | int(in ms) |
+| dnsTime | The DNS query time. | | int(in ms) |
+| ttfbTime | Time to first byte. | | int(in ms) |
+| tcpTime | TCP connection time. | | int(in ms) |
+| transTime | Content transfer time. | | int(in ms) |
+| domAnalysisTime | Dom parsing time. | | int(in ms) |
+| fptTime | First paint time or blank screen time. | | int(in ms) |
+| domReadyTime | Dom ready time. | | int(in ms) |
+| loadPageTime | Page full load time. | | int(in ms) |
+| resTime | Synchronous load resources in the page. | | int(in ms) |
+| sslTime | Only valid for HTTPS. | | int(in ms) |
+| ttlTime | Time to interact. | | int(in ms) |
+| firstPackTime | First pack time. | | int(in ms) |
+| fmpTime | First Meaningful Paint. | | int(in ms) |
+
+### SCOPE `Event`
+
+This calculates the metrics data from [events](event.md).
+
+| Name | Remarks | Group Key | Type |
+|-----------------|-------------------------------------------------------------------------|-----------|--------|
+| name | The name of the event. | | string |
+| service | The service name to which the event belongs to. | | string |
+| serviceInstance | The service instance to which the event belongs to, if any. | | string |
+| endpoint | The service endpoint to which the event belongs to, if any. | | string |
+| type | The type of the event, `Normal` or `Error`. | | string |
+| message | The message of the event. | | string |
+| parameters | The parameters in the `message`, see [parameters](event.md#parameters). | | string |
+
+### SCOPE `DatabaseAccess`
+
+This calculates the metrics data from each request of database.
+
+| Name | Remarks | Group Key | Type |
+|----------------|--------------------------------------------------|-----------|------------|
+| name | The service name of virtual database service. | | string |
+| databaseTypeId | The ID of the component used in this call. | | int |
+| latency | The time taken by each request. | | int(in ms) |
+| status | Indicates the success or failure of the request. | | boolean |
+
+### SCOPE `DatabaseSlowStatement`
+
+This calculates the metrics data from slow request of database.
+
+| Name | Remarks | Group Key | Type |
+|-------------------|------------------------------------------|-----------|------------|
+| databaseServiceId | The service id of virtual cache service. | | string |
+| statement | The sql statement . | | string |
+| latency | The time taken by each request. | | int(in ms) |
+| traceId | The traceId of this slow statement | | string |
+
+### SCOPE `CacheAccess`
+
+This calculates the metrics data from each request of cache system.
+
+| Name | Remarks | Group Key | Type |
+|-------------|-----------------------------------------------------|-----------|------------|
+| name | The service name of virtual cache service. | | string |
+| cacheTypeId | The ID of the component used in this call. | | int |
+| latency | The time taken by each request. | | int(in ms) |
+| status | Indicates the success or failure of the request. | | boolean |
+| operation | Indicates this access is used for `write` or `read` | | string |
+
+### SCOPE `CacheSlowAccess`
+
+This calculates the metrics data from slow request of cache system , which is used for `write` or `read` operation.
+
+| Name | Remarks | Group Key | Type |
+|----------------|-----------------------------------------------------|-----------|------------|
+| cacheServiceId | The service id of virtual cache service. | | string |
+| command | The cache command . | | string |
+| key | The cache command key. | | string |
+| latency | The time taken by each request. | | int(in ms) |
+| traceId | The traceId of this slow access | | string |
+| status | Indicates the success or failure of the request. | | boolean |
+| operation | Indicates this access is used for `write` or `read` | | string |
+
+### SCOPE `MQAccess`
+
+This calculates the service dimensional metrics data from each request of MQ system on consume/produce side
+
+| Name | Remarks | Group Key | Type |
+|---------------------|---------------------------------------------------------|-----------|------------|
+| name | The service name , usually it's MQ address(es) | | string |
+| transmissionLatency | The latency from produce side to consume side . | | int(in ms) |
+| status | Indicates the success or failure of the request. | | boolean |
+| operation | Indicates this access is on `Produce` or `Consume` side | | enum |
+
+### SCOPE `MQEndpointAccess`
+
+This calculates the endpoint dimensional metrics data from each request of MQ system on consume/produce side
+
+| Name | Remarks | Group Key | Type |
+|---------------------|--------------------------------------------------------------|-----------|------------|
+| serviceName | The service name that this endpoint belongs to. | | string |
+| endpoint | The endpoint name , usually it's combined by `queue`,`topic` | | string |
+| transmissionLatency | The latency from produce side to consume side . | | int(in ms) |
+| status | Indicates the success or failure of the request. | | boolean |
+| operation | Indicates this access is on `Produce` or `Consume` side | | enum |
+
+### SCOPES with `K8S` Prefix
+
+All metrics starting with `K8S` are derived from Kubernetes monitoring by Rover(eBPF agent).
+
+#### Service, Service Instance and relations
+
+For all `K8SService`, `K8SServiceInstance`, `K8SServiceRelation` and `K8SServiceInstanceRelation`, they all have the
+following **package**/**protocol** level metric contents.
+
+| Name | Remarks | Group Key | Type |
+|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------------------|
+| type | The metrics from log type, the following names should have the type prefix. The value may be connect, accept, close, write, read, protocol. | | string |
+| connect.duration | Connect to other service use duration. | | long(in nanoseconds) |
+| connect.success | The connect is success or not. | | boolean |
+| accept.duration | Accept connection from client use duration. | | long(in nanoseconds) |
+| close.duration | Close one connection use duration. | | long(in nanoseconds) |
+| close.success | Close one connection is success or not. | | boolean |
+| write.duration | Write data to the connection use duration. | | long(in nanoseconds) |
+| write.syscall | Write data to the connection syscall name. The value should be Write, Writev, Send, SendTo, SendMsg, SendMmsg, SendFile, SendFile64. | | string |
+| write.l4.duration | Write data to the connection use duration on Linux Layer 4. | | long(in nanoseconds) |
+| write.l4.transmitPackageCount | Total package count on write data to the connection. | | long |
+| write.l4.retransmitPackageCount | Total retransmit package count on write data to the connection. | | long |
+| write.l4.totalPackageSize | Total transmit package size on write data to the connection. | | long(bytes) |
+| write.l3.duration | Write data to the connection use duration on Linux Layer 3. | | long(in nanoseconds) |
+| write.l3.localDuration | Write data to the connection use local duration on Linux Layer 3. | | long(in nanoseconds) |
+| write.l3.outputDuration | Write data to the connection use output duration on Linux Layer 3. | | long(in nanoseconds) |
+| write.l3.resolveMACCount | Total resolve remote MAC address count on write data to the connection. | | long |
+| write.l3.resolveMACDuration | Total resolve remote MAC address use duration on write data to the connection. | | long(in nanoseconds) |
+| write.l3.netFilterCount | Total do net filtering count on write data to the connection. | | long |
+| write.l3.netFilterDuration | Total do net filtering use duration on write data to the connection. | | long(in nanoseconds) |
+| write.l2.duration | Write data to the connection use duration on Linux L2. | | long(nanoseconds) |
+| write.l2.networkDeviceName | The network device name on write data to the connection. | | string |
+| write.l2.enterQueueBufferCount | The write package count to the network device queue on write data to the connection. | | long |
+| write.l2.readySendDuration | Total ready send buffer duration on write data to the connection. | | long(in nanoseconds) |
+| write.l2.networkDeviceSendDuration | Total network send buffer use duration on write data to the connection. | | long(in nanoseconds) |
+| read.duration | Read data from the connection use duration. | | long(in nanoseconds) |
+| read.syscall | Read data from the connection syscall name. The value should Read, Readv, Recv, RecvFrom, RecvMsg, RecvMmsg. | | string |
+| read.l4.duration | Read data to the connection use duration on Linux Layer 4. | | long(in nanoseconds) |
+| read.l3.duration | Read data to the connection use duration on Linux Layer 3. | | long(in nanoseconds) |
+| read.l3.rcvDuration | Read data to the connection use receive duration on Linux Layer 3. | | long(in nanoseconds) |
+| read.l3.localDuration | Read data to the connection use local duration on Linux Layer 3. | | long(in nanoseconds) |
+| read.l3.netFilterCount | Total do net filtering count on read data from the connection. | | long |
+| read.l3.netFilterDuration | Total do net filtering use duration on read data from the connection. | | long(in nanoseconds) |
+| read.l2.netDeviceName | The network device name on read data from the connection. | | string |
+| read.l2.packageCount | Total read package count on the connection. | | long |
+| read.l2.totalPackageSize | Total read package size on the connection. | | long(bytes) |
+| read.l2.packageToQueueDuration | Total read package to the queue duration on the connection. | | long(in nanoseconds) |
+| read.l2.rcvPackageFromQueueDuration | Total read package from the queue duration on the connection. | | long(in nanoseconds) |
+| protocol.type | The protocol type name, the following names should have the type prefix. The value should be HTTP. | | string |
+| protocol.success | This protocol request and response is success or not. | | boolean |
+| protocol.http.latency | The latency of HTTP response. | | long(in nanoseconds) |
+| protocol.http.url | The url path of HTTP request. | | string |
+| protocol.http.method | The method name of HTTP request. | | string |
+| protocol.http.statusCode | The response code of HTTP response. | | int |
+| protocol.http.sizeOfRequestHeader | The header size of HTTP request. | | long(bytes) |
+| protocol.http.sizeOfRequestBody | The body size of HTTP request. | | long(bytes) |
+| protocol.http.sizeOfResponseHeader | The header size of HTTP response. | | long(bytes) |
+| protocol.http.sizeOfResponseBody | The body size of HTTP response. | | long(bytes) |
+
+##### SCOPE `K8SService`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------|-----------|--------|
+| name | The service name in kubernetes. | | string |
+| layer | The layer in kubernetes service. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+
+#### SCOPE `K8SServiceInstance`
+
+| Name | Remarks | Group Key | Type |
+|---------------------|--------------------------------------------------------------------|-----------|--------|
+| serviceName | The service name in kubernetes. | | string |
+| serviceInstanceName | The pod name in kubernetes. | | string |
+| layer | The layer of kubernetes service. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+
+##### SCOPE `K8SServiceRelation`
+
+| Name | Remarks | Group Key | Type |
+|-------------------|--------------------------------------------------------------------|-----------|--------------|
+| sourceServiceName | The source service name in kubernetes. | | string |
+| sourceLayer | The source layer service in kubernetes. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentIds | The ID of component used in this call. | | List |
+| tlsMode | The TLS mode of relation. The value may be Plain or TLS. | | enum |
+| destServiceName | The dest service name in kubernetes. | | string |
+| destLayer | The dest layer service in kubernetes. | | string |
+
+##### SCOPE `K8SServiceRelation`
+
+| Name | Remarks | Group Key | Type |
+|-------------------|--------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The source service name in kubernetes. | | string |
+| sourceLayer | The source layer service in kubernetes. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentId | The ID of component used in this call. | | string |
+| tlsMode | The TLS mode of relation. The value may be Plain or TLS. | | enum |
+| destServiceName | The dest service name in kubernetes. | | string |
+| destLayer | The dest layer service in kubernetes. | | string |
+
+##### SCOPE `K8SServiceInstanceRelation`
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|--------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The source service name in kubernetes. | | string |
+| sourceServiceInstanceName | The source pod name in kubernetes. | | string |
+| sourceLayer | The source layer service in kubernetes. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentId | The ID of component used in this call. | | string |
+| tlsMode | The TLS mode of relation. The value may be Plain or TLS. | | enum |
+| destServiceName | The dest service name in kubernetes. | | string |
+| destServiceInstanceName | The dest pod name in kubernetes. | | string |
+| destLayer | The dest layer service in kubernetes. | | string |
+
+#### Endpoint
+
+For `K8SEndpoint`, they only have the following **protocol** level metric contents.
+
+| Name | Remarks | Group Key | Type |
+|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------------------|
+| protocol.type | The protocol type name, the following names should have the type prefix. The value should be HTTP. | | string |
+| protocol.success | This protocol request and response is success or not. | | boolean |
+| protocol.http.latency | The latency of HTTP response. | | long(in nanoseconds) |
+| protocol.http.url | The url path of HTTP request. | | string |
+| protocol.http.method | The method name of HTTP request. | | string |
+| protocol.http.statusCode | The response code of HTTP response. | | int |
+| protocol.http.sizeOfRequestHeader | The header size of HTTP request. | | long(bytes) |
+| protocol.http.sizeOfRequestBody | The body size of HTTP request. | | long(bytes) |
+| protocol.http.sizeOfResponseHeader | The header size of HTTP response. | | long(bytes) |
+| protocol.http.sizeOfResponseBody | The body size of HTTP response. | | long(bytes) |
+
+##### SCOPE `K8SEndpoint`
+
+| Name | Remarks | Group Key | Type |
+|--------------|---------------------------------------------------------|-----------|--------|
+| serviceName | The service name in kubernetes. | | string |
+| layer | The layer in kubernetes service. | | string |
+| endpointName | The endpoint name detect in kubernetes service. | | string |
+| duration | The duration of the service endpoint response latency. | | long |
+
+### SCOPES with `Cilium` Prefix
+
+All metrics starting with `Cilium` are derived from Cilium monitoring by Cilium Hubble.
+
+#### Service, Service Instance and relations
+
+For all `CiliumService`, `CiliumServiceInstance`, `CiliumServiceRelation` and `CiliumServiceInstanceRelation`, they all have the
+following **L4**/**L7** metric contents.
+
+| Name | Remarks | Group Key | Type |
+|-----------------------|-----------------------------------------------------------------------------|-----------|--------|
+| verdict | The metrics verdict from Flow. The value may be `forwarded` and `dropped`. | | string |
+| type | The metrics type from Flow. The value may be `tcp`, `http`, `dns`, `kakfa`. | | string |
+| direction | The metrics direction from Flow. The value may be `ingress` and `egress`. | | string |
+| dropReason | When the verdict is `dropped`, the drop reason would be recorded. | | string |
+| http.url | The URL of the HTTP request. | | string |
+| http.code | The Response code of the HTTP response. | | int |
+| http.protocol | The protocol of the HTTP request. | | string |
+| http.method | The method of the HTTP request. | | string |
+| kafka.errorCode | The error code of the Kafka request. | | int |
+| kafka.errorCodeString | The error code explaination of the Kafka request. | | string |
+| kafka.apiVersion | The API version of the Kafka request. | | string |
+| kafka.apiKey | The API key of the Kafka request. | | string |
+| kafka.correlationId | The correlation ID of the Kafka request. | | string |
+| kafka.topic | The topic of the Kafka request. | | string |
+| dns.domain | The domain of the DNS request. | | string |
+| dns.queryType | The query type of the DNS request. | | string |
+| dns.rcode | The response code of the DNS request. | | int |
+| dns.recodeString | The response code explaination of the DNS request. | | string |
+| dns.ttl | The TTL of the DNS request. | | int |
+| dns.ipCount | The count of the IP addresses of the DNS responsed. | | int |
+| duration | The duration(millisecond) of the L7 response. | | long |
+| success | Is the response success of the L7 response. | | bool |
+
+##### SCOPE `CiliumService`
+
+| Name | Remarks | Group Key | Type |
+|-------------|--------------------------------------------------------------------|-----------|--------|
+| name | The service name in Cilium. | | string |
+| layer | The layer in Cilium service. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+
+##### SCOPE `CiliumServiceInstance`
+
+| Name | Remarks | Group Key | Type |
+|---------------------|--------------------------------------------------------------------|-----------|--------|
+| serviceName | The service name in Cilium. | | string |
+| serviceInstanceName | The pod name in Cilium. | | string |
+| layer | The layer of Cilium service. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+
+##### SCOPE `CiliumServiceRelation`
+
+| Name | Remarks | Group Key | Type |
+|-------------------|--------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The source service name in Cilium. | | string |
+| sourceLayer | The source layer service in Cilium. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentId | The ID of component used in this call. | | int |
+| destServiceName | The dest service name in Cilium. | | string |
+| destLayer | The dest layer service in Cilium. | | string |
+
+##### SCOPE `CiliumServiceInstanceRelation`
+
+| Name | Remarks | Group Key | Type |
+|---------------------------|--------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The source service name in Cilium. | | string |
+| sourceServiceInstanceName | The source pod name in Cilium. | | string |
+| sourceLayer | The source layer service in Cilium. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentId | The ID of component used in this call. | | int |
+| destServiceName | The dest service name in Cilium. | | string |
+| destServiceInstanceName | The dest pod name in Cilium. | | string |
+| destLayer | The dest layer service in Cilium. | | string |
+
+#### Endpoint and Endpoint Relation
+
+For `CiliumEndpoint` and `CiliumEndpointRelation`, they have all the fields of **L4**/**L7** metric contents, but the `type` only would be `http`, `dns` or `kafka`.
+
+##### SCOPE `CiliumEndpoint`
+
+| Name | Remarks | Group Key | Type |
+|--------------|---------------------------------------------------------|-----------|--------|
+| serviceName | The service name in Cilium. | | string |
+| layer | The layer in Cilium service. | | string |
+| endpointName | The endpoint name detect in Cilium service. | | string |
+
+##### SCOPE `CiliumEndpointRelation`
+
+| Name | Remarks | Group Key | Type |
+|--------------------|--------------------------------------------------------------------|-----------|--------|
+| sourceServiceName | The source service name in Cilium. | | string |
+| sourceLayer | The layer in Cilium source service. | | enum |
+| sourceEndpointName | The endpoint name detect in Cilium source service. | | string |
+| detectPoint | Where the relation is detected. The value may be client or server. | | enum |
+| componentId | The ID of component used in this call. | | int |
+| destServiceName | The dest service name in Cilium. | | string |
+| destLayer | The layer in Cilium dest service. | | enum |
+| destEndpointName | The endpoint name detect in Cilium dest service. | | string |
+
+
diff --git a/docs/en/concepts-and-designs/sdk-profiling.md b/docs/en/concepts-and-designs/sdk-profiling.md
new file mode 100644
index 000000000000..bd7e6e963fbf
--- /dev/null
+++ b/docs/en/concepts-and-designs/sdk-profiling.md
@@ -0,0 +1,140 @@
+# Use Profiling to Fix the Blind Spot of Distributed Tracing
+
+> This post introduces a way to automatically profile code in production with Apache SkyWalking.
+> We believe the profile method helps reduce maintenance and overhead while increasing the precision in root cause analysis.
+
+This post introduces a way to automatically profile code in production
+with [Apache SkyWalking](https://skywalking.apache.org). We believe the profile method helps reduce maintenance and
+overhead while increasing the precision in root cause analysis.
+
+### Limitations of the Distributed Tracing
+
+In the early days, metrics and logging systems were the key solutions in monitoring platforms. With the adoption of
+microservice and distributed system-based architecture, distributed tracing has become more important. Distributed
+tracing provides relevant service context, such as system topology map and RPC parent-child relationships.
+
+Some claim that distributed tracing is the best way to discover the cause of performance issues in a distributed system.
+It’s good at finding issues at the RPC abstraction, or in the scope of components instrumented with spans. However, it
+isn’t that perfect.
+
+Have you been surprised to find a span duration longer than expected, but no insight into why? What should you do next?
+Some may think that the next step is to add more instrumentation, more spans into the trace, thinking that you would
+eventually find the root cause, with more data points. We’ll argue this is not a good option within a production
+environment. Here’s why:
+
+1. There is a risk of application overhead and system overload. Ad-hoc spans measure the performance of specific scopes
+ or methods, but picking the right place can be difficult. To identify the precise cause, you can “instrument” (add
+ spans to) many suspicious places. The additional instrumentation costs more CPU and memory in the production
+ environment. Next, ad-hoc instrumentation that didn’t help is often forgotten, not deleted. This creates a valueless
+ overhead load. In the worst case, excess instrumentation can cause performance problems in the production app or
+ overload the tracing system.
+2. The process of ad-hoc (manual) instrumentation usually implies at least a restart. Trace instrumentation libraries,
+ like Zipkin Brave, are integrated into many framework libraries. To instrument a method’s performance typically
+ implies changing code, even if only an annotation. This implies a re-deploy. Even if you have the way to do auto
+ instrumentation, like Apache SkyWalking, you still need to change the configuration and reboot the app. Otherwise,
+ you take the risk of GC caused by hot dynamic instrumentation.
+3. Injecting instrumentation into an uninstrumented third party library is hard and complex. It takes more time and many
+ won’t know how to do this.
+4. Usually, we don’t have code line numbers in the distributed tracing. Particularly when lambdas are in use, it can be
+ difficult to identify the line of code associated with a span. Regardless of the above choices, to dive deeper
+ requires collaboration with your Ops or SRE team, and a shared deep level of knowledge in distributed tracing.
+
+Regardless of the above choices, to dive deeper requires collaboration with your Ops or SRE team, and a shared deep
+level of knowledge in distributed tracing.
+
+### Profiling in Production
+
+#### Introduction
+
+To reuse distributed tracing to achieve method scope precision requires an understanding of the above limitations and a
+different approach. We called it PROFILE.
+
+Most high-level languages build and run on a thread concept. The profile approach takes continuous thread dumps. We
+merge the thread dumps to estimate the execution time of every method shown in the thread dumps. The key for distributed
+tracing is the tracing context, identifiers active (or current) for the profiled method. Using this trace context, we
+can weave data harvested from profiling into existing traces. This allows the system to automate otherwise ad-hoc
+instrumentation. Let’s dig deeper into how profiling works:
+
+We consider a method invocation with the same stack depth and signature (method, line number etc), the same operation.
+We derive span timestamps from the thread dumps the same operation is in. Let’s put this visually:
+
+
+
+Above, represents 10 successive thread dumps. If this method is in dumps 4-8, we assume it started before dump 4 and
+finished after dump 8. We can’t tell exactly when the method started and stopped. but the timestamps of thread dumps are
+close enough.
+
+To reduce overhead caused by thread dumps, we only profile methods enclosed by a specific entry point, such as a URI or
+MVC Controller method. We identify these entry points through the trace context and the APM system.
+
+The profile does thread dump analysis and gives us:
+
+1. The root cause, precise to the line number in the code.
+2. Reduced maintenance as ad-hoc instrumentation is obviated.
+3. Reduced overload risk caused by ad-hoc instrumentation.
+4. Dynamic activation: only when necessary and with a very clear profile target.
+
+### Implementing Precise Profiling
+
+Distributed profiling is built-into Apache SkyWalking application performance monitoring (APM). Let’s demonstrate how
+the profiling approach locates the root cause of the performance issue.
+
+```
+final CountDownLatchcountDownLatch= new CountDownLatch(2);
+
+threadPool.submit(new Task1(countDownLatch));
+threadPool.submit(new Task2(countDownLatch));
+
+try {
+ countDownLatch.await(500, TimeUnit.MILLISECONDS);
+} catch (InterruptedException) {
+}
+```
+
+Task1 and Task2 have a race condition and unstable execution time: they will impact the performance of each other and
+anything calling them. While this code looks suspicious, it is representative of real life. People in the OPS/SRE team
+are not usually aware of all code changes and who did them. They only know something in the new code is causing a
+problem.
+
+To make matters interesting, the above code is not always slow: it only happens when the condition is locked. In
+SkyWalking APM, we have metrics of endpoint p99/p95 latency, so, we are easy to find out the p99 of this endpoint is far
+from the avg response time. However, this is not the same as understanding the cause of the latency. To locate the root
+cause, add a profile condition to this endpoint: duration greater than 500ms. This means faster executions will not add
+profiling load.
+
+
+
+This is a typical profiled trace segment (part of the whole distributed trace) shown on the SkyWalking UI. We now notice
+the “service/processWithThreadPool” span is slow as we expected, but why? This method is the one we added the faulty
+code to. As the UI shows that method, we know the profiler is working. Now, let’s see what the profile analysis result
+say.
+
+
+
+This is the profile analysis stack view. We see the stack element names, duration (include/exclude the children) and
+slowest methods have been highlighted. It shows clearly, “sun.misc.Unsafe.park” costs the most time. If we look for the
+caller, it is the code we added: **CountDownLatch.await**.
+
+### The Limitations of the Profile Method
+
+No diagnostic tool can fit all cases, not even the profile method.
+
+The first consideration is mistaking a repeatedly called method for a slow method. Thread dumps are periodic. If there
+is a loop of calling one method, the profile analysis result would say the target method is slow because it is captured
+every time in the dump process. There could be another reason. A method called many times can also end up captured in
+each thread dump. Even so, the profile did what it is designed for. It still helps the OPS/SRE team to locate the code
+having the issue.
+
+The second consideration is overhead, the impact of repeated thread dumps is real and can’t be ignored. In SkyWalking,
+we set the profile dump period to at least 10ms. This means we can’t locate method performance issues if they complete
+in less than 10ms. SkyWalking has a threshold to control the maximum parallel degree as well.
+
+The third consideration is profiling wouldn't work for a low latency trace. Because the trace could be completed before
+profiling starts. But in reality, this is not an issue, profiling targets slow requests.
+
+Understanding the above keeps distributed tracing and APM systems useful for your OPS/SRE team.
+
+### Supported Agents
+
+This feature was first implemented in Java agent since 7.0. The Python agent supported this since 0.7.0.
+Read [this](https://skywalking.apache.org/blog/2021-09-12-skywalking-python-profiling/) for more details
\ No newline at end of file
diff --git a/docs/en/concepts-and-designs/service-agent.md b/docs/en/concepts-and-designs/service-agent.md
new file mode 100644
index 000000000000..ee52af152888
--- /dev/null
+++ b/docs/en/concepts-and-designs/service-agent.md
@@ -0,0 +1,33 @@
+# Service Auto Instrument Agent
+The service auto instrument agent is a subset of language-based native agents. This kind of agents is based on
+some language-specific features, especially those of a VM-based language.
+
+## What does Auto Instrument mean?
+Many users learned about these agents when they first heard that "Not a single line of code has to be changed". SkyWalking used to mention this in its readme page as well.
+However, this does not reflect the full picture. For end users, it is true that they no longer have to modify their codes in most cases.
+But it is important to understand that the codes are in fact still modified by the agent, which is usually known as "runtime code manipulation". The underlying logic is that the
+auto instrument agent uses the VM interface for code modification to dynamically add in the instrument code, such as modifying the class in Java through
+`javaagent premain`.
+
+In fact, although the SkyWalking team has mentioned that most auto instrument agents are VM-based, you may build such tools during compiling time rather than
+runtime.
+
+## What are the limitations?
+Auto instrument is very helpful, as you may perform auto instrument during compiling time, without having to depend on VM features. But there are also certain limitations that come with it:
+
+- **Higher possibility of in-process propagation in many cases**. Many high-level languages, such as Java and .NET, are used for building business systems.
+ Most business logic codes run in the same thread for each request, which causes propagation to be based on thread ID, in order for the stack module to make sure that the context is safe.
+
+- **Only works in certain frameworks or libraries**. Since the agents are responsible for modifying the codes during runtime, the codes are already known
+to the agent plugin developers. There is usually a list of frameworks or libraries supported by this kind of probes.
+For example, see the [SkyWalking Java agent supported list](https://github.com/apache/skywalking-java/blob/20fb8c81b3da76ba6628d34c12d23d3d45c973ef/docs/en/setup/service-agent/java-agent/Supported-list.md).
+
+- **Cross-thread operations are not always supported**. Like what is mentioned above regarding in-process propagation, most codes (especially business codes)
+run in a single thread per request. But in some other cases, they operate across different threads, such as assigning tasks to other threads, task pools or batch processes. Some languages may even provide coroutine or similar components like `Goroutine`, which allows developers to run async process with low payload. In such cases, auto instrument will face problems.
+
+So, there's nothing mysterious about auto instrument. In short, agent developers write an activation script to make
+instrument codes work for you. That's it!
+
+## What is next?
+If you want to learn about manual instrument libs in SkyWalking, see the [Manual instrument SDK](manual-sdk.md) section.
+
diff --git a/docs/en/concepts-and-designs/service-hierarchy-configuration.md b/docs/en/concepts-and-designs/service-hierarchy-configuration.md
new file mode 100644
index 000000000000..6aa0d40d56b2
--- /dev/null
+++ b/docs/en/concepts-and-designs/service-hierarchy-configuration.md
@@ -0,0 +1,80 @@
+# Define Service Hierarchy
+SkyWalking v10 introduces a new concept `Service Hierarchy` which defines the relationships of existing logically same services in various layers.
+The concept and design could be found [here](service-hierarchy.md).
+
+## Service Hierarchy Configuration
+All the relationships defined in the `config/hierarchy-definition.yml` file. You can customize it according to your own needs.
+Here is an example:
+
+```yaml
+hierarchy:
+ MESH:
+ MESH_DP: name
+ K8S_SERVICE: short-name
+
+ MESH_DP:
+ K8S_SERVICE: short-name
+
+ GENERAL:
+ K8S_SERVICE: lower-short-name-remove-ns
+
+ MYSQL:
+ K8S_SERVICE: short-name
+
+ POSTGRESQL:
+ K8S_SERVICE: short-name
+
+ SO11Y_OAP:
+ K8S_SERVICE: short-name
+
+ VIRTUAL_DATABASE:
+ MYSQL: lower-short-name-with-fqdn
+ POSTGRESQL: lower-short-name-with-fqdn
+
+auto-matching-rules:
+ # the name of the upper service is equal to the name of the lower service
+ name: "{ (u, l) -> u.name == l.name }"
+ # the short name of the upper service is equal to the short name of the lower service
+ short-name: "{ (u, l) -> u.shortName == l.shortName }"
+ # remove the k8s namespace from the lower service short name
+ # this rule is only works on k8s env.
+ lower-short-name-remove-ns: "{ (u, l) -> { if(l.shortName.lastIndexOf('.') > 0) return u.shortName == l.shortName.substring(0, l.shortName.lastIndexOf('.')); return false; } }"
+ # the short name of the upper remove port is equal to the short name of the lower service with fqdn suffix
+ # this rule is only works on k8s env.
+ lower-short-name-with-fqdn: "{ (u, l) -> { if(u.shortName.lastIndexOf(':') > 0) return u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local'); return false; } }"
+
+layer-levels:
+ # The hierarchy level of the service layer, the level is used to define the order of the service layer for UI presentation.
+ # The level of the upper service should greater than the level of the lower service in `hierarchy` section.
+ MESH: 3
+ GENERAL: 3
+ SO11Y_OAP: 3
+ VIRTUAL_DATABASE: 3
+ MYSQL: 2
+ POSTGRESQL: 2
+ MESH_DP: 1
+ CILIUM_SERVICE: 1
+ K8S_SERVICE: 0
+```
+
+### Hierarchy
+- The hierarchy of service layers are defined in the `hierarchy` section.
+- The layers under the specific layer are related lower of the layer.
+- The relation could have a matching rule for auto matching, which are defined in the `auto-matching-rules` section.
+- The relation without a matching rule should be built through the internal API.
+- All the layers are defined in the file `org.apache.skywalking.oap.server.core.analysis.Layers.java`.
+- If the hierarchy is not defined, the service hierarchy relationship will not be built.
+- If you want to add a new relationship, you should certainly know they can be matched automatically by [Auto Matching Rules](#auto-matching-rules).
+- Notice: some hierarchy relations and auto matching rules are only works on k8s env.
+
+### Auto Matching Rules
+- The auto matching rules are defined in the `auto-matching-rules` section.
+- Use Groovy script to define the matching rules, the input parameters are the upper service(u) and the lower service(l) and the return value is a boolean,
+which are used to match the relation between the upper service(u) and the lower service(l) on the different layers.
+- The default matching rules required the service name configured as SkyWalking default and follow the [Showcase](https://github.com/apache/skywalking-showcase).
+If you customized the service name in any layer, you should customize the related matching rules according your service name rules.
+
+### Layer Levels
+- Define the hierarchy level of the service layer in the `layer-levels` section.
+- The level is used to define the order of the service layer for UI presentation.
+- The level of the upper service should greater than the level of the lower service in `hierarchy` section.
diff --git a/docs/en/concepts-and-designs/service-hierarchy.md b/docs/en/concepts-and-designs/service-hierarchy.md
new file mode 100644
index 000000000000..8cd18bccda73
--- /dev/null
+++ b/docs/en/concepts-and-designs/service-hierarchy.md
@@ -0,0 +1,250 @@
+# Service Hierarchy
+SkyWalking v10 introduces a new concept `Service Hierarchy` which defines the relationships of existing logically same services in various layers.
+OAP will detect the services from different layers, and try to build the connections.
+
+## Detect Service Hierarchy Connections
+There 2 ways to detect the connections:
+1. Automatically matching through OAP internal mechanism, no extra work is required.
+2. Build the connections through specific agents.
+
+**Note:** All the relationships and auto-matching rules should be defined in the `config/hierarchy-definition.yml` file.
+If you want to customize it according to your own needs, please refer to [Service Hierarchy Configuration](service-hierarchy-configuration.md).
+
+### Automatically Matching
+
+| Upper layer | Lower layer | Matching rule |
+|------------------|-------------|-------------------------------------------------------------------|
+| GENERAL | K8S_SERVICE | [GENERAL On K8S_SERVICE](#general-on-k8s_service) |
+| GENERAL | APISIX | [GENERAL On APISIX](#general-on-apisix) |
+| VIRTUAL_DATABASE | MYSQL | [VIRTUAL_DATABASE On MYSQL](#virtual_database-on-mysql) |
+| VIRTUAL_DATABASE | POSTGRESQL | [VIRTUAL_DATABASE On POSTGRESQL](#virtual_database-on-postgresql) |
+| VIRTUAL_DATABASE | CLICKHOUSE | [VIRTUAL_DATABASE On CLICKHOUSE](#virtual_database-on-clickhouse) |
+| VIRTUAL_MQ | RABBITMQ | [VIRTUAL_MQ On RABBITMQ](#virtual_mq-on-rabbitmq) |
+| VIRTUAL_MQ | ROCKETMQ | [VIRTUAL_MQ On K8S_SERVICE](#virtual_mq-on-rocketmq) |
+| VIRTUAL_MQ | KAFKA | [VIRTUAL_MQ On KAFKA](#virtual_mq-on-kafka) |
+| VIRTUAL_MQ | RABBITMQ | [VIRTUAL_MQ On RABBITMQ](#virtual_mq-on-rabbitmq) |
+| VIRTUAL_MQ | PULSAR | [VIRTUAL_MQ On PULSAR](#virtual_mq-on-pulsar) |
+| MESH | MESH_DP | [MESH On MESH_DP](#mesh-on-mesh_dp) |
+| MESH | K8S_SERVICE | [MESH On K8S_SERVICE](#mesh-on-k8s_service) |
+| MESH_DP | K8S_SERVICE | [MESH_DP On K8S_SERVICE](#mesh_dp-on-k8s_service) |
+| MYSQL | K8S_SERVICE | [MYSQL On K8S_SERVICE](#mysql-on-k8s_service) |
+| POSTGRESQL | K8S_SERVICE | [POSTGRESQL On K8S_SERVICE](#postgresql-on-k8s_service) |
+| CLICKHOUSE | K8S_SERVICE | [CLICKHOUSE On K8S_SERVICE](#clickhouse-on-k8s_service) |
+| NGINX | K8S_SERVICE | [NGINX On K8S_SERVICE](#nginx-on-k8s_service) |
+| APISIX | K8S_SERVICE | [APISIX On K8S_SERVICE](#apisix-on-k8s_service) |
+| ROCKETMQ | K8S_SERVICE | [ROCKETMQ On K8S_SERVICE](#rocketmq-on-k8s_service) |
+| RABBITMQ | K8S_SERVICE | [RABBITMQ On K8S_SERVICE](#rabbitmq-on-k8s_service) |
+| KAFKA | K8S_SERVICE | [KAFKA On K8S_SERVICE](#kafka-on-k8s_service) |
+| PULSAR | K8S_SERVICE | [PULSAR On K8S_SERVICE](#pulsar-on-k8s_service) |
+| SO11Y_OAP | K8S_SERVICE | [SO11Y_OAP On K8S_SERVICE](#so11y_oap-on-k8s_service) |
+| KONG | K8S_SERVICE | [KONG On K8S_SERVICE](#kong-on-k8s_service) |
+
+- The following sections will describe the **default matching rules** in detail and use the `upper-layer On lower-layer` format.
+- The example service name are based on SkyWalking [Showcase](https://github.com/apache/skywalking-showcase) default deployment.
+- In SkyWalking the service name could be composed of `group` and `short name` with `::` separator.
+
+#### GENERAL On K8S_SERVICE
+- Rule name: `lower-short-name-remove-ns`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName.substring(0, l.shortName.lastIndexOf('.')) }`
+- Description: GENERAL.service.shortName == K8S_SERVICE.service.shortName without namespace
+- Matched Example:
+ - GENERAL.service.name: `agent::songs`
+ - K8S_SERVICE.service.name: `skywalking-showcase::songs.sample-services`
+
+#### GENERAL On APISIX
+- Rule name: `lower-short-name-remove-ns`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName.substring(0, l.shortName.lastIndexOf('.')) }`
+- Description: GENERAL.service.shortName == APISIX.service.shortName without namespace
+- Matched Example:
+ - GENERAL.service.name: `agent::frontend`
+ - APISIX.service.name: `APISIX::frontend.sample-services`
+
+
+#### VIRTUAL_DATABASE On MYSQL
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_DATABASE.service.shortName remove port == MYSQL.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_DATABASE.service.name: `mysql.skywalking-showcase.svc.cluster.local:3306`
+ - MYSQL.service.name: `mysql::mysql.skywalking-showcase`
+
+#### VIRTUAL_DATABASE On POSTGRESQL
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_DATABASE.service.shortName remove port == POSTGRESQL.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_DATABASE.service.name: `psql.skywalking-showcase.svc.cluster.local:5432`
+ - POSTGRESQL.service.name: `postgresql::psql.skywalking-showcase`
+
+#### VIRTUAL_DATABASE On CLICKHOUSE
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_DATABASE.service.shortName remove port == CLICKHOUSE.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_DATABASE.service.name: `clickhouse.skywalking-showcase.svc.cluster.local:8123`
+ - CLICKHOUSE.service.name: `clickhouse::clickhouse.skywalking-showcase`
+
+
+#### VIRTUAL_MQ On ROCKETMQ
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_MQ.service.shortName remove port == ROCKETMQ.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_MQ.service.name: `rocketmq.skywalking-showcase.svc.cluster.local:9876`
+ - ROCKETMQ.service.name: `rocketmq::rocketmq.skywalking-showcase`
+
+#### VIRTUAL_MQ On RABBITMQ
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_MQ.service.shortName remove port == RABBITMQ.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_MQ.service.name: `rabbitmq.skywalking-showcase.svc.cluster.local:5672`
+ - RABBITMQ.service.name: `rabbitmq::rabbitmq.skywalking-showcase`
+ -
+#### VIRTUAL_MQ On KAFKA
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_MQ.service.shortName remove port == KAFKA.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_MQ.service.name: `kafka.skywalking-showcase.svc.cluster.local:9092`
+ - KAFKA.service.name: `kafka::rocketmq.skywalking-showcase`
+
+#### VIRTUAL_MQ On PULSAR
+- Rule name: `lower-short-name-with-fqdn`
+- Groovy script: `{ (u, l) -> u.shortName.substring(0, u.shortName.lastIndexOf(':')) == l.shortName.concat('.svc.cluster.local') }`
+- Description: VIRTUAL_MQ.service.shortName remove port == PULSAR.service.shortName with fqdn suffix
+- Matched Example:
+ - VIRTUAL_MQ.service.name: `pulsar.skywalking-showcase.svc.cluster.local:6650`
+ - PULSAR.service.name: `pulsar::pulsar.skywalking-showcase`
+
+#### MESH On MESH_DP
+- Rule name: `name`
+- Groovy script: `{ (u, l) -> u.name == l.name }`
+- Description: MESH.service.name == MESH_DP.service.name
+- Matched Example:
+ - MESH.service.name: `mesh-svr::songs.sample-services`
+ - MESH_DP.service.name: `mesh-svr::songs.sample-services`
+
+#### MESH On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: MESH.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - MESH.service.name: `mesh-svr::songs.sample-services`
+ - K8S_SERVICE.service.name: `skywalking-showcase::songs.sample-services`
+
+#### MESH_DP On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: MESH_DP.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - MESH_DP.service.name: `mesh-svr::songs.sample-services`
+ - K8S_SERVICE.service.name: `skywalking-showcase::songs.sample-services`
+
+#### MYSQL On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: MYSQL.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - MYSQL.service.name: `mysql::mysql.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::mysql.skywalking-showcase`
+
+#### POSTGRESQL On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: POSTGRESQL.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - POSTGRESQL.service.name: `postgresql::psql.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::psql.skywalking-showcase`
+
+#### CLICKHOUSE On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: CLICKHOUSE.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - CLICKHOUSE.service.name: `clickhouse::clickhouse.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::clickhouse.skywalking-showcase`
+
+#### NGINX On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: NGINX.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - NGINX.service.name: `nginx::nginx.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::nginx.skywalking-showcase`
+
+#### APISIX On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: APISIX.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - APISIX.service.name: `APISIX::frontend.sample-services`
+ - K8S_SERVICE.service.name: `skywalking-showcase::frontend.sample-services`
+
+#### ROCKETMQ On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: ROCKETMQ.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - ROCKETMQ.service.name: `rocketmq::rocketmq.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::rocketmq.skywalking-showcase`
+
+#### RABBITMQ On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: RABBITMQ.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - RABBITMQ.service.name: `rabbitmq::rabbitmq.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::rabbitmq.skywalking-showcase`
+
+#### KAFKA On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: KAFKA.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - KAFKA.service.name: `kafka::kafka.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::kafka.skywalking-showcase`
+
+#### PULSAR On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: PULSAR.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - PULSAR.service.name: `pulsar::pulsar.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::pulsar.skywalking-showcase`
+
+#### SO11Y_OAP On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: SO11Y_OAP.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - SO11Y_OAP.service.name: `demo-oap.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::demo-oap.skywalking-showcase`
+
+#### KONG On K8S_SERVICE
+- Rule name: `short-name`
+- Groovy script: `{ (u, l) -> u.shortName == l.shortName }`
+- Description: KONG.service.shortName == K8S_SERVICE.service.shortName
+- Matched Example:
+ - KONG.service.name: `kong::kong.skywalking-showcase`
+ - K8S_SERVICE.service.name: `skywalking-showcase::kong.skywalking-showcase`
+
+### Build Through Specific Agents
+Use agent tech involved(such as eBPF) and deployment tools(such as operator and agent injector) to detect the service hierarchy relations.
+
+| Upper layer | Lower layer | Agent |
+|-------------|--------------|-------|
+
+
+# Instance Hierarchy
+Instance Hierarchy relationship follows the same definition as Service Hierarchy.
+
+### Automatically Matching
+If the service hierarchy is built, the instance hierarchy relationship could be detected automatically through
+the following rules:
+1. The upper instance name equals the lower instance name.
+2. The upper instance attribute `pod/hostname` equals the lower instance attribute `pod/hostname`.
+3. The upper instance attribute `pod/hostname` equals the lower instance name.
+4. The upper instance name equals the lower instance attribute `pod/hostname`.
+
+### Build Through Specific Agents
diff --git a/docs/en/debugging/config_dump.md b/docs/en/debugging/config_dump.md
new file mode 100644
index 000000000000..c416719c502a
--- /dev/null
+++ b/docs/en/debugging/config_dump.md
@@ -0,0 +1,89 @@
+# Dump Effective Initial Configurations
+
+SkyWalking OAP behaviors could be controlled through hundreds of configurations. It is hard to know what is the final
+configuration as all the configurations could be override by system environments.
+
+The core config file [application.yml](../../../oap-server/server-starter/src/main/resources/application.yml) lists all the configurations
+and their default values. However, it is still hard to know the runtime value.
+
+Dump Effective Initial Configurations API is designed to help users to understand the effective configurations, no matter
+they are initialized in the `application.yml`, or override through system environments.
+- URL, `http://{core restHost}:{core restPort}/debugging/config/dump`
+- HTTP GET method.
+
+```shell
+> curl http://127.0.0.1:12800/debugging/config/dump
+cluster.provider=standalone
+core.provider=default
+core.default.prepareThreads=2
+core.default.restHost=0.0.0.0
+core.default.searchableLogsTags=level,http.status_code
+core.default.role=Mixed
+core.default.persistentPeriod=25
+core.default.syncPeriodHttpUriRecognitionPattern=10
+core.default.restIdleTimeOut=30000
+core.default.dataKeeperExecutePeriod=5
+core.default.topNReportPeriod=10
+core.default.gRPCSslTrustedCAPath=
+core.default.downsampling=[Hour, Day]
+core.default.serviceNameMaxLength=70
+core.default.gRPCSslEnabled=false
+core.default.restPort=12800
+core.default.serviceCacheRefreshInterval=10
+...
+```
+
+All booting configurations with their runtime values are listed, including the selected provider for each module.
+
+This API also provides the response in JSON format, which is more friendly for programmatic usage.
+
+```shell
+> curl -X GET 'http://127.0.0.1:12800/debugging/config/dump' \
+ -H 'Accept: application/json'
+
+// The following JSON is manually formatted for better readability.
+
+{
+ "core.default.autocompleteTagKeysQueryMaxSize":"100",
+ "receiver-sharing-server.default.gRPCPort":"0",
+ "aws-firehose.default.port":"12801",
+ "core.default.restPort":"12800",
+ "receiver-sharing-server.default.gRPCSslCertChainPath":"",
+ "agent-analyzer.default.meterAnalyzerActiveFiles":"datasource,threadpool,satellite,go-runtime,python-runtime,continuous-profiling,java-agent,go-agent",
+ "agent-analyzer.default.traceSamplingPolicySettingsFile":"trace-sampling-policy-settings.yml",
+ "core.default.gRPCSslTrustedCAPath":"",
+ "configuration-discovery.default.disableMessageDigest":"false",
+ "core.default.serviceNameMaxLength":"70",
+ "aws-firehose.default.tlsCertChainPath":"",
+ ....
+}
+```
+
+## Protect The Secrets
+
+Some of the configurations contain sensitive values, such as username, password, token, etc. These values would be
+masked
+in the dump result. For example, the `storage.elasticsearch.password` in the following configurations,
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:elasticsearch}
+ elasticsearch:
+ password: ${SW_ES_PASSWORD:""}
+```
+
+It would be masked and shown as `********` in the dump result.
+
+```shell
+> curl http://127.0.0.1:12800/debugging/config/dump
+...
+storage.elasticsearch.password=********
+...
+```
+
+By default, we mask the config keys through the following configurations.
+
+```yaml
+# Include the list of keywords to filter configurations including secrets. Separate keywords by a comma.
+keywords4MaskingSecretsOfConfig: ${SW_DEBUGGING_QUERY_KEYWORDS_FOR_MASKING_SECRETS:user,password,token,accessKey,secretKey,authentication}
+```
\ No newline at end of file
diff --git a/docs/en/debugging/query-tracing.md b/docs/en/debugging/query-tracing.md
new file mode 100644
index 000000000000..cd824e9242d5
--- /dev/null
+++ b/docs/en/debugging/query-tracing.md
@@ -0,0 +1,802 @@
+# Tracing OAP query
+SkyWalking OAP provides the metrics/trace/log/topology query tracing to help users debug and diagnose the query performance for the SkyWalking backend self.
+
+## Tracing Structure
+- Trace
+
+| Field | Description |
+|-----------|-------------------------------------------------|
+| traceId | The unique ID of the trace |
+| condition | The query conditions |
+| startTime | The start time of the trace. In nanoseconds |
+| endTime | The end time of the trace. In nanoseconds |
+| duration | The operation name of the trace. in nanoseconds |
+| spans | spans in this trace |
+
+- Span
+
+| Field | Description |
+|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| spanId | The unique ID of the span |
+| parentSpanId | The parent span ID of the span |
+| operation | The operation name of the span |
+| startTime | The start time of the span. In nanoseconds, this is a relative time based on different env and implementation |
+| endTime | The end time of the span. In nanoseconds, this is a relative time based on different env and implementation |
+| duration | The duration of the span. In nanoseconds |
+| msg | The message of the span, could include additional info such as request condition and response from the Database or Tags from BanyanDB internal trace |
+| error | The error message of the span, if the span has an error. |
+
+
+## Debugging through HTTP APIs
+The query tracing service is provided within the OAP rest server,
+which could be accessed through HTTP GET `http://{core restHost}:{core restPort}/debugging/query/...`.
+
+### Tracing MQE Execution
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/mqe?{parameters}`.
+- Parameters
+
+| Field | Description | Required |
+|---------------------|-----------------------------------------------------------------------------|--------------------|
+| dumpDBRsp | Dump the response from the database, **support Elasticsearch and BanyanDB** | No, default: false |
+| expression | The MQE query expression | Yes |
+| startTime | The start time of the query | Yes |
+| endTime | The end time of the query | Yes |
+| step | The query step | Yes |
+| coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+| service | The service name | Yes |
+| serviceLayer | The service layer name | Yes |
+| serviceInstance | The service instance name | No |
+| endpoint | The endpoint name | No |
+| process | The process name | No |
+| destService | The destination service name | No |
+| destServiceInstance | The destination service instance name | No |
+| destServiceInstance | The destination service instance name | No |
+| destEndpoint | The destination endpoint name | No |
+| destProcess | The destination process name | No |
+
+The time and step parameters are follow the [Duration](../api/query-protocol.md#duration) format.
+
+- Example
+
+Tracing an avg query with the MQE query expression `avg(service_sla)` from 2024-07-03 to 2024-07-03 with the step DAY for the service `mock_a_service` and the service layer `GENERAL`.
+
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/mqe?dumpDBRsp=true&expression=avg(service_sla)&startTime=2024-07-03&endTime=2024-07-03&step=DAY&service=mock_a_service&serviceLayer=GENERAL'
+```
+
+Response will include query result and the debuggingTrace information:
+
+```yaml
+type: "SINGLE_VALUE"
+results:
+ - metric:
+ labels: []
+ values:
+ - id: null
+ value: "10000"
+ traceID: null
+ doubleValue: 10000.0
+ emptyValue: false
+error: null
+debuggingTrace:
+ traceId: "4f972417-c543-4f7d-a3f1-f5e694cfeb2b"
+ condition: "Expression: avg(service_sla), Entity: Entity(scope=null, serviceName=mock_a_service,\
+ \ normal=true, serviceInstanceName=null, endpointName=null, processName=null,\
+ \ destServiceName=null, destNormal=null, destServiceInstanceName=null, destEndpointName=null,\
+ \ destProcessName=null), Duration: Duration(start=2024-07-03, end=2024-07-03,\
+ \ step=DAY)"
+ startTime: 115828803080350
+ endTime: 115828877400237
+ duration: 74319887
+ rootSpan:
+ spanId: 0
+ parentSpanId: -1
+ operation: "MQE query"
+ startTime: 115828803110686
+ endTime: 115828877396756
+ duration: 74286070
+ msg: null
+ error: null
+ childSpans:
+ - spanId: 1
+ parentSpanId: 0
+ operation: "MQE syntax analysis"
+ startTime: 115828803699331
+ endTime: 115828805015745
+ duration: 1316414
+ msg: null
+ error: null
+ childSpans: []
+ - spanId: 2
+ parentSpanId: 0
+ operation: "MQE Aggregation OP: avg(service_sla)"
+ startTime: 115828805052267
+ endTime: 115828876877134
+ duration: 71824867
+ msg: null
+ error: null
+ childSpans:
+ - spanId: 3
+ parentSpanId: 2
+ operation: "MQE Metric OP: service_sla"
+ startTime: 115828805209453
+ endTime: 115828875634953
+ duration: 70425500
+ msg: null
+ error: null
+ childSpans:
+...
+```
+
+**Note:** if using the SkyWalking native storage [BanyanDB](../setup/backend/storages/banyandb.md),
+the debuggingTrace will include the BanyanDB internal execution trace info, such as:
+```yaml
+...
+childSpans:
+ - spanId: 7
+ parentSpanId: 6
+ operation: "BanyanDB: measure-grpc"
+ startTime: 1720059017222584700
+ endTime: 1720059017223492400
+ duration: 907700
+ msg: "[Tag(key=request, value={\"groups\":[\"measure-default\"], \"\
+ name\":\"service_sla_day\", \"timeRange\":{\"begin\":\"2024-07-02T16:00:00Z\"\
+ , \"end\":\"2024-07-03T16:00:00Z\"}, \"criteria\":{\"condition\"\
+ :{\"name\":\"entity_id\", \"op\":\"BINARY_OP_EQ\", \"value\":{\"\
+ str\":{\"value\":\"bW9ja19hX3NlcnZpY2U=.1\"}}}}, \"tagProjection\"\
+ :{\"tagFamilies\":[{\"name\":\"storage-only\", \"tags\":[\"entity_id\"\
+ ]}]}, \"fieldProjection\":{\"names\":[\"percentage\"]}, \"trace\"\
+ :true})]"
+ error: null
+ childSpans:
+ - spanId: 8
+ parentSpanId: 7
+ operation: "BanyanDB: data-0ebf3a27de83:17912"
+ startTime: 1720059017222821600
+ endTime: 1720059017223473500
+ duration: 651900
+ msg: "[Tag(key=plan, value=IndexScan: startTime=1719936000,endTime=1720022400,Metadata{group=measure-default,name=service_sla_day},conditions=%!s();\
+ \ projection=#storage-only:entity_id; order=OrderBy:\
+ \ [], sort=SORT_UNSPECIFIED; limit=100 Limit: 0, 100)]"
+ error: null
+ childSpans:
+ - spanId: 9
+ parentSpanId: 8
+ operation: "BanyanDB: indexScan-group:\"measure-default\" name:\"\
+ service_sla_day\""
+ startTime: 1720059017222879200
+ endTime: 1720059017223293300
+ duration: 414100
+ msg: "[Tag(key=orderBy, value=time SORT_UNSPECIFIED), Tag(key=details,\
+ \ value=IndexScan: startTime=1719936000,endTime=1720022400,Metadata{group=measure-default,name=service_sla_day},conditions=%!s();\
+ \ projection=#storage-only:entity_id; order=OrderBy:\
+ \ [], sort=SORT_UNSPECIFIED; limit=100)]"
+ error: null
+ childSpans:
+...
+```
+
+### Tracing SkyWalking Trace Query
+
+#### Tracing SkyWalking API queryBasicTraces
+
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/queryBasicTraces?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |--------------------|---------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | service | The service name | Yes |
+ | serviceLayer | The service layer name | Yes |
+ | serviceInstance | The service instance name | No |
+ | endpoint | The endpoint name | No |
+ | minTraceDuration | The minimum duration of the trace | No |
+ | maxTraceDuration | The maximum duration of the trace | No |
+ | traceState | The state of the trace, `ALL`, `SUCCESS`, `ERROR` | Yes |
+ | queryOrder | The order of the query result, `BY_START_TIME`, `BY_DURATION` | Yes |
+ | tags | The tags of the trace, `key1=value1,key2=value2` | No |
+ | pageNum | The page number of the query result | Yes |
+ | pageSize | The page size of the query result | Yes |
+
+The time and step parameters are follow the [Duration](../api/query-protocol.md#duration) format.
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/trace/queryBasicTraces?startTime=2024-06-26%200900&endTime=2024-06-26%200915&step=MINUTE&service=mock_a_service&serviceLayer=GENERAL&serviceInstance=mock_a_service_instance&traceState=ALL&queryOrder=BY_DURATION&pageNum=1&pageSize=15&tags=http.status_code%3D404%2Chttp.method%3Dget'
+```
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+traces:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API queryTrace
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/trace/queryTrace?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |-------------------|---------------------|--------------------|
+ | traceId | The ID of the trace | Yes |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/trace/queryTrace?traceId=8211a1d1-de0f-4485-8766-c88866a8f034'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+spans:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API queryTraceFromColdStage
+Only for BanyanDB, can be used to query the trace in the cold stage.
+
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/trace/queryTraceFromColdStage?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |-----------------|----------------------------------|-----------------|
+ | traceId | The ID of the trace | Yes |
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+
+### Tracing Zipkin Trace Query
+
+#### Tracing Zipkin API /api/v2/traces
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/zipkin/api/v2/traces?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |-------------------|-----------------------------------|--------------------------------|
+ | serviceName | The service name | No |
+ | remoteServiceName | The remote service name | No |
+ | spanName | The span name | No |
+ | annotationQuery | The annotation query | No |
+ | minDuration | The minimum duration of the trace | No |
+ | maxDuration | The maximum duration of the trace | No |
+ | endTs | The end timestamp of the trace | No, default, current timestamp |
+ | lookback | The lookback of the trace query | No, default: 86400000 |
+ | limit | The limit of the trace query | No, default: 10 |
+
+ All parameters are the same as the Zipkin API `/api/v2/traces`.
+
+- Example
+
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/zipkin/api/v2/traces?serviceName=frontend'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+traces:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing /api/v2/trace/{traceId}
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/zipkin/api/v2/trace?{parameters}`
+- Parameters
+
+ | Field | Description | Required |
+ |-------------------|---------------------|--------------------|
+ | traceId | The ID of the trace | Yes |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/zipkin/api/v2/trace?traceId=fcb10b060c6b2492`
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+spans:
+...
+debuggingTrace:
+...
+```
+
+### Tracing Topology Query
+
+#### Tracing SkyWalking API getGlobalTopology
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/topology/getGlobalTopology?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |---------------|-------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | serviceLayer | The service layer name | No |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/topology/getGlobalTopology?startTime=2024-07-03&endTime=2024-07-03&step=DAY&serviceLayer=GENERAL'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+nodes:
+...
+calls:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API getServicesTopology
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/topology/getServicesTopology?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |---------------|-----------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | serviceLayer | The service layer name | Yes |
+ | services | The services names list, separate by comma `mock_a_service, mock_b_service` | Yes |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/topology/getServicesTopology?startTime=2024-07-03&endTime=2024-07-03&step=DAY&serviceLayer=GENERAL&services=mock_a_service%2Cmock_b_service'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+nodes:
+...
+calls:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API getServiceInstanceTopology
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/topology/getServiceInstanceTopology?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |--------------------|-------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | clientService | The client side service name | Yes |
+ | serverService | The server side service name | Yes |
+ | clientServiceLayer | The client side service layer name | Yes |
+ | serverServiceLayer | The server side service layer name | Yes |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/topology/getServiceInstanceTopology?startTime=2024-07-03&endTime=2024-07-03&step=DAY&clientService=mock_a_service&serverService=mock_b_service&clientServiceLayer=GENERAL&serverServiceLayer=GENERAL'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+nodes:
+...
+calls:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API getEndpointDependencies
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/topology/getEndpointDependencies?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |----------------|-------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | service | The service name | Yes |
+ | serviceLayer | The service layer name | Yes |
+ | endpoint | The endpoint name | Yes |
+
+- Example
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/topology/getEndpointDependencies?startTime=2024-07-03&endTime=2024-07-03&step=DAY&service=mock_a_service&serviceLayer=GENERAL&endpoint=%2Fdubbox-case%2Fcase%2Fdubbox-rest%2F404-test'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+nodes:
+...
+calls:
+...
+debuggingTrace:
+...
+```
+
+#### Tracing SkyWalking API getProcessTopology
+- URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/topology/getProcessTopology?{parameters}`.
+- Parameters
+
+ | Field | Description | Required |
+ |--------------|-------------------------------------------------------------------------|----------|
+ | startTime | The start time of the query | Yes |
+ | endTime | The end time of the query | Yes |
+ | step | The query step | Yes |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | service | The service name | Yes |
+ | serviceLayer | The service layer name | Yes |
+ | instance | The instance name | Yes |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/topology/getProcessTopology?startTime=2024-07-03&endTime=2024-07-03&step=DAY&service=mock_a_service&serviceLayer=GENERAL&instance=mock_a_service_instance'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+nodes:
+...
+calls:
+...
+debuggingTrace:
+...
+```
+
+### Tracing Log Query
+
+#### Tracing SkyWalking API queryLogs
+ URL: HTTP GET `http://{core restHost}:{core restPort}/debugging/query/log/queryLogs?{parameters}`.
+ Parameters
+
+ | Field | Description | Required |
+ |----------------------------|-------------------------------------------------------------------------|-------------------------------|
+ | startTime | The start time of the query | Yes, unless traceId not empty |
+ | endTime | The end time of the query | Yes, unless traceId not empty |
+ | step | The query step | Yes, unless traceId not empty |
+ | coldStage | Only for BanyanDB, the flag to query from cold stage, default is false. | No |
+ | service | The service name | No, require serviceLayer |
+ | serviceLayer | The service layer name | No |
+ | serviceInstance | The service instance name | No, require service |
+ | endpoint | The endpoint name | No, require service |
+ | traceId | The trace ID | No |
+ | segmentId | The segment ID | No, require traceId |
+ | spanId | The span ID | No, require traceId |
+ | queryOrder | The order of the query result, `ASC`, `DES` | No, default `DES` |
+ | tags | The tags of the trace, `key1=value1,key2=value2` | No |
+ | pageNum | The page number of the query result | Yes |
+ | pageSize | The page size of the query result | Yes |
+ | keywordsOfContent | The keywords of the log content, `keyword1,keyword2` | No |
+ | excludingKeywordsOfContent | The excluding keywords of the log content, `keyword1,keyword2` | No |
+
+- Example
+```shell
+curl -X GET 'http://127.0.0.1:12800/debugging/query/log/queryLogs?service=e2e-service-provider&serviceLayer=GENERAL&startTime=2024-07-09&endTime=2024-07-09&step=DAY&pageNum=1&pageSize=15&queryOrder=ASC&tags=level%3DINFO'
+```
+
+Response will include query result and the debuggingTrace information, the debuggingTrace information is the same as the MQE query tracing:
+
+```yaml
+logs:
+...
+debuggingTrace:
+...
+```
+
+## Debugging with GraphQL bundled
+When querying the metrics though the [GraphQL APIs](../api/query-protocol.md),
+the query tracing service is also provided within the GraphQL bundled.
+
+### Tracing MQE Execution
+- Bundle API: [Metrics V3 APIs](../api/query-protocol.md#v3-apis)
+
+```graphql
+extend type Query {
+ ...
+ # Param, if debug is true will enable the query tracing and return DebuggingTrace in the ExpressionResult.
+ # Param, if dumpDBRsp is true the database response will dump into the DebuggingTrace span message.
+ execExpression(expression: String!, entity: Entity!, duration: Duration!, debug: Boolean, dumpDBRsp: Boolean): ExpressionResult!
+}
+```
+
+```graphql
+type ExpressionResult {
+ ...
+ debuggingTrace: DebuggingTrace
+}
+```
+
+- Example
+
+Query the metrics using the above condition through the GraphQL and tracing the query:
+```text
+http://127.0.0.1:12800/graphql
+```
+
+```graphql
+{
+ execExpression(expression: "avg(service_sla)", entity: {serviceName: "mock_a_service", normal: true}, duration: {start: "2024-07-03", end: "2024-07-03", step: DAY}, debug: true, dumpDBRsp: true) {
+ type
+ error
+ results {
+ metric {
+ labels {
+ key
+ value
+ }
+ }
+ values {
+ id
+ value
+ traceID
+ }
+ }
+ debuggingTrace {
+ traceId
+ condition
+ startTime
+ endTime
+ duration
+ spans {
+ spanId
+ parentSpanId
+ operation
+ startTime
+ endTime
+ duration
+ msg
+ error
+ }
+ }
+ }
+}
+
+
+```
+Response will include query result and the execTrace information:
+
+```json
+{
+ "data": {
+ "execExpression": {
+ "type": "SINGLE_VALUE",
+ "error": null,
+ "results": [
+ {
+ "metric": {
+ "labels": []
+ },
+ "values": [
+ {
+ "id": null,
+ "value": "10000",
+ "traceID": null
+ }
+ ]
+ }
+ ],
+ "debuggingTrace": {
+ "traceId": "3116ffe3-ee9c-4047-9f22-c135c237aad5",
+ "condition": "Expression: avg(service_sla), Entity: Entity(scope=null, serviceName=mock_a_service, normal=true, serviceInstanceName=null, endpointName=null, processName=null, destServiceName=null, destNormal=null, destServiceInstanceName=null, destEndpointName=null, destProcessName=null), Duration: Duration(start=2024-07-03, end=2024-07-03, step=DAY)",
+ "startTime": 117259274324665,
+ "endTime": 117259279847720,
+ "duration": 5523055,
+ "spans": [
+ {
+ "spanId": 0,
+ "parentSpanId": -1,
+ "operation": "MQE query",
+ "startTime": 117259274328719,
+ "endTime": 117259279846559,
+ "duration": 5517840,
+ "msg": null,
+ "error": null
+ },
+ {
+ "spanId": 1,
+ "parentSpanId": 0,
+ "operation": "MQE syntax analysis",
+ "startTime": 117259274333084,
+ "endTime": 117259274420159,
+ "duration": 87075,
+ "msg": null,
+ "error": null
+ },
+ {
+ "spanId": 2,
+ "parentSpanId": 0,
+ "operation": "MQE Aggregation OP: avg(service_sla)",
+ "startTime": 117259274433533,
+ "endTime": 117259279812549,
+ "duration": 5379016,
+ "msg": null,
+ "error": null
+ },
+...
+ ]
+ }
+ }
+ }
+}
+```
+**Note:** if using the SkyWalking native storage [BanyanDB](../setup/backend/storages/banyandb.md),
+the debuggingTrace will include the BanyanDB internal execution trace info, such as:
+```json
+...
+{
+ "spanId": 7,
+ "parentSpanId": 6,
+ "operation": "BanyanDB: measure-grpc",
+ "startTime": 1720060447687765300,
+ "endTime": 1720060447688830200,
+ "duration": 1064900,
+ "msg": "[Tag(key=request, value={\"groups\":[\"measure-default\"], \"name\":\"service_sla_day\", \"timeRange\":{\"begin\":\"2024-07-02T16:00:00Z\", \"end\":\"2024-07-03T16:00:00Z\"}, \"criteria\":{\"condition\":{\"name\":\"entity_id\", \"op\":\"BINARY_OP_EQ\", \"value\":{\"str\":{\"value\":\"bW9ja19hX3NlcnZpY2U=.1\"}}}}, \"tagProjection\":{\"tagFamilies\":[{\"name\":\"storage-only\", \"tags\":[\"entity_id\"]}]}, \"fieldProjection\":{\"names\":[\"percentage\"]}, \"trace\":true})]",
+ "error": null
+},
+{
+"spanId": 8,
+"parentSpanId": 7,
+"operation": "BanyanDB: data-0ebf3a27de83:17912",
+"startTime": 1720060447687956700,
+"endTime": 1720060447688810000,
+"duration": 853300,
+"msg": "[Tag(key=plan, value=IndexScan: startTime=1719936000,endTime=1720022400,Metadata{group=measure-default,name=service_sla_day},conditions=%!s(); projection=#storage-only:entity_id; order=OrderBy: [], sort=SORT_UNSPECIFIED; limit=100 Limit: 0, 100)]",
+"error": null
+},
+{
+"spanId": 9,
+"parentSpanId": 8,
+"operation": "BanyanDB: indexScan-group:\"measure-default\" name:\"service_sla_day\"",
+"startTime": 1720060447687997400,
+"endTime": 1720060447688664700,
+"duration": 667300,
+"msg": "[Tag(key=orderBy, value=time SORT_UNSPECIFIED), Tag(key=details, value=IndexScan: startTime=1719936000,endTime=1720022400,Metadata{group=measure-default,name=service_sla_day},conditions=%!s(); projection=#storage-only:entity_id; order=OrderBy: [], sort=SORT_UNSPECIFIED; limit=100)]",
+"error": null
+},
+{
+"spanId": 10,
+"parentSpanId": 9,
+"operation": "BanyanDB: seriesIndex.Search",
+"startTime": 1720060447688023800,
+"endTime": 1720060447688101800,
+"duration": 78000,
+"msg": "[]",
+"error": null
+},
+...
+```
+
+### Tracing SkyWalking Trace Query
+
+#### Tracing SkyWalking API queryBasicTraces
+- Bundle API: [Trace](../api/query-protocol.md#trace)
+
+```graphql
+# Param, if debug is true will enable the query tracing and return DebuggingTrace in the result.
+extend type Query {
+ # Search segment list with given conditions
+ queryBasicTraces(condition: TraceQueryCondition, debug: Boolean): TraceBrief
+ # Read the specific trace ID with given trace ID
+ queryTrace(traceId: ID!, debug: Boolean): Trace
+...
+}
+```
+
+```graphql
+# The list of traces
+type TraceBrief {
+...
+ #For OAP internal query debugging
+ debuggingTrace: DebuggingTrace
+}
+
+# The trace represents a distributed trace, includes all segments and spans.
+type Trace {
+...
+ #For OAP internal query debugging
+ debuggingTrace: DebuggingTrace
+}
+```
+
+- Example
+
+Same as the MQE query tracing, follow the GraphQL protocol and grammar to query the result and get debuggingTrace information,
+just enable the debug parameter to true.
+
+### Tracing Topology Query
+- Bundle API: [Topology](../api/query-protocol.md#topology)
+
+```graphql
+# Param, if debug is true will enable the query tracing and return DebuggingTrace in the result.
+extend type Query {
+ # Query the global topology
+ # When layer is specified, the topology of this layer would be queried
+ getGlobalTopology(duration: Duration!, layer: String, debug: Boolean): Topology
+ # Query the topology, based on the given service
+ getServiceTopology(serviceId: ID!, duration: Duration!, debug: Boolean): Topology
+ # Query the topology, based on the given services.
+ # `#getServiceTopology` could be replaced by this.
+ getServicesTopology(serviceIds: [ID!]!, duration: Duration!, debug: Boolean): Topology
+ # Query the instance topology, based on the given clientServiceId and serverServiceId
+ getServiceInstanceTopology(clientServiceId: ID!, serverServiceId: ID!, duration: Duration!, debug: Boolean): ServiceInstanceTopology
+...
+ # v2 of getEndpointTopology
+ getEndpointDependencies(endpointId: ID!, duration: Duration!, debug: Boolean): EndpointTopology
+ # Query the topology, based on the given instance
+ getProcessTopology(serviceInstanceId: ID!, duration: Duration!, debug: Boolean): ProcessTopology
+}
+```
+
+```graphql
+# The overview topology of the whole application cluster or services,
+type Topology {
+ nodes: [Node!]!
+ calls: [Call!]!
+ debuggingTrace: DebuggingTrace
+}
+
+# The instance topology based on the given serviceIds
+type ServiceInstanceTopology {
+ nodes: [ServiceInstanceNode!]!
+ calls: [Call!]!
+ debuggingTrace: DebuggingTrace
+}
+
+# The endpoint topology
+type EndpointTopology {
+ nodes: [EndpointNode!]!
+ calls: [Call!]!
+ debuggingTrace: DebuggingTrace
+}
+
+# The process topology
+type ProcessTopology {
+ nodes: [ProcessNode!]!
+ calls: [Call!]!
+ debuggingTrace: DebuggingTrace
+}
+```
+
+- Example
+Same as the MQE query tracing, follow the GraphQL protocol and grammar to query the result and get debuggingTrace information,
+just enable the debug parameter to true.
+
+### Tracing Log Query
+- Bundle API: [Log](../api/query-protocol.md#logs)
+
+```graphql
+extend type Query {
+...
+ queryLogs(condition: LogQueryCondition, debug: Boolean): Logs
+...
+}
+```
+
+```graphql
+type Logs {
+ # When this field is not empty, frontend should display it in UI
+ errorReason: String
+ logs: [Log!]!
+ debuggingTrace: DebuggingTrace
+}
+```
+
+- Example
+Same as the MQE query tracing, follow the GraphQL protocol and grammar to query the result and get debuggingTrace information,
+just enable the debug parameter to true.
diff --git a/docs/en/guides/Component-library-settings.md b/docs/en/guides/Component-library-settings.md
new file mode 100644
index 000000000000..a27df6eeb8ba
--- /dev/null
+++ b/docs/en/guides/Component-library-settings.md
@@ -0,0 +1,99 @@
+# Component library settings
+Component library settings are about your own or third-party libraries used in the monitored application.
+
+In agent or SDK, regardless of whether the library name is collected as ID or String (literally, e.g. SpringMVC), the collector
+formats data in ID for better performance and less storage requirements.
+
+Also, the collector conjectures the remote service based on the component library. For example: if
+the component library is MySQL Driver library, then the remote service should be MySQL Server.
+
+For these two reasons, the collector requires two parts of settings in this file:
+1. Component library ID, names and languages.
+1. Remote server mapping based on the local library.
+
+**All component names and IDs must be defined in this file.**
+
+## Component Library ID
+Define all names and IDs from component libraries which are used in the monitored application.
+This uses a two-way mapping strategy. The agent or SDK could use the value (ID) to represent the component name in uplink data.
+
+- Name: the component name used in agent and UI
+- ID: Unique ID. All IDs are reserved once they are released.
+- Languages: Program languages may use this component. Multi languages should be separated by `,`.
+
+### ID rules
+- Java and multi languages shared: (0, 3000)
+- .NET Platform reserved: [3000, 4000)
+- Node.js Platform reserved: [4000, 5000)
+- Go reserved: [5000, 6000)
+- Lua reserved: [6000, 7000)
+- Python reserved: [7000, 8000)
+- PHP reserved: [8000, 9000)
+- C++ reserved: [9000, 10000)
+- Javascript reserved: [10000, 11000)
+- Rust reserved: [11000, 12000)
+
+Example:
+```yaml
+Tomcat:
+ id: 1
+ languages: Java
+HttpClient:
+ id: 2
+ languages: Java,C#,Node.js
+Dubbo:
+ id: 3
+ languages: Java
+H2:
+ id: 4
+ languages: Java
+```
+
+## Component Library Priority
+Component ID priority represents the component is degree of closeness between the library and business codes
+The higher the atomic number, the higher the priority, which mean it is closer to the business codes,
+further away from OS kernel or general Computer Science concept.
+
+The range of priorities is [0, 100], both sided included. 0 is the lowest priority.
+To keep forward compatibility, the default(when not set) priority is 50.
+
+For example, a typical priority sequence is TCP < TLS(TCP) < RPC < HTTP < HTTPS < gRPC/SpringMVC/Dubbo
+
+Example:
+```yaml
+Unknown:
+ id: 0
+ language: All
+ priority: 0
+tcp:
+ id: 110
+ languages: Java
+ priority: 10
+https:
+ id: 129
+ languages: ebpf
+ priority: 46
+tls:
+ id: 130
+ languages: ebpf, mesh
+ priority: 11
+```
+
+## Remote server mapping
+The remote server will be conjectured by the local component. The mappings are based on names in the component library.
+
+- Key: client component library name
+- Value: server component name
+
+```yaml
+Component-Server-Mappings:
+ Jedis: Redis
+ StackExchange.Redis: Redis
+ Redisson: Redis
+ Lettuce: Redis
+ Zookeeper: Zookeeper
+ SqlClient: SqlServer
+ Npgsql: PostgreSQL
+ MySqlConnector: Mysql
+ EntityFrameworkCore.InMemory: InMemoryDatabase
+```
diff --git a/docs/en/guides/How-to-build.md b/docs/en/guides/How-to-build.md
new file mode 100644
index 000000000000..ed2200193f54
--- /dev/null
+++ b/docs/en/guides/How-to-build.md
@@ -0,0 +1,88 @@
+# How to build a project
+This document will help you compile and build a project in your maven and set your IDE.
+
+## Building the Project
+**Since we are using Git submodule, we do not recommend using the `GitHub` tag or release page to download source codes for compiling.**
+
+### Maven behind the Proxy
+If you need to execute build behind the proxy, edit the *.mvn/jvm.config* and set the follow properties:
+```properties
+-Dhttp.proxyHost=proxy_ip
+-Dhttp.proxyPort=proxy_port
+-Dhttps.proxyHost=proxy_ip
+-Dhttps.proxyPort=proxy_port
+-Dhttp.proxyUser=username
+-Dhttp.proxyPassword=password
+```
+
+### Building from GitHub
+1. Prepare git, JDK 11, 17, 21 (LTS versions), and Maven 3.6+.
+1. Clone the project.
+
+ If you want to build a release from source codes, set a `tag name` by using `git clone -b [tag_name] ...` while cloning.
+
+ ```bash
+ git clone --recurse-submodules https://github.com/apache/skywalking.git
+ cd skywalking/
+
+ OR
+
+ git clone https://github.com/apache/skywalking.git
+ cd skywalking/
+ git submodule init
+ git submodule update
+ ```
+
+1. Run `./mvnw clean package -Dmaven.test.skip`
+1. All packages are in `/dist` (.tar.gz for Linux and .zip for Windows).
+
+### Building from Apache source code release
+- What is the `Apache source code release`?
+
+For each official Apache release, there is a complete and independent source code tar, which includes all source codes. You could download it from [SkyWalking Apache download page](http://skywalking.apache.org/downloads/). There is no requirement related to git when compiling this. Just follow these steps.
+
+1. Prepare JDK11+ and Maven 3.6+.
+1. Run `./mvnw clean package -Dmaven.test.skip`.
+1. All packages are in `/dist`.(.tar.gz for Linux and .zip for Windows).
+
+### Advanced compiling
+SkyWalking is a complex maven project that has many modules. Therefore, the time to compile may be a bit longer than usual.
+If you just want to recompile part of the project, you have the following options:
+- Compile backend and package
+> ./mvnw package -Pbackend,dist
+
+or
+
+> make build.backend
+
+If you intend to compile a single plugin, such as one in the dev stage, you could
+> cd plugin_module_dir & mvn clean package
+
+- Compile UI and package
+> ./mvnw package -Pui,dist
+
+or
+
+> make build.ui
+
+
+### Building docker images
+You can build docker images of `backend` and `ui` with `Makefile` located in root folder.
+
+Refer to [Build docker image](../../../docker) for more details.
+
+## Setting up your IntelliJ IDEA
+**NOTE**: If you clone the codes from GitHub, please make sure that you have finished steps 1 to 3 in section **[Build from GitHub](#building-from-github)**. If you download the source codes from the official website of SkyWalking, please make sure that you have followed the steps in section **[Build from Apache source code release](#building-from-apache-source-code-release)**.
+
+1. Import the project as a maven project.
+1. Run `./mvnw compile -Dmaven.test.skip=true` to compile project and generate source codes. The reason is that we use gRPC and protobuf.
+1. Set **Generated Source Codes** folders.
+ * `grpc-java` and `java` folders in **apm-protocol/apm-network/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/server-core/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/server-receiver-plugin/receiver-proto/target/generated-sources/fbs**
+ * `grpc-java` and `java` folders in **oap-server/server-receiver-plugin/receiver-proto/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/exporter/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/server-configuration/grpc-configuration-sync/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/server-alarm-plugin/target/generated-sources/protobuf**
+ * `grpc-java` and `java` folders in **oap-server/server-fetcher-plugin/fetcher-proto/target/generated-sources/protobuf**
+ * `antlr4` folder in **oap-server/oal-grammar/target/generated-sources**
diff --git a/docs/en/guides/How-to-bump-up-zipkin.md b/docs/en/guides/How-to-bump-up-zipkin.md
new file mode 100644
index 000000000000..3fd931e4f14a
--- /dev/null
+++ b/docs/en/guides/How-to-bump-up-zipkin.md
@@ -0,0 +1,81 @@
+# How to bump up Zipkin Lens dependency
+
+Because SkyWalking embeds Zipkin Lens UI as a part of the SkyWalking UI, and Zipkin Lens UI contains
+a lot of other front-end dependencies that we also distribute in SkyWalking binary tars, so we have
+to take care of the dependencies' licenses when we bump up the Zipkin Lens dependency.
+
+Make sure to do the following steps when you bump up the Zipkin Lens dependency:
+
+- Clone the Zipkin project into a directory.
+
+```shell
+ZIPKIN_VERSION=
+git clone https://github.com/openzipkin/zipkin && cd zipkin
+git checkout $ZIPKIN_VERSION
+
+cd zipkin-lens
+```
+
+- Create `.licenserc.yaml` with the following content.
+
+```shell
+cat > .licenserc.yaml << EOF
+header:
+ license:
+ spdx-id: Apache-2.0
+ copyright-owner: Apache Software Foundation
+dependency:
+ files:
+ - package.json
+ licenses:
+ - name: cli-table
+ version: 0.3.1
+ license: MIT
+ - name: domutils
+ version: 1.5.1
+ license: BSD-2-Clause
+ - name: rework
+ version: 1.0.1
+ license: MIT
+EOF
+```
+
+- Create license template `LICENSE.tpl` with the following content.
+
+```
+{{ range .Groups }}
+========================================================================
+{{ .LicenseID }} licenses
+========================================================================
+The following components are provided under the {{ .LicenseID }} License. See project link for details.
+{{- if eq .LicenseID "Apache-2.0" }}
+The text of each license is the standard Apache 2.0 license.
+{{- else }}
+The text of each license is also included in licenses/LICENSE-[project].txt.
+{{ end }}
+
+ {{- range .Deps }}
+ https://npmjs.com/package/{{ .Name }}/v/{{ .Version }} {{ .Version }} {{ .LicenseID }}
+ {{- end }}
+{{ end }}
+```
+
+- Make sure you're using the supported NodeJS version and NPM version.
+
+```shell
+node -v
+# should be v14.x.x
+npm -v
+# should be 6.x.x
+```
+
+- Run the following command to generate the license file.
+
+```shell
+license-eye dependency resolve --summary LICENSE.tpl
+```
+
+- Copy the generated file `LICENSE` to replace the `zipkin-LICENSE` in SkyWalking repo.
+
+Note: if there are dependencies that license-eye failed to identify the license, you should manually
+identify the license and add it to the step above in `.licenserc.yaml`.
diff --git a/docs/en/guides/How-to-release.md b/docs/en/guides/How-to-release.md
new file mode 100644
index 000000000000..4bee867f0df5
--- /dev/null
+++ b/docs/en/guides/How-to-release.md
@@ -0,0 +1,205 @@
+Apache SkyWalking release guide
+--------------------
+If you're a committer, you can learn how to release SkyWalking in The Apache Way and start the voting process by reading this document.
+
+
+## Prerequisites
+Add your GPG public key into the [SkyWalking GPG KEYS](https://dist.apache.org/repos/dist/release/skywalking/KEYS) file.
+- If you are a PMC member, use your Apache ID and password to log in this svn, and update the file. **Don't override the existing file.**
+- If you are a committer, please ask a PMC member to help you.
+
+## Create artifacts for the release
+
+- Create a new empty folder to do the release work.
+- Set the version numbers and run the release script file [`tools/releasing/create_release_tars.sh`](https://github.com/apache/skywalking/blob/master/tools/releasing/create_release_tars.sh)
+
+```bash
+export RELEASE_VERSION=x.y.z # (example: RELEASE_VERSION=10.1.0)
+export NEXT_RELEASE_VERSION=x.y.z # (example: NEXT_RELEASE_VERSION=10.2.0)
+curl -Ls https://raw.githubusercontent.com/apache/skywalking/refs/heads/master/tools/releasing/create_release_tars.sh | bash -
+```
+
+After all the steps are completed, you will have the following files in the folder:
+
+```text
+apache-skywalking-apm-${RELEASE_VERSION}-bin.tar.gz
+apache-skywalking-apm-${RELEASE_VERSION}-bin.tar.gz.asc
+apache-skywalking-apm-${RELEASE_VERSION}-bin.tar.gz.sha512
+apache-skywalking-apm-${RELEASE_VERSION}-src.tar.gz
+apache-skywalking-apm-${RELEASE_VERSION}-src.tar.gz.asc
+apache-skywalking-apm-${RELEASE_VERSION}-src.tar.gz.sha512
+```
+
+## Start the next iteration
+
+Once the binary and source packages are created, you can start updating the version to the next number and open a pull request.
+
+```bash
+curl -Ls https://raw.githubusercontent.com/apache/skywalking/refs/heads/master/tools/releasing/start_next_version.sh | bash -
+```
+
+## Upload to Apache svn
+1. Use your Apache ID to log in to `https://dist.apache.org/repos/dist/dev/skywalking/`.
+1. Create a folder and name it by the release version and round, such as: `x.y.z`
+1. Upload the source code package to the folder with files ending with `.asc` and `.sha512`.
+ * Package name: `apache-skywalking-x.y.z-src.tar.gz`
+ * See Section "Build and sign the source code package" for more details
+1. Upload the distribution package to the folder with files ending with `.asc` and `.sha512`.
+ * Package name: `apache-skywalking-bin-x.y.z.tar.gz`.
+ * Create a `.sha512` package: `shasum -a 512 file > file.sha512`
+
+## Call a vote in dev
+Call a vote in `dev@skywalking.apache.org`
+
+```
+Mail title: [VOTE] Release Apache SkyWalking version x.y.z
+
+Mail content:
+Hi All,
+This is a call for vote to release Apache SkyWalking version x.y.z.
+
+Release notes:
+
+ * https://github.com/apache/skywalking/blob/master/docs/en/changes/changes-x.y.z.md
+
+Release Candidate:
+
+ * https://dist.apache.org/repos/dist/dev/skywalking/xxxx
+ * sha512 checksums
+ - sha512xxxxyyyzzz apache-skywalking-apm-x.x.x-src.tgz
+ - sha512xxxxyyyzzz apache-skywalking-apm-bin-x.x.x.tar.gz
+
+Release Tag :
+
+ * (Git Tag) vx.y.z
+
+Release CommitID :
+
+ * https://github.com/apache/skywalking/tree/(Git Commit ID)
+ * Git submodule
+ * skywalking-ui: https://github.com/apache/skywalking-booster-ui/tree/(Git Commit ID)
+ * apm-protocol/apm-network/src/main/proto: https://github.com/apache/skywalking-data-collect-protocol/tree/(Git Commit ID)
+ * oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol https://github.com/apache/skywalking-query-protocol/tree/(Git Commit ID)
+
+Keys to verify the Release Candidate :
+
+ * https://dist.apache.org/repos/dist/release/skywalking/KEYS
+
+Guide to build the release from source :
+
+ * https://github.com/apache/skywalking/blob/vx.y.z/docs/en/guides/How-to-build.md
+
+Voting will start now (xxxx date) and will remain open for at least 72 hours, Request all PMC members to give their vote.
+[ ] +1 Release this package.
+[ ] +0 No opinion.
+[ ] -1 Do not release this package because....
+```
+
+## Vote Check
+All PMC members and committers should check these before casting +1 votes.
+
+1. Features test.
+1. Source code and distribution package (`apache-skywalking-x.y.z-src.tar.gz`, `apache-skywalking-bin-x.y.z.tar.gz`, `apache-skywalking-bin-x.y.z.zip`)
+are found in `https://dist.apache.org/repos/dist/dev/skywalking/x.y.z` with `.asc` and `.sha512`.
+1. `LICENSE` and `NOTICE` are in the source code and distribution package.
+1. Check `shasum -c apache-skywalking-apm-x.y.z-src.tgz.sha512`.
+1. Check `gpg --verify apache-skywalking-apm-x.y.z-src.tgz.asc apache-skywalking-apm-x.y.z-src.tgz`
+1. Build a distribution package from the source code package (`apache-skywalking-x.y.z-src.tar.gz`) by following this [doc](https://github.com/apache/skywalking/blob/master/docs/en/guides/How-to-build.md#build-from-apache-source-code-release).
+1. Check the Apache License Header. Run `docker run --rm -v $(pwd):/github/workspace apache/skywalking-eyes header check`. (No binaries in source codes)
+
+
+The voting process is as follows:
+1. All PMC member votes are +1 binding, and all other votes are +1 but non-binding.
+1. If you obtain at least 3 (+1 binding) votes with more +1 than -1 votes within 72 hours, the release will be approved.
+
+
+## Publish the release
+1. Move source codes tar and distribution packages to `https://dist.apache.org/repos/dist/release/skywalking/`.
+```
+> export SVN_EDITOR=vim
+> svn mv https://dist.apache.org/repos/dist/dev/skywalking/x.y.z https://dist.apache.org/repos/dist/release/skywalking
+....
+enter your apache password
+....
+
+```
+2. Public download source and distribution tar/zip with asc and sha512 are located in `http://www.apache.org/dyn/closer.cgi/skywalking/x.y.z/xxx`.
+The Apache mirror path is the only release information that we publish.
+3. Update the website download page. http://skywalking.apache.org/downloads/ . Add a new download source, distribution, sha512, asc, and document
+links. The links can be found following rules (3) to (6) above.
+4. Add a release event on the website homepage and event page. Announce the public release with changelog or key features.
+5. Send ANNOUNCE email to `dev@skywalking.apache.org`, `announce@apache.org`. The sender should use the Apache email account.
+```
+Mail title: [ANNOUNCE] Apache SkyWalking x.y.z released
+
+Mail content:
+Hi all,
+
+Apache SkyWalking Team is glad to announce the first release of Apache SkyWalking x.y.z.
+
+SkyWalking: APM (application performance monitor) tool for distributed systems,
+especially designed for microservices, cloud native and container-based architectures.
+
+This release contains a number of new features, bug fixes and improvements compared to
+version a.b.c(last release). The notable changes since x.y.z include:
+
+(Highlight key changes)
+1. ...
+2. ...
+3. ...
+
+Please refer to the change log for the complete list of changes:
+https://skywalking.apache.org/docs/main/vx.y.z/en/changes/changes/
+
+Apache SkyWalking website:
+http://skywalking.apache.org/
+
+Downloads:
+https://skywalking.apache.org/downloads/#SkyWalkingAPM
+
+Twitter:
+https://twitter.com/ASFSkyWalking
+
+SkyWalking Resources:
+- GitHub: https://github.com/apache/skywalking
+- Issue: https://github.com/apache/skywalking/issues
+- Mailing list: dev@skywalkiing.apache.org
+
+
+- Apache SkyWalking Team
+```
+
+## Publish the Docker images
+
+We have a [GitHub workflow](../../../.github/workflows/publish-docker.yaml) to automatically publish the Docker images to
+Docker Hub after you set the version from `pre-release` to `release`, all you need to do is to watch that workflow and see
+whether it succeeds, if it fails, you can use the following steps to publish the Docker images in your local machine.
+
+```shell
+export SW_VERSION=x.y.z
+git clone --depth 1 --branch v$SW_VERSION https://github.com/apache/skywalking.git
+cd skywalking
+
+svn co https://dist.apache.org/repos/dist/release/skywalking/$SW_VERSION release # (1)
+
+export CONTEXT=release
+export HUB=apache
+export OAP_NAME=skywalking-oap-server
+export UI_NAME=skywalking-ui
+export TAG=$SW_VERSION
+export DIST=
+make docker.push
+```
+
+## Clean up the old releases
+Once the latest release has been published, you should clean up the old releases from the mirror system.
+1. Update the download links (source, dist, asc, and sha512) on the website to the archive repo (https://archive.apache.org/dist/skywalking).
+2. Remove previous releases from https://dist.apache.org/repos/dist/release/skywalking/.
+
+## Update the Quick Start Versions
+
+We hosted the [SkyWalking Quick Start script](https://skywalking.apache.org/docs/main/latest/en/setup/backend/backend-docker/#start-the-storage-oap-and-booster-ui-with-docker-compose),
+which is a shell script that helps users to download and start SkyWalking quickly.
+The versions of OAP and BanyanDB are hard-coded in the script, so you need to update the versions in the script.
+
+Update the versions for [shell script](https://github.com/apache/skywalking-website/blob/master/content/quickstart-docker.sh#L23-L24) and [powershell script](https://github.com/apache/skywalking-website/blob/master/content/quickstart-docker.ps1#L18-L19).
diff --git a/docs/en/guides/IT-guide.md b/docs/en/guides/IT-guide.md
new file mode 100644
index 000000000000..b5317e14b52f
--- /dev/null
+++ b/docs/en/guides/IT-guide.md
@@ -0,0 +1,20 @@
+# Integration Tests
+IT(Integration Tests) represents the JUnit driven integration test to verify the features and compatibility between lib
+and known server with various versions.
+
+After setting up the environment and writing your codes, to facilitate integration with the SkyWalking project, you'll
+need to run tests locally to verify that your codes would not break any existing features,
+as well as write some unit test (UT) codes to verify that the new codes would work well. This will prevent them from being broken by future contributors.
+If the new codes involve other components or libraries, you should also write integration tests (IT).
+
+SkyWalking leverages the plugin `maven-surefire-plugin` to run the UTs and uses `maven-failsafe-plugin`
+to run the ITs. `maven-surefire-plugin` excludes ITs (whose class name starts or ends with `*IT`, `IT*`)
+and leaves them for `maven-failsafe-plugin` to run, which is bound to the `integration-test` goal.
+Therefore, to run the UTs, try `./mvnw clean test`, which only runs the UTs but not the ITs.
+
+If you would like to run the ITs, please run `./mvnw integration-test` as well as the profiles of the modules whose ITs you want to run.
+If you don't want to run UTs, please add `-DskipUTs=true`.
+E.g. if you would like to only run the ITs in `oap-server`, try `./mvnw -Pbackend clean verify -DskipUTs=true`,
+and if you would like to run all the ITs, simply run `./mvnw clean integration-test -DskipUTs=true`.
+
+Please be advised that if you're writing integration tests, name it with the pattern `IT*` or `*IT` so they would only run in goal `integration-test`.
diff --git a/docs/en/guides/asf/committer.md b/docs/en/guides/asf/committer.md
new file mode 100644
index 000000000000..55340fe2a08f
--- /dev/null
+++ b/docs/en/guides/asf/committer.md
@@ -0,0 +1,153 @@
+# Apache SkyWalking committer
+SkyWalking Project Management Committee (PMC) is responsible for assessing the contributions of candidates.
+
+Like many Apache projects, SkyWalking welcome all contributions, including code contributions, blog entries, guides for new users, public speeches, and enhancement of the project in various ways.
+
+## Committer
+### Nominate new committer
+In SkyWalking, **new committer nomination** could only be officially started by existing PMC members. If a new committer feels that he/she is qualified, he/she should contact any existing PMC member and discuss. If this is agreed among some members of the PMC, the process will kick off.
+
+The following steps are recommended (to be initiated only by an existing PMC member):
+1. Send an email titled `[DISCUSS] Promote xxx as new committer` to `private@skywalking.a.o`. List the important contributions of the candidate,
+so you could gather support from other PMC members for your proposal.
+1. Keep the discussion open for more than 3 days but no more than 1 week, unless there is any express objection or concern.
+1. If the PMC generally agrees to the proposal, send an email titled `[VOTE] Promote xxx as new committer` to `private@skywalking.a.o`.
+1. Keep the voting process open for more than 3 days, but no more than 1 week. Consider the result as `Consensus Approval` if there are three +1 votes and
++1 votes > -1 votes.
+1. Send an email titled `[RESULT][VOTE] Promote xxx as new committer` to `private@skywalking.a.o`, and list the voting details, including who the voters are.
+
+### Invite new committer
+The PMC member who starts the promotion is responsible for sending an invitation to the new committer and guiding him/her to set up the ASF env.
+
+The PMC member should send an email using the following template to the new committer:
+```
+To: JoeBloggs@foo.net
+Cc: private@skywalking.apache.org
+Subject: Invitation to become SkyWalking committer: Joe Bloggs
+
+Hello [invitee name],
+
+The SkyWalking Project Management Committee] (PMC)
+hereby offers you committer privileges to the project. These privileges are
+offered on the understanding that you'll use them
+reasonably and with common sense. We like to work on trust
+rather than unnecessary constraints.
+
+Being a committer enables you to more easily make
+changes without needing to go through the patch
+submission process.
+
+Being a committer does not require you to
+participate any more than you already do. It does
+tend to make one even more committed. You will
+probably find that you spend more time here.
+
+Of course, you can decline and instead remain as a
+contributor, participating as you do now.
+
+A. This personal invitation is a chance for you to
+accept or decline in private. Either way, please
+let us know in reply to the [private@skywalking.apache.org]
+address only.
+
+B. If you accept, the next step is to register an iCLA:
+ 1. Details of the iCLA and the forms are found
+ through this link: http://www.apache.org/licenses/#clas
+
+ 2. Instructions for its completion and return to
+ the Secretary of the ASF are found at
+ http://www.apache.org/licenses/#submitting
+
+ 3. When you transmit the completed iCLA, request
+ to notify the Apache SkyWalking and choose a
+ unique Apache id. Look to see if your preferred
+ id is already taken at
+ http://people.apache.org/committer-index.html
+ This will allow the Secretary to notify the PMC
+ when your iCLA has been recorded.
+
+When recording of your iCLA is noticed, you will
+receive a follow-up message with the next steps for
+establishing you as a committer.
+```
+
+### Invitation acceptance process
+The new committer should reply to `private@skywalking.apache.org` (choose `reply all`), and express his/her intention to accept the invitation.
+Then, this invitation will be treated as accepted by the project's PMC. Of course, the new committer may also choose to decline the invitation.
+
+Once the invitation has been accepted, the new committer has to take the following steps:
+1. Subscribe to `dev@skywalking.apache.org`. Usually this is already done.
+1. Choose a Apache ID that is not on the [apache committers list page](http://people.apache.org/committer-index.html).
+1. Download the [ICLA](https://www.apache.org/licenses/icla.pdf) (If the new committer contributes to the project as a day job, [CCLA](http://www.apache.org/licenses/cla-corporate.pdf) is expected).
+1. After filling in the `icla.pdf` (or `ccla.pdf`) with the correct information, print, sign it by hand, scan it as an PDF, and send it as an attachment to [secretary@apache.org](mailto:secretary@apache.org). (If electronic signature is preferred, please follow the steps on [this page](http://www.apache.org/licenses/contributor-agreements.html#submitting))
+1. The PMC will wait for the Apache secretary to confirm the ICLA (or CCLA) filed. The new committer and PMC will receive the following email:
+
+```
+Dear XXX,
+
+This message acknowledges receipt of your ICLA, which has been filed in the Apache Software Foundation records.
+
+Your account has been requested for you and you should receive email with next steps
+within the next few days (can take up to a week).
+
+Please refer to https://www.apache.org/foundation/how-it-works.html#developers
+for more information about roles at Apache.
+```
+
+In the unlikely event that the account has not yet been requested, the PMC member should contact the project V.P..
+The V.P. could request through the [Apache Account Submission Helper Form](https://whimsy.apache.org/officers/acreq).
+
+After several days, the new committer will receive an email confirming creation of the account, titled `Welcome to the Apache Software Foundation (ASF)!`.
+Congratulations! The new committer now has an official Apache ID.
+
+The PMC member should add the new committer to the official committer list through [roster](https://whimsy.apache.org/roster/committee/skywalking).
+
+### Set up the Apache ID and dev env
+1. Go to [Apache Account Utility Platform](https://id.apache.org/), create your password, set up your personal mailbox (`Forwarding email address`) and GitHub account(`Your GitHub Username`). An organizational invite will be sent to you via email shortly thereafter (within 2 hours).
+1. If you would like to use the `xxx@apache.org` email service, please refer to [here](https://infra.apache.org/committer-email.html). Gmail is recommended, because this forwarding mode is not easy to find in most mailbox service settings.
+1. Follow the [authorized GitHub 2FA wiki](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app) to enable two-factor authorization (2FA) on [Github](http://github.com/). When you set 2FA to "off", it will be delisted by the corresponding Apache committer write permission group until you set it up again. (**NOTE: Treat your recovery codes with the same level of attention as you would your password!**)
+1. Use [GitBox Account Linking Utility](https://gitbox.apache.org/setup/) to obtain write permission of the SkyWalking project.
+1. Follow this [doc](https://github.com/apache/skywalking-website#how-to-add-a-new-committer) to update the website.
+
+If you would like to show up publicly in the Apache GitHub org, you need to go to the [Apache GitHub org people page](https://github.com/orgs/apache/people),
+search for yourself, and choose `Organization visibility` to `Public`.
+
+### Committer rights, duties, and responsibilities
+The SkyWalking project doesn't require continuing contributions from you after you have become a committer, but we truly hope that you will continue to play a part in our community!
+
+As a committer, you could
+1. Review and merge the pull request to the master branch in the Apache repo. A pull request often contains multiple commits. Those commits **must be squashed and merged** into a single commit **with explanatory comments**. It is recommended for new committers to request recheck of the pull request from senior committers.
+1. Create and push codes to the new branch in the Apache repo.
+1. Follow the [release process](../How-to-release.md) to prepare a new release. Remember to confirm with the committer team
+that it is the right time to create the release.
+
+The PMC hopes that the new committer will take part in the release process as well as release voting, even though their vote will be regarded as `+1 no binding`.
+Being familiar with the release process is key to being promoted to the role of PMC member.
+
+## Project Management Committee
+The Project Management Committee (PMC) member does not have any special rights in code contributions.
+They simply oversee the project and make sure that it follows the Apache requirements. Its functions include:
+1. Binding voting for releases and license checks;
+1. New committer and PMC member recognition;
+1. Identification of branding issues and brand protection; and
+1. Responding to questions raised by the ASF board, and taking necessary actions.
+
+The V.P. and chair of the PMC is the secretary, who is responsible for initializing the board report.
+
+In most cases, a new PMC member is nominated from the committer team. But it is also possible to become a PMC member directly, so long as the PMC agrees to the nomination and is confident that the candidate is ready. For instance, this can be demonstrated by the fact that he/she has been an Apache member, an Apache officer, or a PMC member of another project.
+
+The new PMC voting process should also follow the `[DISCUSS]`, `[VOTE]` and `[RESULT][VOTE]` procedures using a private mail list, just like the [voting process for new committers](#nominate-new-committer).
+Before sending the invitation, the PMC [must also send a NOTICE mail to the Apache board](http://www.apache.org/dev/pmc.html#newpmc).
+```
+To: board@apache.org
+Cc: private@skywalking.apache.org
+Subject: [NOTICE] Jane Doe for SkyWalking PMC
+
+SkyWalking proposes to invite Jane Doe (janedoe) to join the PMC.
+
+(include if a vote was held) The vote result is available here: https://lists.apache.org/...
+```
+
+After 72 hours, if the board doesn't object to the nomination (which it won't most cases), an invitation may then be sent to the candidate.
+
+Once the invitation is accepted, a PMC member should add the new member to the official PMC list through [roster](https://whimsy.apache.org/roster/committee/skywalking).
diff --git a/docs/en/guides/backend-oal-scripts.md b/docs/en/guides/backend-oal-scripts.md
new file mode 100644
index 000000000000..d9b2fce97724
--- /dev/null
+++ b/docs/en/guides/backend-oal-scripts.md
@@ -0,0 +1,34 @@
+# Official OAL script
+First, read the [OAL introduction](../concepts-and-designs/oal.md) to learn the OAL script grammar and the source concept.
+
+From 8.0.0, you may find the OAL script at `/config/oal/*.oal` of the SkyWalking dist.
+You could change it, such as by adding filter conditions or new metrics. Then, reboot the OAP server, and it will come into effect.
+
+All metrics named in this script could be used in alarm and UI query.
+
+# Extension
+
+## Logic Endpoint
+In default, SkyWalking only treats the operation name of entry span as the endpoint, which are used in the OAL engine.
+Users could declare their custom endpoint names by adding the `logic endpoint` tag manually through agent's plugins or manual APIs.
+
+The logic endpoint is a concept that doesn't represent a real RPC call, but requires the statistic.
+The value of `x-le` should be in JSON format. There are two options:
+1. Define a new logic endpoint in the entry span as a separate new endpoint. Provide its own endpoint name, latency and status. Suitable for entry and local span.
+```json
+{
+ "name": "GraphQL-service",
+ "latency": 100,
+ "status": true
+}
+```
+2. Declare the current local span representing a logic endpoint.
+```json
+{
+ "logic-span": true
+}
+```
+
+### References
+1. [Java plugin API](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/java-plugin-development-guide/#extension-logic-endpoint-tag-key-x-le) guides users to write plugins with logic endpoint.
+2. Java agent's plugins include native included logic endpoints, also it provides ways to set the tag of logic span. The document could be found [here](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/logic-endpoint/).
diff --git a/docs/en/guides/backend-profile-export.md b/docs/en/guides/backend-profile-export.md
new file mode 100644
index 000000000000..cf10644e6729
--- /dev/null
+++ b/docs/en/guides/backend-profile-export.md
@@ -0,0 +1,24 @@
+# Exporter tool for profile raw data
+When visualization doesn't work well on the official UI, users may submit issue reports. This tool helps users package the original profile data to assist the community in locating the issues in the users' cases. NOTE: This report includes the class name, method name, line number, etc. Before making your submission, please make sure that the security of your system wouldn't be compromised.
+
+## Export using command line
+1. Set the storage in the `tools/profile-exporter/application.yml` file based on your use case.
+1. Prepare the data
+ - Profile task ID: Profile task ID
+ - Trace ID: Trace ID of the profile error
+ - Export dir: Directory exported by the data
+1. Enter the Skywalking root path
+1. Execute shell command
+ ```bash
+ bash tools/profile-exporter/profile_exporter.sh --taskid={profileTaskId} --traceid={traceId} {exportDir}
+ ```
+1. The file `{traceId}.tar.gz` will be generated after executing shell.
+
+## Exported data content
+1. `basic.yml`: Contains the complete information of the profiled segments in the trace.
+1. `snapshot.data`: All monitored thread snapshot data in the current segment.
+
+## Report profile issues
+1. Provide exported data generated from this tool.
+1. Provide the operation name and the mode of analysis (including/excluding child span) for the span.
+1. Issue description. (It would be great if you could provide UI screenshots.)
diff --git a/docs/en/guides/benchmark.md b/docs/en/guides/benchmark.md
new file mode 100644
index 000000000000..5f11314bbc9a
--- /dev/null
+++ b/docs/en/guides/benchmark.md
@@ -0,0 +1,15 @@
+# Java Microbenchmark Harness (JMH)
+JMH is a Java harness for building, running, and analysing nano/micro/milli/macro benchmarks written in Java and other languages targeting the JVM.
+
+We have a module called `microbench` which performs a series of micro-benchmark tests for JMH testing.
+Make new JMH tests extend the `org.apache.skywalking.oap.server.microbench.base.AbstractMicrobenchmark`
+to customize runtime conditions (Measurement, Fork, Warmup, etc.).
+
+You can build the jar with command `./mvnw -Dmaven.test.skip -DskipTests -pl :microbench package -am -Pbenchmark`.
+
+JMH tests could run as a normal unit test. And they could run as an independent uber jar via `java -jar benchmark.jar` for all benchmarks,
+or via `java -jar /benchmarks.jar exampleClassName` for a specific test.
+
+Output test results in JSON format, you can add `-rf json` like `java -jar benchmarks.jar -rf json`, if you run through the IDE, you can configure the `-DperfReportDir=savePath` parameter to set the JMH report result save path, a report results in JSON format will be generated when the run ends.
+
+More information about JMH can be found here: [jmh docs](https://openjdk.java.net/projects/code-tools/jmh/).
diff --git a/docs/en/guides/community.md b/docs/en/guides/community.md
new file mode 100644
index 000000000000..45099236e48a
--- /dev/null
+++ b/docs/en/guides/community.md
@@ -0,0 +1,8 @@
+# Guides
+There are many ways you can connect and contribute to the SkyWalking community.
+
+* Submit an [issue](https://github.com/apache/skywalking/issues) for an addressed issue or feature implementation plan.
+* Submit a [discussion](https://github.com/apache/skywalking/issues) to ask questions, feature proposal and uncertain bug discussion.
+* Mail list: **dev@skywalking.apache.org**. Mail to `dev-subscribe@skywalking.apache.org`. Follow the instructions in the reply to subscribe to the mail list.
+* Send `Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
+* For Chinese speaker, send `[CN] Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
diff --git a/docs/en/guides/dependencies.md b/docs/en/guides/dependencies.md
new file mode 100644
index 000000000000..091004b49c37
--- /dev/null
+++ b/docs/en/guides/dependencies.md
@@ -0,0 +1,12 @@
+# OAP backend dependency management
+> This section is only applicable to dependencies of the OAP server and UI.
+
+As one of the Top Level Projects of The Apache Software Foundation (ASF), SkyWalking must follow the [ASF 3RD PARTY LICENSE POLICY](https://apache.org/legal/resolved.html). So if you're adding new dependencies to the project, you should make sure that the new dependencies would not break the policy, and add their LICENSE and NOTICE to the project.
+
+We use [license-eye](https://github.com/apache/skywalking-eyes) to help you make sure that you haven't missed out any new dependencies:
+- Install `license-eye` according to [the doc](https://github.com/apache/skywalking-eyes#usage).
+- Run `license-eye dependency resolve --summary ./dist-material/release-docs/LICENSE.tpl` in the root directory of this project.
+- Check the modified lines in `./dist-material/release-docs/LICENSE` (via command `git diff -U0 ./dist-material/release-docs/LICENSE`) and
+ check whether the new dependencies' licenses are compatible with Apache 2.0.
+- Add the new dependencies' notice files (if any) to `./dist-material/release-docs/NOTICE` if they are Apache 2.0 license. Copy their license files to `./dist-material/release-docs/licenses` if they are not standard Apache 2.0 license.
+- Copy the new dependencies' license file to `./dist-material/release-docs/licenses` if they are not standard Apache 2.0 license.
diff --git a/docs/en/guides/e2e.md b/docs/en/guides/e2e.md
new file mode 100644
index 000000000000..74fa36903b7c
--- /dev/null
+++ b/docs/en/guides/e2e.md
@@ -0,0 +1,45 @@
+# End to End Tests (E2E)
+SkyWalking heavily rely more automatic tests to perform software quality assurance. E2E is an integral part of it.
+
+> End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish.
+The purpose of carrying out end-to-end tests is to identify system dependencies and to ensure that the right information is passed between various system components and systems.
+
+E2E in SkyWalking is always setting the OAP, monitored services and relative remote server dependencies in a real environment,
+and verify the dataflow and ultimate query results.
+
+The E2E test involves some/all of the OAP server, storage, coordinator, webapp, and the instrumented services, all of which are orchestrated by `docker-compose` or `KinD`.
+Since version 8.9.0, we immigrate to e2e-v2 which leverage [skywalking-infra-e2e](https://github.com/apache/skywalking-infra-e2e) and [skywalking-cli](https://github.com/apache/skywalking-cli) to do the whole e2e process.
+`skywalking-infra-e2e` is used to control the e2e process and `skywalking-cli` is used to interact with the OAP such as request and get response metrics from OAP.
+
+## Writing E2E Cases
+
+- Set up the environment
+1. Set up `skywalking-infra-e2e`
+1. Set up `skywalking-cli`, `yq` (generally these 2 are enough) and others tools if your cases need. Can reference the script under `skywalking/test/e2e-v2/script/prepare/setup-e2e-shell`.
+
+- Orchestrate the components
+
+The goal of the E2E tests is to test the SkyWalking project as a whole, including the OAP server, storage, coordinator, webapp, and even the frontend UI (not for now), on the single node mode as well as the cluster mode. Therefore, the first step is to determine what case we are going to verify, and orchestrate the
+components.
+
+To make the orchestration process easier, we're using a [docker-compose](https://docs.docker.com/compose/) that provides a simple file format (`docker-compose.yml`) for orchestrating the required containers, and offers an opportunity to define the dependencies of the components.
+
+Follow these steps:
+1. Decide what (and how many) containers will be needed. For example, for cluster testing, you'll need > 2 OAP nodes, coordinators (e.g. zookeeper), storage (e.g. ElasticSearch), and instrumented services;
+1. Define the containers in `docker-compose.yml`, and carefully specify the dependencies, starting orders, and most importantly, link them together, e.g. set the correct OAP address on the agent end, and set the correct coordinator address in OAP, etc.
+1. Define the e2e case [config](https://skywalking.apache.org/docs/skywalking-infra-e2e/next/en/setup/configuration-file/) in `e2e.yaml`.
+1. Write the expected data(yml) for verify.
+
+- [Run e2e test](https://skywalking.apache.org/docs/skywalking-infra-e2e/next/en/setup/run-e2e-tests/)
+
+All e2e cases should under `skywalking/test/e2e-v2/cases`. You could execute e2e run command in `skywalking/` e.g.
+```
+e2e run -c test/e2e-v2/cases/alarm/h2/e2e.yaml
+```
+
+- Troubleshooting
+
+We expose all logs from all containers to the stdout in the non-CI (local) mode, but save and upload them to the GitHub server. You can download them (only when the tests have failed) at "Artifacts/Download artifacts/logs" (see top right) for debugging.
+
+**NOTE:** Please verify the newly-added E2E test case locally first. However, if you find that it has passed locally but failed in the PR check status, make sure that all the updated/newly-added files (especially those in the submodules)
+are committed and included in the PR, or reset the git HEAD to the remote and verify locally again.
diff --git a/docs/en/guides/i18n.md b/docs/en/guides/i18n.md
new file mode 100644
index 000000000000..5739d40bb0ef
--- /dev/null
+++ b/docs/en/guides/i18n.md
@@ -0,0 +1,13 @@
+# Guide
+> This section explains how to manage translations for internationalization of menu items.
+
+SkyWalking UI's internationalization translations are in the [src/locales/lang](https://github.com/apache/skywalking-booster-ui/tree/main/src/locales/lang).
+The translations include `menu name` and `description`. The translation key of `menu name` is the value of `i18nKey` from [menu definition file](../../../oap-server/server-starter/src/main/resources/ui-initialized-templates/menu.yaml). The translation key of `description` consists of the `i18nKey` value and `_desc` suffix. The `description` contents will be displayed on the Marketplace page.
+
+The following is a typical `menu name` and `description` for i18nKey=`general_service`
+```json
+{
+ "general_service": "General Service",
+ "general_service_desc": "Observe services and relative direct dependencies through telemetry data collected from SkyWalking Agents."
+}
+```
diff --git a/docs/en/guides/source-extension.md b/docs/en/guides/source-extension.md
new file mode 100644
index 000000000000..9d07c6fba54a
--- /dev/null
+++ b/docs/en/guides/source-extension.md
@@ -0,0 +1,62 @@
+# Source and scope extension for new metrics
+From the [OAL scope introduction](../concepts-and-designs/oal.md#from), you should already have understood what a scope is.
+If you would like to create more extensions, you need to have a deeper understanding of what a **source** is.
+
+**Source** and **scope** are interrelated concepts. **Scope** declares the ID (int) and name, while **source** declares the attributes.
+Follow these steps to create a new source and sccope.
+
+1. In the OAP core module, it provides **SourceReceiver** internal services.
+```java
+public interface SourceReceiver extends Service {
+ void receive(Source source);
+}
+```
+
+2. All data of the analysis must be a **org.apache.skywalking.oap.server.core.source.Source** sub class that is
+tagged by `@SourceType` annotation, and included in the `org.apache.skywalking` package. Then, it can be supported by the OAL script and OAP core.
+
+Take the existing source **service** as an example.
+```java
+@ScopeDeclaration(id = SERVICE_INSTANCE, name = "ServiceInstance", catalog = SERVICE_INSTANCE_CATALOG_NAME)
+@ScopeDefaultColumn.VirtualColumnDefinition(fieldName = "entityId", columnName = "entity_id", isID = true, type = String.class)
+public class ServiceInstance extends Source {
+ @Override public int scope() {
+ return DefaultScopeDefine.SERVICE_INSTANCE;
+ }
+
+ @Override public String getEntityId() {
+ return String.valueOf(id);
+ }
+
+ @Getter @Setter private int id;
+ @Getter @Setter @ScopeDefaultColumn.DefinedByField(columnName = "service_id") private int serviceId;
+ @Getter @Setter private String name;
+ @Getter @Setter private String serviceName;
+ @Getter @Setter private String endpointName;
+ @Getter @Setter private int latency;
+ @Getter @Setter private boolean status;
+ @Getter @Setter private int responseCode;
+ @Getter @Setter private RequestType type;
+}
+```
+
+3. The `scope()` method in source returns an ID, which is not a random value. This ID must be declared through the `@ScopeDeclaration` annotation too. The ID in `@ScopeDeclaration` and ID in `scope()` method must be the same for this source.
+
+4. The `String getEntityId()` method in source requests the return value representing the unique entity to which the scope relates. For example, in this service scope, the ID is the service ID, which represents a particular service, like the `Order` service.
+This value is used in the [OAL group mechanism](../concepts-and-designs/oal.md#group).
+
+5. `@ScopeDefaultColumn.VirtualColumnDefinition` and `@ScopeDefaultColumn.DefinedByField` are required. All declared fields (virtual/byField) will be pushed into a persistent entity, and maps to lists such as the ElasticSearch index and Database table column.
+For example, the entity ID and service ID for endpoint and service instance level scope are usually included. Take a reference from all existing scopes.
+All these fields are detected by OAL Runtime, and are required during query.
+
+6. Add scope name as keyword to OAL grammar definition file, `OALLexer.g4`, which is at the `antlr4` folder of the `generate-tool-grammar` module.
+
+7. Add scope name as keyword to the parser definition file, `OALParser.g4`, which is located in the same folder as `OALLexer.g4`.
+
+
+___
+After finishing these steps, you could build a receiver, which do
+1. Obtain the original data of the metrics.
+1. Build the source, and send to `SourceReceiver`.
+1. Complete your OAL scripts.
+1. Repackage the project.
diff --git a/docs/en/papers/stam.md b/docs/en/papers/stam.md
new file mode 100644
index 000000000000..1a84e40c4e1b
--- /dev/null
+++ b/docs/en/papers/stam.md
@@ -0,0 +1,153 @@
+# STAM: Enhancing Topology Auto Detection For A Highly Distributed and Large-Scale Application System
+
+- Sheng Wu 吴 晟
+- wusheng@apache.org
+
+### Editor's note
+This paper was written by Sheng Wu, project founder, in 2017, to describe the fundamental theory of all current
+agent core concepts.
+Readers could learn why SkyWalking agents are significantly different from other tracing system and
+Dapper[1] Paper's description.
+
+# Abstract
+Monitoring, visualizing and troubleshooting a large-scale distributed system is a major challenge. One common tool used today is the distributed tracing system (e.g., Google Dapper)[1], and detecting topology and metrics based on the tracing data. One big limitation of today’s topology detection is that the analysis depends on aggregating the client-side and server-side tracing spans in a given time window to generate the dependency of services. This causes more latency and memory use, because the client and server spans of every RPC must be matched in millions of randomly occurring requests in a highly distributed system. More importantly, it could fail to match if the duration of RPC between client and server is longer than the prior setup time window, or across the two windows.
+
+In this paper, we present the STAM, Streaming Topology Analysis Method. In STAM, we could use auto instrumentation or a manual instrumentation mechanism to intercept and manipulate RPC at both client-side and server-side. In the case of auto instrumentation, STAM manipulates application codes at runtime, such as Java agent. As such, this monitoring system doesn’t require any source code changes from the application development team or RPC framework development team. The STAM injects an RPC network address used at client side, a service name and a service instance name into the RPC context, and binds the server-side service name and service instance name as the alias name for this network address used at the client side. Freeing the dependency analysis from the mechanisms that cause blocking and delay, the analysis core can process the monitoring data in stream mode and generate the accurate topology.
+
+The STAM has been implemented in the Apache SkyWalking[2], an open source APM (application performance monitoring system) project of the Apache Software Foundation, which is widely used in many big enterprises[3] including Alibaba, Huawei, Tencent, Didi, Xiaomi, China Mobile and other enterprises (airlines, financial institutions and others) to support their large-scale distributed systems in the production environment. It reduces the load and memory cost significantly, with better horizontal scale capability.
+
+# Introduction
+Monitoring the highly distributed system, especially with a micro-service architecture, is very complex. Many RPCs, including HTTP, gRPC, MQ, Cache, and Database accesses, are behind a single client-side request. Allowing the IT team to understand the dependency relationships among thousands of services is the key feature and first step for observability of a whole distributed system. A distributed tracing system is capable of collecting traces, including all distributed request paths. Dependency relationships have been logically included in the trace data. A distributed tracing system, such as Zipkin [4] or Jaeger Tracing [10], provides built-in dependency analysis features, but many analysis features build on top of that. There are at least two fundamental limitations: timeliness and consistent accuracy.
+
+Strong timeliness is required to match the mutability of distributed application system dependency relationship, including service level and service instance level dependency.
+
+A Service is a logic group of instances which have the same functions or codes.
+
+A Service Instance is usually an OS level process, such as a JVM process. The relationships between services and instances are mutable, depending on the configuration, codes and network status. The dependency could change over time.
+
+
+
+
+Figure 1, Generated spans in traditional Dapper based tracing system.
+
+
+The span model in the Dapper paper and existing tracing systems，such as Zipkin instrumenting mode[9], just propagates the span id to the server side. Due to this model,
+dependency analysis requires a certain time window. The tracing spans are collected at both client- and server-sides, because the relationship is recorded. Due to that, the analysis process has to wait for the client and server spans to match in the same time window, in order to output the result, Service A depending on Service B. So, this time window must be over the duration of this RPC request; otherwise, the conclusion will be lost. This condition makes the analysis would not react the dependency mutation in second level, in production, it sometimes has to set the window duration in 3-5 mins.
+Also, because of the Windows-based design, if one side involves a long duration task, it can’t easily achieve consistent accuracy. Because in order to make the analysis as fast as possible, the analysis period is less than 5 minutes. But some spans can’t match its parent or children if the analysis is incomplete or crosses two time windows. Even if we added a mechanism to process the spans left in the previous stages, still some would have to be abandoned to keep the dataset size and memory usage reasonable.
+
+In the STAM, we introduce a new span and context propagation models, with the new analysis method. These new models add the peer network address (IP or hostname) used at client side, client service instance name and client service name, into the context propagation model. Then it passes the RPC call from client to server, just as the original trace id and span id in the existing tracing system, and collects it in the server-side span. The new analysis method can easily generate the client-server relationship directly without waiting on the client span. It also sets the peer network address as one alias of the server service. After the across cluster node data sync, the client-side span analysis could use this alias metadata to generate the client-server relationship directly too. By using these new models and method in Apache SkyWalking, we remove the time windows-based analysis permanently, and fully use the streaming analysis mode with less than 5 seconds latency and consistent accuracy
+
+# New Span Model and Context Model
+The traditional span of a tracing system includes the following fields [1][6][10].
+- A trace id to represent the whole trace.
+- A span id to represent the current span.
+- An operation name to describe what operation this span did.
+- A start timestamp.
+- A finish timestamp
+- Service and Service Instance names of current span.
+- A set of zero or more key:value Span Tags.
+- A set of zero or more Span Logs, each of which is itself a key:value map paired with a timestamp.
+- References to zero or more causally related Spans. Reference includes the parent span id and trace id.
+
+In the new span model of STAM we add the following fields in the span.
+
+**Span type**. Enumeration, including exit, local and entry. Entry and Exit spans are used in a networking related library. Entry spans represent a server-side networking library, such as Apache Tomcat[7]. Exit spans represent the client-side networking library, such as Apache HttpComponents [8].
+
+**Peer Network Address**. Remote "address," suitable for use in exit and entry spans. In Exit spans, the peer network address is the address by the client library to access the server.
+
+These fields usually are optionally included in many tracing system,. But in STAM, we require them in all RPC cases.
+
+**Context Model** is used to propagate the client-side information to server-side carried by the original RPC call, usually in the header, such as HTTP header or MQ header. In the old design, it carries the trace id and span id of client-side span. In the STAM, we enhance this model, adding the parent service name, parent service instance name and peer of exit span. The names could be literal strings. All these extra fields will help to remove the block of streaming analysis. Compared to the existing context model, this uses a little more bandwidth, but it could be optimized. In Apache SkyWalking, we design a register mechanism to exchange unique IDs to represent these names. As a result, only 3 integers are added in the RPC context, so the increase of bandwidth is at least less than 1% in the production environment.
+
+The changes of two models could eliminate the time windows in the analysis process. Server-side span analysis enhances the context aware capability.
+
+# New Topology Analysis Method
+The new topology analysis method at the core of STAM is processing the span in stream mode.
+The analysis of the server-side span, also named entry span, includes the parent service name, parent service instance name and peer of exit span. So the analysis process could establish the following results.
+1. Set the peer of exit span as client using alias name of current service and instance. `Peer network address <-> service name` and `peer network address <-> Service instance name` aliases created. These two will sync with all analysis nodes and persistent in the storage, allowing more analysis processers to have this alias information.
+2. Generate relationships of `parent service name -> current service name` and `parent service instance name -> current service instance name`, unless there is another different `Peer network address <-> Service Instance Name` mapping found. In that case, only generate relationships of `peer network address <-> service name` and `peer network address <-> Service instance name`.
+
+For analysis of the client-side span (exit span), there could three possibilities.
+1. The peer in the exit span already has the alias names established by server-side span analysis from step (1). Then use alias names to replace the peer, and generate traffic of `current service name -> alias service name` and `current service instance name -> alias service instance name`.
+2. If the alias could not be found, then just simply generate traffic for `current service name -> peer` and `current service instance name -> peer`.
+3. If multiple alias names of `peer network address <-> Service Instance Name` could be found, then keep generating traffic for `current service name -> peer network address` and `current service instance name -> peer network address`.
+
+
+
+
+Figure 2, Apache SkyWalking uses STAM to detect and visualize the topology of distributed systems.
+
+
+# Evaluation
+In this section, we evaluate the new models and analysis method in the context of several typical cases in which the old method loses timeliness and consistent accuracy.
+
+- 1.**New Service Online or Auto Scale Out**
+
+New services could be added into the whole topology by the developer team randomly, or container operation platform automatically by some scale out policy, like Kubernetes [5]. The monitoring system could not be notified in any case manually. By using STAM, we could detect the new node automatically and also keep the analysis process unblocked and consistent with detected nodes.
+In this case, a new service and network address (could be IP, port or both) are used. The peer network address <-> service mapping does not exist, the traffic of client service -> peer network address will be generated and persistent in the storage first. After mapping is generated, further traffic of client-service to server-service could be identified, generated and aggregated in the analysis platform. For filling the gap of a few traffic before the mapping generated, we require doing peer network address <-> service mapping translation again in query stage, to merge client service->peer network address and client-service to server-service. In production, the amount of VM for the whole SkyWalking analysis platform deployment is less than 100, syncing among them will finish less than 10 seconds, in most cases it only takes 3-5 seconds. And in the query stage, the data has been aggregated in minutes or seconds at least. The query merge performance is not related to how much traffic happens before the mapping generated, only affected by sync duration, in here, only 3 seconds. Due to that, in minute level aggregation topology, it only adds 1 or 2 relationship records in the whole topology relationship dataset. Considering an over 100 services topology having over 500 relationship records per minute, the payload increase for this query merge is very limited and affordable. This feature is significant in a large and high load distributed system, as we don’t need to concern its scaling capability. And in some fork versions, they choose to update the existing client service->peer network address to client-service to server-service after detecting the new mapping for peer generated, in order to remove the extra load at query stage permanently.
+
+
+
+
+Figure 3, Span analysis by using the new topology analysis method
+
+
+- 2.**Existing Uninstrumented Nodes**
+
+Every topology detection method has to work in this case. In many cases, there are nodes in the production environment that can’t be instrumented. Causes for this might include:(1) Restriction of the technology. In some golang or C++ written applications, there is no easy way in Java or .Net to do auto instrumentation by the agent. So, the codes may not be instrumented automatically. (2) The middleware, such as MQ, database server, has not adopted the tracing system. This would make it difficult or time consuming to implement the middleware instrumentation. (3) A 3rd party service or cloud service doesn’t support work with the current tracing system. (4) Lack of resources: e.g., the developer or operation team lacks time to make the instrumentation ready.
+
+The STAM works well even if the client or server side has no instrumentation. It still keeps the topology as accurate as possible.
+
+If the client side hasn’t instrumented, the server-side span wouldn’t get any reference through RPC context, so, it would simply use peer to generate traffic, as shown in Figure 4.
+
+
+
+
+Figure 4, STAM traffic generation when no client-side instrumentation
+
+
+As shown in Figure 5, in the other case, with no server-side instrumentation, the client span analysis doesn’t need to process this case. The STAM analysis core just simply keeps generating client service->peer network address traffic. As there is no mapping for peer network address generated, there is no merging.
+
+
+
+
+Figure 5, STAM traffic generation when no server-side instrumentation
+
+
+- 3.**Uninstrumented Node Having Header Forward Capability**
+
+Besides the cases we evaluated in (2) Uninstrumented Nodes, there is one complex and special case: the instrumented node has the capability to propagate the header from downstream to upstream, typically in all proxy, such as Envoy[11], Nginx[12], Spring Cloud Gateway[13]. As proxy, it has the capability to forward all headers from downstream to upstream to keep some of information in the header, including the tracing context, authentication, browser information, and routing information, in order to make them accessible by the business services behind the proxy, like Envoy route configuration. When some proxy can’t be instrumented, no matter what the reason, it should not affect the topology detection.
+
+In this case, the proxy address would be used at the client side and propagate through RPC context as peer network address, and the proxy forwards this to different upstream services. Then STAM could detect this case and generate the proxy as a conjectural node. In the STAM, more than one alias names for this network address should be generated. After those two are detected and synchronized to the analysis node, the analysis core knows there is at least one uninstrumented service standing between client and servers. So, it will generate the relationships of `client service->peer network address`, `peer->server service B` and `peer network address ->server service C`, as shown in Figure 6.
+
+
+
+
+Figure 6, STAM traffic generation when the proxy uninstrumentation
+
+
+# Conclusion
+
+This paper described the STAM, which is to the best of our knowledge the best topology detection method for distributed tracing systems. It replaces the time-window based topology analysis method for tracing-based monitoring systems. It removes the resource cost of disk and memory for time-window baseds analysis permanently and totally, and the barriers of horizontal scale. One STAM implementation, Apache SkyWalking, is widely used for monitoring hundreds of applications in production. Some of them generated over 100 TB tracing data per day and topology for over 200 services in real time.
+
+# Acknowledgments
+We thank all contributors of Apache SkyWalking project for suggestions, code contributions to implement the STAM, and feedback from using the STAM and SkyWalking in their production environment.
+
+# License
+This paper and the STAM are licensed in the Apache 2.0.
+
+# References
+
+1. Dapper, a Large-Scale Distributed Systems Tracing Infrastructure, https://research.google.com/pubs/pub36356.html?spm=5176.100239.blogcont60165.11.OXME9Z
+1. Apache SkyWalking, http://skywalking.apache.org/
+1. Apache Open Users, https://skywalking.apache.org/users/
+1. Zipkin, https://zipkin.io/
+1. Kubernetes, Production-Grade Container Orchestration. Automated container deployment, scaling, and management. https://kubernetes.io/
+1. OpenTracing Specification https://github.com/opentracing/specification/blob/master/specification.md
+1. Apache Tomcat, http://tomcat.apache.org/
+1. Apache HttpComponents, https://hc.apache.org/
+1. Zipkin doc, ‘Instrumenting a library’ section, ‘Communicating trace information’ paragraph. https://zipkin.io/pages/instrumenting
+1. Jaeger Tracing, https://jaegertracing.io/
+1. Envoy Proxy, http://envoyproxy.io/
+1. Nginx, http://nginx.org/
+1. Spring Cloud Gateway, https://spring.io/projects/spring-cloud-gateway
diff --git a/docs/en/security/README.md b/docs/en/security/README.md
new file mode 100644
index 000000000000..6cb3aa488391
--- /dev/null
+++ b/docs/en/security/README.md
@@ -0,0 +1,30 @@
+# Security Notice
+
+The SkyWalking OAP server, UI, and agent deployments should run in a secure environment, such as only inside your data center.
+OAP server, UI, and agent deployments should only be reachable by the operation team on default
+deployment.
+
+All telemetry data are trusted. The OAP server **would not validate any field** of the telemetry data to avoid extra
+load for the server.
+
+It is up to the operator(OPS team) whether to expose the OAP server, UI, or some agent deployment to unsecured
+environment.
+The following security policies should be considered to add to secure your SkyWalking deployment.
+
+1. HTTPs and gRPC+TLS should be used between agents and OAP servers, as well as UI.
+2. Set up TOKEN or username/password based authentications for the OAP server and UI through your Gateway.
+3. Validate all fields of the traceable RPC(including HTTP 1/2, MQ) headers(header names are `sw8`, `sw8-x` and `sw8-correlation`)
+ when requests are from out of the trusted zone. Or simply block/remove those headers unless you are using the client-js agent.
+4. All fields of telemetry data(HTTP in raw text or encoded Protobuf format) should be validated and reject malicious
+ data.
+
+Without these protections, an attacker could embed executable Javascript code in those fields, causing XSS or even
+Remote Code Execution (RCE) issues.
+
+For some sensitive environment, consider to limit the telemetry report frequency in case of DoS/DDoS for exposed OAP
+and UI services.
+
+## appendix
+
+The SkyWalking [client-js](https://github.com/apache/skywalking-client-js) agent is always running out of the secured
+environment. Please follow its **security notice** for more details.
diff --git a/docs/en/setup/ai-pipeline/http-restful-uri-pattern.md b/docs/en/setup/ai-pipeline/http-restful-uri-pattern.md
new file mode 100644
index 000000000000..f08eab97b5f1
--- /dev/null
+++ b/docs/en/setup/ai-pipeline/http-restful-uri-pattern.md
@@ -0,0 +1,47 @@
+# HTTP Restful URI recognition
+
+As introduced in the [Group Parameterized Endpoints](../backend/endpoint-grouping-rules.md) doc, HTTP Restful URIs are identified
+as endpoints. With some additional rules, we can identify the parameters in the URI and group the endpoints in case of annoying
+and huge size of endpoint candidates with low value of the metrics.
+
+In the ML/AI specific fields, decision trees or neural networks can be trained on labeled URI data to automatically
+recognize and classify different URI patterns, as well as many other ways.
+
+In this pipeline, OAP has the capabilities to cache the URI candidates with occurrence count,
+and push the data to 3rd party for further analysis. Then OAP would pull the analyzed results for
+processing the further telemetry traffic.
+
+## Set up OAP to connect remote URI recognition server
+`uriRecognitionServerAddr` and `uriRecognitionServerPort` are the configurations to set up the remote URI recognition server.
+
+The URI recognition server is a gRPC server, which is defined in [URIRecognition.proto](../../../../oap-server/ai-pipeline/src/main/proto/ai_http_uri_recognition.proto).
+
+```protobuf
+service HttpUriRecognitionService {
+ // Sync for the pattern recognition dictionary.
+ rpc fetchAllPatterns(HttpUriRecognitionSyncRequest) returns (HttpUriRecognitionResponse) {}
+ // Feed new raw data and matched patterns to the AI-server.
+ rpc feedRawData(HttpUriRecognitionRequest) returns (google.protobuf.Empty) {}
+}
+```
+
+- fetchAllPatterns service
+
+fetchAllPatterns is up and running in 1 minute period from every OAP to fetch all recognized patterns from the remote server.
+
+- feedRawData service
+
+feedRawData is running in 25-30 minutes period to push the raw data to the remote server for training.
+
+## Configurations
+
+- `core/maxHttpUrisNumberPerService` The max number of HTTP URIs per service for further URI pattern recognition.
+- `core/syncPeriodHttpUriRecognitionPattern` The period of HTTP URI pattern recognition(feedRawData). Unit is second, 10s by default.
+- `core/trainingPeriodHttpUriRecognitionPattern` The training period of HTTP URI pattern recognition(fetchAllPatterns). Unit is second, 60s by default.
+
+## Optional Server Implementation
+
+### R3
+
+[RESTful Pattern Recognition(R3)](https://github.com/SkyAPM/r3) is an Apache 2.0 licensed implementation for the URI
+recognition, and natively supports `URIRecognition.proto` defined in OAP.
diff --git a/docs/en/setup/ai-pipeline/introduction.md b/docs/en/setup/ai-pipeline/introduction.md
new file mode 100644
index 000000000000..a2f62710e4b0
--- /dev/null
+++ b/docs/en/setup/ai-pipeline/introduction.md
@@ -0,0 +1,29 @@
+# AI Pipeline
+
+**Warning, this module is still in the ALPHA stage. This is not stable.**
+
+Pattern Recognition, Machine Learning(ML) and Artificial Intelligence(AI) are common technology to identify patterns in data.
+From the industry practice, these three are always overestimated for the marketing interests,
+they are good at many things but have to run in a clear context.
+Hence, SkyWalking OAP AI pipeline features are designed for very specific solutions and scenarios with at
+least one recommended (remote) implementations for the integration。
+
+The ai-pipeline module is activated by default for the latest release. Make sure you have these configurations when upgrade
+from a previous version.
+
+```yaml
+ai-pipeline:
+ selector: ${SW_AI_PIPELINE:default}
+ default:
+ # HTTP Restful URI recognition service address configurations
+ uriRecognitionServerAddr: ${SW_AI_PIPELINE_URI_RECOGNITION_SERVER_ADDR:}
+ uriRecognitionServerPort: ${SW_AI_PIPELINE_URI_RECOGNITION_SERVER_PORT:17128}
+ # Metrics Baseline Calculation service address configurations
+ baselineServerAddr: ${SW_API_PIPELINE_BASELINE_SERVICE_HOST:}
+ baselineServerPort: ${SW_API_PIPELINE_BASELINE_SERVICE_PORT:18080}
+```
+
+We supported the following AI features:
+
+* [**HTTP Restful URI recognition**](./http-restful-uri-pattern.md).
+* [**Metrics Baseline Calculation and Alerting**](./metrics-baseline-integration.md).
diff --git a/docs/en/setup/ai-pipeline/metrics-baseline-integration.md b/docs/en/setup/ai-pipeline/metrics-baseline-integration.md
new file mode 100644
index 000000000000..785c204e8fb9
--- /dev/null
+++ b/docs/en/setup/ai-pipeline/metrics-baseline-integration.md
@@ -0,0 +1,22 @@
+# Metrics Baseline Calculation and Alerting
+
+Metrics baseline calculation and alerting is a feature that calculates the baseline of metrics data and feed for the
+alarm engine as additional metrics to setup rules for alerting.
+[Alarm docs](../backend/backend-alarm.md#use-the-baseline-predicted-value-to-trigger-the-alarm) has more details about
+how to use the baseline, and further about MQE usages of the baseline values.
+
+SkyAPM community provides a default implementation [SkyAPM/SkyPredictor](https://github.com/SkyAPM/SkyPredictor).
+It has complete support for the baseline calculation by following SkyWalking's metrics data model through GraphQL, and
+feed baseline data back to the OAP server through the following gRPC service per SkyWalking requirement..
+
+```protobuf
+service AlarmBaselineService {
+ // Query the supported metrics names.
+ rpc querySupportedMetricsNames(google.protobuf.Empty) returns (AlarmBaselineMetricsNames);
+ // Query the predicted metrics of the given service.
+ rpc queryPredictedMetrics(AlarmBaselineRequest) returns (AlarmBaselineResponse);
+}
+```
+
+You could find the protocol definition
+in [AlarmBaseline.proto](../../../../oap-server/ai-pipeline/src/main/proto/baseline.proto).
\ No newline at end of file
diff --git a/docs/en/setup/backend/advanced-deployment.md b/docs/en/setup/backend/advanced-deployment.md
new file mode 100644
index 000000000000..67f9f329eda5
--- /dev/null
+++ b/docs/en/setup/backend/advanced-deployment.md
@@ -0,0 +1,41 @@
+# Advanced deployment
+OAP servers communicate with each other in a cluster environment to do distributed aggregation.
+In the cluster mode, all OAP nodes are running in Mixed mode by default.
+
+The available roles for OAP are,
+- Mixed(default)
+- Receiver
+- Aggregator
+
+Sometimes users may wish to deploy cluster nodes with a clearly defined role. They could then use this function.
+
+## Mixed
+By default, the OAP is responsible for:
+1. Receiving agent traces or metrics.
+1. L1 aggregation
+1. Internal communication (sending/receiving)
+1. L2 aggregation
+1. Persistence
+1. Alarm
+
+## Receiver
+The OAP is responsible for:
+1. Receiving agent traces or metrics.
+1. L1 aggregation
+1. Internal communication (sending)
+
+## Aggregator
+The OAP is responsible for:
+1. Internal communication(receiving from Receiver and Mixed roles OAP)
+1. L2 aggregation
+1. Persistence
+1. Alarm
+
+___
+These roles are designed for complex deployment requirements on security and network policy.
+
+## Kubernetes
+If you are using our native [Kubernetes coordinator](backend-cluster.md#kubernetes), and you insist to install OAP nodes
+with a clearly defined role. There should be two deployments for each role,
+one for receiver OAPs and the other for aggregator OAPs to separate different system environment settings.
+Then, the `labelSelector` should be set for `Aggregator` role selection rules to choose the right OAP deployment based on your needs.
diff --git a/docs/en/setup/backend/apdex-threshold.md b/docs/en/setup/backend/apdex-threshold.md
new file mode 100644
index 000000000000..7a4e80d8795e
--- /dev/null
+++ b/docs/en/setup/backend/apdex-threshold.md
@@ -0,0 +1,27 @@
+# Apdex threshold
+
+Apdex is a measure of response time based against a set threshold. It measures the ratio of satisfactory response times
+to unsatisfactory response times. The response time is measured from an asset request to completed delivery back to
+the requestor.
+
+A user defines a response time threshold T. All responses handled in T or less time satisfy the user.
+
+For example, if T is 1.2 seconds and a response completes in 0.5 seconds, then the user is satisfied. All responses
+greater than 1.2 seconds dissatisfy the user. Responses greater than 4.8 seconds frustrate the user.
+
+The apdex threshold T can be configured in `service-apdex-threshold.yml` file or via [Dynamic Configuration](dynamic-config.md).
+The `default` item will apply to a service that isn't defined in this configuration as the default threshold.
+
+## Configuration Format
+
+The configuration content includes the names and thresholds of the services:
+
+```yml
+# default threshold is 500ms
+default: 500
+# example:
+# the threshold of service "tomcat" is 1s
+# tomcat: 1000
+# the threshold of service "springboot1" is 50ms
+# springboot1: 50
+```
diff --git a/docs/en/setup/backend/aws-firehose-receiver.md b/docs/en/setup/backend/aws-firehose-receiver.md
new file mode 100644
index 000000000000..e39efb7fde49
--- /dev/null
+++ b/docs/en/setup/backend/aws-firehose-receiver.md
@@ -0,0 +1,38 @@
+# AWS Firehose receiver
+
+AWS Firehose receiver listens on `0.0.0.0:12801` by default, and provides an HTTP Endpoint `/aws/firehose/metrics` that follows [Amazon Kinesis Data Firehose Delivery Stream HTTP Endpoint Delivery Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html)
+You could leverage the receiver to collect [AWS CloudWatch metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/working_with_metrics.html), and analysis it through [MAL](../../concepts-and-designs/mal.md) as the receiver bases on [OpenTelemetry receiver](./opentelemetry-receiver.md)
+
+## Setup(S3 example)
+
+1. Create CloudWatch metrics configuration for S3 (refer to [S3 CloudWatch metrics](https://docs.aws.amazon.com/AmazonS3/latest/userguide/configure-request-metrics-bucket.html))
+2. Stream CloudWatch metrics to AWS Kinesis Data Firehose delivery stream by [CloudWatch metrics stream](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-metric-streams-setup-datalake.html)
+3. Specify AWS Kinesis Data Firehose delivery stream HTTP Endpoint (refer to [Choose HTTP Endpoint for Your Destination](https://docs.aws.amazon.com/firehose/latest/dev/create-destination.html#create-destination-http))
+
+Usually, the [AWS CloudWatch metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/working_with_metrics.html) process flow with OAP is as follows:
+```
+CloudWatch metrics with S3 --> CloudWatch Metric Stream (OpenTelemetry formart) --> Kinesis Data Firehose Delivery Stream --> AWS Firehose receiver(OAP) --> OpenTelemetry receiver(OAP)
+```
+
+The following blogs demonstrate complete setup process for AWS S3 and API Gateway:
+
+* [Monitoring DynamoDB with SkyWalking](https://skywalking.apache.org/blog/2023-03-13-skywalking-aws-dynamodb/)
+* [Monitoring AWS EKS and S3 with SkyWalking](https://skywalking.apache.org/blog/2023-03-12-skywalking-aws-s3-eks/)
+
+## Supported metrics
+
+| Description | Configuration File | Data Source |
+|-----------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| Metrics of AWS Cloud S3 | otel-rules/aws-s3/s3-service.yaml | AWS CloudWatcher Metrics Stream -> AWS Firehose delivery stream -> SkyWalking OAP Server with [AWS Firehose receiver](./aws-firehose-receiver.md) |
+| Metrics of AWS DynamoDB | otel-rules/aws-dynamodb/dynamodb-service.yaml | AWS CloudWatcher Metrics Stream -> AWS Firehose delivery stream -> SkyWalking OAP Server with [AWS Firehose receiver](./aws-firehose-receiver.md) |
+| Metrics of AWS DynamoDB | otel-rules/aws-dynamodb/dynamodb-endpoint.yaml | AWS CloudWatcher Metrics Stream -> AWS Firehose delivery stream -> SkyWalking OAP Server with [AWS Firehose receiver](./aws-firehose-receiver.md) |
+| Metrics of AWS API Gateway | otel-rules/aws-gateway/gateway-service.yaml | AWS CloudWatcher Metrics Stream -> AWS Firehose delivery stream -> SkyWalking OAP Server with [AWS Firehose receiver](./aws-firehose-receiver.md) |
+| Metrics of AWS API Gateway | otel-rules/aws-gateway/gateway-endpoint.yaml | AWS CloudWatcher Metrics Stream -> AWS Firehose delivery stream -> SkyWalking OAP Server with [AWS Firehose receiver](./aws-firehose-receiver.md) |
+
+## Notice
+
+1. Only OpenTelemetry format is supported (refer to [Metric streams output formats](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-metric-streams-formats.html))
+2. According to HTTPS requirement by AWS Firehose(refer to [Amazon Kinesis Data Firehose Delivery Stream HTTP Endpoint Delivery Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html), users have two options
+ - A proxy(e.g. Nginx, Envoy) is required in front of OAP's Firehose receiver to accept HTTPS requests from AWS Firehose through port `443`. (Recommended based on the general security policy)
+ - Set `aws-firehose/enableTLS=true` with suitable cert/key files through `aws-firehose/tlsKeyPath` and `aws-firehose/tlsCertChainPath` at OAP side to accept requests from firehose directly.
+3. AWS Firehose receiver support setting accessKey for Kinesis Data Firehose, please refer to [configuration vocabulary](./configuration-vocabulary.md)
diff --git a/docs/en/setup/backend/backend-activemq-monitoring.md b/docs/en/setup/backend/backend-activemq-monitoring.md
new file mode 100644
index 000000000000..883ca9e431e4
--- /dev/null
+++ b/docs/en/setup/backend/backend-activemq-monitoring.md
@@ -0,0 +1,107 @@
+# ActiveMQ classic monitoring
+
+SkyWalking leverages jmx prometheus exporter for collecting metrics data from ActiveMQ classic. It leverages OpenTelemetry
+Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. ActiveMQ classic has extensive support for JMX to allow you to monitor and control the behavior of the broker via the JMX MBeans.
+2. The [jmx prometheus exporter](https://github.com/prometheus/jmx_exporter) collects metrics data from ActiveMQ classic, this exporter is intended to be run as a Java Agent, exposing a HTTP server and serving metrics of the local JVM.
+3. OpenTelemetry Collector fetches metrics from jmx prometheus exporter via Prometheus Receiver and pushes metrics to
+ SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+4. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. [Enable JMX](https://activemq.apache.org/components/classic/documentation/jmx) in `activemq.xml`, the JMX remote port defaults to `1616`, you can change it through `ACTIVEMQ_SUNJMX_START`. The example for ActiveMQ configuration, refer
+ to [here](../../../../test/e2e-v2/cases/activemq/config/amq/activemq.xml).
+2. Set up [jmx prometheus exporter](https://github.com/prometheus/jmx_exporter) which runs as a Java Agent(recommended) of ActiveMQ classic. If you work with docker, you also can set up [a single server](https://github.com/bitnami/containers/tree/main/bitnami/jmx-exporter) for exporter, refer
+ to [here](../../../../test/e2e-v2/cases/activemq/config/amq/config.yaml)(note the configuration of `includeObjectNames`).
+3. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#docker). The example for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/activemq/otel-collector-config.yaml).
+4. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## ActiveMQ classic Monitoring
+
+ActiveMQ classic monitoring provides multidimensional metrics monitoring of ActiveMQ Exporter as `Layer: ActiveMQ` `Service` in
+the OAP. In each cluster, the broker is represented as `Instance` and the destination is represented as `Endpoint`.
+
+### ActiveMQ Cluster Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------|
+| System Load Average | Count | meter_activemq_cluster_system_load_average | The average system load, range:[0, 10000]. | JMX Prometheus Exporter |
+| Thread Count | Count | meter_activemq_cluster_thread_count | Threads currently used by the JVM. | JMX Prometheus Exporter |
+| Init Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_init | The initial amount of heap memory available. | JMX Prometheus Exporter |
+| Committed Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_committed | The memory is guaranteed to be available for the JVM to use. | JMX Prometheus Exporter |
+| Used Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_used | The amount of JVM heap memory currently in use. | JMX Prometheus Exporter |
+| Max Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_max | The maximum possible size of the heap memory. | JMX Prometheus Exporter |
+| GC G1 Old Collection Count | Count | meter_activemq_cluster_gc_g1_old_collection_count | The gc count of G1 Old Generation(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Young Collection Count | Count | meter_activemq_cluster_gc_g1_young_collection_count | The gc count of G1 Young Generation(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Old Collection Time | ms | meter_activemq_cluster_gc_g1_old_collection_time | The gc time spent in G1 Old Generation in milliseconds(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Young Collection Time | ms | meter_activemq_cluster_gc_g1_young_collection_time | The gc time spent in G1 Young Generation in milliseconds(JDK[9,17]). | JMX Prometheus Exporter |
+| GC Parallel Old Collection Count | Count | meter_activemq_cluster_gc_parallel_old_collection_count | The gc count of Parallel Old Generation(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Young Collection Count | Count | meter_activemq_cluster_gc_parallel_young_collection_count | The gc count of Parallel Young Generation(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Old Collection Time | ms | meter_activemq_cluster_gc_parallel_old_collection_time | The gc time spent in Parallel Old Generation in milliseconds(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Young Collection Time | ms | meter_activemq_cluster_gc_parallel_young_collection_time | The gc time spent in Parallel Young Generation in milliseconds(JDK[6,8]). | JMX Prometheus Exporter |
+| Enqueue Rate | Count/s | meter_activemq_cluster_enqueue_rate | Number of messages that have been sent to the cluster per second(JDK[6,8]). | JMX Prometheus Exporter |
+| Dequeue Rate | Count/s | meter_activemq_cluster_dequeue_rate | Number of messages that have been acknowledged or discarded on the cluster per second.| JMX Prometheus Exporter |
+| Dispatch Rate | Count/s | meter_activemq_cluster_dispatch_rate | Number of messages that has been delivered to consumers per second. | JMX Prometheus Exporter |
+| Expired Rate | Count/s | meter_activemq_cluster_expired_rate | Number of messages that have been expired per second. | JMX Prometheus Exporter |
+| Average Enqueue Time | ms | meter_activemq_cluster_average_enqueue_time | The average time a message was held on this cluster. | JMX Prometheus Exporter |
+| Max Enqueue Time | ms | meter_activemq_cluster_max_enqueue_time | The max time a message was held on this cluster. | JMX Prometheus Exporter |
+
+### ActiveMQ Broker Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|-----------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------- |-------------------------|
+| Uptime | sec | meter_activemq_broker_uptime | Uptime of the broker in day. | JMX Prometheus Exporter |
+| State | | meter_activemq_broker_state | If slave broker 1 else 0. | JMX Prometheus Exporter |
+| Current Connections | Count | meter_activemq_broker_current_connections | The number of clients connected to the broker currently. | JMX Prometheus Exporter |
+| Current Producer Count | Count | meter_activemq_broker_current_producer_count | The number of producers currently attached to the broker. | JMX Prometheus Exporter |
+| Current Consumer Count | Count | meter_activemq_broker_current_consumer_count | The number of consumers consuming messages from the broker. | JMX Prometheus Exporter |
+| Producer Count | Count | meter_activemq_broker_producer_count | Number of message producers active on destinations. | JMX Prometheus Exporter |
+| Consumer Count | Count | meter_activemq_broker_consumer_count | Number of message consumers subscribed to destinations. | JMX Prometheus Exporter |
+| Enqueue Count | Count | meter_activemq_broker_enqueue_count | The total number of messages sent to the broker. | JMX Prometheus Exporter |
+| Dequeue Count | Count | meter_activemq_broker_dequeue_count | The total number of messages the broker has delivered to consumers. | JMX Prometheus Exporter |
+| Enqueue Rate | Count/sec | meter_activemq_broker_enqueue_rate | The total number of messages sent to the broker per second. | JMX Prometheus Exporter |
+| Dequeue Rate | Count/sec | meter_activemq_broker_dequeue_rate | The total number of messages the broker has delivered to consumers per second. | JMX Prometheus Exporter |
+| Memory Percent Usage | % | meter_activemq_broker_memory_percent_usage | Percentage of configured memory used by the broker. | JMX Prometheus Exporter |
+| Memory Usage | Bytes | meter_activemq_broker_memory_percent_usage | Memory used by undelivered messages in bytes. | JMX Prometheus Exporter |
+| Memory Limit | Bytes | meter_activemq_broker_memory_limit | Memory limited used for holding undelivered messages before paging to temporary storage. | JMX Prometheus Exporter |
+| Store Percent Usage | % | meter_activemq_broker_store_percent_usage | Percentage of available disk space used for persistent message storage. | JMX Prometheus Exporter |
+| Store Limit | Bytes | meter_activemq_broker_store_limit | Disk limited used for persistent messages before producers are blocked. | JMX Prometheus Exporter |
+| Temp Percent Usage | Bytes | meter_activemq_broker_temp_percent_usage | Percentage of available disk space used for non-persistent message storage. | JMX Prometheus Exporter |
+| Temp Limit | Bytes | meter_activemq_broker_temp_limit | Disk limited used for non-persistent messages and temporary data before producers are blocked. | JMX Prometheus Exporter |
+| Average Message Size | Bytes | meter_activemq_broker_average_message_size | Average message size on this broker. | JMX Prometheus Exporter |
+| Max Message Size | Bytes | meter_activemq_broker_max_message_size | Max message size on this broker. | JMX Prometheus Exporter |
+| Queue Size | Count | meter_activemq_broker_queue_size | Number of messages on this broker that have been dispatched but not acknowledged. | JMX Prometheus Exporter |
+
+### ActiveMQ Destination Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------------------|
+| Producer Count | Count | meter_activemq_destination_producer_count | Number of producers attached to this destination. | JMX Prometheus Exporter |
+| Consumer Count | Count | meter_activemq_destination_consumer_count | Number of consumers subscribed to this destination. | JMX Prometheus Exporter |
+| Topic Consumer Count | Count | meter_activemq_destination_topic_consumer_count | Number of consumers subscribed to the topics. | JMX Prometheus Exporter |
+| Queue Size | Count | meter_activemq_destination_queue_size | The number of messages that have not been acknowledged by a consumer. | JMX Prometheus Exporter |
+| Memory Usage | Bytes | meter_activemq_destination_memory_usage | Memory used by undelivered messages in bytes. | JMX Prometheus Exporter |
+| Memory Percent Usage | % | meter_activemq_destination_memory_percent_usage | Percentage of configured memory used by the destination. | JMX Prometheus Exporter |
+| Enqueue Count | Count | meter_activemq_destination_enqueue_count | The number of messages sent to the destination. | JMX Prometheus Exporter |
+| Dequeue Count | Count | meter_activemq_destination_dequeue_count | The number of messages the destination has delivered to consumers. | JMX Prometheus Exporter |
+| Average Enqueue Time | ms | meter_activemq_destination_average_enqueue_time | The average time a message was held on this destination. | JMX Prometheus Exporter |
+| Max Enqueue Time | ms | meter_activemq_destination_max_enqueue_time | The max time a message was held on this destination. | JMX Prometheus Exporter |
+| Dispatch Count | Count | meter_activemq_destination_dispatch_count | Number of messages that has been delivered to consumers. | JMX Prometheus Exporter |
+| Expired Count | Count | meter_activemq_destination_expired_count | Number of messages that have been expired. | JMX Prometheus Exporter |
+| Inflight Count | Count | meter_activemq_destination_inflight_count | Number of messages that have been dispatched to but not acknowledged by consumers. | JMX Prometheus Exporter |
+| Average Message Size | Bytes | meter_activemq_destination_average_message_size | Average message size on this destination. | JMX Prometheus Exporter |
+| Max Message Size | Bytes | meter_activemq_destination_max_message_size | Max message size on this destination. | JMX Prometheus Exporter |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `otel-rules/activemq/activemq-cluster.yaml, otel-rules/activemq/activemq-broker.yaml, otel-rules/activemq/activemq-destination.yaml`.
+The ActiveMQ dashboard panel configurations are found in `ui-initialized-templates/activemq`.
diff --git a/docs/en/setup/backend/backend-alarm.md b/docs/en/setup/backend/backend-alarm.md
new file mode 100644
index 000000000000..1ef45343ff4b
--- /dev/null
+++ b/docs/en/setup/backend/backend-alarm.md
@@ -0,0 +1,444 @@
+# Alerting
+Alerting mechanism measures system performance according to the metrics of services/instances/endpoints from different layers.
+Alerting kernel is an in-memory, time-window based queue.
+
+The alerting core is driven by a collection of rules defined in `config/alarm-settings.yml.`
+There are three parts to alerting rule definitions.
+1. [alerting rules](#rules). They define how metrics alerting should be triggered and what conditions should be considered.
+1. [hooks](#hooks). The list of hooks, which should be called after an alerting is triggered.
+
+## Entity name
+Defines the relation between scope and entity name.
+- **Service**: Service name
+- **Instance**: {Instance name} of {Service name}
+- **Endpoint**: {Endpoint name} in {Service name}
+- **Service Relation**: {Source service name} to {Dest service name}
+- **Instance Relation**: {Source instance name} of {Source service name} to {Dest instance name} of {Dest service name}
+- **Endpoint Relation**: {Source endpoint name} in {Source Service name} to {Dest endpoint name} in {Dest service name}
+
+## Rules
+An alerting rule is made up of the following elements:
+- **Rule name**. A unique name shown in the alarm message. It must end with `_rule`.
+- **Expression**. A [MQE](../../api/metrics-query-expression.md) expression that defines the conditions of the rule.
+The result type must be `SINGLE_VALUE` and the root operation of the expression must be a
+[Compare Operation](../../api/metrics-query-expression.md#compare-operation) or [Bool Operation](../../api/metrics-query-expression.md#bool-operation) which provides `1`(true) or `0`(false) result.
+When the result is `1`(true), the alarm will be triggered.
+For example, `avg(service_resp_time / 1000) > 1` is a valid expression to indicate the request latency is slower than 1s. The typical illegal expressions are
+ - `avg(service_resp_time > 1000) + 1` expression root doesn't use `Compare Operation`
+ - `service_resp_time > 1000` expression return a `TIME_SERIES_VALUES` type of values rather than a `SINGLE_VALUE` value.
+
+The metrics names in the expression could be found in the [list of all potential metrics name](#list-of-all-potential-metrics-name) doc.
+- **Include names**. Entity names that are included in this rule. Please follow the [entity name definitions](#entity-name).
+- **Exclude names**. Entity names that are excluded from this rule. Please follow the [entity name definitions](#entity-name).
+- **Include names regex**. A regex that includes entity names. If both include-name list and include-name regex are set, both rules will take effect.
+- **Exclude names regex**. A regex that excludes entity names. Both rules will take effect if both include-label list and include-label regex are set.
+- **Tags**. Tags are key/value pairs that are attached to alarms. Tags are used to specify distinguishing attributes of alarms that are meaningful and relevant to users. If you want to make these tags searchable on the SkyWalking UI, you may set the tag keys in `core/default/searchableAlarmTags` or through the system environment variable `SW_SEARCHABLE_ALARM_TAG_KEYS`. The key `level` is supported by default.
+- **Period**. The size of metrics cache in minutes for checking the alarm conditions. This is a time window that corresponds to the backend deployment env time.
+- **Hooks**. Binding the specific names of the hooks when the alarm is triggered.
+ The name format is `{hookType}.{hookName}` (slack.custom1 e.g.) and must be defined in the `hooks` section of the `alarm-settings.yml` file.
+ If the hook name is not specified, the global hook will be used.
+- **Silence period**. After the alarm is triggered at Time-N (TN), there will be silence during the **TN -> TN + period**.
+By default, it works in the same manner as **period**. The same Alarm (having the same ID in the same metrics name) may only be triggered once within a period.
+
+Such as for a metric, there is a shifting window as following at T7.
+
+| T1 | T2 | T3 | T4 | T5 | T6 | T7 |
+|--------|--------|--------|--------|--------|--------|--------|
+| Value1 | Value2 | Value3 | Value4 | Value5 | Value6 | Value7 |
+
+* `Period`(Time point T1 ~ T7) are continuous data points for minutes. Notice, alerts are not supported above minute-by-minute periods as they would not be efficient.
+* Values(Value1 ~ Value7) are the values or labeled values for every time point.
+* `Expression` is calculated based on the metric values(Value1 ~ Value7).
+For example, expression `avg(service_resp_time) > 1000`, if the value are `1001, 1001, 1001, 1001, 1001, 1001, 1001`,
+the calculation is `((1001 + 10001 + ... + 1001) / 7) > 1000` and the result would be `1`(true). Then the alarm would be triggered.
+* In every minute, the window would shift automatically. At T8, Value8 would be cached, and T1/Value1 would be removed from the window.
+
+**NOTE**:
+* If the expression include labeled metrics and result has multiple labeled value(e.g. `sum(service_percentile{p='50,75'} > 1000) >= 3`), the alarm will be triggered if any of the labeled value result matches 3 times of the condition(P50 > 1000 or P75 > 1000).
+* One alarm rule is targeting the same entity level, such as service-level expression (`avg(service_resp_time) > 1000`).
+ Set entity names(Include/Exclude names...) according to metrics entity levels,
+ do not include different entity levels metrics in the same expression, such as service metrics and endpoint metrics.
+
+```yaml
+rules:
+ # Rule unique name, must be ended with `_rule`.
+ endpoint_percent_rule:
+ # A MQE expression and the root operation of the expression must be a Compare Operation.
+ expression: sum((endpoint_sla / 100) < 75) >= 3
+ # The length of time to evaluate the metrics
+ period: 10
+ # How many times of checks, the alarm keeps silence after alarm triggered, default as same as period.
+ silence-period: 10
+ message: Successful rate of endpoint {name} is lower than 75%
+ tags:
+ level: WARNING
+ service_percent_rule:
+ expression: sum((service_sla / 100) < 85) >= 4
+ # [Optional] Default, match all services in this metrics
+ include-names:
+ - service_a
+ - service_b
+ exclude-names:
+ - service_c
+ period: 10
+ message: Service {name} successful rate is less than 85%
+ service_resp_time_percentile_rule:
+ expression: sum(service_percentile{p='50,75,90,95,99'} > 1000) >= 3
+ period: 10
+ silence-period: 5
+ message: Percentile response time of service {name} alarm in 3 minutes of last 10 minutes, due to more than one condition of p50 > 1000, p75 > 1000, p90 > 1000, p95 > 1000, p99 > 1000
+ meter_service_status_code_rule:
+ expression: sum(aggregate_labels(meter_status_code{status='4xx,5xx'},sum) > 10) > 3
+ period: 10
+ silence-period: 5
+ message: The request number of entity {name} 4xx and 5xx status is more than expected.
+ hooks:
+ - "slack.custom1"
+ - "pagerduty.custom1"
+ comp_rule:
+ expression: (avg(service_sla / 100) > 80) && (avg(service_percentile{p='0'}) > 1000)
+ period: 10
+ message: Service {name} avg successful rate is less than 80% and P50 of avg response time is over 1000ms in last 10 minutes.
+ tags:
+ level: CRITICAL
+ hooks:
+ - "slack.default"
+ - "slack.custom1"
+ - "pagerduty.custom1"
+```
+
+
+### Default alarm rules
+For convenience's sake, we have provided a default `alarm-setting.yml` in our release. It includes the following rules:
+1. Service average response time over 1s in the last 3 minutes.
+1. Service success rate lower than 80% in the last 2 minutes.
+1. Percentile of service response time over 1s in the last 3 minutes
+1. Service Instance average response time over 1s in the last 2 minutes, and the instance name matches the regex.
+1. Endpoint average response time over 1s in the last 2 minutes.
+1. Database access average response time over 1s in the last 2 minutes.
+1. Endpoint relation average response time over 1s in the last 2 minutes.
+
+### List of all potential metrics name
+The metrics names are defined in the official [OAL scripts](../../guides/backend-oal-scripts.md) and [MAL scripts](../../concepts-and-designs/mal.md).
+
+Currently, metrics from the **Service**, **Service Instance**, **Endpoint**, **Service Relation**, **Service Instance Relation**, **Endpoint Relation** scopes could be used in Alarm, and the **Database access** scope is the same as **Service**.
+
+Submit an issue or a pull request if you want to support any other scopes in Alarm.
+
+### Use the Baseline Predicted Value to trigger the Alarm
+Since 10.2.0, SkyWalking supports using the baseline predicted value in the alarm rule expression.
+The MQE expression can refer to [Baseline Operation](../../api/metrics-query-expression.md#baseline-operation).
+
+For example, the following rule will compare the service response time with the baseline predicted value in each time bucket, and
+when the service response time is higher than the baseline predicted value in 3 minutes of the last 10 minutes, the alarm will be triggered.
+
+```yaml
+rules:
+ service_resp_time_rule:
+ expression: sum(service_resp_time > baseline(service_resp_time, upper)) > 3
+ period: 10
+ message: Service {name} response time is higher than the baseline predicted value in 3 minutes of last 10 minutes.
+```
+
+Note, the baseline predicted value is calculated based on the historical data of the same time window in the past, which
+is through [AI powered baseline calculation](../ai-pipeline/metrics-baseline-integration.md).
+
+## Hooks
+Hooks are a way to send alarm messages to the outside world. SkyWalking supports multiple hooks of the same type, each hook can support different configurations.
+For example, you can configure two Slack hooks, one named `default` and set `is-default: true` means this hook will apply on all `Alarm Rules` **without config** `hooks`.
+Another named `custom1` will only apply on the `Alarm Rules` which **with config** `hooks` and include the name `slack.custom1`.
+
+```yaml
+hooks:
+ slack:
+ # default here is just a name, set the field 'is-default: true' if this notification hook is expected to be default globally.
+ default:
+ # If true, this hook will apply on all rules, unless a rule has its own specific hook. Could have more than one default hooks in the same hook type.
+ is-default: true
+ text-template: |-
+ {
+ "type": "section",
+ "text": {
+ "type": "mrkdwn",
+ "text": ":alarm_clock: *Apache Skywalking Alarm* \n **%s**."
+ }
+ }
+ webhooks:
+ - https://hooks.slack.com/services/x/y/zssss
+ custom1:
+ text-template: |-
+ {
+ "type": "section",
+ "text": {
+ "type": "mrkdwn",
+ "text": ":alarm_clock: *Apache Skywalking Alarm* \n **%s**."
+ }
+ }
+ webhooks:
+ - https://hooks.slack.com/services/x/y/custom1
+```
+
+Currently, SkyWalking supports the following hook types:
+
+### Webhook
+The Webhook requires the peer to be a web container. The alarm message will be sent through HTTP post by `application/json` content type after you have set up Webhook hooks as follows:
+```yml
+webhook:
+ default:
+ is-default: true
+ urls:
+ - http://ip:port/xxx
+ - http://ip:port/yyy
+ custom1:
+ urls:
+ - http://127.0.0.1/custom1
+ # headers config is provided to add custom configurations or authentications that are required from the server side.
+ headers:
+ Authorization: Bearer bearer_token
+ custom2:
+ urls:
+ - http://127.0.0.1/custom2
+ # headers config is provided to add custom configurations or authentications that are required from the server
+ headers:
+ Authorization: Basic basic_token
+ custom3:
+ urls:
+ - http://127.0.0.1/internal-hook
+ # headers config is provided to add custom configurations or authentications that are required from the server
+ headers:
+ x-company-token: whatever-token-defined-internally-within-the-company
+ x-company-header: arbitrary-additional-http-headers
+```
+
+The JSON format is based on `List` with the following key information:
+- **scopeId**, **scope**. All scopes are defined in `org.apache.skywalking.oap.server.core.source.DefaultScopeDefine`.
+- **name**. Target scope entity name. Please follow the [entity name definitions](#entity-name).
+- **id0**. The ID of the scope entity that matches with the name. When using the relation scope, it is the source entity ID.
+- **id1**. When using the relation scope, it is the destination entity ID. Otherwise, it is empty.
+- **ruleName**. The rule name configured in `alarm-settings.yml`.
+- **alarmMessage**. The alarm text message.
+- **startTime**. The alarm time measured in milliseconds, which occurs between the current time and the midnight of January 1, 1970 UTC.
+- **tags**. The tags configured in `alarm-settings.yml`.
+
+See the following example:
+```json
+[{
+ "scopeId": 1,
+ "scope": "SERVICE",
+ "name": "serviceA",
+ "id0": "12",
+ "id1": "",
+ "ruleName": "service_resp_time_rule",
+ "alarmMessage": "alarmMessage xxxx",
+ "startTime": 1560524171000,
+ "tags": [{
+ "key": "level",
+ "value": "WARNING"
+ }]
+}, {
+ "scopeId": 1,
+ "scope": "SERVICE",
+ "name": "serviceB",
+ "id0": "23",
+ "id1": "",
+ "ruleName": "service_resp_time_rule",
+ "alarmMessage": "alarmMessage yyy",
+ "startTime": 1560524171000,
+ "tags": [{
+ "key": "level",
+ "value": "CRITICAL"
+ }]
+}]
+```
+
+### gRPC
+The alarm message will be sent through remote gRPC method by `Protobuf` content type after you have set up gRPC hooks as follows:
+```yml
+gRPC:
+ default:
+ is-default: true
+ target-host: ip
+ target-port: port
+```
+
+The message contains key information which are defined in `oap-server/server-alarm-plugin/src/main/proto/alarm-hook.proto`.
+
+Part of the protocol looks like this:
+```protobuf
+message AlarmMessage {
+ int64 scopeId = 1;
+ string scope = 2;
+ string name = 3;
+ string id0 = 4;
+ string id1 = 5;
+ string ruleName = 6;
+ string alarmMessage = 7;
+ int64 startTime = 8;
+ AlarmTags tags = 9;
+}
+
+message AlarmTags {
+ // String key, String value pair.
+ repeated KeyStringValuePair data = 1;
+}
+
+message KeyStringValuePair {
+ string key = 1;
+ string value = 2;
+}
+```
+
+### Slack Chat
+Follow the [Getting Started with Incoming Webhooks guide](https://api.slack.com/messaging/webhooks) and create new Webhooks.
+
+The alarm message will be sent through HTTP post by `application/json` content type if you have configured Slack Incoming Webhooks as follows:
+```yml
+slack:
+ default:
+ is-default: true
+ text-template: |-
+ {
+ "type": "section",
+ "text": {
+ "type": "mrkdwn",
+ "text": ":alarm_clock: *Apache Skywalking Alarm* \n **%s**."
+ }
+ }
+ webhooks:
+ - https://hooks.slack.com/services/x/y/z
+```
+
+### WeChat
+Note that only the WeChat Company Edition (WeCom) supports WebHooks. To use the WeChat WebHook, follow the [Wechat Webhooks guide](https://work.weixin.qq.com/help?doc_id=13376).
+The alarm message will be sent through HTTP post by `application/json` content type after you have set up Wechat Webhooks as follows:
+```yml
+wechat:
+ default:
+ is-default: true
+ text-template: |-
+ {
+ "msgtype": "text",
+ "text": {
+ "content": "Apache SkyWalking Alarm: \n %s."
+ }
+ }
+ webhooks:
+ - https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=dummy_key
+```
+
+### DingTalk
+Follow the [Dingtalk Webhooks guide](https://ding-doc.dingtalk.com/doc#/serverapi2/qf2nxq/uKPlK) and create new Webhooks.
+You can configure an optional secret for an individual webhook URL for security purposes.
+The alarm message will be sent through HTTP post by `application/json` content type if you have configured DingTalk Webhooks as follows:
+```yml
+dingtalk:
+ default:
+ is-default: true
+ text-template: |-
+ {
+ "msgtype": "text",
+ "text": {
+ "content": "Apache SkyWalking Alarm: \n %s."
+ }
+ }
+ webhooks:
+ - url: https://oapi.dingtalk.com/robot/send?access_token=dummy_token
+ secret: dummysecret
+```
+
+### Feishu
+Follow the [Feishu Webhooks guide](https://www.feishu.cn/hc/zh-cn/articles/360024984973) and create new Webhooks.
+You can configure an optional secret for an individual webhook URL for security purposes.
+If you want to direct a text to a user, you can configure `ats`, which is Feishu's user_id and separated by "," .
+The alarm message will be sent through HTTP post by `application/json` content type if you have configured Feishu Webhooks as follows:
+```yml
+feishu:
+ default:
+ is-default: true
+ text-template: |-
+ {
+ "msg_type": "text",
+ "content": {
+ "text": "Apache SkyWalking Alarm: \n %s."
+ },
+ "ats":"feishu_user_id_1,feishu_user_id_2"
+ }
+ webhooks:
+ - url: https://open.feishu.cn/open-apis/bot/v2/hook/dummy_token
+ secret: dummysecret
+```
+
+### WeLink
+Follow the [WeLink Webhooks guide](https://open.welink.huaweicloud.com/apiexplorer/#/apiexplorer?type=internal&method=POST&path=/welinkim/v1/im-service/chat/group-chat) and create new Webhooks.
+The alarm message will be sent through HTTP post by `application/json` content type if you have configured WeLink Webhooks as follows:
+```yml
+welink:
+ default:
+ is-default: true
+ text-template: "Apache SkyWalking Alarm: \n %s."
+ webhooks:
+ # you may find your own client_id and client_secret in your app, below are dummy, need to change.
+ - client-id: "dummy_client_id"
+ client-secret: dummy_secret_key
+ access-token-url: https://open.welink.huaweicloud.com/api/auth/v2/tickets
+ message-url: https://open.welink.huaweicloud.com/api/welinkim/v1/im-service/chat/group-chat
+ # if you send to multi group at a time, separate group_ids with commas, e.g. "123xx","456xx"
+ group-ids: "dummy_group_id"
+ # make a name you like for the robot, it will display in group
+ robot-name: robot
+```
+
+
+### PagerDuty
+The PagerDuty hook is based on [Events API v2](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview).
+
+Follow the [Getting Started](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview#getting-started) section to create an **Events API v2** integration on your PagerDuty service and copy the integration key.
+
+Then configure as follows:
+```yml
+pagerduty:
+ default:
+ is-default: true
+ text-template: "Apache SkyWalking Alarm: \n %s."
+ integration-keys:
+ - 5c6d805c9dcf4e03d09dfa81e8789ba1
+```
+
+You can also configure multiple integration keys.
+
+### Discord
+Follow the [Discord Webhooks guide](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) and create a new webhook.
+
+Then configure as follows:
+```yml
+discord:
+ default:
+ is-default: true
+ text-template: "Apache SkyWalking Alarm: \n %s."
+ webhooks:
+ - url: https://discordapp.com/api/webhooks/1008166889777414645/8e0Am4Zb-YGbBqqbiiq0jSHPTEEaHa4j1vIC-zSSm231T8ewGxgY0_XUYpY-k1nN4HBl
+ username: robot
+```
+
+## Update the settings dynamically
+Since 6.5.0, the alerting settings can be updated dynamically at runtime by [Dynamic Configuration](dynamic-config.md),
+which will override the settings in `alarm-settings.yml`.
+
+In order to determine whether an alerting rule is triggered or not, SkyWalking needs to cache the metrics of a time window for
+each alerting rule. If any attribute (`expression`, `period`, etc.) of a rule is changed,
+the sliding window will be destroyed and re-created, causing the Alarm of this specific rule to restart again.
+
+### Keys with data types of alerting rule configuration file
+
+| Alerting element | Configuration property key | Type | Description |
+|----------------------|----------------------------|----------------|--------------------|
+| Expression | expression | string | MQE expression |
+| Include names | include-names | string array | |
+| Exclude names | exclude-names | string array | |
+| Include names regex | include-names-regex | string | Java regex Pattern |
+| Exclude names regex | exclude-names-regex | string | Java regex Pattern |
+| Tags | tags | key-value pair | |
+| Period | Period | int | |
+| Silence period | silence-period | int | |
+| Message | message | string | |
+| Hooks | hooks | string array | |
diff --git a/docs/en/setup/backend/backend-apisix-monitoring.md b/docs/en/setup/backend/backend-apisix-monitoring.md
new file mode 100644
index 000000000000..28e243c82c57
--- /dev/null
+++ b/docs/en/setup/backend/backend-apisix-monitoring.md
@@ -0,0 +1,80 @@
+# APISIX monitoring
+## APISIX performance from `apisix prometheus plugin`
+SkyWalking leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. [APISIX Prometheus plugin](https://apisix.apache.org/docs/apisix/plugins/prometheus/) collects metrics data from APSIX.
+2. OpenTelemetry Collector fetches metrics from [APISIX Prometheus plugin](https://apisix.apache.org/docs/apisix/plugins/prometheus/) via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Enable APISIX [APISIX Prometheus plugin](https://apisix.apache.org/docs/apisix/plugins/prometheus/) .
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on Prometheus Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/apisix/otel-collector/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### APISIX Monitoring
+[APISIX prometheus plugin](https://apisix.apache.org/docs/apisix/plugins/prometheus/) provide multiple dimensions metrics for APISIX server , upstream , route , etc.
+Accordingly, SkyWalking observes the status, payload, and latency of the APISIX server, which is cataloged as a `LAYER: APISIX` `Service` in the OAP. Meanwhile, the instances would be recognized as `LAYER: APISIX` `instance`s. The route rules and nodes would be recognized as `endpoint`s with `route/` and `upstream/` prefixes.
+
+#### Specify SkyWalking Service name
+
+SkyWalking expects OTEL Collector attribute `skywalking_service` to be the `Service` name.
+
+Make sure `skywalking_service` attribute exists through `static_configs` of OTEL Prometheus scape config.
+
+```yaml
+receivers:
+ prometheus:
+ config:
+ scrape_configs:
+ - job_name: 'apisix-monitoring'
+ static_configs:
+ - targets: ['apisix:9091']
+ labels:
+ skywalking_service: exmple_service_name # Specify SkyWalking Service name
+```
+
+You also could leverage OTEL Collector processor to add `skywalking_service` attribute , as following :
+
+```yaml
+processors:
+ resource/skywalking-service:
+ attributes:
+ - key: skywalking_service
+ value: exmple_service_name # Specify Skywalking Service name
+ action: insert
+```
+Notice , if you don't specify `skywalking_service` attribute, SkyWalking OAP would use `APISIX` as the default service name
+
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|-------------------------------------|------|----------------------------------------------------|----------|------------------------------------------------------------------------------------------------------------------------|--------------------------|
+| HTTP status | | meter_apisix_sv_http_status | Service | The increment rate of the status of HTTP requests | APISIX Prometheus plugin |
+| HTTP latency | | meter_apisix_sv_http_latency | Service | The increment rate of the latency of HTTP requests | APISIX Prometheus plugin |
+| HTTP bandwidth | KB | meter_apisix_sv_bandwidth | Service | The increment rate of the bandwidth of HTTP requests | APISIX Prometheus plugin |
+| HTTP status of non-matched requests | | meter_apisix_sv_http_status | Service | The increment rate of the status of HTTP requests, which don't match any route | APISIX Prometheus plugin |
+| HTTP latency non-matched requests | | meter_apisix_sv_http_latency | Service | The increment rate of the latency of HTTP requests, which don't match any route | APISIX Prometheus plugin |
+| HTTP bandwidth non-matched requests | KB | meter_apisix_sv_bandwidth | Service | The increment rate of the bandwidth of HTTP requests ,which don't match any route | APISIX Prometheus plugin |
+| HTTP connection | | meter_apisix_sv_http_connections | Service | The avg number of the connections | APISIX Prometheus plugin |
+| HTTP Request Trend | | meter_apisix_http_requests | Service | The increment rate of HTTP requests | APISIX Prometheus plugin |
+| HTTP status | | meter_apisix_instance_http_status | Instance | The increment rate of the status of HTTP requests | APISIX Prometheus plugin |
+| HTTP latency | | meter_apisix_instance_http_latency | Instance | The increment rate of the latency of HTTP requests | APISIX Prometheus plugin |
+| HTTP bandwidth | KB | meter_apisix_instance_bandwidth | Instance | The increment rate of the bandwidth of HTTP requests | APISIX Prometheus plugin |
+| HTTP status of non-matched requests | | meter_apisix_instance_http_status | Instance | The increment rate of the status of HTTP requests, which don't match any route | APISIX Prometheus plugin |
+| HTTP latency non-matched requests | | meter_apisix_instance_http_latency | Instance | The increment rate of the latency of HTTP requests, which don't match any route | APISIX Prometheus plugin |
+| HTTP bandwidth non-matched requests | KB | meter_apisix_instance_bandwidth | Instance | The increment rate of the bandwidth of HTTP requests ,which don't match any route | APISIX Prometheus plugin |
+| HTTP connection | | meter_apisix_instance_http_connections | Instance | The avg number of the connections | APISIX Prometheus plugin |
+| HTTP Request Trend | | meter_apisix_instance_http_requests | Instance | The increment rate of HTTP requests | APISIX Prometheus plugin |
+| Shared dict capacity | MB | meter_apisix_instance_shared_dict_capacity_bytes | Instance | The avg capacity of shared dict capacity | APISIX Prometheus plugin |
+| Shared free space | MB | meter_apisix_instance_shared_dict_free_space_bytes | Instance | The avg free space of shared dict capacity | APISIX Prometheus plugin |
+| etcd index | | meter_apisix_instance_sv_etcd_indexes | Instance | etcd modify index for APISIX keys | APISIX Prometheus plugin |
+| etcd latest reachability | | meter_apisix_instance_sv_etcd_reachable | Instance | etcd latest reachable , Refer to [APISIX Prometheus plugin](https://apisix.apache.org/docs/apisix/plugins/prometheus/) | APISIX Prometheus plugin |
+| HTTP status | | meter_apisix_endpoint_node_http_status | Endpoint | The increment rate of the status of HTTP requests | APISIX Prometheus plugin |
+| HTTP latency | | meter_apisix_endpoint_node_http_latency | Endpoint | The increment rate of the latency of HTTP requests | APISIX Prometheus plugin |
+| HTTP bandwidth | KB | meter_apisix_endpoint_node_bandwidth | Endpoint | The increment rate of the bandwidth of HTTP requests | APISIX Prometheus plugin |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/apisix.yaml`.
+The APISIX dashboard panel configurations are found in `/config/ui-initialized-templates/apisix`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-aws-api-gateway-monitoring.md b/docs/en/setup/backend/backend-aws-api-gateway-monitoring.md
new file mode 100644
index 000000000000..4b3e7d308ec6
--- /dev/null
+++ b/docs/en/setup/backend/backend-aws-api-gateway-monitoring.md
@@ -0,0 +1,46 @@
+# AWS API Gateway monitoring
+Amazon API Gateway is an AWS service for creating, publishing, maintaining, monitoring, and securing REST, HTTP, and WebSocket APIs. SkyWalking leverages [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md) to transfer the CloudWatch metrics of API Gateway(HTTP and REST APIs) to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. AWS CloudWatch collect metrics for API Gateway(REST and HTTP APIs), refer to [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html)
+2. [CloudWatch metric streams](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html) stream CloudWatch metrics of API Gateway to AWS Kinesis Data Firehose
+3. AWS Kinesis Data Firehose delivery metrics to [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md) through the HTTP endpoint
+
+### Set up
+1. Enable CloudWatch metrics for API Gateway
+2. Create an Amazon Kinesis Data Firehose Delivery Stream, and set [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md)'s address as HTTP(s) Destination, refer to [Create Delivery Stream](https://docs.aws.amazon.com/firehose/latest/dev/basic-create.html)
+3. Create CloudWatch metric stream, and select the Firehose Delivery Stream which has been created above, set `Select namespaces` to `AWS/ApiGateway`, `Select output format` to `OpenTelemetry 0.7`. refer to [CloudWatch Metric Streams](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html)
+
+### Gateway Monitoring
+
+SkyWalking observes CloudWatch metrics of the AWS API Gateway, which is cataloged as a `LAYER: AWS_GATEWAY` `Service` in the OAP. Meanwhile, the routes would be recognized as `LAYER: AWS_GATEWAY` `endpoint`s
+
+#### Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|-------------------------------------|-------|------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Request Count | count | aws_gateway_service_count | Service | The total number API requests in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| 4xx Count | count | aws_gateway_service_4xx | Service | The number of client-side errors captured in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| 5xx Count | count | aws_gateway_service_5xx | Service | The number of server-side errors captured in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Request Average Latency | ms | aws_gateway_service_latency | Service | The time between when API Gateway receives a request from a client and when it returns a response to the client. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Request Average Integration Latency | ms | aws_gateway_service_integration_latency | Service | The time between when API Gateway relays a request to the backend and when it receives a response from the backend. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Data Processed | KB | aws_gateway_service_data_processed | Service | The amount of data processed | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) |
+| Cache Hit Count Rate | % | aws_gateway_service_cache_hit_rate | Service | The number of requests served from the API cache | [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Cache Miss Count Rate | % | aws_gateway_service_cache_miss_rate | Service | The number of requests served from the backend | [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Request Count | count | aws_gateway_endpoint_count | Endpoint | The total number API requests in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| 4xx Count | count | aws_gateway_endpoint_4xx | Endpoint | The number of client-side errors captured in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| 5xx Count | count | aws_gateway_endpoint_5xx | Endpoint | The number of server-side errors captured in a given period. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Request Average Latency | ms | aws_gateway_endpoint_latency | Endpoint | The time between when API Gateway receives a request from a client and when it returns a response to the client. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Request Average Integration Latency | ms | aws_gateway_endpoint_integration_latency | Endpoint | The time between when API Gateway relays a request to the backend and when it receives a response from the backend. | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) and [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Data Processed | KB | aws_gateway_endpoint_data_processed | Endpoint | The amount of data processed | [API Gateway HTTP APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-metrics.html) |
+| Cache Hit Count Rate | % | aws_gateway_endpoint_cache_hit_rate | Endpoint | The number of requests served from the API cache | [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+| Cache Miss Count Rate | % | aws_gateway_endpoint_cache_miss_rate | Endpoint | The number of requests served from the backend | [API Gateway REST APIs monitoring with CloudWatch](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-metrics-and-dimensions.html) |
+
+
+
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/aws-gateway/`.
+The AWS Cloud EKS dashboard panel configurations are found in `/config/ui-initialized-templates/aws_gateway`.
diff --git a/docs/en/setup/backend/backend-aws-dynamodb-monitoring.md b/docs/en/setup/backend/backend-aws-dynamodb-monitoring.md
new file mode 100644
index 000000000000..053cbed4ec3b
--- /dev/null
+++ b/docs/en/setup/backend/backend-aws-dynamodb-monitoring.md
@@ -0,0 +1,38 @@
+# AWS DynamoDb monitoring
+SkyWalking leverages Amazon Kinesis Data Filehose with [Amazon CloudWatch](https://aws.amazon.com/cn/cloudwatch/) to transfer the metrics into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. Amazon CloudWatch fetches metrics from DynamoDB and pushes metrics to SkyWalking OAP Server via Amazon Kinesis data firehose.
+2. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Create CloudWatch metrics configuration for DynamoDB, refer to [DynamoDB metrics configuration](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/monitoring-cloudwatch.html)
+ Create an Amazon Kinesis Data Firehose Delivery Stream, and set [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md)'s address as HTTP(s) Destination, refer to [Create Delivery Stream](https://docs.aws.amazon.com/firehose/latest/dev/basic-create.html)3. Create a [metric stream](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html), set namespace to DynanoDB, and set `Kinesis Data Firehose` to the firehose you just created.
+2. Config [aws-firehose-receiver](aws-firehose-receiver.md) to receive data.
+3. Create CloudWatch metric stream, and select the Firehose Delivery Stream which has been created above, set `Select namespaces` to `AWS/DynamoDB`, `Select output format` to `OpenTelemetry 0.7`. refer to [CloudWatch Metric Streams](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html)
+
+Read [Monitoring DynamoDB with SkyWalking](https://skywalking.apache.org/blog/2023-03-13-skywalking-aws-dynamodb/) for more details
+
+### DynamoDB Monitoring
+DynamoDB monitoring provides monitoring of the status and resources of the DynamoDB server. AWS user id is cataloged as a `Layer: AWS_DYNAMODB` `Service` in OAP.
+Each DynamoDB table is cataloged as an `Endpoint` in OAP.
+
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|-----|-----|-----|--|
+| Read Usage | unit/s | consumed_read_capacity_units
provisioned_read_capacity_units| The situation of read capacity units consumed and provisioned over the specified time period | Amazon CloudWatch |
+| Write Usage | unit/s | consumed_write_capacity_units
provisioned_write_capacity_units| The situation of write capacity units consumed and provisioned over the specified time period | Amazon CloudWatch |
+| Successful Request Latency | ms | get_successful_request_latency
put_successful_request_latency
query_successful_request_latency
scan_successful_request_latency | The latency of successful request | Amazon CloudWatch |
+| TTL Deleted Item count | | time_to_live_deleted_item_count | The count of items deleted by TTL | Amazon CloudWatch |
+| Throttle Events| | read_throttle_events
write_throttle_events | Requests to DynamoDB that exceed the provisioned read/write capacity units for a table or a global secondary index. | Amazon CloudWatch |
+| Throttled Requests | | read_throttled_requests
write_throttled_requests | Requests to DynamoDB that exceed the provisioned throughput limits on a resource (such as a table or an index). | Amazon CloudWatch |
+| Scan/Query Operation Returned Item Ccount | | scan_returned_item_count
query_returned_item_count
| The number of items returned by Query, Scan or ExecuteStatement (select) operations during the specified time period. | Amazon CloudWatch |
+| System Errors | | read_system_errors
write_system_errors | The requests to DynamoDB or Amazon DynamoDB Streams that generate an HTTP 500 status code during the specified time period. | Amazon CloudWatch |
+| User Errors | | user_errors | Requests to DynamoDB or Amazon DynamoDB Streams that generate an HTTP 400 status code during the specified time period.| Amazon CloudWatch |
+| Condition Checked Fail Requests | | conditional_check_failed_requests | The number of failed attempts to perform conditional writes. | Amazon CloudWatch |
+| Transaction Conflict | | transaction_conflict | Rejected item-level requests due to transactional conflicts between concurrent requests on the same items. | Amazon CloudWatch |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/aws-dynamodb`.
+The DynamoDB dashboard panel configurations are found in `/config/ui-initialized-templates/aws_dynamodb`.
diff --git a/docs/en/setup/backend/backend-aws-eks-monitoring.md b/docs/en/setup/backend/backend-aws-eks-monitoring.md
new file mode 100644
index 000000000000..b787aea6dfcf
--- /dev/null
+++ b/docs/en/setup/backend/backend-aws-eks-monitoring.md
@@ -0,0 +1,102 @@
+# AWS Cloud EKS monitoring
+SkyWalking leverages OpenTelemetry Collector with [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. OpenTelemetry Collector fetches metrics from EKS via [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+2. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Deploy [amazon/aws-otel-collector](https://hub.docker.com/r/amazon/aws-otel-collector) with [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) to EKS
+2. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+Read [Monitoring AWS EKS and S3 with SkyWalking](https://skywalking.apache.org/blog/2023-03-12-skywalking-aws-s3-eks/) for more details
+
+### EKS Monitoring
+[AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) provides multiple dimensions metrics for EKS cluster, node, service, etc.
+Accordingly, SkyWalking observes the status, and payload of the EKS cluster, which is cataloged as a `LAYER: AWS_EKS` `Service` in the OAP. Meanwhile, the k8s nodes would be recognized as `LAYER: AWS_EKS` `instance`s. The k8s service would be recognized as `endpoint`s.
+
+#### Specify Job Name
+
+SkyWalking distinguishes AWS Cloud EKS metrics by attributes `job_name`, which value is `aws-cloud-eks-monitoring`.
+You could leverage OTEL Collector processor to add the attribute as follows:
+
+```yaml
+processors:
+ resource/job-name:
+ attributes:
+ - key: job_name
+ value: aws-cloud-eks-monitoring
+ action: insert
+```
+
+Notice, if you don't specify `job_name` attribute, SkyWalking OAP will ignore the metrics
+
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|---------------------------------------|---------|--------------------------------------------|------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Node Count | | eks_cluster_node_count | Service | The node count of the EKS cluster | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Failed Node Count | | eks_cluster_failed_node_count | Service | The failed node count of the EKS cluster | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Pod Count (namespace dimension) | | eks_cluster_namespace_count | Service | The count of pod in the EKS cluster(namespace dimension) | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Pod Count (service dimension) | | eks_cluster_service_count | Service | The count of pod in the EKS cluster(service dimension) | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX Dropped Count (per second) | count/s | eks_cluster_net_rx_dropped | Service | Network RX dropped count | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX Error Count (per second) | count/s | eks_cluster_net_rx_error | Service | Network RX error count | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX Dropped Count (per second) | count/s | eks_cluster_net_rx_dropped | Service | Network TX dropped count | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX Error Count (per second) | count/s | eks_cluster_net_rx_error | Service | Network TX error count | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Pod Count | | eks_cluster_node_pod_number | Instance | The count of pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| CPU Utilization | percent | eks_cluster_node_cpu_utilization | Instance | The CPU Utilization of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Memory Utilization | percent | eks_cluster_node_memory_utilization | Instance | The Memory Utilization of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX | bytes/s | eks_cluster_node_net_rx_bytes | Instance | Network RX bytes of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX Error Count | count/s | eks_cluster_node_net_rx_bytes | Instance | Network RX error count of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX | bytes/s | eks_cluster_node_net_rx_bytes | Instance | Network TX bytes of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX Error Count | count/s | eks_cluster_node_net_rx_bytes | Instance | Network TX error count of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Disk IO Write | bytes/s | eks_cluster_node_net_rx_bytes | Instance | The IO write bytes of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Disk IO Read | bytes/s | eks_cluster_node_net_rx_bytes | Instance | The IO read bytes of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| FS Utilization | percent | eks_cluster_node_net_rx_bytes | Instance | The filesystem utilization of the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| CPU Utilization | percent | eks_cluster_node_pod_cpu_utilization | Instance | The CPU Utilization of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Memory Utilization | percent | eks_cluster_node_pod_memory_utilization | Instance | The Memory Utilization of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX | bytes/s | eks_cluster_node_pod_net_rx_bytes | Instance | Network RX bytes of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX Error Count | count/s | eks_cluster_node_pod_net_rx_error | Instance | Network RX error count of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX | bytes/s | eks_cluster_node_pod_net_tx_bytes | Instance | Network RX bytes of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX Error Count | count/s | eks_cluster_node_pod_net_tx_error | Instance | Network RX error count of the pod running on the node | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| CPU Utilization | percent | eks_cluster_service_pod_cpu_utilization | Endpoint | The CPU Utilization of pod that belong to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Memory Utilization | percent | eks_cluster_service_pod_memory_utilization | Endpoint | The Memory Utilization of pod that belong to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX | bytes/s | eks_cluster_service_pod_net_rx_bytes | Endpoint | Network RX bytes of the pod that belong to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network RX Error Count | count/s | eks_cluster_service_pod_net_rx_error | Endpoint | Network TX error count of the pod that belongs to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX | bytes/s | eks_cluster_service_pod_net_tx_bytes | Endpoint | Network TX bytes of the pod that belong to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+| Network TX Error Count | count/s | eks_cluster_node_pod_net_tx_error | Endpoint | Network TX error count of the pod that belongs to the service | [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/aws-eks/`.
+The AWS Cloud EKS dashboard panel configurations are found in `/config/ui-initialized-templates/aws_eks`.
+
+### OTEL Configuration Sample With AWS Container Insights Receiver
+
+```yaml
+extensions:
+ health_check:
+receivers:
+ awscontainerinsightreceiver:
+processors:
+ resource/job-name:
+ attributes:
+ - key: job_name
+ value: aws-cloud-eks-monitoring
+ action: insert
+exporters:
+ otlp:
+ endpoint: oap-service:11800
+ tls:
+ insecure: true
+ logging:
+ loglevel: debug
+service:
+ pipelines:
+ metrics:
+ receivers: [awscontainerinsightreceiver]
+ processors: [resource/job-name]
+ exporters: [otlp,logging]
+ extensions: [health_check]
+```
+Refer to [AWS Container Insights Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awscontainerinsightreceiver/README.md) for more information
diff --git a/docs/en/setup/backend/backend-aws-s3-monitoring.md b/docs/en/setup/backend/backend-aws-s3-monitoring.md
new file mode 100644
index 000000000000..3ada7a600990
--- /dev/null
+++ b/docs/en/setup/backend/backend-aws-s3-monitoring.md
@@ -0,0 +1,39 @@
+# AWS Cloud S3 monitoring
+Amazon Simple Storage Service (Amazon S3) is an object storage service. SkyWalking leverages [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md) to transfer the CloudWatch metrics of s3 to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. AWS CloudWatch collect metrics for S3, refer to [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html)
+2. [CloudWatch metric streams](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html) stream CloudWatch metrics of S3 to AWS Kinesis Data Firehose
+3. AWS Kinesis Data Firehose delivery metrics to [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md) through the HTTP endpoint
+
+### Set up
+1. Create CloudWatch metrics configuration for S3, refer to [S3 metrics configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metrics-configurations.html)
+2. Create an Amazon Kinesis Data Firehose Delivery Stream, and set [AWS Kinesis Data Firehose receiver](./aws-firehose-receiver.md)'s address as HTTP(s) Destination, refer to [Create Delivery Stream](https://docs.aws.amazon.com/firehose/latest/dev/basic-create.html)
+3. Create CloudWatch metric stream, and select the Firehose Delivery Stream which has been created above, set `Select namespaces` to `AWS/S3`, `Select output format` to `OpenTelemetry 0.7`. refer to [CloudWatch Metric Streams](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html)
+
+Read [Monitoring AWS EKS and S3 with SkyWalking](https://skywalking.apache.org/blog/2023-03-12-skywalking-aws-s3-eks/) for more details
+
+### S3 Monitoring
+
+SkyWalking observes CloudWatch metrics of the S3 bucket, which is cataloged as a `LAYER: AWS_S3` `Service` in the OAP.
+
+#### Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|----------------------------|-------|-----------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| 4xx Errors | count | aws_s3_4xx | Service | The number of HTTP 4xx client error status code requests made to the S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| 5xx Errors | count | aws_s3_5xx | Service | The number of HTTP 5xx client error status code requests made to the S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Downloaded | bytes | aws_s3_downloaded_bytes | Service | The number of bytes downloaded for requests made to an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Uploaded | bytes | aws_s3_uploaded_bytes | Service | The number of bytes uploaded for requests made to an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Request Average Latency | bytes | aws_s3_request_latency | Service | The average of elapsed per-request time from the first byte received to the last byte sent to an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| First Byte Average Latency | bytes | aws_s3_request_latency | Service | The average of per-request time from the complete request being received by an Amazon S3 bucket to when the response starts to be returned | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| All Requests | bytes | aws_s3_delete_requests | Service | The number of HTTP All requests made for objects in an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Get Requests | bytes | aws_s3_delete_requests | Service | The number of HTTP Get requests made for objects in an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Put Requests | bytes | aws_s3_delete_requests | Service | The number of HTTP PUT requests made for objects in an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+| Delete Requests | bytes | aws_s3_delete_requests | Service | The number of HTTP Delete requests made for objects in an Amazon S3 bucket | [S3 monitoring with CloudWatch](https://docs.aws.amazon.com/AmazonS3/latest/userguide/cloudwatch-monitoring.html) |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/aws-s3/`.
+The AWS Cloud EKS dashboard panel configurations are found in `/config/ui-initialized-templates/aws_s3`.
diff --git a/docs/en/setup/backend/backend-bookkeeper-monitoring.md b/docs/en/setup/backend/backend-bookkeeper-monitoring.md
new file mode 100644
index 000000000000..b6f337714b27
--- /dev/null
+++ b/docs/en/setup/backend/backend-bookkeeper-monitoring.md
@@ -0,0 +1,61 @@
+# BookKeeper monitoring
+
+SkyWalking leverages OpenTelemetry Collector to collect metrics data from the BookKeeper and leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+Kafka entity as a `Service` in OAP and on the `Layer: BOOKKEEPER.
+
+## Data flow
+
+1. BookKeeper exposes metrics through Prometheus endpoint.
+2. OpenTelemetry Collector fetches metrics from BookKeeper cluster via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.`
+
+## Setup
+
+1. Set up [BookKeeper Cluster](https://bookkeeper.apache.org/docs/deployment/manual).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). The example
+ for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/pulsar/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## BookKeeper Monitoring
+
+Bookkeeper monitoring provides multidimensional metrics monitoring of BookKeeper cluster as `Layer: BOOKKEEPER` `Service` in
+the OAP. In each cluster, the nodes are represented as `Instance`.
+
+### BookKeeper Cluster Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|--------------------------------|------------------------------------------------------------------|---------------------------------------------------|---------------------|
+| Bookie Ledgers Count | meter_bookkeeper_bookie_ledgers_count | The number of the bookie ledgers. | Bookkeeper Cluster |
+| Bookie Ledger Writable Dirs | meter_bookkeeper_bookie_ledger_writable_dirs | The number of writable directories in the bookie. | Bookkeeper Cluster |
+| Bookie Ledger Dir Usage | meter_bookkeeper_bookie_ledger_dir_data_bookkeeper_ledgers_usage | The number of successfully created connections. | Bookkeeper Cluster |
+| Bookie Entries Count | meter_bookkeeper_bookie_entries_count | The number of the bookie write entries. | Bookkeeper Cluster |
+| Bookie Write Cache Size | meter_bookkeeper_bookie_write_cache_size | The size of the bookie write cache (MB). | Bookkeeper Cluster |
+| Bookie Write Cache Entry Count | meter_bookkeeper_bookie_write_cache_count | The entry count in the bookie write cache. | Bookkeeper Cluster |
+| Bookie Read Cache Size | meter_bookkeeper_bookie_read_cache_size | The size of the bookie read cache (MB). | Bookkeeper Cluster |
+| Bookie Read Cache Entry Count | meter_bookkeeper_bookie_read_cache_count | The entry count in the bookie read cache. | Bookkeeper Cluster |
+| Bookie Read Rate | meter_bookkeeper_bookie_read_rate | The bookie read rate (bytes/s). | Bookkeeper Cluster |
+| Bookie Write Rate | meter_bookkeeper_bookie_write_rate | The bookie write rate (bytes/s). | Bookkeeper Cluster |
+
+### BookKeeper Node Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|--------------------|
+| JVM Memory Pool Used | meter_bookkeeper_node_jvm_memory_pool_used | The usage of the broker jvm memory pool. | Bookkeeper Bookie |
+| JVM Memory | meter_bookkeeper_node_jvm_memory_used
meter_bookkeeper_node_jvm_memory_committed
meter_bookkeeper_node_jvm_memory_init | The usage of the broker jvm memory. | Bookkeeper Bookie |
+| JVM Threads | meter_bookkeeper_node_jvm_threads_current
meter_bookkeeper_node_jvm_threads_daemon
meter_bookkeeper_node_jvm_threads_peak
meter_bookkeeper_node_jvm_threads_deadlocked | The count of the jvm threads. | Bookkeeper Bookie |
+| GC Time | meter_bookkeeper_node_jvm_gc_collection_seconds_sum | Time spent in a given JVM garbage collector in seconds. | Bookkeeper Bookie |
+| GC Count | meter_bookkeeper_node_jvm_gc_collection_seconds_count | The count of a given JVM garbage. | Bookkeeper Bookie |
+| Thread Executor Completed | meter_bookkeeper_node_thread_executor_completed | The count of the executor thread. | Bookkeeper Bookie |
+| Thread Executor Tasks | meter_bookkeeper_node_thread_executor_tasks_completed
meter_bookkeeper_node_thread_executor_tasks_rejected
meter_bookkeeper_node_thread_executor_tasks_failed | The count of the executor tasks. | Bookkeeper Bookie |
+| Pooled Threads | meter_bookkeeper_node_high_priority_threads
meter_bookkeeper_node_read_thread_pool_threads | The count of the pooled thread. | Bookkeeper Bookie |
+| Pooled Threads Max Queue Size | meter_bookkeeper_node_high_priority_thread_max_queue_size
meter_bookkeeper_node_read_thread_pool_max_queue_size | The count of the pooled threads max queue size. | Bookkeeper Bookie |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `otel-rules/bookkeeper/bookkeeper-cluster.yaml, otel-rules/bookkeeper/bookkeeper-node.yaml`.
+The Bookkeeper dashboard panel configurations are found in `/config/ui-initialized-templates/bookkeeper`.
diff --git a/docs/en/setup/backend/backend-clickhouse-monitoring.md b/docs/en/setup/backend/backend-clickhouse-monitoring.md
new file mode 100644
index 000000000000..65f8bba73d4f
--- /dev/null
+++ b/docs/en/setup/backend/backend-clickhouse-monitoring.md
@@ -0,0 +1,140 @@
+# ClickHouse monitoring
+
+## ClickHouse server performance from built-in metrics data
+
+SkyWalking leverages ClickHouse built-in metrics data since v20.1.2.4. It leverages OpenTelemetry Collector to transfer
+the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+
+1. Configure ClickHouse to expose metrics data for scraping from Prometheus.
+2. OpenTelemetry Collector fetches metrics from ClickeHouse server through Prometheus endpoint, and pushes metrics to SkyWalking OAP Server via
+ OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+### Set up
+
+1. Set
+ up [built-in prometheus endpoint](https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#prometheus)
+ .
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on
+ Prometheus Receiver in OpenTelemetry Collector, refer
+ to [here](../../../../test/e2e-v2/cases/clickhouse/clickhouse-prometheus-endpoint/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### ClickHouse Monitoring
+
+ClickHouse monitoring provides monitoring of the metrics 、events and asynchronous_metrics of the ClickHouse server.
+ClickHouse cluster is cataloged as a `Layer: CLICKHOUSE` `Service` in OAP. Each ClickHouse server is cataloged as
+an `Instance` in OAP.
+
+#### ClickHouse Instance Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | ---------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | ----------- |
+| CpuUsage | count | meter_clickhouse_instance_cpu_usage | CPU time spent seen by OS per second(according to ClickHouse.system.dashboard.CPU Usage (cores)). | ClickHouse |
+| MemoryUsage | percentage | meter_clickhouse_instance_memory_usage | Total amount of memory (bytes) allocated by the server/ total amount of OS memory. | ClickHouse |
+| MemoryAvailable | percentage | meter_clickhouse_instance_memory_available | Total amount of memory (bytes) available for program / total amount of OS memory. | ClickHouse |
+| Uptime | sec | meter_clickhouse_instance_uptime | The server uptime in seconds. It includes the time spent for server initialization before accepting connections. | ClickHouse |
+| Version | string | meter_clickhouse_instance_version | Version of the server in a single integer number in base-1000. | ClickHouse |
+| FileOpen | count | meter_clickhouse_instance_file_open | Number of files opened. | ClickHouse |
+
+#### ClickHouse Network Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------------- | ----- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- | ----------- |
+| TcpConnections | count | meter_clickhouse_instance_tcp_connections
meter_clickhouse_tcp_connections | Number of connections to TCP server. | ClickHouse |
+| MysqlConnections | count | meter_clickhouse_instance_mysql_connections
meter_clickhouse_mysql_connections | Number of client connections using MySQL protocol. | ClickHouse |
+| HttpConnections | count | meter_clickhouse_instance_http_connections
meter_clickhouse_mysql_connections | Number of connections to HTTP server. | ClickHouse |
+| InterserverConnections | count | meter_clickhouse_instance_interserver_connections
meter_clickhouse_interserver_connections | Number of connections from other replicas to fetch parts. | ClickHouse |
+| PostgresqlConnections | count | meter_clickhouse_instance_postgresql_connections
meter_clickhouse_postgresql_connections | Number of client connections using PostgreSQL protocol. | ClickHouse |
+| ReceiveBytes | bytes | meter_clickhouse_instance_network_receive_bytes
meter_clickhouse_network_receive_bytes | Total number of bytes received from network. | ClickHouse |
+| SendBytes | bytes | meter_clickhouse_instance_network_send_bytes
meter_clickhouse_network_send_bytes | Total number of bytes send to network. | ClickHouse |
+
+#### ClickHouse Query Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | --------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------- |
+| QueryCount | count | meter_clickhouse_instance_query
meter_clickhouse_query | Number of executing queries. | ClickHouse |
+| SelectQueryCount | count | meter_clickhouse_instance_query_select
meter_clickhouse_query_select | Number of executing queries, but only for SELECT queries. | ClickHouse |
+| InsertQueryCount | count | meter_clickhouse_instance_query_insert
meter_clickhouse_query_insert | Number of executing queries, but only for INSERT queries. | ClickHouse |
+| SelectQueryRate | count/sec | meter_clickhouse_instance_query_select_rate
meter_clickhouse_query_select_rate | Number of SELECT queries per second. | ClickHouse |
+| InsertQueryRate | count/sec | meter_clickhouse_instance_query_insert_rate
meter_clickhouse_query_insert_rate | Number of INSERT queries per second. | ClickHouse |
+| Querytime | microsec | meter_clickhouse_instance_querytime_microseconds
meter_clickhouse_querytime_microseconds | Total time of all queries. | ClickHouse |
+| SelectQuerytime | microsec | meter_clickhouse_instance_querytime_select_microseconds
meter_clickhouse_querytime_select_microseconds | Total time of SELECT queries. | ClickHouse |
+| InsertQuerytime | microsec | meter_clickhouse_instance_querytime_insert_microseconds
meter_clickhouse_querytime_insert_microseconds | Total time of INSERT queries. | ClickHouse |
+| OtherQuerytime | microsec | meter_clickhouse_instance_querytime_other_microseconds
meter_clickhouse_querytime_other_microseconds | Total time of queries that are not SELECT or INSERT. | ClickHouse |
+| QuerySlowCount | count | meter_clickhouse_instance_query_slow
meter_clickhouse_query_slow | Number of reads from a file that were slow. | ClickHouse |
+
+#### ClickHouse Insertion Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ------------------ | ----- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| InsertQueryCount | count | meter_clickhouse_instance_query_insert
meter_clickhouse_query_insert | Number of executing queries, but only for INSERT queries. | ClickHouse |
+| InsertedRowCount | count | meter_clickhouse_instance_inserted_rows
meter_clickhouse_inserted_rows | Number of rows INSERTed to all tables. | ClickHouse |
+| InsertedBytes | bytes | meter_clickhouse_instance_inserted_bytes
meter_clickhouse_inserted_bytes | Number of bytes INSERTed to all tables. | ClickHouse |
+| DelayedInsertCount | count | meter_clickhouse_instance_delayed_insert
meter_clickhouse_delayed_insert | Number of times the INSERT of a block to a MergeTree table was throttled due to high number of active data parts for partition. | ClickHouse |
+
+#### ClickHouse Replicas Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | ----- | ---------------------------------------------------------------------------------- | ------------------------------------------------ | ----------- |
+| ReplicatedChecks | count | meter_clickhouse_instance_replicated_checks
meter_clickhouse_replicated_checks | Number of data parts checking for consistency. | ClickHouse |
+| ReplicatedFetch | count | meter_clickhouse_instance_replicated_fetch
meter_clickhouse_replicated_fetch | Number of data parts being fetched from replica. | ClickHouse |
+| ReplicatedSend | count | meter_clickhouse_instance_replicated_send
meter_clickhouse_replicated_send | Number of data parts being sent to replicas. | ClickHouse |
+
+#### ClickHouse MergeTree Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------------- | ----- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| BackgroundMergeCount | count | meter_clickhouse_instance_background_merge
meter_clickhouse_background_merge | Number of executing background merges. | ClickHouse |
+| MergeRows | count | meter_clickhouse_instance_merge_rows
meter_clickhouse_merge_rows | Rows read for background merges. This is the number of rows before merge. | ClickHouse |
+| MergeUncompressedBytes | bytes | meter_clickhouse_instance_merge_uncompressed_bytes
meter_clickhouse_merge_uncompressed_bytes | Uncompressed bytes (for columns as they stored in memory) that was read for background merges. This is the number before merge. | ClickHouse |
+| MoveCount | count | meter_clickhouse_instance_move
meter_clickhouse_move | Number of currently executing moves. | ClickHouse |
+| PartsActive | Count | meter_clickhouse_instance_parts_active
meter_clickhouse_parts_active | Active data part, used by current and upcoming SELECTs. | ClickHouse |
+| MutationsCount | count | meter_clickhouse_instance_mutations
meter_clickhouse_mutations | Number of mutations (ALTER DELETE/UPDATE). | ClickHouse |
+
+#### ClickHouse Kafka Table Engine Supported Metrics
+
+When [table engine](https://clickhouse.com/docs/en/engines/table-engines/integrations/kafka) works
+with [Apache Kafka](http://kafka.apache.org/).
+
+Kafka lets you:
+
+- Publish or subscribe to data flows.
+- Organize fault-tolerant storage.
+- Process streams as they become available.
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ----------------- | ----- | -------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------- |
+| KafkaMessagesRead | count | meter_clickhouse_instance_kafka_messages_read
meter_clickhouse_kafka_messages_read | Number of Kafka messages already processed by ClickHouse. | ClickHouse |
+| KafkaWrites | count | meter_clickhouse_instance_kafka_writes
meter_clickhouse_kafka_writes | Number of writes (inserts) to Kafka tables. | ClickHouse |
+| KafkaConsumers | count | meter_clickhouse_instance_kafka_consumers
meter_clickhouse_kafka_consumers | Number of active Kafka consumers. | ClickHouse |
+| KafkaProducers | count | meter_clickhouse_instance_kafka_producers
meter_clickhouse_kafka_producers | Number of active Kafka producer created. | ClickHouse |
+
+#### ClickHouse ZooKeeper Supported Metrics
+
+ClickHouse uses ZooKeeper for storing metadata of replicas when using replicated tables. If replicated tables are not
+used, this section of parameters can be omitted.
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| --------------------- | ----- | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ----------- |
+| ZookeeperSession | count | meter_clickhouse_instance_zookeeper_session
meter_clickhouse_zookeeper_session | Number of sessions (connections) to ZooKeeper. | ClickHouse |
+| ZookeeperWatch | count | meter_clickhouse_instance_zookeeper_watch
meter_clickhouse_zookeeper_watch | Number of watches (event subscriptions) in ZooKeeper. | ClickHouse |
+| ZookeeperBytesSent | bytes | meter_clickhouse_instance_zookeeper_bytes_sent
meter_clickhouse_zookeeper_bytes_sent | Number of bytes send over network while communicating with ZooKeeper. | ClickHouse |
+| ZookeeperBytesReceive | bytes | meter_clickhouse_instance_zookeeper_bytes_received
meter_clickhouse_zookeeper_bytes_received | Number of bytes send over network while communicating with ZooKeeper. | ClickHouse |
+
+### ClickHouse Keeper Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ------------------------ | ----- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ----------- |
+| KeeperAliveConnections | count | meter_clickhouse_instance_keeper_connections_alive
meter_clickhouse_keeper_connections_alive | Number of alive connections for embedded ClickHouse Keeper. | ClickHouse |
+| KeeperOutstandingRequets | count | meter_clickhouse_instance_keeper_outstanding_requests
meter_clickhouse_keeper_outstanding_requests| Number of outstanding requests for embedded ClickHouse Keeper. | ClickHouse |
+
+### Customizations
+
+You can customize your own metrics/expression/dashboard panel. The metrics definition and expression rules are found
+in `/config/otel-rules/clickhouse`. The ClickHouse dashboard panel configurations are found
+in `/config/ui-initialized-templates/clickhouse`.
diff --git a/docs/en/setup/backend/backend-cluster.md b/docs/en/setup/backend/backend-cluster.md
new file mode 100644
index 000000000000..f5db853620c2
--- /dev/null
+++ b/docs/en/setup/backend/backend-cluster.md
@@ -0,0 +1,216 @@
+# Cluster Management
+
+In many production environments, the backend needs to support **distributed aggregation**, high throughput
+and provide high availability (HA) to maintain robustness, so **you always need to setup CLUSTER management in product env**.
+Otherwise, you would face metrics **inaccurate**.
+
+`core/gRPCHost` is listening on `0.0.0.0` for quick start as the single mode for most cases.
+Besides the `Kubernetes` coordinator, which is using the cloud-native mode to establish cluster, all other coordinators
+requires `core/gRPCHost` updated to real IP addresses or take reference of `internalComHost` and `internalComPort` in each
+coordinator doc.
+
+NOTICE, cluster management doesn't provide a service discovery mechanism for agents and probes. We recommend
+agents/probes using gateway to load balancer to access OAP clusters.
+
+There are various ways to manage the cluster in the backend. Choose the one that best suits your needs.
+
+- [Kubernetes](#kubernetes). When the backend clusters are deployed inside Kubernetes, you could make use of this method
+ by using k8s native APIs to manage clusters.
+- [Zookeeper coordinator](#zookeeper-coordinator). Use Zookeeper to let the backend instances detect and communicate
+ with each other.
+- [Consul](#consul). Use Consul as the backend cluster management implementor and coordinate backend instances.
+- [Etcd](#etcd). Use Etcd to coordinate backend instances.
+- [Nacos](#nacos). Use Nacos to coordinate backend instances.
+
+In the `application.yml` file, there are default configurations for the aforementioned coordinators under the
+section `cluster`. You can specify any of them in the `selector` property to enable it.
+
+___
+**NOTICE**,
+Before you set up the cluster, please read the [Query Cluster Nodes](../../status/query_cluster_nodes.md) API to understand how to
+verify the cluster node list. If the nodes don't match the expectation, the cluster is not working properly, there could
+be many feature impacts, e.g. the metrics could be inaccurate and the alarms could not be triggered correctly.
+___
+
+# Cloud Native
+## Kubernetes
+
+The required backend clusters are deployed inside Kubernetes. See the guides in [Deploy in kubernetes](backend-k8s.md).
+Set the selector to `kubernetes`.
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:kubernetes}
+ # other configurations
+```
+Meanwhile, the OAP cluster requires the pod's UID which is laid at `metadata.uid` as the value of the system environment variable **SKYWALKING_COLLECTOR_UID**
+
+```yaml
+containers:
+ # Original configurations of OAP container
+ - name: {{ .Values.oap.name }}
+ image: {{ .Values.oap.image.repository }}:{{ required "oap.image.tag is required" .Values.oap.image.tag }}
+ # ...
+ # ...
+ env:
+ # Add metadata.uid as the system environment variable, SKYWALKING_COLLECTOR_UID
+ - name: SKYWALKING_COLLECTOR_UID
+ valueFrom:
+ fieldRef:
+ fieldPath: metadata.uid
+```
+
+Read [the complete helm](https://github.com/apache/skywalking-helm/blob/476afd51d44589c77a4cbaac950272cd5d064ea9/chart/skywalking/templates/oap-deployment.yaml#L125) for more details.
+
+# Traditional Coordinator
+
+**NOTICE**
+In all the following coordinators, `oap.internal.comm.host`:`oap.internal.comm.port` is registered as the ID
+and address for the current OAP node. By default, because they are same in all OAP nodes, the registrations are conflicted,
+and (may) show as one registered node, which actually would be the node itself. **In this case, the cluster mode is NOT working.**
+
+Please check the registered nodes on your coordinator servers, to make the registration information unique for every node.
+You could have two options
+
+1. Change `core/gRPCHost`(`oap.internal.comm.host`) and `core/gRPCPort`(`oap.internal.comm.port`) for internal,
+ and [setup external communication channels](backend-expose.md) for data reporting and query.
+2. Use `internalComHost` and `internalComPort` in the config to provide a unique host and port for every OAP node. This
+ host name port should be accessible for other OAP nodes.
+
+## Zookeeper coordinator
+
+Zookeeper is a very common and widely used cluster coordinator. Set the **cluster/selector** to **zookeeper** in the yml
+to enable it.
+
+Required Zookeeper version: 3.5+
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:zookeeper}
+ # other configurations
+```
+
+- `hostPort` is the list of zookeeper servers. Format is `IP1:PORT1,IP2:PORT2,...,IPn:PORTn`
+- `enableACL`
+ enable [Zookeeper ACL](https://zookeeper.apache.org/doc/r3.5.5/zookeeperProgrammers.html#sc_ZooKeeperAccessControl) to
+ control access to its znode.
+- `schema` is Zookeeper ACL schemas.
+- `expression` is a expression of ACL. The format of the expression is specific to
+ the [schema](https://zookeeper.apache.org/doc/r3.5.5/zookeeperProgrammers.html#sc_BuiltinACLSchemes).
+- `hostPort`, `baseSleepTimeMs` and `maxRetries` are settings of Zookeeper curator client.
+
+Note:
+
+- If `Zookeeper ACL` is enabled and `/skywalking` exists, you must ensure that `SkyWalking` has `CREATE`, `READ`
+ and `WRITE` permissions. If `/skywalking` does not exist, it will be created by SkyWalking, and all permissions to the
+ specified user will be granted. Simultaneously, znode grants READ permission to anyone.
+- If you set `schema` as `digest`, the password of the expression is set in **clear text**.
+
+In some cases, the OAP default gRPC host and port in the core are not suitable for internal communication among the OAP
+nodes, such as the default host(`0.0.0.0`) should not be used in cluster mode.
+The following settings are provided to set the host and port manually, based on your own LAN env.
+
+- internalComHost: The exposed host name for other OAP nodes in the cluster internal communication.
+- internalComPort: the exposed port for other OAP nodes in the cluster internal communication.
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:zookeeper}
+ ...
+ zookeeper:
+ namespace: ${SW_NAMESPACE:""}
+ hostPort: ${SW_CLUSTER_ZK_HOST_PORT:localhost:2181}
+ #Retry Policy
+ baseSleepTimeMs: ${SW_CLUSTER_ZK_SLEEP_TIME:1000} # initial amount of time to wait between retries
+ maxRetries: ${SW_CLUSTER_ZK_MAX_RETRIES:3} # max number of times to retry
+ internalComHost: ${SW_CLUSTER_INTERNAL_COM_HOST:172.10.4.10}
+ internalComPort: ${SW_CLUSTER_INTERNAL_COM_PORT:11800}
+ # Enable ACL
+ enableACL: ${SW_ZK_ENABLE_ACL:false} # disable ACL in default
+ schema: ${SW_ZK_SCHEMA:digest} # only support digest schema
+ expression: ${SW_ZK_EXPRESSION:skywalking:skywalking}
+```
+
+## Consul
+
+Recently, the Consul system has become more and more popular, and many companies and developers now use Consul as
+their service discovery solution. Set the **cluster/selector** to **consul** in the yml to enable it.
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:consul}
+ ...
+ consul:
+ serviceName: ${SW_SERVICE_NAME:"SkyWalking_OAP_Cluster"}
+ # Consul cluster nodes, example: 10.0.0.1:8500,10.0.0.2:8500,10.0.0.3:8500
+ hostPort: ${SW_CLUSTER_CONSUL_HOST_PORT:localhost:8500}
+ aclToken: ${SW_CLUSTER_CONSUL_ACLTOKEN:""}
+ internalComHost: ${SW_CLUSTER_INTERNAL_COM_HOST:""}
+ internalComPort: ${SW_CLUSTER_INTERNAL_COM_PORT:-1}
+```
+
+Same as the Zookeeper coordinator,
+in some cases, the OAP default gRPC host and port in the core are not suitable for internal communication among the OAP
+nodes, such as the default host(`0.0.0.0`) should not be used in cluster mode.
+The following settings are provided to set the host and port manually, based on your own LAN env.
+
+- internalComHost: The exposed host name for other OAP nodes in the cluster internal communication.
+- internalComPort: the exposed port for other OAP nodes in the cluster internal communication.
+
+## Etcd
+
+Set the **cluster/selector** to **etcd** in the yml to enable it. The Etcd client has upgraded to v3 protocol and
+changed to the CoreOS official library. **Since 8.7.0, only the v3 protocol is supported for Etcd.**
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:etcd}
+ # other configurations
+ etcd:
+ # etcd cluster nodes, example: 10.0.0.1:2379,10.0.0.2:2379,10.0.0.3:2379
+ endpoints: ${SW_CLUSTER_ETCD_ENDPOINTS:localhost:2379}
+ namespace: ${SW_CLUSTER_ETCD_NAMESPACE:/skywalking}
+ serviceName: ${SW_CLUSTER_ETCD_SERVICE_NAME:"SkyWalking_OAP_Cluster"}
+ authentication: ${SW_CLUSTER_ETCD_AUTHENTICATION:false}
+ user: ${SW_CLUSTER_ETCD_USER:}
+ password: ${SW_CLUSTER_ETCD_PASSWORD:}
+```
+
+Same as the Zookeeper coordinator,
+in some cases, the OAP default gRPC host and port in the core are not suitable for internal communication among the OAP
+nodes, such as the default host(`0.0.0.0`) should not be used in cluster mode.
+The following settings are provided to set the host and port manually, based on your own LAN env.
+
+- internalComHost: The exposed host name for other OAP nodes in the cluster internal communication.
+- internalComPort: the exposed port for other OAP nodes in the cluster internal communication.
+
+## Nacos
+
+Set the **cluster/selector** to **nacos** in the yml to enable it.
+
+Nacos 2.x is required.
+
+```yaml
+cluster:
+ selector: ${SW_CLUSTER:nacos}
+ # other configurations
+```
+
+Nacos supports authentication by username or accessKey. Empty means that there is no need for authentication. Extra
+config is as follows:
+
+```yaml
+nacos:
+ username:
+ password:
+ accessKey:
+ secretKey:
+```
+
+Same as the Zookeeper coordinator,
+in some cases, the OAP default gRPC host and port in the core are not suitable for internal communication among the OAP
+nodes, such as the default host(`0.0.0.0`) should not be used in cluster mode.
+The following settings are provided to set the host and port manually, based on your own LAN env.
+
+- internalComHost: The exposed host name for other OAP nodes in the cluster internal communication.
+- internalComPort: the exposed port for other OAP nodes in the cluster internal communication.
diff --git a/docs/en/setup/backend/backend-continuous-profiling.md b/docs/en/setup/backend/backend-continuous-profiling.md
new file mode 100644
index 000000000000..e058f59bf9fa
--- /dev/null
+++ b/docs/en/setup/backend/backend-continuous-profiling.md
@@ -0,0 +1,71 @@
+# Continuous Profiling
+
+Continuous profiling utilizes [eBPF](https://ebpf.io), process monitoring, and other technologies to collect data.
+When the configured threshold is met, it would automatically start profiling tasks. Corresponds to [Continuous Profiling](../../concepts-and-designs/profiling.md#continuous-profiling) in the concepts and designs.
+This approach helps identify performance bottlenecks and potential issues in a proactive manner,
+allowing users to optimize their applications and systems more effectively.
+
+## Active in the OAP
+Continuous profiling uses the same protocol service as eBPF Profiling, so you only need to ensure that the eBPF Profiling receiver is running.
+
+```yaml
+receiver-ebpf:
+ selector: ${SW_RECEIVER_EBPF:default}
+ default:
+```
+
+## Configuration of Continuous Profiling Policy
+
+Continuous profiling can be configured on a service entity, with the following fields in the configuration:
+
+1. **Service**: The service entity for which you want to monitor the processes.
+2. **Targets**: Configuration conditions.
+ 1. **Target Type**: Target profiling type, currently supporting On CPU Profiling, Off CPU Profiling, and Network Profiling.
+ 2. **Check Items**: Detection conditions, only one of the multiple condition rules needs to be met to start the task.
+ 1. **Type**: Monitoring type, currently supporting "System Load", "Process CPU", "Process Thread Count", "HTTP Error Rate", "HTTP Avg Response Time".
+ 2. **Threshold**: Check if the monitoring value meets the specified expectations.
+ 3. **Period**: The time period(seconds) for monitoring data, which can also be understood as the most recent duration.
+ 4. **Count**: The number of times(seconds) the threshold is triggered within the detection period, which can also be understood as the total number of times the specified threshold rule is triggered in the most recent duration(seconds). Once the count check is met, the specified Profiling task will be started.
+ 5. **URI**: For HTTP-related monitoring types, used to filter specific URIs.
+
+## Monitoring
+
+After saving the configuration, the eBPF agent can perform monitoring operations on the processes under the specified service based on the service-level configuration.
+
+### Metrics
+
+While performing monitoring, the eBPF agent would report the monitoring data to OAP for storage, making it more convenient to understand the real-time monitoring status. The main metrics include:
+
+| Monitor Type | Unit | Description |
+|--------------|------|-------------|
+| System Load | Load | System load average over a specified period. |
+| Process CPU | Percentage | The CPU usage of the process as a percentage. |
+| Process Thread Count | Count | The number of threads in the process. |
+| HTTP Error Rate | Percentage | The percentage of HTTP requests that result in error responses (e.g., 4xx or 5xx status codes). |
+| HTTP Avg Response Time | Millisecond | The average response time for HTTP requests. |
+
+### Threshold With Trigger
+
+In the eBPF agent, data is collected periodically, and the sliding time window technique is used to store the data from the most recent **Period** cycles.
+The **Threshold** rule is used to verify whether the data within each cycle meets the specified criteria.
+If the number of times the conditions are met within the sliding time window exceeds the **Count** value, the corresponding Profiling task would be triggered.
+
+The sliding time window technique ensures that the most recent and relevant data is considered when evaluating the conditions.
+This approach allows for a more accurate and dynamic assessment of the system's performance,
+making it possible to identify and respond to issues in a timely manner.
+By triggering Profiling tasks when specific conditions are met, the system can automatically initiate performance analysis and help uncover potential bottlenecks or areas for improvement.
+
+#### Causes
+
+When the eBPF agent reports a Profiling task, it also reports the reason for triggering the Profiling task, which mainly includes the following information:
+
+1. **Process**: The specific process that triggered the policy.
+2. **Monitor Type**: The type of monitoring that was triggered.
+3. **Threshold**: The configured threshold value.
+4. **Current**: The monitoring value at the time the rule was triggered.
+
+#### Silence Period
+
+Upon triggering a continuous profiling task, the eBPF agent supports a feature that prevents re-triggering tasks within a specified period.
+This feature is designed to prevent an unlimited number of profiling tasks from being initiated if the process continuously reaches the threshold,
+which could potentially cause system issues.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-data-generator.md b/docs/en/setup/backend/backend-data-generator.md
new file mode 100644
index 000000000000..a2084bd27b95
--- /dev/null
+++ b/docs/en/setup/backend/backend-data-generator.md
@@ -0,0 +1,207 @@
+# Mock data generator for testing
+
+In 9.1.0, SkyWalking adds a module to generate mock data for testing. You can use this module to generate
+mock data that will be sent to the storage.
+
+To start the data generator, execute the script `tools/data-generator/bin/start.sh`.
+
+Note that SkyWalking doesn't release a Docker image for this module, but you can still build it yourselves
+by running the commands:
+
+```shell
+# build a Docker image for local use
+make docker.data-generator
+
+# or push to your registry
+export HUB=
+make push.docker.data-generator
+```
+
+Currently the module can generate two kinds of SkyWalking data, segments and logs. For each type,
+there are some generators that can be used to fill the fields.
+
+## Generate mock data
+
+To generate mock data, `POST` a request to URL path `/mock-data/segments/tasks` (segments) or
+`/mock-data/logs/tasks` (logs) with a generator template:
+
+```shell
+curl -XPOST 'http://localhost:12800/mock-data/segments/tasks?size=20' -H'Content-Type: application/json' -d "@segment-template.json"
+
+curl -XPOST 'http://localhost:12800/mock-data/logs/tasks?size=20' -H'Content-Type: application/json' -d "@logs-template.json"
+```
+
+There are two possible types of task to generate mock data, `size` and `qps`:
+
+- `size` (`/mock-data/segments/tasks?size=20`): the task will generate total number of `size` segments/logs and then finish.
+- `qps` (`/mock-data/segments/tasks?qps=20`): the task will generate `qps` segments/logs per second continuously, until the task is [cancelled](#cancel-a-task).
+
+Refer to [the segment template](segment-template.json), [the log template](logs-template.json) and the [Generators](#generators) for more details
+about how to compose a template.
+
+## Cancel a task
+
+When the task is acknowledged by the server it will return a task id that can be used to cancelled
+the task by sending a `DELETE` request to URL path `/mock-data/logs/tasks` with a parameter `requestId` (i.e.
+`/mock-data/logs/tasks?requestId={request id returned in previous request}`):
+
+```shell
+curl -XDELETE 'http://localhost:12800/mock-data/segments/task?requestId=70d8a39e-b51e-49de-a6fc-43abf80482c1'
+curl -XDELETE 'http://localhost:12800/mock-data/logs/task?requestId=70d8a39e-b51e-49de-a6fc-43abf80482c1'
+```
+
+## Cancel all tasks
+
+When needed, you can also send a `DELETE` request to path `/mock-data/segments/tasks` to cancel all segment tasks.
+
+```shell
+curl -XDELETE 'http://localhost:12800/mock-data/segments/tasks
+curl -XDELETE 'http://localhost:12800/mock-data/logs/tasks
+```
+
+## Generators
+
+### `uuid`
+
+`uuid` generator leverages `java.util.UUID` to generate a string. You can use `uuid` generator to fill the
+`traceId` field of segments.
+
+`changingFrequency` property can be used when you want to reuse a `uuid` for multiple times, for example,
+if you want a `traceId` to be reused by 5 segments, then setting `changingFrequency` to `5` would do the trick.
+By setting `changingFrequency` to `5`, `uuid` generates 1 string, and uses it for 5 times, then re-generates
+a new uuid string and uses it for another 5 times.
+
+```json
+"traceId": {
+ "type": "uuid",
+ "changingFrequency": "5"
+}
+```
+
+### `randomString` (`String`)
+
+#### `length` (`int`)
+
+`length` specifies the length of the random string to be generated,
+i.e. `generatedString.length() == length` is always `true`.
+
+#### `prefix` (`String`)
+
+`prefix` is always added to the random strings **after** they are generated, that means:
+
+- `generatedString.startsWith(prefix)` is always `true`, and,
+- `generatedString.length() == length + prefix.length()` is always true.
+
+#### `letters` (`boolean`)
+
+Specifies whether the random string contains letters (i.e. `a-zA-Z`).
+
+#### `numbers` (`boolean`)
+
+Specifies whether the random string contains numbers (i.e. `0-9`).
+
+#### `domainSize` (`int`)
+
+When generating random strings, you might just want some random strings and use them over and over again randomly,
+by setting `domainSize`, the generator generates `domainSize` random strings, and pick them randomly every time
+you need a string.
+
+### `randomBool` (`boolean`)
+
+This generator generates a `Boolean` value, `true` or `false` with a default possibility of 50%, while you can change the `possibility` below.
+
+#### `possibility` (`double`, `[0, 1]`)
+
+`possibility` is a `double` value `>= 0` and `<= 1`, it's `0.5` by default, meaning **about** half of the generated values are `true`.
+
+To always return a fixed boolean value `true`, you can just set the `possibility` to `1`, to always return a fixed boolean value `false`, you can set the `possibility` to `0`
+
+```json
+"error": {
+ "type": "randomBool",
+ "possibility": "0.9"
+}
+```
+
+> 90 percent of the generated values are `true`.
+
+### `randomInt` (`long`)
+
+#### `min` (`long`)
+
+The minimum value of the random integers, meaning all generated values satisfy `generatedInt >= min`.
+
+#### `max` (`long`)
+
+The maximum value of the random integers, meaning all generated values satisfy `generatedInt < min`.
+
+#### `domainSize` (`int`)
+
+This is similar to [`randomString`'s `domainSize`](#domainsize-int).
+
+### `randomList` (`list` / `array`)
+
+#### `size` (`int`)
+
+The list size of the generated list, i.e. `generatedList.size() == size`.
+
+#### `item` (`object`)
+
+`item` is a template that will be use as a prototype to generate the list items, for example when generating a
+list of `Tag`, the `item` should be the prototype of `Tag`, which can be composed by the generators again.
+
+```json
+"tags": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "key": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_tag_",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ },
+ "value": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_value_",
+ "letters": true,
+ "numbers": true
+ }
+ }
+}
+```
+
+### `fixedString` (`string`)
+
+This generator always returns a fixed `value` of string.
+
+### `sequence` (`long`)
+
+`sequence` generator generates a sequence of monotonically increasing integers, with a configurable `fluctuation`.
+
+#### `min` (`long`)
+
+The minimum value of the sequence.
+
+#### `max` (`long`)
+
+The maximum value of the sequence.
+
+#### `step` (`long`)
+
+The increasing step of this sequence, i.e. `the next generated value == the previous value + step`.
+
+#### `domainSize` (`int`)
+
+This is similar to [`randomString`'s `domainSize`](#domainsize-int).
+
+#### `fluctuation` (`int`)
+
+By default, sequence is strictly increasing numbers, but in some cases you might want the numbers to fluctuate
+slightly while they are increasing. Adding property `fluctuation` to the generator will add a random number
+`>= -fluctuation, <= fluctuation` to the sequence elements.
+
+For example, `min = 10, max = 15, step = 1` generates a sequence `[10, 11, 12, 13, 14, 15]`, but adding `fluctuation = 2` **might** generate a sequence `[10, 12, 11, 14, 13, 15]`.
diff --git a/docs/en/setup/backend/backend-docker.md b/docs/en/setup/backend/backend-docker.md
new file mode 100644
index 000000000000..230daa01c23e
--- /dev/null
+++ b/docs/en/setup/backend/backend-docker.md
@@ -0,0 +1,50 @@
+# How to use the Docker images
+
+## Start the storage, OAP and Booster UI with docker-compose
+
+As a quick start, you can use our one-liner script to start ElasticSearch or [BanyanDB](https://skywalking.apache.org/docs/skywalking-banyandb/next/readme/) as the storage, OAP server and Booster UI, please make sure you have installed Docker.
+The versions of the OAP and BanyanDB images are the latest release versions.
+
+**Linux, macOS, Windows (WSL)**
+```shell
+bash <(curl -sSL https://skywalking.apache.org/quickstart-docker.sh)
+```
+
+**Windows (Powershell)**
+```powershell
+Invoke-Expression ([System.Text.Encoding]::UTF8.GetString((Invoke-WebRequest -Uri https://skywalking.apache.org/quickstart-docker.ps1 -UseBasicParsing).Content))
+```
+
+You will be prompted to choose the storage type, and then the script will start the backend cluster with the selected storage.
+
+To tear down the cluster, run the following command:
+
+```shell
+docker compose --project-name=skywalking-quickstart down
+```
+
+## Start a `standalone` container with BanyanDB as storage, whose address is `banyandb:17912`
+
+```shell
+export RELEASE_VERSION=x.y.z
+docker run --name oap --restart always -d -e SW_STORAGE=banyandb -e SW_STORAGE_BANYANDB_TARGETS=banyandb:17912 apache/skywalking-oap-server:${RELEASE_VERSION}
+```
+
+## Start a `standalone` container with ElasticSearch 7 as storage, whose address is `elasticsearch:9200`
+
+```shell
+export RELEASE_VERSION=x.y.z
+docker run --name oap --restart always -d -e SW_STORAGE=elasticsearch -e SW_STORAGE_ES_CLUSTER_NODES=elasticsearch:9200 apache/skywalking-oap-server:${RELEASE_VERSION}
+```
+
+# Configuration
+
+We could set up environment variables to configure this image. They are defined in [backend-setup](backend-setup.md).
+
+# Extend image
+
+If you intend to override or add config files in `/skywalking/config`, `/skywalking/ext-config` is the location for you to put extra files.
+The files with the same name will be overridden; otherwise, they will be added to `/skywalking/config`.
+
+If you want to add more libs/jars into the classpath of OAP, for example, new metrics for OAL. These jars can be mounted into `/skywalking/ext-libs`, then
+`entrypoint` bash will append them into the classpath. Notice, you can't override an existing jar in classpath.
diff --git a/docs/en/setup/backend/backend-ebpf-profiling.md b/docs/en/setup/backend/backend-ebpf-profiling.md
new file mode 100644
index 000000000000..9b039efd1b8a
--- /dev/null
+++ b/docs/en/setup/backend/backend-ebpf-profiling.md
@@ -0,0 +1,198 @@
+# eBPF Profiling
+
+eBPF Profiling utilizes the [eBPF](https://ebpf.io/) technology to monitor applications without requiring any modifications to the application itself. Corresponds to [Out-Process Profiling](../../concepts-and-designs/profiling.md#out-of-process-profiling).
+
+To use eBPF Profiling, the SkyWalking Rover application (eBPF Agent) needs to be installed on the host machine.
+When the agent receives a Profiling task, it starts the Profiling task for the specific application to analyze performance bottlenecks for the corresponding type of Profiling.
+
+Lean more about the eBPF profiling in following blogs:
+1. [**Pinpoint Service Mesh Critical Performance Impact by using eBPF**](../../concepts-and-designs/ebpf-cpu-profiling.md)
+2. [**Diagnose Service Mesh Network Performance with eBPF**](../../academy/diagnose-service-mesh-network-performance-with-ebpf.md)
+
+## Active in the OAP
+OAP and the agent use a brand-new protocol to exchange eBPF Profiling data, so it is necessary to start OAP with the following configuration:
+
+```yaml
+receiver-ebpf:
+ selector: ${SW_RECEIVER_EBPF:default}
+ default:
+```
+
+## Profiling type
+
+eBPF Profiling leverages eBPF technology to provide support for the following types of tasks:
+
+1. **On CPU Profiling**: Periodically samples the thread stacks of the current program while it's executing on the CPU using `PERF_COUNT_SW_CPU_CLOCK`.
+2. **Off CPU Profiling**: Collects and aggregates thread stacks when the program executes the kernel function `finish_task_switch`.
+3. **Network Profiling**: Collects the execution details of the application when performing network-related syscalls, and then aggregates them into a topology map and metrics for different network protocols.
+
+### On CPU Profiling
+
+On CPU Profiling periodically samples the thread stacks of the target program while it's executing on the CPU and aggregates the thread stacks to create a flame graph.
+This helps users identify performance bottlenecks based on the flame graph information.
+
+#### Creating task
+
+When creating an On CPU Profiling task, you need to specify which eligible processes need to be sampled. The required configuration information is as follows:
+
+1. **Service**: The processes under which service entity need to perform Profiling tasks.
+2. **Labels**: Specifies which processes with certain labels under the service entity can perform profiling tasks. If left blank, all processes under the specified service will require profiling.
+3. **Start Time**: Whether the current task needs to be executed immediately or at a future point in time.
+4. **Duration**: The execution time of the current profiling task.
+
+The eBPF agent would periodically request from the OAP whether there are any eligible tasks among all the processes collected by the current eBPF agent.
+When the eBPF agent receives a task, it would start the profiling task with the process.
+
+#### Profiling analyze
+
+Once the eBPF agent starts a profiling task for a specific process, it would periodically collect data and report it to the OAP.
+At this point, a scheduling of task is generated. The scheduling data contains the following information:
+
+1. **Schedule ID**: The ID of current schedule.
+2. **Task**: The task to which the current scheduling data belongs.
+3. **Process**: The process for which the current scheduling Profiling data is being collected.
+4. **Start Time**: The execution start time of the current schedule.
+5. **End Time**: The time when the last sampling of the current schedule was completed.
+
+Once the schedule is created, we can use the existing scheduling ID and time range to query the CPU execution situation of the specified process within a specific time period.
+The query contains the following fields:
+1. **Schedule ID**: The schedule ID you want to query.
+2. **Time**: The start and end times you want to query.
+
+After the query, the following data would be returned. With the data, it's easy to generate a flame graph:
+1. **Id**: Element ID.
+2. **Parent ID**: Parent element ID. The dependency relationship between elements can be determined using the element ID and parent element ID.
+3. **Symbol**: The symbol name of the current element. Usually, it represents the method names of thread stacks in different languages.
+4. **Stack Type**: The type of thread stack where the current element is located. Supports `KERNEL_SPACE` and `USER_SPACE`, which represent user mode and kernel mode, respectively.
+5. **Dump Count**: The number of times the current element was sampled. The more samples of symbol, means the longer the method execution time.
+
+### Off CPU Profiling
+
+Off CPU Profiling can analyze the thread state when a thread switch occurs in the current process, thereby determining performance loss caused by blocked on I/O, locks, timers, paging/swapping, and other reasons.
+The execution flow between the eBPF agent and OAP in Off CPU Profiling is the same as in On CPU Profiling, but the data content being analyzed is different.
+
+#### Create task
+
+The process of creating an Off CPU Profiling task is the same as creating an On CPU Profiling task,
+with the only difference being that the Profiling task type is changed to OFF CPU Profiling. For specific parameters, please refer to the [previous section](#on-cpu-profiling).
+
+#### Profiling analyze
+
+When the eBPF agent receives a Off CPU Profiling task, it would also collect data and generate a schedule.
+When analyzing data, unlike On CPU Profiling, Off CPU Profiling can generate different flame graphs based on the following two aggregation methods:
+1. **By Time**: Aggregate based on the time consumed by each method, allowing you to analyze which methods take longer.
+2. **By Count**: Aggregate based on the number of times a method switches to non-CPU execution, allowing you to analyze which methods cause more non-CPU executions for the task.
+
+### Network Profiling
+
+Network Profiling can analyze and monitor network requests related to process, and based on the data, generate topology diagrams, metrics, and other information.
+Furthermore, it can be integrated with existing Tracing systems to enhance the data content.
+
+#### Create task
+
+Unlike On/Off CPU Profiling, Network Profiling requires specifying the instance entity information when creating a task.
+For example, in a Service Mesh, there may be multiple processes under a single instance(Pod), such as an application and Envoy.
+In network analysis, they usually work together, so analyzing them together can give you a better understanding of the network execution situation of the Pod.
+The following parameters are needed:
+
+1. **Instance**: The current Instance entity.
+2. **Sampling**: Sampling information for network requests.
+
+Sampling represents how the current system samples raw data and combines it with the existing Tracing system,
+allowing you to see the complete network data corresponding to a Span in Tracing Span.
+Currently, it supports sampling Raw information for Spans using HTTP/1.x as RPC and parsing SkyWalking and Zipkin protocols.
+The sampling information configuration is as follows:
+
+1. **URI Regex**: Only collect requests that match the specified URI. If empty, all requests will be collected.
+2. **Min Duration**: Only sample data with a response time greater than or equal to the specified duration. If empty, all requests will be collected.
+3. **When 4XX**: Only sample data with a response status code between 400 and 500 (exclusive).
+4. **When 5XX**: Only sample data with a response status code between 500 and 600 (exclusive).
+5. **Settings**: When network data meets the above rules, how to collect the data.
+ 1. **Require Complete Request**: Whether to collect request data.
+ 2. **Max Request Size**: The maximum data size for collecting requests. If empty, all data will be collected.
+ 3. **Require Complete Response**: Whether to collect response data.
+ 4. **Max Response Size**: The maximum data size for collecting responses. If empty, all data will be collected.
+
+#### Profiling analysis
+
+After starting the task, the following data can be analyzed:
+
+1. **Topology**: Analyze the data flow and data types when the current instance interacts internally and externally.
+2. **TCP Metrics**: Network Layer-4 metrics between two process.
+3. **HTTP/1.x Metrics**: If there are HTTP/1.x requests between two nodes, the HTTP/1.x metrics would be analyzed based on the data content.
+4. **HTTP Request**: If two nodes use HTTP/1.x and include a tracing system, the tracing data would be extended with events.
+
+##### Topology
+
+The topology can generate two types of data:
+1. **Internal entities**: The network call relationships between all processes within the current instance.
+2. **Entities and external**: The call relationships between processes inside the entity and external network nodes.
+
+For external nodes, since eBPF can only collect remote IP and port information during data collection,
+OAP can use Kubernetes cluster information to recognize the corresponding **Service** or **Pod** names.
+
+Between two nodes, data flow direction can be detected, and the following types of data protocols can be identified:
+
+1. **HTTP**: Two nodes communicate using HTTP/1.x or HTTP/2.x protocol.
+2. **HTTPS**: Two nodes communicate using HTTPS.
+3. **TLS**: Two nodes use encrypted data for transition, such as when using `OpenSSL`.
+4. **TCP**: There is TCP data transmission between two nodes.
+
+##### TCP Metrics
+
+In the TCP metrics, each metric includes both **client-side** and **server-side** data. The metrics are as follows:
+
+|Name|Unit|Description|
+|----|----|------|
+|Write CPM|Count|Number of write requests initiated per minute|
+|Write Total Bytes|B|Total data size written per minute|
+|Write Avg Execute Time|ns|Average execution time for each write operation|
+|Write RTT|ns|Round Trip Time (RTT)|
+|Read CPM|Count|Number of read requests per minute|
+|Read Total Bytes|B|Total data size read per minute|
+|Read Avg Execute Time|ns|Average execution time for each read operation|
+|Connect CPM|Count|Number of new connections established|
+|Connect Execute Time|ns|Time taken to establish a connection|
+|Close CPM|Count|Number of closed connections|
+|Close Execute Time|ns|Time taken to close a connection|
+|Retransmit CPM|Count|Number of data retransmissions per minute|
+|Drop CPM|Count|Number of dropped packets per minute|
+
+##### HTTP/1.x Metrics
+
+If there is HTTP/1.x protocol communication between two nodes, the eBPF agent can recognize the request data and parse the following metric information:
+
+|Name|Unit|Description|
+|----|----|------|
+|Request CPM|Count|Number of requests received per minute|
+|Response Status CPM|Count|Number of occurrences of each response status code per minute|
+|Request Package Size|B|Average request package data size|
+|Response Package Size|B|Average response package data size|
+|Client Duration|ns|Time taken for the client to receive a response|
+|Server Duration|ns|Time taken for the server to send a response|
+
+##### HTTP Request
+
+If two nodes communicate using the HTTP/1.x protocol, and they employ a distributed tracing system,
+then eBPf agent can collect raw data according to the sampling rules configured in the previous sections.
+
+###### Sampling Raw Data
+
+When the sampling conditions are met, the original request or response data would be collected, including the following fields:
+
+1. **Data Size**: The data size of the current request/response content.
+2. **Data Content**: The raw data content. **Non-plain** format content would not be collected.
+3. **Data Direction**: The data transfer direction, either Ingress or Egress.
+4. **Data Type**: The data type, either Request or Response.
+5. **Connection Role**: The current node's role as a client or server.
+6. **Entity**: The entity information of the current process.
+7. **Time**: The Request or response sent/received time.
+
+###### Syscall Event
+
+When sampling rules are applied, the related Syscall invocations for the request or response would also be collected, including the following information:
+
+1. **Method Name**: System Syscall method names such as `read`, `write`, `readv`, `writev`, etc.
+2. **Packet Size**: The current TCP packet size.
+3. **Packet Count**: The number of sent or received packets.
+4. **Network Interface Information**: The network interface from which the packet was sent.
diff --git a/docs/en/setup/backend/backend-elasticsearch-monitoring.md b/docs/en/setup/backend/backend-elasticsearch-monitoring.md
new file mode 100644
index 000000000000..defd0a778a80
--- /dev/null
+++ b/docs/en/setup/backend/backend-elasticsearch-monitoring.md
@@ -0,0 +1,115 @@
+# Elasticsearch monitoring
+
+SkyWalking leverages elasticsearch-exporter for collecting metrics data from Elasticsearch. It leverages OpenTelemetry
+Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. The elasticsearch-exporter collect metrics data from Elasticsearch.
+2. OpenTelemetry Collector fetches metrics from elasticsearch-exporter via Prometheus Receiver and pushes metrics to
+ SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Setup [elasticsearch-exporter](https://github.com/prometheus-community/elasticsearch_exporter).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). The example for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/elasticsearch/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Elasticsearch Monitoring
+
+Elasticsearch monitoring provides multidimensional metrics monitoring of Elasticsearch clusters as `Layer: ELASTICSEARCH` `Service` in the OAP. In each cluster, the nodes are represented as `Instance` and indices are `Endpoint`s.
+
+### Elasticsearch Cluster Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|---------------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------|
+| Cluster Health | meter_elasticsearch_cluster_health_status | Whether all primary and replica shards are allocated | elasticsearch-exporter |
+| Tripped Of Breakers | meter_elasticsearch_cluster_breakers_tripped | Tripped for breaker | elasticsearch-exporter |
+| Nodes | meter_elasticsearch_cluster_nodes | Number of nodes in the cluster. | elasticsearch-exporter |
+| Data Nodes | meter_elasticsearch_cluster_data_nodes | Number of data nodes in the cluster | elasticsearch-exporter |
+| Pending Tasks | meter_elasticsearch_cluster_pending_tasks_total | Cluster level changes which have not yet been executed | elasticsearch-exporter |
+| CPU Usage Avg. (%) | meter_elasticsearch_cluster_cpu_usage_avg | Cluster level percent CPU used by process | elasticsearch-exporter |
+| JVM Memory Used Avg. (%) | meter_elasticsearch_cluster_jvm_memory_used_avg | Cluster level percent JVM memory used | elasticsearch-exporter |
+| Open Files | meter_elasticsearch_cluster_open_file_count | Open file descriptors | elasticsearch-exporter |
+| Active Primary Shards | meter_elasticsearch_cluster_primary_shards_total | The number of primary shards in your cluster. This is an aggregate total across all indices | elasticsearch-exporter |
+| Active Shards | meter_elasticsearch_cluster_shards_total | Aggregate total of all shards across all indices, which includes replica shards | elasticsearch-exporter |
+| Initializing Shards | meter_elasticsearch_cluster_initializing_shards_total | Count of shards that are being freshly created | elasticsearch-exporter |
+| Delayed Unassigned Shards | meter_elasticsearch_cluster_delayed_unassigned_shards_total | Shards delayed to reduce reallocation overhead | elasticsearch-exporter |
+| Relocating Shards | meter_elasticsearch_cluster_relocating_shards_total | The number of shards that are currently moving from one node to another node | elasticsearch-exporter |
+| Unassigned Shards | meter_elasticsearch_cluster_unassigned_shards_total | The number of shards that exist in the cluster state, but cannot be found in the cluster itself | elasticsearch-exporter |
+
+### Elasticsearch Node Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|---------------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------|
+| Node Rules | | meter_elasticsearch_node_rules | Node roles | elasticsearch-exporter |
+| JVM Memory Used | MB | meter_elasticsearch_node_jvm_memory_used | Node level JVM memory used size | elasticsearch-exporter |
+| CPU Percent | % | meter_elasticsearch_node_process_cpu_percent | Node level percent CPU used by process | elasticsearch-exporter |
+| Documents | | meter_elasticsearch_node_indices_docs | Count of index documents on this node | elasticsearch-exporter |
+| Segments | | meter_elasticsearch_node_segment_count | Count of index segments on this node | elasticsearch-exporter |
+| Disk Free Space | GB | meter_elasticsearch_node_all_disk_free_space | Available space on all block device | elasticsearch-exporter |
+| Open Files | | meter_elasticsearch_node_open_file_count | Open file descriptors | elasticsearch-exporter |
+| Process CPU Usage Percent | % | meter_elasticsearch_node_process_cpu_percent | Percent CPU used by process | elasticsearch-exporter |
+| OS CPU usage percent | % | meter_elasticsearch_node_os_cpu_percent | Percent CPU used by the OS | elasticsearch-exporter |
+| Load Average | | meter_elasticsearch_node_os_load1
meter_elasticsearch_node_os_load5
meter_elasticsearch_node_os_load15 | Shortterm, Midterm, Longterm load average | elasticsearch-exporter |
+| JVM Memory Usage | MB | meter_elasticsearch_node_jvm_memory_nonheap_used
meter_elasticsearch_node_jvm_memory_heap_used
meter_elasticsearch_node_jvm_memory_heap_max | JVM memory currently usage by area | elasticsearch-exporter |
+| JVM Pool Peak Used | MB | meter_elasticsearch_node_jvm_memory_pool_peak_used | JVM memory currently used by pool | elasticsearch-exporter |
+| GC Count | | meter_elasticsearch_node_jvm_gc_count | Count of JVM GC runs | elasticsearch-exporter |
+| GC Time | ms/min | meter_elasticsearch_node_jvm_gc_time | GC run time | elasticsearch-exporter |
+| All Operations ReqRate | | meter_elasticsearch_node_indices_*_req_rate | All Operations ReqRate on node | elasticsearch-exporter |
+| Indexing Rate | reqps | meter_elasticsearch_node_indices_indexing_index_total_req_rate
meter_elasticsearch_node_indices_indexing_index_total_proc_rate | Indexing rate on node | elasticsearch-exporter |
+| Searching Rate | reqps | meter_elasticsearch_node_indices_search_fetch_total_req_rate
meter_elasticsearch_node_indices_search_query_time_seconds_proc_rate | Searching rate on node | elasticsearch-exporter |
+| Total Translog Operations | | meter_elasticsearch_node_indices_translog_operations | Total translog operations | elasticsearch-exporter |
+| Total Translog Size | MB | meter_elasticsearch_node_indices_translog_size | Total translog size | elasticsearch-exporter |
+| Tripped For Breakers | | meter_elasticsearch_node_breakers_tripped | Tripped for breaker | elasticsearch-exporter |
+| Estimated Size Of Breaker | MB | meter_elasticsearch_node_breakers_estimated_size | Estimated size of breaker | elasticsearch-exporter |
+| Documents Count | KB/s | meter_elasticsearch_node_indices_docs | Count of documents on this node | elasticsearch-exporter |
+| Merged Documents Count | count/s | meter_elasticsearch_node_indices_merges_docs_total | Cumulative docs merged | elasticsearch-exporter |
+| Deleted Documents Count | | meter_elasticsearch_node_indices_docs_deleted_total | Count of deleted documents on this node | elasticsearch-exporter |
+| Documents Index Rate | calls/s | meter_elasticsearch_node_indices_indexing_index_total_req_rate | Total index calls per second | elasticsearch-exporter |
+| Merged Documents Rate | MB / s | meter_elasticsearch_node_indices_merges_total_size_bytes_total | Total merge size per second | elasticsearch-exporter |
+| Documents Deleted Rate | docs/s | meter_elasticsearch_node_indices_docs_deleted | Count of deleted documents per second on this node | elasticsearch-exporter |
+| Count Of Index Segments | | meter_elasticsearch_node_segment_count | Count of index segments on this node | elasticsearch-exporter |
+| Current Memory Size Of Segments | MB | meter_elasticsearch_node_segment_memory | Current memory size of segments | elasticsearch-exporter |
+| Network | bytes/sec | meter_elasticsearch_node_network_send_bytes
meter_elasticsearch_node_network_receive_bytes | Total number of bytes sent and receive | elasticsearch-exporter |
+| Disk Usage Percent | % | meter_elasticsearch_node_disk_usage_percent | Used space on block device | elasticsearch-exporter |
+| Disk Usage | GB | meter_elasticsearch_node_disk_usage | Used space size of block device | elasticsearch-exporter |
+| Disk Read | KBs | meter_elasticsearch_node_disk_io_read_bytes | Total kilobytes read from disk | elasticsearch-exporter |
+| Disk Write | KBs | meter_elasticsearch_node_disk_io_write_bytes | Total kilobytes write from disk | elasticsearch-exporter |
+
+### Elasticsearch Index Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|
+| Documents Primary | | meter_elasticsearch_index_indices_docs_primary | Count of documents with only primary shards on all nodes | elasticsearch-exporter |
+| Deleted Documents Primary | | meter_elasticsearch_index_indices_deleted_docs_primary | Count of deleted documents with only primary shards | elasticsearch-exporter |
+| Data Primary | GB | meter_elasticsearch_index_indices_store_size_bytes_primary | Current total size of stored index data with only primary shards on all nodes | elasticsearch-exporter |
+| Data | GB | meter_elasticsearch_index_indices_store_size_bytes_total | Current total size of stored index data with all shards on all nodes | elasticsearch-exporter |
+| Segments Primary | | meter_elasticsearch_index_indices_segment_count_primary | Current number of segments with only primary shards on all nodes | elasticsearch-exporter |
+| Segments Memory Primary | MB | meter_elasticsearch_index_indices_segment_memory_bytes_primary | Current size of segments with only primary shards on all nodes | elasticsearch-exporter |
+| Segments | | meter_elasticsearch_index_indices_segment_count_total | Current number of segments with all shards on all nodes | elasticsearch-exporter |
+| Segments Memory | MB | meter_elasticsearch_index_indices_segment_memory_bytes_total | Current size of segments with all shards on all nodes | elasticsearch-exporter |
+| Indexing Rate | | meter_elasticsearch_index_stats_indexing_index_total_req_rate
meter_elasticsearch_index_stats_indexing_index_total_proc_rate | Indexing rate on index | elasticsearch-exporter |
+| Searching Rate | | meter_elasticsearch_index_stats_search_query_total_req_rate
meter_elasticsearch_index_stats_search_query_total_proc_rate | Searching rate on index | elasticsearch-exporter |
+| All Operations ReqRate | | meter_elasticsearch_index_stats_*_req_rate | All Operations ReqRate on index | elasticsearch-exporter |
+| All Operations Runtime | | meter_elasticsearch_index_stats_*_time_seconds_total | All Operations Runtime/s on index | elasticsearch-exporter |
+| Avg. Search Time Execute / Request | s | meter_elasticsearch_index_search_fetch_avg_time
meter_elasticsearch_index_search_query_avg_time
meter_elasticsearch_index_search_scroll_avg_time
meter_elasticsearch_index_search_suggest_avg_time | Search Operation Avg. time on index | elasticsearch-exporter |
+| Search Operations Rate | req/s | meter_elasticsearch_index_stats_search_query_total_req_rate
meter_elasticsearch_index_stats_search_fetch_total_req_rate
meter_elasticsearch_index_stats_search_scroll_total_req_rate
meter_elasticsearch_index_stats_search_suggest_total_req_rate | Search Operations ReqRate on index | elasticsearch-exporter |
+| Shards Documents | | meter_elasticsearch_index_indices_shards_docs | Count of documents per shards on index | elasticsearch-exporter |
+| Documents (Primary Shards) | | meter_elasticsearch_index_indices_docs_primary | Count of documents with only primary shards on index | elasticsearch-exporter |
+| Documents Created Per Min (Primary Shards) | | meter_elasticsearch_index_indices_docs_primary_rate | Documents rate with only primary shards on index | elasticsearch-exporter |
+| Total Size Of Index (Primary Shards) | MB | meter_elasticsearch_index_indices_store_size_bytes_primary | Current total size of stored index data in bytes with only primary shards on all nodes | elasticsearch-exporter |
+| Documents (All Shards) | | meter_elasticsearch_index_indices_docs_total | Count of documents with all shards on index | elasticsearch-exporter |
+| Documents Created Per Min (All Shards) | | meter_elasticsearch_index_indices_docs_total_rate | Documents rate with only all shards on index | elasticsearch-exporter |
+| Total Size Of Index (All Shards) | MB | meter_elasticsearch_index_indices_store_size_bytes_total | Current total size of stored index data in bytes with all shards on all nodes | elasticsearch-exporter |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `/config/otel-rules/elasticsearch/elasticsearch-cluster.yaml, /config/otel-rules/elasticsearch/elasticsearch-node.yaml, /config/otel-rules/elasticsearch/elasticsearch-index.yaml`.
+The Elasticsearch dashboard panel configurations are found in `/config/ui-initialized-templates/elasticsearch`.
diff --git a/docs/en/setup/backend/backend-expose.md b/docs/en/setup/backend/backend-expose.md
new file mode 100644
index 000000000000..f540a77f2834
--- /dev/null
+++ b/docs/en/setup/backend/backend-expose.md
@@ -0,0 +1,36 @@
+# Setup External Communication Channels
+
+SkyWalking has default activated gRPC/HTTP servers in the core module, which serve for both internal communication
+and external data report or query.
+
+In some advanced scenarios, such as security requirements, specific gRPC/HTTP servers should be exposed for external
+requests.
+
+```yaml
+receiver-sharing-server:
+ selector: ${SW_RECEIVER_SHARING_SERVER:default}
+ default:
+ # For REST server
+ restHost: ${SW_RECEIVER_SHARING_REST_HOST:0.0.0.0}
+ restPort: ${SW_RECEIVER_SHARING_REST_PORT:0}
+ restContextPath: ${SW_RECEIVER_SHARING_REST_CONTEXT_PATH:/}
+ restMaxThreads: ${SW_RECEIVER_SHARING_REST_MAX_THREADS:200}
+ restIdleTimeOut: ${SW_RECEIVER_SHARING_REST_IDLE_TIMEOUT:30000}
+ restAcceptQueueSize: ${SW_RECEIVER_SHARING_REST_QUEUE_SIZE:0}
+ httpMaxRequestHeaderSize: ${SW_RECEIVER_SHARING_HTTP_MAX_REQUEST_HEADER_SIZE:8192}
+ # For gRPC server
+ gRPCHost: ${SW_RECEIVER_GRPC_HOST:0.0.0.0}
+ gRPCPort: ${SW_RECEIVER_GRPC_PORT:0}
+ maxConcurrentCallsPerConnection: ${SW_RECEIVER_GRPC_MAX_CONCURRENT_CALL:0}
+ maxMessageSize: ${SW_RECEIVER_GRPC_MAX_MESSAGE_SIZE:52428800} #50MB
+ gRPCThreadPoolSize: ${SW_RECEIVER_GRPC_THREAD_POOL_SIZE:0}
+ gRPCSslEnabled: ${SW_RECEIVER_GRPC_SSL_ENABLED:false}
+ gRPCSslKeyPath: ${SW_RECEIVER_GRPC_SSL_KEY_PATH:""}
+ gRPCSslCertChainPath: ${SW_RECEIVER_GRPC_SSL_CERT_CHAIN_PATH:""}
+ gRPCSslTrustedCAsPath: ${SW_RECEIVER_GRPC_SSL_TRUSTED_CAS_PATH:""}
+ authentication: ${SW_AUTHENTICATION:""}
+```
+
+Set `restPort`(HTTP) and `gRPCPort`(gRPC) to a legal port(greater than 0), would initialize new gRPC/HTTP servers for
+external requests with other relative settings. In this case, `core/gRPC` and `core/rest` could be served for cluster
+internal communication only.
diff --git a/docs/en/setup/backend/backend-flink-monitoring.md b/docs/en/setup/backend/backend-flink-monitoring.md
new file mode 100644
index 000000000000..99f4a25b5e83
--- /dev/null
+++ b/docs/en/setup/backend/backend-flink-monitoring.md
@@ -0,0 +1,105 @@
+# Flink monitoring
+
+## Flink server performance from built-in metrics data
+SkyWalking leverages OpenTelemetry Collector to transfer the flink metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. Configure Flink jobManager and TaskManager to expose metrics data for scraping through Prometheus endpoint.
+2. OpenTelemetry Collector fetches metrics from Flink jobManager and TaskManager through Prometheus endpoint, and pushes metrics to SkyWalking OAP Server via
+ OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Set up [built-in prometheus endpoint](https://nightlies.apache.org/flink/flink-docs-release-2.0-preview1/docs/deployment/metric_reporters/#prometheus).
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker).
+ Please note that the OpenTelemetry Collector uses the job_name label by default, which may conflict with the job_name label in Flink.
+ Please modify the Flink label name in the configuration to avoid this conflict, you can refer to [here](../../../../test/e2e-v2/cases/flink/otel-collector-config.yaml)
+ for details on Prometheus Receiver in OpenTelemetry Collector.
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Flink Monitoring
+
+Flink monitoring provides multidimensional metrics monitoring of Flink cluster as `Layer: Flink` `Service` in
+the OAP. In each cluster, the taskManager is represented as `Instance` and the job is represented as `Endpoint`.
+
+### Flink service Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-------------------------------|-------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------|
+| Running Jobs | Count | meter_flink_jobManager_running_job_number | The number of running jobs. | Flink JobManager |
+| TaskManagers | Count | meter_flink_jobManager_taskManagers_registered_number | The number of taskManagers. | Flink JobManager |
+| JVM CPU Load | % | meter_flink_jobManager_jvm_cpu_load | The number of the jobManager JVM CPU load. | Flink JobManager |
+| JVM thread count | Count | meter_flink_jobManager_jvm_thread_count | The total number of the jobManager JVM live threads. | Flink JobManager |
+| JVM Memory Heap Used | MB | meter_flink_jobManager_jvm_memory_heap_used | The amount of the jobManager JVM memory heap used. | Flink JobManager |
+| JVM Memory NonHeap Used | MB | meter_flink_jobManager_jvm_memory_NonHeap_used | The amount of the jobManager JVM nonHeap memory used. | Flink JobManager |
+| Task Managers Slots Total | Count | meter_flink_jobManager_taskManagers_slots_total | The number of total slots. | Flink JobManager |
+| Task Managers Slots Available | Count | meter_flink_jobManager_taskManagers_slots_available | The number of available slots. | Flink JobManager |
+| JVM CPU Time | ms | meter_flink_jobManager_jvm_cpu_time | The jobManager CPU time used by the JVM increase per minute. | Flink JobManager |
+| JVM Memory Heap Available | MB | meter_flink_jobManager_jvm_memory_heap_available | The amount of the jobManager available JVM memory Heap. | Flink JobManager |
+| JVM Memory NoHeap Available | MB | meter_flink_jobManager_jvm_memory_nonHeap_available | The amount of the jobManager available JVM memory noHeap. | Flink JobManager |
+| JVM Memory Metaspace Used | MB | meter_flink_jobManager_jvm_memory_metaspace_used | The amount of the jobManager Used JVM metaspace memory. | Flink JobManager |
+| JVM Metaspace Available | MB | meter_flink_jobManager_jvm_memory_metaspace_available | The amount of the jobManager available JVM Metaspace Memory. | Flink JobManager |
+| JVM G1 Young Generation Count | Count | meter_flink_jobManager_jvm_g1_young_generation_count | The incremental number of the jobManager JVM G1 young generation count per minute. | Flink JobManager |
+| JVM G1 Old Generation Count | Count | meter_flink_jobManager_jvm_g1_old_generation_count | The incremental number of the jobManager JVM G1 old generation count per minute. | Flink JobManager |
+| JVM G1 Young Generation Time | Count | meter_flink_jobManager_jvm_g1_young_generation_time | The incremental time of the jobManager JVM G1 young generation per minute. | Flink JobManager |
+| JVM G1 Old Generation Time | ms | meter_flink_jobManager_jvm_g1_old_generation_time | The incremental time of JVM G1 old generation increase per minute. | Flink JobManager |
+| JVM G1 Old Generation Count | Count | meter_flink_jobManager_jvm_all_garbageCollector_count | The incremental number of the jobManager JVM all garbageCollector count per minute. | Flink JobManager |
+| JVM All GarbageCollector Time | ms | meter_flink_jobManager_jvm_all_garbageCollector_time | The incremental time spent performing garbage collection for the given (or all) collector for the jobManager per minute. | Flink JobManager |
+
+### Flink instance Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|----------------------------------|---------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| JVM CPU Load | % | meter_flink_taskManager_jvm_cpu_load | The number of the JVM CPU load. | Flink TaskManager |
+| JVM Thread Count | Count | meter_flink_taskManager_jvm_thread_count | The total number of JVM live threads. | Flink TaskManager |
+| JVM Memory Heap Used | MB | meter_flink_taskManager_jvm_memory_heap_used | The amount of JVM memory heap used. | Flink TaskManager |
+| JVM Memory NonHeap Used | MB | meter_flink_taskManager_jvm_memory_nonHeap_used | The amount of JVM nonHeap memory used. | Flink TaskManager |
+| JVM CPU Time | ms | meter_flink_taskManager_jvm_cpu_time | The CPU time used by the JVM increase per minute. | Flink TaskManager |
+| JVM Memory Heap Available | MB | meter_flink_taskManager_jvm_memory_heap_available | The amount of available JVM memory Heap. | Flink TaskManager |
+| JVM Memory NonHeap Available | MB | meter_flink_taskManager_jvm_memory_nonHeap_available | The amount of available JVM memory nonHeap. | Flink TaskManager |
+| JVM Memory Metaspace Used | MB | meter_flink_taskManager_jvm_memory_metaspace_used | The amount of Used JVM metaspace memory. | Flink TaskManager |
+| JVM Metaspace Available | MB | meter_flink_taskManager_jvm_memory_metaspace_available | The amount of Available JVM Metaspace Memory. | Flink TaskManager |
+| NumRecordsIn | Count | meter_flink_taskManager_numRecordsIn | The incremental number of records this task has received per minute. | Flink TaskManager |
+| NumRecordsOut | Count | meter_flink_taskManager_numRecordsOut | The incremental number of records this task has emitted per minute. | Flink TaskManager |
+| NumBytesInPerSecond | Bytes/s | meter_flink_taskManager_numBytesInPerSecond | The number of bytes received per second. | Flink TaskManager |
+| NumBytesOutPerSecond | Bytes/s | meter_flink_taskManager_numBytesOutPerSecond | The number of bytes this task emits per second. | Flink TaskManager |
+| Netty UsedMemory | MB | meter_flink_taskManager_netty_usedMemory | The amount of used netty memory. | Flink TaskManager |
+| Netty AvailableMemory | MB | meter_flink_taskManager_netty_availableMemory | The amount of available netty memory. | Flink TaskManager |
+| IsBackPressured | Count | meter_flink_taskManager_isBackPressured | Whether the task is back-pressured. | Flink TaskManager |
+| InPoolUsage | % | meter_flink_taskManager_inPoolUsage | An estimate of the input buffers usage. (ignores LocalInputChannels). | Flink TaskManager |
+| OutPoolUsage | % | meter_flink_taskManager_outPoolUsage | An estimate of the output buffers usage. The pool usage can be > 100% if overdraft buffers are being used. | Flink TaskManager |
+| SoftBackPressuredTimeMsPerSecond | ms | meter_flink_taskManager_softBackPressuredTimeMsPerSecond | The time this task is softly back pressured per second.Softly back pressured task will be still responsive and capable of for example triggering unaligned checkpoints. | Flink TaskManager |
+| HardBackPressuredTimeMsPerSecond | ms | meter_flink_taskManager_hardBackPressuredTimeMsPerSecond | The time this task is back pressured in a hard way per second.During hard back pressured task is completely blocked and unresponsive preventing for example unaligned checkpoints from triggering. | Flink TaskManager |
+| IdleTimeMsPerSecond | ms | meter_flink_taskManager_idleTimeMsPerSecond | The time this task is idle (has no data to process) per second. Idle time excludes back pressured time, so if the task is back pressured it is not idle. | Flink TaskManager |
+| BusyTimeMsPerSecond | ms | meter_flink_taskManager_busyTimeMsPerSecond | The time this task is busy (neither idle nor back pressured) per second. Can be NaN, if the value could not be calculated. | Flink TaskManager |
+
+### Flink Endpoint Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-------------------------|---------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| Job RunningTime | min | meter_flink_job_runningTime | The job running time. | Flink JobManager |
+| Job Restart Number | Count | meter_flink_job_restart_number | The number of job restart. | Flink JobManager |
+| Job RestartingTime | min | meter_flink_job_restartingTime | The job restarting Time. | Flink JobManager |
+| Job CancellingTime | min | meter_flink_job_cancellingTime | The job cancelling time. | Flink JobManager |
+| Checkpoints Total | Count | meter_flink_job_checkpoints_total | The total number of checkpoints. | Flink JobManager |
+| Checkpoints Failed | Count | meter_flink_job_checkpoints_failed | The number of failed checkpoints. | Flink JobManager |
+| Checkpoints Completed | Count | meter_flink_job_checkpoints_completed | The number of completed checkpoints. | Flink JobManager |
+| Checkpoints InProgress | Count | meter_flink_job_checkpoints_inProgress | The number of inProgress checkpoints. | Flink JobManager |
+| CurrentEmitEventTimeLag | ms | meter_flink_job_currentEmitEventTimeLag | The latency between a data record's event time and its emission time from the source. | Flink TaskManager |
+| NumRecordsIn | Count | meter_flink_job_numRecordsIn | The total number of records this operator/task has received. | Flink TaskManager |
+| NumRecordsOut | Count | meter_flink_job_numRecordsOut | The total number of records this operator/task has emitted. | Flink TaskManager |
+| NumBytesInPerSecond | Bytes/s | meter_flink_job_numBytesInPerSecond | The number of bytes this task received per second. | Flink TaskManager |
+| NumBytesOutPerSecond | Bytes/s | meter_flink_job_numBytesOutPerSecond | The number of bytes this task emits per second. | Flink TaskManager |
+| LastCheckpointSize | Bytes | meter_flink_job_lastCheckpointSize | The checkPointed size of the last checkpoint (in bytes), this metric could be different from lastCheckpointFullSize if incremental checkpoint or changelog is enabled. | Flink JobManager |
+| LastCheckpointDuration | ms | meter_flink_job_lastCheckpointDuration | The time it took to complete the last checkpoint. | Flink JobManager |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `otel-rules/flink/flink-jobManager.yaml, otel-rules/flink/flink-taskManager.yaml, otel-rules/flink/flink-job.yaml`.
+The Flink dashboard panel configurations are found in `ui-initialized-templates/flink`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-health-check.md b/docs/en/setup/backend/backend-health-check.md
new file mode 100644
index 000000000000..c717851ca16d
--- /dev/null
+++ b/docs/en/setup/backend/backend-health-check.md
@@ -0,0 +1,70 @@
+# Health Check
+
+Health check intends to provide a unique approach to checking the health status of the OAP server. It includes the health status
+of modules, GraphQL, and gRPC services readiness.
+
+> 0 means healthy, and more than 0 means unhealthy.
+> less than 0 means that the OAP doesn't start up.
+
+## Health Checker Module.
+
+The Health Checker module helps observe the health status of modules. You may activate it as follows:
+```yaml
+health-checker:
+ selector: ${SW_HEALTH_CHECKER:default}
+ default:
+ checkIntervalSeconds: ${SW_HEALTH_CHECKER_INTERVAL_SECONDS:5}
+```
+Note: The `telemetry` module should be enabled at the same time. This means that the provider should not be `-` and `none`.
+
+After that, we can check the OAP server health status by querying the http endpoint: `/healthcheck`,
+see [the health check http endpoint doc](../../api/health-check.md).
+
+You can also query the healthiness via other methods like GraphQL, see following.
+```
+query{
+ checkHealth{
+ score
+ details
+ }
+}
+```
+
+If the OAP server is healthy, the response should be
+
+```json
+{
+ "data": {
+ "checkHealth": {
+ "score": 0,
+ "details": ""
+ }
+ }
+}
+```
+
+If some modules are unhealthy (e.g. storage H2 is down), then the result may look as follows:
+
+```json
+{
+ "data": {
+ "checkHealth": {
+ "score": 1,
+ "details": "storage_h2,"
+ }
+ }
+}
+```
+Refer to [checkHealth query](https://github.com/apache/skywalking-query-protocol/blob/master/common.graphqls)
+for more details.
+
+## The readiness of GraphQL and gRPC
+
+Use the query above to check the readiness of GraphQL.
+
+OAP has implemented the [gRPC Health Checking Protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md).
+You may use the [grpc-health-probe](https://github.com/grpc-ecosystem/grpc-health-probe) or any other tools to check the
+health of OAP gRPC services.
+
+## CLI tool
+Please follow the [CLI doc](https://github.com/apache/skywalking-cli#checkhealth) to get the health status score directly through the `checkhealth` command.
diff --git a/docs/en/setup/backend/backend-init-mode.md b/docs/en/setup/backend/backend-init-mode.md
new file mode 100644
index 000000000000..669ec6cacf1f
--- /dev/null
+++ b/docs/en/setup/backend/backend-init-mode.md
@@ -0,0 +1,20 @@
+# Init mode
+The SkyWalking backend supports multiple storage implementors. Most of them would automatically initialize the storage,
+such as Elastic Search or Database, when the backend starts up first.
+
+But there may be some unexpected events that may occur with the storage, such as
+`When multiple Elastic Search indexes are created concurrently, these backend instances would startup at the same time.`,
+When there is a change, the APIs of Elastic Search would be blocked without reporting any exception.
+This often happens on container management platforms, such as k8s.
+
+This is where you need the **Init mode** startup.
+
+## Solution
+Only a single instance should run in the **Init mode** before other instances start up.
+And this instance will exit graciously after all initialization steps are done.
+
+Use `oapServiceInit.sh`/`oapServiceInit.bat` to start up backend. You should see the following logs:
+> 2018-11-09 23:04:39,465 - org.apache.skywalking.oap.server.starter.OAPServerStartUp -2214 [main] INFO [] - OAP starts up in init mode successfully, exit now...
+
+## Kubernetes
+Initialization in this mode would be included in our Kubernetes scripts and Helm.
diff --git a/docs/en/setup/backend/backend-ip-port.md b/docs/en/setup/backend/backend-ip-port.md
new file mode 100644
index 000000000000..419e53b1276c
--- /dev/null
+++ b/docs/en/setup/backend/backend-ip-port.md
@@ -0,0 +1,26 @@
+# IP and port setting
+The backend uses IP and port binding in order to allow the OS to have multiple IPs.
+The binding/listening IP and port are specified by the core module
+```yaml
+core:
+ default:
+ restHost: 0.0.0.0
+ restPort: 12800
+ restContextPath: /
+ gRPCHost: 0.0.0.0
+ gRPCPort: 11800
+```
+There are two IP/port pairs for gRPC and HTTP REST services.
+
+- Most agents and probes use gRPC service for better performance and code readability.
+- Some agents use REST service because gRPC may not be supported in that language.
+- The UI uses REST service, but the data is always in GraphQL format.
+
+
+## Note
+### IP binding
+For users unfamiliar with IP binding, note that once IP binding is complete, the client could only use this IP to access the service. For example, if `172.09.13.28` is bound, even if you are
+in this machine, you must use `172.09.13.28`, rather than `127.0.0.1` or `localhost`, to access the service.
+
+### Module provider specified IP and port
+The IP and port in the core module are provided by default. But it is common for some module providers, such as receiver modules, to provide other IP and port settings.
diff --git a/docs/en/setup/backend/backend-java-app-profiling.md b/docs/en/setup/backend/backend-java-app-profiling.md
new file mode 100644
index 000000000000..b76c1cc4cd11
--- /dev/null
+++ b/docs/en/setup/backend/backend-java-app-profiling.md
@@ -0,0 +1,98 @@
+# Java App Profiling
+
+Java App Profiling uses the AsyncProfiler for sampling
+
+Async Profiler is bound within the auto-instrument agent and corresponds to [In-Process Profiling](../../concepts-and-designs/profiling.md#in-process-profiling).
+
+It is delivered to the agent in the form of a task, allowing it to be enabled or disabled dynamically.
+When service encounters performance issues (cpu usage, memory allocation, locks), Async Profiler task can be created.
+When the agent receives a task, it enables Async Profiler for sampling.
+After sampling is completed, the sampling results are analyzed by requesting the server to render a flame graph for performance
+analysis to determine the specific business code lines that cause performance problems.
+
+## Activate Async Profiler in the OAP
+OAP and the agent use a brand-new protocol to exchange Async Profiler data, so it is necessary to start OAP with the following configuration:
+
+```yaml
+receiver-async-profiler:
+ selector: ${SW_RECEIVER_ASYNC_PROFILER:default}
+ default:
+ # Used to manage the maximum size of the jfr file that can be received, the unit is Byte, default is 30M
+ jfrMaxSize: ${SW_RECEIVER_ASYNC_PROFILER_JFR_MAX_SIZE:31457280}
+ # Used to determine whether to receive jfr in memory file or physical file mode
+ #
+ # The memory file mode have fewer local file system limitations, so they are by default. But it costs more memory.
+ #
+ # The physical file mode will use less memory when parsing and is more friendly to parsing large files.
+ # However, if the storage of the tmp directory in the container is insufficient, the oap server instance may crash.
+ # It is recommended to use physical file mode when volume mounting is used or the tmp directory has sufficient storage.
+ memoryParserEnabled: ${SW_RECEIVER_ASYNC_PROFILER_MEMORY_PARSER_ENABLED:true}
+```
+
+## Async Profiler Task with Analysis
+
+To use the Async Profiler feature, please follow these steps:
+
+1. **Create Async Profiler task**: Use the UI or CLI tool to create a task.
+2. **Wait agent collect data and upload**: Wait for Async Profiler to collect JFR data and report
+3. **Query task progress**: Query the progress of tasks, including analyzing successful and failed instances and task logs
+4. **Analyze the data**: Analyze the JFR data to determine where performance bottlenecks exist in the service.
+
+### Create an Async Profiler task
+
+Create an Async Profiler task to notify some java-agent instances in the execution service to start Async Profiler for data collection.
+
+When creating a task, the following configuration fields are required:
+
+1. **serviceId**: Define the service to execute the task.
+2. **serviceInstanceIds**: Define which instances need to execute tasks.
+3. **duration**: Define the duration of this task (second).
+4. **events**: Define which event types this task needs to collect.
+5. **execArgs**: Other Async Profiler execution options, e.g. alloc=2k,lock=2s.
+
+When the Agent receives a Async Profiler task from OAP, it automatically generates a log to notify that the task has been acknowledged. The log contains the following field information:
+
+1. **Instance**: The name of the instance where the Agent is located.
+2. **Type**: Supports "NOTIFIED" and "EXECUTION_FINISHED" and "JFR_UPLOAD_FILE_TOO_LARGE_ERROR", "EXECUTION_TASK_ERROR", with the current log displaying "NOTIFIED".
+3. **Time**: The time when the Agent received the task.
+
+### Wait the agent to collect data and upload
+
+At this point, Async Profiler will trace the events you selected when you created the task:
+
+1. CPU,WALL,ITIMER,CTIMER: CPU cycles
+2. ALLOC: Allocations in Java Heap
+3. LOCK: Contented lock attempts, including both Java object monitors and ReentrantLocks
+
+Finally, the agent will upload the jfr file produced by Async Profiler to the oap server for online performance analysis.
+
+### Query the profiling task progresses
+
+Wait for Async Profiler to complete data collection and upload successfully.
+We can query the execution logs of the Async Profiler task and the task status, which includes the following information:
+
+1. **successInstanceIds**: SuccessInstanceIds gives instances that have executed the task successfully.
+2. **errorInstanceIds**: ErrorInstanceIds gives instances that failed to execute the task.
+3. **logs**: All task execution logs of the current task.
+ 1. **id**: The task id.
+ 2. **instanceId**: InstanceId is the id of the instance which reported this task log.
+ 3. **instanceName**: InstanceName is the name of the instance which reported this task log.
+ 4. **operationType**: Contains "NOTIFIED" and "EXECUTION_FINISHED" and "JFR_UPLOAD_FILE_TOO_LARGE_ERROR", "EXECUTION_TASK_ERROR".
+ 5. **operationTime**: operationTime is the time when the operation occurs.
+
+### Analyze the profiling data
+
+Once some agents completed the task, we can analyze the data through the following query:
+
+1. **taskId**: The task id.
+2. **instanceIds**: InstanceIds defines the instances to be included for analysis
+3. **eventType**: EventType is the specific JFR Event type to be selected for analysis even if multiple events are included in the JFR file.
+
+After the query, the following data would be returned to render a flame graph:
+1. **type**: eventType in query parameters.
+2. **elements**: Combined with "id" to determine the hierarchical relationship.
+ 1. **Id**: Id is the identity of the stack element.
+ 2. **parentId**: Parent element ID. The dependency relationship between elements can be determined using the element ID and parent element ID.
+ 3. **codeSignature**: Method signatures in tree nodes.
+ 4. **total**:The total number of samples of the current tree node, including child nodes.
+ 5. **self**: The sampling number of the current tree node, excluding samples of the children.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-k8s-monitoring-cilium.md b/docs/en/setup/backend/backend-k8s-monitoring-cilium.md
new file mode 100644
index 000000000000..7ec68f89e6ae
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s-monitoring-cilium.md
@@ -0,0 +1,128 @@
+# Kubernetes (K8s) monitoring from Rover
+
+SkyWalking uses the Cilium Fetcher to gather traffic data between services from Cilium Hubble via the Observe API. It then leverages the [OAL System](./../../concepts-and-designs/oal.md) for metrics and entity analysis.
+
+## Data flow
+
+SkyWalking fetches Cilium Node and Observability Data from gRPC API, analysis to generate entity and using [OAL](./../../concepts-and-designs/oal.md) to generating metrics.
+
+## API Requirements
+
+1. [Peers API](https://github.com/cilium/cilium/blob/main/api/v1/peer/peer_grpc.pb.go#L33-L39): Listen the hubble node in the cluster, OAP would communicate with Hubble node to obtain Observe data.
+2. [Observe API](https://github.com/cilium/cilium/blob/main/api/v1/observer/observer_grpc.pb.go#L41): Fetch the Flow data from Hubble node.
+
+## Setup
+1. Please following the [Setup Hubble Observability documentation](https://docs.cilium.io/en/stable/gettingstarted/hubble_setup/) to setting the Hubble for provided API.
+2. To activate Cilium receiver module, set `selector=default` in the YAML or `set SW_CILIUM_FETCHER=default` through the system environment variable.
+```yaml
+cilium-fetcher:
+ selector: ${SW_CILIUM_FETCHER:default}
+ default:
+ # Host name and port of Hubble peer component
+ peerHost: ${SW_CILIUM_FETCHER_PEER_HOST:hubble-peer.kube-system.svc.cluster.local}
+ peerPort: ${SW_CILIUM_FETCHER_PEER_PORT:80}
+ fetchFailureRetrySecond: ${SW_CILIUM_FETCHER_FETCH_FAILURE_RETRY_SECOND:10}
+ sslConnection: ${SW_CILIUM_FETCHER_SSL_CONNECTION:false}
+ sslPrivateKeyFile: ${SW_CILIUM_FETCHER_PRIVATE_KEY_FILE_PATH:}
+ sslCertChainFile: ${SW_CILIUM_FETCHER_CERT_CHAIN_FILE_PATH:}
+ sslCaFile: ${SW_CILIUM_FETCHER_CA_FILE_PATH:}
+ convertClientAsServerTraffic: ${SW_CILIUM_FETCHER_CONVERT_CLIENT_AS_SERVER_TRAFFIC:true}
+```
+3. If enabled the [TLS certificate within the Hubble](https://docs.cilium.io/en/stable/gettingstarted/hubble-configuration/#tls-certificates), please update these few configurations.
+ 1. `peerPort`: usually should be updated to the `443`.
+ 2. `sslConnection`: should be set to `true`.
+ 3. `sslPrivateKeyFile`: the path of the private key file.
+ 4. `sslCertChainFile`: the path of the certificate chain file.
+ 5. `sslCaFile`: the path of the CA file.
+3. Configure the cilium rules please configure the following configuration:
+ 1. `cilium-rules/exclude.yaml`: Configure the which endpoint should be excluded from the monitoring, Please read [exclude rules selection](#exclude-rules) for more detail.
+ 2. `cilium-rules/metadata-service-mapping.yaml`: Configure the service name and endpoint mapping.
+
+### Exclude Rules
+
+The exclude configuration in Cilium rules is used to specify which Cilium Endpoints would be excluded from being added to the topology map or from the generation of metrics and other data.
+
+```yaml
+namespaces: # define with traffic from which namespace should be excluded
+ - kube-system
+
+labels: # define with traffic from which endpoint labels should be excluded, if matches any labels, the traffic would be excluded.
+ - k8s:io.cilium.k8s.namespace.labels.istio-injection: "enabled" # Each labels is a key-value pair, the key is the label key, the value is the label value.
+ k8s:security.istio.io/tlsMode: istio
+```
+
+By default, all the traffic from `kube-system` and traffic management by istio mesh would be excluded.
+
+NOTE: Only the endpoint in both source and destination matches the exclude rules would be excluded. Otherwise, the traffic would be still included.
+
+## Generated Entities
+
+SkyWalking fetch the flow from Cilium, analyzes the source and destination endpoint to parse out the following corresponding entities:
+1. Service
+2. Service Instance
+3. Service Endpoint
+4. Service Relation
+5. Service Instance Relation
+6. Service Endpoint Relation
+
+## Generate Metrics
+
+For each of the above-mentioned entities, metrics such as L4 and L7 protocols can be analyzed.
+
+### L4 Metrics
+
+Record the relevant metrics for every service read/write packages with other services.
+
+| Name | Unit | Description |
+|---------------------------|---------------|---------------------------------------------------------------------------|
+| Read Package CPM | Count | Total Read Package from other Service counts per minutes. |
+| Write Package CPM | Count | Total Write Package from other Service counts per minutes. |
+| Drop Package CPM | Count | Total Drop Package from other Service counts per minutes. |
+| Drop Package Reason Count | Labeled Count | Total Read Package reason(labeled) from other Service counts per minutes. |
+
+### Protocol
+
+Based on each transfer data analysis, extract the information of the 7-layer network protocol.
+
+NOTE: By default, Cilium only reports L4 metrics. If you need L7 metrics,
+they must be explicitly specified in each service's CiliumNetworkPolicy. For details please [refer to this document](https://docs.cilium.io/en/latest/security/).
+
+#### HTTP
+
+| Name | Unit | Description |
+|--------------------|-------------|---------------------------------------------------------|
+| CPM | Count | HTTP Request calls per minutes. |
+| Duration | Nanoseconds | Total HTTP Response use duration. |
+| Success CPM | Count | Total HTTP Response success(status < 500) count. |
+| Status 1/2/3/4/5xx | Count | HTTP Response status code group by 1xx/2xx/3xx/4xx/5xx. |
+
+#### DNS
+
+| Name | Unit | Description |
+|-------------|-------------|--------------------------------------------------------|
+| CPM | Count | DNS Request calls per minutes. |
+| Duration | Nanoseconds | Total DNS Response use duration. |
+| Success CPM | Count | Total DNS Response success(code == 0) count. |
+| Error Count | Label Count | DNS Response error count with error description label. |
+
+#### Kafka
+
+| Name | Unit | Description |
+|-------------|-------------|----------------------------------------------------------|
+| CPM | Count | Kafka Request calls per minutes. |
+| Duration | Nanoseconds | Total Kafka Response use duration. |
+| Success CPM | Count | Total Kafka Response success(errorCode == 0) count. |
+| Error Count | Label Count | Kafka Response error count with error description label. |
+
+## Load Balance for Cilium Fetcher with OAP cluster
+
+The Cilium Fetcher module relies on the Cluster module, when the Cilium Fetcher module starts up,
+it obtains information about all Cilium nodes and node information in the OAP cluster through Peers API on each OAP node.
+
+Additionally, it averagely distributes collected Cilium nodes to every OAP node.
+Moreover, it ensures that a single Cilium node is not monitored by multiple OAP nodes.
+
+## Customizations
+You can customize your own metrics/dashboard panel.
+The metrics definition and expression rules are found in `/config/oal/cilium.oal`, please refer the [Scope Declaration Documentation](../../concepts-and-designs/scope-definitions.md#scopes-with-cilium-prefix).
+The Cilium dashboard panel configurations are found in `/config/ui-initialized-templates/cilium_service`.
diff --git a/docs/en/setup/backend/backend-k8s-monitoring-metrics-cadvisor.md b/docs/en/setup/backend/backend-k8s-monitoring-metrics-cadvisor.md
new file mode 100644
index 000000000000..56661079e188
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s-monitoring-metrics-cadvisor.md
@@ -0,0 +1,75 @@
+# Kubernetes (K8s) monitoring from kube-state-metrics and cAdvisor
+SkyWalking leverages K8s kube-state-metrics (KSM) and cAdvisor for collecting metrics data from K8s. It leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md). This feature requires authorizing the OAP Server to access K8s's `API Server`.
+
+## Data flow
+1. K8s kube-state-metrics and cAdvisor collect metrics data from K8s.
+2. OpenTelemetry Collector fetches metrics from kube-state-metrics and cAdvisor via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server access to K8s's `API Server` gets meta info and parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Setup
+1. Setup [kube-state-metric](https://github.com/kubernetes/kube-state-metrics#kubernetes-deployment).
+2. cAdvisor is integrated into `kubelet` by default.
+3. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). For details on Prometheus Receiver in OpenTelemetry Collector for K8s, refer to [here](https://github.com/prometheus/prometheus/blob/main/documentation/examples/prometheus-kubernetes.yml).
+For a quick start, we have provided a complete example of configuration and recommended version; you can refer to [showcase](https://github.com/apache/skywalking-showcase/tree/main/deploy/platform/kubernetes/templates/feature-kubernetes-monitor).
+4. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Kubernetes Cluster Monitoring
+K8s cluster monitoring provides monitoring of the status and resources of the whole cluster and each node. K8s cluster as a `Service` in OAP, K8s node as an `Instance` in OAP, and land on the `Layer: K8S`.
+
+### Kubernetes Cluster Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|--------------------------|------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------------------|
+| Node Total | | k8s_cluster_node_total | The number of nodes | K8s kube-state-metrics |
+| Namespace Total | | k8s_cluster_namespace_total | The number of namespaces | K8s kube-state-metrics |
+| Deployment Total | | k8s_cluster_deployment_total | The number of deployments | K8s kube-state-metrics |
+| StatefulSet Total | | k8s_cluster_statefulset_total | The number of statefulsets | K8s kube-state-metrics |
+| DaemonSet Total | | k8s_cluster_daemonset_total | The number of daemonsets | K8s kube-state-metrics |
+| Service Total | | k8s_cluster_service_total | The number of services | K8s kube-state-metrics |
+| Pod Total | | k8s_cluster_pod_total | The number of pods | K8s kube-state-metrics |
+| Container Total | | k8s_cluster_container_total | The number of containers | K8s kube-state-metrics |
+| CPU Resources | m | k8s_cluster_cpu_cores
k8s_cluster_cpu_cores_requests
k8s_cluster_cpu_cores_limits
k8s_cluster_cpu_cores_allocatable | The capacity and the Requests / Limits / Allocatable of the CPU | K8s kube-state-metrics |
+| Memory Resources | Gi | k8s_cluster_memory_total
k8s_cluster_memory_requests
k8s_cluster_memory_limits
k8s_cluster_memory_allocatable | The capacity and the Requests / Limits / Allocatable of the memory | K8s kube-state-metrics |
+| Storage Resources | Gi | k8s_cluster_storage_total
k8s_cluster_storage_allocatable | The capacity and allocatable of the storage | K8s kube-state-metrics |
+| Node Status | | k8s_cluster_node_status | The current status of the nodes | K8s kube-state-metrics |
+| Deployment Status | | k8s_cluster_deployment_status | The current status of the deployment | K8s kube-state-metrics |
+| Deployment Spec Replicas | | k8s_cluster_deployment_spec_replicas | The number of desired pods for a deployment | K8s kube-state-metrics |
+| Service Status | | k8s_cluster_service_pod_status | The services current status, depending on the related pods' status | K8s kube-state-metrics |
+| Pod Status Not Running | | k8s_cluster_pod_status_not_running | The pods which are not running in the current phase | K8s kube-state-metrics |
+| Pod Status Waiting | | k8s_cluster_pod_status_waiting | The pods and containers which are currently in the waiting status, with reasons shown | K8s kube-state-metrics |
+| Pod Status Terminated | | k8s_cluster_container_status_terminated | The pods and containers which are currently in the terminated status, with reasons shown | K8s kube-state-metrics |
+
+### Kubernetes Cluster Node Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|-----|-----|
+| Pod Total | | k8s_node_pod_total | The number of pods in this node | K8s kube-state-metrics |
+| Node Status | | k8s_node_node_status | The current status of this node | K8s kube-state-metrics |
+| CPU Resources | m | k8s_node_cpu_cores
k8s_node_cpu_cores_allocatable
k8s_node_cpu_cores_requests
k8s_node_cpu_cores_limits | The capacity and the requests / Limits / Allocatable of the CPU | K8s kube-state-metrics |
+| Memory Resources | Gi | k8s_node_memory_total
k8s_node_memory_allocatable
k8s_node_memory_requests
k8s_node_memory_limits | The capacity and the requests / Limits / Allocatable of the memory | K8s kube-state-metrics |
+| Storage Resources | Gi | k8s_node_storage_total
k8s_node_storage_allocatable | The capacity and allocatable of the storage | K8s kube-state-metrics |
+| CPU Usage | m | k8s_node_cpu_usage | The total usage of the CPU core, if there are 2 cores the maximum usage is 2000m | cAdvisor |
+| Memory Usage | Gi | k8s_node_memory_usage | The totaly memory usage | cAdvisor |
+| Network I/O| KB/s | k8s_node_network_receive
k8s_node_network_transmit | The network receive and transmit | cAdvisor |
+
+## Kubernetes Service Monitoring
+K8s Service Monitoring provides observabilities into service status and resources from Kubernetes.
+K8s Service as a `Service` in OAP and land on the `Layer: K8S_SERVICE`.
+
+### Kubernetes Service Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|-----|-----|-----|-----|
+| Service Pod Total | | k8s_service_pod_total | The number of pods | K8s kube-state-metrics |
+| Service Pod Status | | k8s_service_pod_status | The current status of pods | K8s kube-state-metrics |
+| Service CPU Resources | m | k8s_service_cpu_cores_requests
k8s_service_cpu_cores_limits | The CPU resources requests / Limits of this service | K8s kube-state-metrics |
+| Service Memory Resources | MB | k8s_service_memory_requests
k8s_service_memory_limits | The memory resources requests / Limits of this service | K8s kube-state-metrics |
+| Pod CPU Usage | m | k8s_service_pod_cpu_usage | The CPU resources total usage of pods | cAdvisor |
+| Pod Memory Usage | MB | k8s_service_pod_memory_usage | The memory resources total usage of pods | cAdvisor |
+| Pod Waiting | | k8s_service_pod_status_waiting | The pods and containers which are currently in the waiting status, with reasons shown | K8s kube-state-metrics |
+| Pod Terminated | | k8s_service_pod_status_terminated | The pods and containers which are currently in the terminated status, with reasons shown | K8s kube-state-metrics |
+| Pod Restarts | | k8s_service_pod_status_restarts_total | The number of per container restarts related to the pods | K8s kube-state-metrics |
+
+## Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/k8s/k8s-cluster.yaml，/config/otel-rules/k8s/k8s-node.yaml, /config/otel-rules/k8s/k8s-service.yaml`.
+The K8s Cluster dashboard panel configurations are found in `/config/ui-initialized-templates/k8s`.
+The K8s Service dashboard panel configurations are found in `/config/ui-initialized-templates/k8s_service`.
diff --git a/docs/en/setup/backend/backend-k8s-monitoring-rover.md b/docs/en/setup/backend/backend-k8s-monitoring-rover.md
new file mode 100644
index 000000000000..28614f201e09
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s-monitoring-rover.md
@@ -0,0 +1,102 @@
+# Kubernetes (K8s) monitoring from Rover
+
+SkyWalking uses the SkyWalking Rover system to collect access logs from Kubernetes clusters and hands them over to the [OAL system](./../../concepts-and-designs/oal.md) for metrics and entity analysis.
+
+## Data flow
+1. SkyWalking Rover monitoring access log data from K8s and send to the OAP.
+2. The SkyWalking OAP Server receive access log from Rover through gRPC, analysis the generate entity, and using [OAL](../../concepts-and-designs/oal.md) to generating metrics.
+
+## Setup
+1. Setup [Rover in the Kubernetes](https://skywalking.apache.org/docs/skywalking-rover/next/en/setup/deployment/kubernetes/readme/) and enable [access log service](https://skywalking.apache.org/docs/skywalking-rover/next/en/setup/configuration/traffic/).
+2. Setup eBPF receiver module by the following configuration.
+```yaml
+receiver-ebpf:
+ selector: ${SW_RECEIVER_EBPF:default}
+ default:
+```
+
+## Generated Entities
+
+SkyWalking receive the access logs from Rover, analyzes the kubernetes connection information to parse out the following corresponding entities:
+1. Service
+2. Service Instance
+3. Service Endpoint
+4. Service Relation
+5. Service Instance Relation
+6. Service Endpoint Relation
+
+## Generate Metrics
+
+For each of the above-mentioned entities, metrics such as connection, transmission, and protocol can be analyzed.
+
+### Connection Metrics
+
+Record the relevant metrics for every service establishing/closing connections with other services.
+
+| Name | Unit | Description |
+|---------------------|-------------|--------------------------------------------------------------|
+| Connect CPM | Count | Total Connect to other Service counts per minutes. |
+| Connect Duration | Nanoseconds | Total Connect to other Service use duration. |
+| Connect Success CPM | Count | Success to connect to other Service counts per minutes. |
+| Accept CPM | Count | Accept new connection from other Service counts per minutes. |
+| Accept Duration | Nanoseconds | Total accept new connection from other Service use duration. |
+| Close CPM | Count | Close one connection counts per minutes. |
+| Close Duration | Nanoseconds | Total Close connections use duration. |
+
+### Transfer Metrics
+
+Record the basic information and L2-L4 layer details for each syscall made during network requests by every service to other services.
+
+#### Read Data from Connection
+
+| Name | Unit | Description |
+|----------------------------------|-------------|----------------------------------------------------------------|
+| Read CPM | Count | Read from connection counts per minutes. |
+| Read Duration | Nanoseconds | Total read data use duration. |
+| Read Package CPM | Count | Total read TCP Package count per minutes. |
+| Read Package Size | Bytes | Total read TCP package size per minutes. |
+| Read Layer 4 Duration | Nanoseconds | Total read data on the Layer 4 use duration. |
+| Read Layer 3 Duration | Nanoseconds | Total read data on the Layer 3 use duration. |
+| Read Layer 3 Recv Duration | Nanoseconds | Total read data on the Layer 3 receive use duration. |
+| Read Layer 3 Local Duration | Nanoseconds | Total read data on the Layer 3 local use duration. |
+| Read Package To Queue Duration | Nanoseconds | Total duration between TCP package received and send to Queue. |
+| Read Package From Queue Duration | Nanoseconds | Total duration between send to Queue and receive from Queue. |
+| Read Net Filter CPM | Count | Total Net Filtered count when read data. |
+| Read Net Filter Duration | Nanoseconds | Total Net Filtered use duration. |
+
+#### Write Data to Connection
+
+| Name | Unit | Description |
+|----------------------------------|-------------|----------------------------------------------------------------------------------|
+| Write CPM | Count | Write to connection counts per minutes. |
+| Write Duration | Nanoseconds | Total write data to connection use duration. |
+| Write Package CPM | Count | Total write TCP Package count per minutes. |
+| Write Package Size | Bytes | Total write TCP Package size per minutes. |
+| Write L4 Duration | Nanoseconds | Total write data to connection Layer 4 use duration. |
+| Write L3 Duration | Nanoseconds | Total write data to connection Layer 3 use duration. |
+| Write L3 Local Duration | Nanoseconds | Total write data to the connection Layer 3 Local use duration. |
+| Write L3 Output Duration | Nanoseconds | Total write data to the connection Layer 3 Output use duration. |
+| Write L2 Duration | Nanoseconds | Total write data to connection Layer 2 use duration. |
+| Write L2 Ready Send Duration | Nanoseconds | Total write data to the connection Layer 2 ready send data queue use duration. |
+| Write L2 Send NetDevice Duration | Nanoseconds | Total write data to the connection Layer 2 send data to net device use duration. |
+
+### Protocol
+
+Based on each transfer data analysis, extract the information of the 7-layer network protocol.
+
+#### HTTP/1.x or HTTP/2.x
+
+| Name | Init | Description |
+|----------------------|--------------|--------------------------------------------------|
+| Call CPM | Count | HTTP Request calls per minutes. |
+| Duration | Milliseconds | Total HTTP Response use duration. |
+| Success CPM | Count | Total HTTP Response success(status < 500) count. |
+| Request Header Size | Bytes | Total Request Header size. |
+| Request Body Size | Bytes | Total Request Body size. |
+| Response Header Size | Bytes | Total Response Header size. |
+| Response Body Size | Bytes | Total Response Body size. |
+
+## Customizations
+You can customize your own metrics/dashboard panel.
+The metrics definition and expression rules are found in `/config/oal/ebpf.oal`, please refer the [Scope Declaration Documentation](../../concepts-and-designs/scope-definitions.md#scopes-with-k8s-prefix).
+The K8s dashboard panel configurations are found in `/config/ui-initialized-templates/k8s_service`.
diff --git a/docs/en/setup/backend/backend-k8s-monitoring.md b/docs/en/setup/backend/backend-k8s-monitoring.md
new file mode 100644
index 000000000000..3c94a445a4f1
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s-monitoring.md
@@ -0,0 +1,21 @@
+# Kubernetes (K8s) monitoring
+
+Kubernetes is an open-source container-orchestration system for automating computer application deployment, scaling, and
+management. It was originally designed by Google and is now maintained by the Cloud Native Computing Foundation. It aims
+to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of
+hosts". It works with a range of container tools, including Docker.
+
+Nowadays, Kubernetes is the fundamental infrastructure for cloud native applications. SkyWalking provides the following
+ways to monitor deployments on Kubernetes.
+
+1. Use kube-state-metrics (KSM) and cAdvisor to collect metrics of Kubernetes resources, such as CPU, service, pod, and
+ node. Read [kube-state-metrics and cAdvisor setup guide](./backend-k8s-monitoring-metrics-cadvisor.md) for more details.
+2. Rover is a SkyWalking native eBPF agent to collect network Access Logs to support topology-aware and metrics
+ analysis. Meanwhile, due to the power of eBPF, it could profile running services written by C++, Rust, Golang, etc.
+ Read [Rover setup guide](./backend-k8s-monitoring-rover.md) for more details.
+3. If Cilium is installed in Kubernetes, use Cilium Fetcher to collect network traffic data of services through Cilium Hubble APIs.
+ This data can be used to create topology maps and to provide L4 and L7 layer metrics.
+ Read [Cilium Fetcher setup guide](./backend-k8s-monitoring-cilium.md) for more details.
+
+SkyWalking deeply integrates with Kubernetes to help users understand the status of their applications on Kubernetes.
+Cillium with Hubble is in our v10 plan.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-k8s-network-monitoring.md b/docs/en/setup/backend/backend-k8s-network-monitoring.md
new file mode 100644
index 000000000000..3be37555cf47
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s-network-monitoring.md
@@ -0,0 +1,62 @@
+# Kubernetes Network monitoring
+SkyWalking leverages [SkyWalking Rover](https://github.com/apache/skywalking-rover) [network profiling feature](https://skywalking.apache.org/docs/skywalking-rover/next/en/setup/configuration/profiling/#network)
+to measure network performance for particular pods on-demand, including metrics of L4(TCP) and L7(HTTP) traffic
+and raw data of HTTP requests and responses.
+Underlying, SkyWalking Rover converts data from socket data to metrics using eBPF technology.
+
+## Data flow
+1. SkyWalking OAP server observes which specific k8s pod needs to monitor the network.
+2. SkyWalking Rover receives tasks from SkyWalking OAP server and executes them, and converts the network data into metrics send to the backend service.
+3. The SkyWalking OAP Server accesses K8s's `API Server` to fetch meta info and parses the expression with [MAL](../../concepts-and-designs/mal.md) to aggregate.
+
+## Setup
+1. Setup [SkyWalking Rover](https://skywalking.apache.org/docs/skywalking-rover/next/en/setup/overview/).
+2. Enable the network profiling MAL file in the OAP server.
+```yaml
+agent-analyzer:
+ selector: ${SW_AGENT_ANALYZER:default}
+ default:
+ meterAnalyzerActiveFiles: ${SW_METER_ANALYZER_ACTIVE_FILES:network-profiling}
+```
+
+## Sampling config
+
+**Notice the precondition, the HTTP request must have the trace header in SkyWalking(`sw8` header) or Zipkin(`b3` header(s)) format.**
+
+The sampling configurations define the sampling boundaries for the HTTP traffic. When a HTTP calling is sampled,
+the SkyWalking Rover could collect the HTTP request/response raw data and upload it to the span attached event.
+
+The sampling config contains multiple rules, and each of rules has the following configurations:
+1. `URI Regex`: The match pattern for HTTP requests is HTTP URI-oriented. Match all requests if the URI regex is not set.
+2. `Minimal Request Duration (ms)`: Sample the HTTP requests with slower latency than this threshold.
+3. `Sample HTTP requests and responses with tracing when the response code is between 400 and 499`: This is OFF by default.
+4. `Sample HTTP requests and responses with tracing when the response code is between 500 and 599`: This is ON by default.
+
+## Supported metrics
+
+After SkyWalking OAP server receives the metrics from the SkyWalking Rover, it supports to analysis the following data:
+1. **Topology**: Based on the process and peer address, the following topology data is supported:
+ 1. **Relation**: Analyze the relationship between local processes, or local process with external pods or services.
+ 2. **SSL**: The socket read or write package with SSL.
+ 3. **Protocol**: The protocols for write or read data.
+2. TCP socket read and write metrics, including following types:
+ 1. **Call Per Minute**: The count of the socket read or write.
+ 2. **Bytes**: The package size of the socket data.
+ 3. **Execute Time**: The executed time of the socket read or write.
+ 4. **Connect**: The socket connect/accept with peer address count and execute time.
+ 5. **Close**: The socket close the socket count and execute time.
+ 6. **RTT**: The RTT(Round Trip Time) of socket communicate with peer address.
+3. Local process communicate with peer address exception data, including following types:
+ 1. **Retransmit**: The count of TCP package is retransmitted.
+ 2. **Drop**: The count of TCP package is dropped.
+4. HTTP/1.x request/response related metrics, including following types:
+ 1. **Request CPM**: The calls per minute of requests.
+ 2. **Response CPM**: The calls per minute of responses with status code.
+ 3. **Request Package Size**: The size(KB) of the request package.
+ 4. **Response Package Size**: The size(KB) of the response package.
+ 5. **Client Side Response Duration**: The duration(ms) of the client receive the response.
+ 6. **Server Side Response Duration**: The duration(ms) of the server send the response.
+5. HTTP sampled request with traces, including following types:
+ 1. **Slow traces**: The traces which have slow duration.
+ 2. **Traces from HTTP Code in [400, 500) (ms)**: The traces which response status code in [400, 500).
+ 3. **Traces from HTTP Code in [500, 600) (ms)**: The traces which response status code in [500, 600).
diff --git a/docs/en/setup/backend/backend-k8s.md b/docs/en/setup/backend/backend-k8s.md
new file mode 100644
index 000000000000..a030f5add307
--- /dev/null
+++ b/docs/en/setup/backend/backend-k8s.md
@@ -0,0 +1,9 @@
+# Deploy SkyWalking backend and UI in Kubernetes
+
+Before you read Kubernetes deployment guidance, please make sure you have read `Quick Start` and `Advanced Setup` documents.
+Most SkyWalking OAP settings are controlled through System environment variables when applying helm deployment.
+
+Follow instructions in the [deploying SkyWalking backend to Kubernetes cluster](https://github.com/apache/skywalking-helm)
+ to deploy OAP and UI to a Kubernetes cluster.
+
+Please refer to the Readme file.
diff --git a/docs/en/setup/backend/backend-kafka-monitoring.md b/docs/en/setup/backend/backend-kafka-monitoring.md
new file mode 100644
index 000000000000..0153c3da0f1d
--- /dev/null
+++ b/docs/en/setup/backend/backend-kafka-monitoring.md
@@ -0,0 +1,84 @@
+# Kafka monitoring
+
+SkyWalking leverages Prometheus JMX Exporter to collect metrics data from the Kafka and leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+Kafka entity as a `Service` in OAP and on the `Layer: KAFKA`.
+
+## Data flow
+
+1. The `prometheus_JMX_Exporter` collect metrics data from Kafka. Note: Running the exporter as a Java agent.
+2. OpenTelemetry Collector fetches metrics from `prometheus_JMX_Exporter` via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Setup [prometheus_JMX_Exporter](https://github.com/prometheus/jmx_exporter). This is an example for JMX Exporter configuration [kafka-2_0_0.yml](https://raw.githubusercontent.com/prometheus/jmx_exporter/91622ad478015364444e5d63475d1673c09e6268/examples/kafka-2_0_0.yml).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). The example
+ for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/kafka/kafka-monitoring/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Kafka Monitoring
+
+Kafka monitoring provides multidimensional metrics monitoring of Kafka cluster as `Layer: KAFKA` `Service` in
+the OAP. In each cluster, the kafka brokers are represented as `Instance`.
+
+### Kafka Cluster Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|-------------------------------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Under-Replicated Partitions | meter_kafka_under_replicated_partitions | Number of under-replicated partitions in the broker. A higher number is a sign of potential issues. | Prometheus JMX Exporter |
+| Offline Partitions Count | meter_kafka_offline_partitions_count | Number of partitions that are offline. Non-zero values indicate a problem. | Prometheus JMX Exporter |
+| Partition Count | meter_kafka_partition_count | Total number of partitions on the broker. | Prometheus JMX Exporter |
+| Leader Count | meter_kafka_leader_count | Number of leader partitions on this broker. | Prometheus JMX Exporter |
+| Active Controller Count | meter_kafka_active_controller_count | The number of active controllers in the cluster. Typically should be 1. | Prometheus JMX Exporter |
+| Leader Election Rate | meter_kafka_leader_election_rate | The rate of leader elections per minute. High rate could be a sign of instability. | Prometheus JMX Exporter |
+| Unclean Leader Elections Per Second | meter_kafka_unclean_leader_elections_per_second | The rate of unclean leader elections per second. Non-zero values indicate a serious problem. | Prometheus JMX Exporter |
+| Max Lag | meter_kafka_max_lag | The maximum lag between the leader and followers in terms of messages still needed to be sent. Higher lag indicates delays. | Prometheus JMX Exporter |
+
+### Kafka Broker Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----------------------------------|-----------|-------------------------------------------------------|---------------------------------------------------------------|-------------------------------|
+| CPU Usage | % | meter_kafka_broker_cpu_time_total | CPU usage in percentage | Prometheus JMX Exporter |
+| Memory Usage | % | meter_kafka_broker_memory_usage_percentage | JVM heap memory usage in percentage | Prometheus JMX Exporter |
+| Incoming Messages | Msg/sec | meter_kafka_broker_messages_per_second | Rate of incoming messages | Prometheus JMX Exporter |
+| Bytes In | Bytes/sec | meter_kafka_broker_bytes_in_per_second | Rate of incoming bytes | Prometheus JMX Exporter |
+| Bytes Out | Bytes/sec | meter_kafka_broker_bytes_out_per_second | Rate of outgoing bytes | Prometheus JMX Exporter |
+| Replication Bytes In | Bytes/sec | meter_kafka_broker_replication_bytes_in_per_second | Rate of incoming bytes for replication | Prometheus JMX Exporter |
+| Replication Bytes Out | Bytes/sec | meter_kafka_broker_replication_bytes_out_per_second | Rate of outgoing bytes for replication | Prometheus JMX Exporter |
+| Under-Replicated Partitions | Count | meter_kafka_broker_under_replicated_partitions | Number of under-replicated partitions | Prometheus JMX Exporter |
+| Under Min ISR Partition Count | Count | meter_kafka_broker_under_min_isr_partition_count | Number of partitions below the minimum ISR (In-Sync Replicas) | Prometheus JMX Exporter |
+| Partition Count | Count | meter_kafka_broker_partition_count | Total number of partitions | Prometheus JMX Exporter |
+| Leader Count | Count | meter_kafka_broker_leader_count | Number of partitions for which this broker is the leader | Prometheus JMX Exporter |
+| ISR Shrinks | Count/sec | meter_kafka_broker_isr_shrinks_per_second | Rate of ISR (In-Sync Replicas) shrinking | Prometheus JMX Exporter |
+| ISR Expands | Count/sec | meter_kafka_broker_isr_expands_per_second | Rate of ISR (In-Sync Replicas) expanding | Prometheus JMX Exporter |
+| Max Lag | Count | meter_kafka_broker_max_lag | Maximum lag between the leader and follower for a partition | Prometheus JMX Exporter |
+| Purgatory Size | Count | meter_kafka_broker_purgatory_size | Size of purgatory for Produce and Fetch operations | Prometheus JMX Exporter |
+| Garbage Collector Count | Count/sec | meter_kafka_broker_garbage_collector_count | Rate of garbage collection cycles | Prometheus JMX Exporter |
+| Requests Per Second | Req/sec | meter_kafka_broker_requests_per_second | Rate of requests to the broker | Prometheus JMX Exporter |
+| Request Queue Time | ms | meter_kafka_broker_request_queue_time_ms | Average time a request spends in the request queue | Prometheus JMX Exporter |
+| Remote Time | ms | meter_kafka_broker_remote_time_ms | Average time taken for a remote operation | Prometheus JMX Exporter |
+| Response Queue Time | ms | meter_kafka_broker_response_queue_time_ms | Average time a response spends in the response queue | Prometheus JMX Exporter |
+| Response Send Time | ms | meter_kafka_broker_response_send_time_ms | Average time taken to send a response | Prometheus JMX Exporter |
+| Network Processor Avg Idle | % | meter_kafka_broker_network_processor_avg_idle_percent | Percentage of idle time for the network processor | Prometheus JMX Exporter |
+| Topic Messages In Total | Count | meter_kafka_broker_topic_messages_in_total | Total number of messages per topic | Prometheus JMX Exporter |
+| Topic Bytes Out Per Second | Bytes/sec | meter_kafka_broker_topic_bytesout_per_second | Rate of outgoing bytes per topic | Prometheus JMX Exporter |
+| Topic Bytes In Per Second | Bytes/sec | meter_kafka_broker_topic_bytesin_per_second | Rate of incoming bytes per topic | Prometheus JMX Exporter |
+| Topic Fetch Requests Per Second | Req/sec | meter_kafka_broker_topic_fetch_requests_per_second | Rate of fetch requests per topic | Prometheus JMX Exporter |
+| Topic Produce Requests Per Second | Req/sec | meter_kafka_broker_topic_produce_requests_per_second | Rate of produce requests per topic | Prometheus JMX Exporter |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `/config/otel-rules/kafka/kafka-cluster.yaml, /config/otel-rules/kafka/kafka-node.yaml`.
+The Kafka dashboard panel configurations are found in `/config/ui-initialized-templates/kafka`.
+
+## Reference
+For more details on monitoring Kafka and the metrics to focus on, see the following articles:
+
+- [Monitoring Kafka Streams Applications](https://docs.confluent.io/platform/current/streams/monitoring.html)
+- [Kafka Monitoring](https://kafka.apache.org/documentation/#monitoring)
+
diff --git a/docs/en/setup/backend/backend-kong-monitoring.md b/docs/en/setup/backend/backend-kong-monitoring.md
new file mode 100644
index 000000000000..a05b383a8823
--- /dev/null
+++ b/docs/en/setup/backend/backend-kong-monitoring.md
@@ -0,0 +1,77 @@
+# KONG monitoring
+
+## KONG performance from `kong prometheus plugin`
+The [kong-prometheus](https://github.com/Kong/kong/tree/master/kong/plugins/prometheus) is a lua library that can be used with Kong to collect metrics.
+It exposes metrics related to Kong and proxied upstream services in Prometheus exposition format, which can be scraped by a Prometheus Server.
+SkyWalking leverages OpenTelemetry Collector to transfer the metrics to[OpenTelemetry receiver](opentelemetry-receiver.md)
+and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. [KONG Prometheus plugin](https://docs.konghq.com/hub/kong-inc/prometheus/) collects metrics data from KONG.
+2. OpenTelemetry Collector fetches metrics from [KONG Prometheus plugin](https://docs.konghq.com/hub/kong-inc/prometheus/) via
+ Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Enable KONG [KONG Prometheus plugin](https://docs.konghq.com/hub/kong-inc/prometheus/). Note that if need to monitor per_consumer,
+ status_code_metrics, ai_metrics, latency_metrics, bandwidth_metrics or upstream_health_metrics, **need to enable them manually as needed**,
+ which can be enabled in the [konga](https://pantsel.github.io/konga/) dashboard or through the Admin API, such as the following command
+ ~~~bash
+ curl -i -X POST http://{KONG-HOST}:{KONG_ADMIN_PORT}/plugins \
+ --data name=prometheus \
+ --data config.per_consumer=true \
+ --data config.status_code_metrics=true \
+ --data config.ai_metrics=true \
+ --data config.latency_metrics=true \
+ --data config.bandwidth_metrics=true \
+ --data config.upstream_health_metrics=true
+ ~~~
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#docker).
+ For details on Prometheus Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/kong/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### KONG Monitoring
+
+[KONG prometheus plugin](https://docs.konghq.com/hub/kong-inc/prometheus/) provide multiple dimensions metrics for KONG server, upstream, route etc.
+Accordingly, SkyWalking observes the status, requests, and latency of the KONG server, which is cataloged as a `LAYER: KONG` `Service` in the OAP.
+Each Kong server is cataloged as a `LAYER: KONG` `instance`, meanwhile, the route rules would be recognized as a `LAYER: KONG` `endpoint`.
+
+
+#### Kong Request Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------|
+| Bandwidth | bytes | meter_kong_service_http_bandwidth
meter_kong_instance_http_bandwidth
meter_kong_endpoint_http_bandwidth | Total bandwidth (ingress/egress) throughput | Kong |
+| HTTP Status | count | meter_kong_service_http_status
meter_kong_instance_http_status
meter_kong_endpoint_http_status | HTTP status codes per consumer/service/route in Kong | Kong |
+| HTTP Request | count | meter_kong_service_http_requests
meter_kong_instance_http_requests | Total number of requests | Kong |
+
+#### Kong Database Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|-------------------------------------------------------------------------------------|-------------------------------------------|-------------|
+| DB | count | meter_kong_service_datastore_reachable
meter_kong_instance_datastore_reachable | Datastore reachable from Kong | Kong |
+| DB | bytes | meter_kong_instance_shared_dict_bytes | Allocated slabs in bytes in a shared_dict | Kong |
+| DB | bytes | meter_kong_instance_shared_dict_total_bytes | Total capacity in bytes of a shared_dict | Kong |
+| DB | bytes | meter_kong_instance_memory_workers_lua_vms_bytes | Allocated bytes in worker Lua VM | Kong |
+
+#### Kong Latencies Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------|
+| Latency | ms | meter_kong_service_kong_latency
meter_kong_instance_kong_latency
meter_kong_endpoint_kong_latency | Latency added by Kong and enabled plugins for each service/route in Kong | Kong |
+| Latency | ms | meter_kong_service_request_latency
meter_kong_instance_request_latency
meter_kong_endpoint_request_latency | Total latency incurred during requests for each service/route in Kong | Kong |
+| Latency | ms | meter_kong_service_upstream_latency
meter_kong_instance_upstream_latency
meter_kong_endpoint_upstream_latency | Latency added by upstream response for each service/route in Kong | Kong |
+
+
+#### Kong Nginx Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|---------------------------------------------------------------------------------------------|---------------------------------------|-------------|
+| Nginx | count | meter_kong_service_nginx_metric_errors_total | Number of nginx-lua-prometheus errors | Kong |
+| Nginx | count | meter_kong_service_nginx_connections_total
meter_kong_instance_nginx_connections_total | Number of connections by subsystem | Kong |
+| Nginx | count | meter_kong_service_nginx_timers
meter_kong_instance_nginx_timers | Number of Nginx timers | Kong |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/kong`.
+The KONG dashboard panel configurations are found in `/config/ui-initialized-templates/kong`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-load-balancer.md b/docs/en/setup/backend/backend-load-balancer.md
new file mode 100644
index 000000000000..f496a7d92b8e
--- /dev/null
+++ b/docs/en/setup/backend/backend-load-balancer.md
@@ -0,0 +1,123 @@
+# Backend Load Balancer
+
+When setting the Agent or Envoy to connect to the OAP server directly by default,
+the OAP server cluster would face the problem of load imbalance. This issue
+becomes severe in high-traffic load scenarios. In this doc, we will introduce
+two means to solve the problem.
+
+## SkyWalking Satellite Project
+
+[SkyWalking Satellite](https://github.com/apache/skywalking-satellite) is recommended to be
+used as a native gateway proxy to provide load balancing capabilities for data content before the data from Agent/ Envoy
+reaches the OAP. The major difference between Satellite and other general wide used proxy(s), like Envoy, is that it would route the data accordingly to contents rather than connection, as gRPC streaming is used widely in SkyWalking.
+
+Follow instructions in the [Setup SkyWalking Satellite](https://skywalking.apache.org/docs/#SkyWalkingSatellite)
+to deploy Satellite and connect your application to the Satellite.
+
+[Scaling with Apache SkyWalking](https://skywalking.apache.org/blog/2022-01-24-scaling-with-apache-skywalking/) blog
+introduces the theory and technology details on how to set up a load balancer for the OAP cluster.
+
+## Envoy Filter to Limit Connections Per OAP Instance
+
+If you don't want to deploy skywalking-satellite, you can enable Istio sidecar
+injection for SkyWalking OAP Pods,
+
+```shell
+kubectl label namespace $SKYWALKING_NAMESPACE istio-injection=enabled
+kubectl -n $SKYWALKING_NAMESPACE rollout restart -l app=skywalking,component=oap
+```
+
+and apply an EnvoyFilter to limit the connections per OAP instance, so that
+each of the OAP instance can have similar amount of gRPC connections.
+
+Before that, you need to calculate the number of connections for each OAP
+instance as follows:
+
+```shell
+NUMBER_OF_SERVICE_PODS=
+
+# Each service Pod has 2 connections to OAP
+NUMBER_OF_TOTAL_CONNECTIONS=$((NUMBER_OF_SERVICE_PODS * 2))
+
+# Divide the total connections by the replicas of OAP
+NUMBER_OF_CONNECTIONS_PER_OAP=$((NUMBER_OF_TOTAL_CONNECTIONS / $NUMBER_OF_OAP_REPLICAS))
+```
+
+And you can apply an EnvoyFilter to limit connections:
+
+```shell
+kubectl -n $SKYWALKING_NAMESPACE apply -f - <
+# filter the metrics, only those metrics that satisfy this condition will be passed into the `metricsRules` below.
+filter: # example: '{ tags -> tags.job_name == "vm-monitoring" }'
+# expPrefix is executed before the metrics executes other functions.
+expPrefix:
+# expSuffix is appended to all expression in this file.
+expSuffix:
+# insert metricPrefix into metric name: _
+metricPrefix:
+# Metrics rule allow you to recompute queries.
+metricsRules:
+ # The name of rule, which combinates with a prefix '_' as the index/table name in storage.
+ # The name with prefix can also be quoted in UI (Dashboard/Template/Item/Metrics)
+ name:
+ # MAL expression. Raw name of custom metrics collected can be used here
+ exp:
+```
+
+For more information on MAL, please refer to [mal.md](../../concepts-and-designs/mal.md)
+
+#### `rate`, `irate`, and `increase`
+
+Although we support the `rate`, `irate`, `increase` functions in the backend, we still recommend users to consider using
+client-side APIs to run these functions. The reasons are as follows:
+
+1. The OAP has to set up caches to calculate the values.
+1. Once the agent reconnects to another OAP instance, the time windows of rate calculation break. This leads to
+ inaccurate results.
diff --git a/docs/en/setup/backend/backend-mongodb-monitoring.md b/docs/en/setup/backend/backend-mongodb-monitoring.md
new file mode 100644
index 000000000000..9179125bee47
--- /dev/null
+++ b/docs/en/setup/backend/backend-mongodb-monitoring.md
@@ -0,0 +1,79 @@
+# MongoDB monitoring
+
+SkyWalking leverages mongodb-exporter for collecting metrics data from MongoDB. It leverages OpenTelemetry
+Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. The `mongodb-exporter` collects metrics data from MongoDB. The exporter works side by side with the MongoDB node.
+2. OpenTelemetry Collector fetches metrics from mongodb-exporter via Prometheus Receiver and pushes metrics to
+ SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Setup [mongodb-exporter](https://github.com/percona/mongodb_exporter).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#docker). The example for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/mongodb/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## MongoDB Monitoring
+
+MongoDB monitoring provides multidimensional metrics monitoring of MongoDB clusters as `Layer: MONGODB` `Service` in the OAP. In each cluster, the nodes are represented as `Instance`.
+
+### MongoDB Cluster Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|---------------------------|------|-------------------------------------------|---------------------------------------------------------------------|------------------|
+| Uptime (day) | day | meter_mongodb_cluster_uptime | Maximum uptime of nodes in the cluster | mongodb-exporter |
+| Data Size (GB) | GB | meter_mongodb_cluster_data_size | Total data size of the cluster | mongodb-exporter |
+| Collection Count | | meter_mongodb_cluster_collection_count | Number of collection of the cluster | mongodb-exporter |
+| Object Count | | meter_mongodb_cluster_object_count | Number of object of the cluster | mongodb-exporter |
+| Document Total QPS | | meter_mongodb_cluster_document_avg_qps | Total document operations rate of nodes | mongodb-exporter |
+| Operation Total QPS | | meter_mongodb_cluster_operation_avg_qps | Total operations rate of nodes | mongodb-exporter |
+| Total Connections | | meter_mongodb_cluster_connections | Cluster total connections of nodes | mongodb-exporter |
+| Cursor Total | | meter_mongodb_cluster_cursor_avg | Total Opened cursor of nodes | mongodb-exporter |
+| Replication Lag (ms) | ms | meter_mongodb_cluster_repl_lag | Repl set member avg replication lag, this metric works in repl mode | mongodb-exporter |
+| DB Total Data Size (GB) | GB | meter_mongodb_cluster_db_data_size | Total data size of every database | mongodb-exporter |
+| DB Total Index Size (GB) | GB | meter_mongodb_cluster_db_index_size | Total index size per of every database | mongodb-exporter |
+| DB Total Collection Count | | meter_mongodb_cluster_db_collection_count | Total collection count of every database | mongodb-exporter |
+| DB Total Index Count | | meter_mongodb_cluster_db_index_count | Total index count of every database | mongodb-exporter |
+
+### MongoDB Node Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------------------|------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------|
+| Uptime (day) | day | meter_mongodb_node_uptime | Uptime of the node | mongodb-exporter |
+| QPS | | meter_mongodb_node_qps | Operations per second of the node | mongodb-exporter |
+| Latency | µs | meter_mongodb_node_op_rate
meter_mongodb_node_latency_rate | Latency of operations | mongodb-exporter |
+| Memory Usage | % | meter_mongodb_node_memory_usage | Memory usage percent of RAM | mongodb-exporter |
+| Version | | meter_mongodb_node_version | MongoDB edition and version | mongodb-exporter |
+| ReplSet State | | meter_mongodb_node_rs_state | Repl set state of the node, this metric works in repl mode | mongodb-exporter |
+| CPU Usage (%) | % | meter_mongodb_node_cpu_total_percentage | Cpu usage percent of the node | mongodb-exporter |
+| Network (KB/s) | KB/s | meter_mongodb_node_network_bytes_in
meter_mongodb_node_network_bytes_out | Inbound and outbound network bytes of node | mongodb-exporter |
+| Memory Free (GB) | GB | meter_mongodb_node_memory_free_kb
meter_mongodb_node_swap_memory_free_kb | Free memory of RAM and swap | mongodb-exporter |
+| Disk (GB) | GB | meter_mongodb_node_fs_used_size
meter_mongodb_node_fs_total_size | Used and total size of disk | mongodb-exporter |
+| Connections | | meter_mongodb_node_connections | Connection nums of node | mongodb-exporter |
+| Active Client | | meter_mongodb_node_active_total_num
meter_mongodb_node_active_reader_num
meter_mongodb_node_active_writer_num | Count of active reader and writer | mongodb-exporter |
+| Transactions | | meter_mongodb_node_transactions_active
meter_mongodb_node_transactions_inactive | Count of transactions running on the node | mongodb-exporter |
+| Document QPS | | meter_mongodb_node_document_qps | Document operations per second | mongodb-exporter |
+| Operation QPS | | meter_mongodb_node_operation_qps | Operations per second | mongodb-exporter |
+| Repl Operation QPS | | meter_mongodb_node_repl_operation_qps | Repl operations per second | mongodb-exporter |
+| Operation Latency (µs) | µs | meter_mongodb_node_op_rate
meter_mongodb_node_latency_rate | Latencies for different operation type | mongodb-exporter |
+| Cursor | | meter_mongodb_node_cursor | Opened cursor of the node | mongodb-exporter |
+| Server Status Memory (MB) | MB | meter_mongodb_node_mem_virtual
meter_mongodb_node_mem_resident | Virtual and resident memory of the node | mongodb-exporter |
+| Asserts | | meter_mongodb_node_asserts | The rate of raised assertions | mongodb-exporter |
+| Repl Buffer Count | | meter_mongodb_node_repl_buffer_count | The current number of operations in the oplog buffer | mongodb-exporter |
+| Repl Buffer Size (MB) | MB | meter_mongodb_node_repl_buffer_size
meter_mongodb_node_repl_buffer_size_max | The maximum size of the oplog buffer | mongodb-exporter |
+| Queued Operation | | meter_mongodb_node_queued_operation | The number of operations queued because of a lock | mongodb-exporter |
+| getLastError Write Num | | meter_mongodb_node_write_wait_num
meter_mongodb_node_write_wait_timeout_num | The number of write concern operation | mongodb-exporter |
+| getLastError Write Time (ms) | ms | meter_mongodb_node_write_wait_time | The wait time of write concern operation | mongodb-exporter |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `/config/otel-rules/mongodb/mongodb-cluster.yaml, /config/otel-rules/mongodb/mongodb-node.yaml`.
+The MongoDB dashboard panel configurations are found in `/config/ui-initialized-templates/mongodb`.
diff --git a/docs/en/setup/backend/backend-mysql-monitoring.md b/docs/en/setup/backend/backend-mysql-monitoring.md
new file mode 100644
index 000000000000..4062920090d1
--- /dev/null
+++ b/docs/en/setup/backend/backend-mysql-monitoring.md
@@ -0,0 +1,63 @@
+# MySQL/MariaDB monitoring
+## MySQL/MariaDB server performance from `prometheus/mysqld_exporter`
+SkyWalking leverages prometheus/mysqld_exporter for collecting metrics data. It leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. mysqld_exporter collect metrics data from MySQL/MariaDB.
+2. OpenTelemetry Collector fetches metrics from mysqld_exporter via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Set up [mysqld_exporter](https://github.com/prometheus/mysqld_exporter#using-docker).
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on Prometheus Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/mysql/prometheus-mysql-exporter/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### MySQL/MariaDB Monitoring
+MySQL/MariaDB monitoring provides monitoring of the status and resources of the MySQL/MariaDB server. MySQL/MariaDB cluster is cataloged as a `Layer: MYSQL` `Service` in OAP.
+Each MySQL/MariaDB server is cataloged as an `Instance` in OAP.
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|
+| MySQL Uptime | day | meter_mysql_uptime | The MySQL startup time | mysqld_exporter|
+| Max Connections | | meter_mysql_max_connections | The max number of connections. | mysqld_exporter|
+| Innodb Buffer Pool Size | MB | meter_mysql_innodb_buffer_pool_size | The buffer pool size in Innodb engine | mysqld_exporter|
+| Thread Cache Size | | meter_mysql_thread_cache_size | The size of thread cache | mysqld_exporter|
+| Current QPS| | meter_mysql_qps | Queries Per Second | mysqld_exporter|
+| Current TPS | | meter_mysql_tps | Transactions Per Second | mysqld_exporter|
+| Commands Rate | | meter_mysql_commands_insert_rate
meter_mysql_commands_select_rate
meter_mysql_commands_delete_rate
meter_mysql_commands_update_rate | The rate of total number of insert/select/delete/update executed by the current server | mysqld_exporter|
+| Threads | | meter_mysql_threads_connected
meter_mysql_threads_created
meter_mysql_threads_cached
meter_mysql_threads_running | The number of currently open connections(threads_connected)
The number of threads created(threads_created)
The number of threads in the thread cache(threads_cached)
The number of threads that are not sleeping(threads_running) | mysqld_exporter|
+| Connects | | meter_mysql_max_connections
meter_mysql_status_thread_connected
meter_mysql_connects_aborted | The number of available connections(connects_available)
The number of MySQL instance connection rejections(connects_aborted)| mysqld_exporter|
+| Connection Errors | | meter_mysql_connection_errors_internal meter_mysql_connection_errors_max_connections | Errors due to exceeding the max_connections(connection_errors_max_connections) Error caused by internal system(connection_errors_internal) | mysqld_exporter|
+| Slow Queries Rate | | meter_mysql_slow_queries_rate | The rate of slow queries | mysqld_exporter|
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/mysql`.
+The MySQL dashboard panel configurations are found in `/config/ui-initialized-templates/mysql`.
+
+## Collect sampled slow SQLs
+SkyWalking leverages [fluentbit](https://fluentbit.io/) or other log agents for collecting slow SQL statements from MySQL/MariaDB.
+
+### Data flow
+1. fluentbit agent collects slow sql logs from MySQL/MariaDB.
+2. fluentbit agent sends data to SkyWalking OAP Server using native meter APIs via HTTP.
+3. The SkyWalking OAP Server parses the expression with [LAL](../../concepts-and-designs/lal.md) to parse/extract and store the results.
+
+### Set up
+1. Set up [fluentbit](https://docs.fluentbit.io/manual/installation/docker).
+2. Config fluentbit from [here](../../../../test/e2e-v2/cases/mysql/mysql-slowsql/fluent-bit.conf) for MySQL or [here](../../../../test/e2e-v2/cases/mariadb/mariadb-slowsql/fluent-bit.conf) for MariaDB.
+3. Enable slow log from [here](../../../../test/e2e-v2/cases/mysql/mysql-slowsql/my.cnf) for MySQL or [here](../../../../test/e2e-v2/cases/mariadb/mariadb-slowsql/my.cnf) for MariaDB.
+
+### Slow SQL Monitoring
+Slow SQL monitoring provides monitoring of the slow SQL statements of the MySQL/MariaDB server. MySQL/MariaDB server is cataloged as a `Layer: MYSQL` `Service` in OAP.
+
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|-----|-----|
+|Slow Statements | ms | top_n_database_statement | The latency and statement of MySQL/MariaDB slow SQLs | fluentbit|
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The slowsql expression rules are found in `/config/lal/mysql-slowsql.yaml`
+The MySQL/MariaDB dashboard panel configurations are found in `/config/ui-initialized-templates/mysql`.
diff --git a/docs/en/setup/backend/backend-nginx-monitoring.md b/docs/en/setup/backend/backend-nginx-monitoring.md
new file mode 100644
index 000000000000..7efd0750666d
--- /dev/null
+++ b/docs/en/setup/backend/backend-nginx-monitoring.md
@@ -0,0 +1,141 @@
+# Nginx monitoring
+## Nginx performance from nginx-lua-prometheus
+The [nginx-lua-prometheus](https://github.com/knyar/nginx-lua-prometheus) is a lua library that can be used with Nginx to collect metrics
+and expose them on a separate web page.
+To use this library, you will need Nginx with [lua-nginx-module](https://github.com/openresty/lua-nginx-module) or directly [OpenResty](https://openresty.org/).
+
+SkyWalking leverages OpenTelemetry Collector to transfer the metrics to [OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. [nginx-lua-prometheus](https://github.com/knyar/nginx-lua-prometheus) collects metrics from Nginx and expose them to an endpoint.
+2. OpenTelemetry Collector fetches metrics from the endpoint expose above via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Collect Nginx metrics and expose the following four metrics by [nginx-lua-prometheus](https://github.com/knyar/nginx-lua-prometheus). For details on metrics definition, refer to [here](../../../../test/e2e-v2/cases/nginx/nginx.conf).
+- histogram: nginx_http_latency
+- gauge: nginx_http_connections
+- counter: nginx_http_size_bytes
+- counter: nginx_http_requests_total
+
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on Prometheus Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/nginx/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### Nginx Monitoring
+
+SkyWalking observes the status, payload, and latency of the Nginx server, which is cataloged as a `LAYER: Nginx` `Service` in the OAP and instances would be recognized as `LAYER: Nginx` `instance`.
+
+About `LAYER: Nginx` `endpoint`, it depends on how precision you want to monitor the nginx.
+We do not recommend expose every request path metrics, because it will cause explosion of metrics endpoint data.
+
+You can collect host metrics:
+```
+http {
+ log_by_lua_block {
+ metric_bytes:inc(tonumber(ngx.var.request_length), {"request", ngx.var.host})
+ metric_bytes:inc(tonumber(ngx.var.bytes_send), {"response", ngx.var.host})
+ metric_requests:inc(1, {ngx.var.status, ngx.var.host})
+ metric_latency:observe(tonumber(ngx.var.request_time), {ngx.var.host})
+ }
+}
+```
+or grouped urls and upstream metrics:
+```
+upstream backend {
+ server ip:port;
+}
+
+server {
+
+ location /test {
+ default_type application/json;
+ return 200 '{"code": 200, "message": "success"}';
+
+ log_by_lua_block {
+ metric_bytes:inc(tonumber(ngx.var.request_length), {"request", "/test/**"})
+ metric_bytes:inc(tonumber(ngx.var.bytes_send), {"response", "/test/**"})
+ metric_requests:inc(1, {ngx.var.status, "/test/**"})
+ metric_latency:observe(tonumber(ngx.var.request_time), {"/test/**"})
+ }
+ }
+
+ location /test_upstream {
+
+ proxy_pass http://backend;
+
+ log_by_lua_block {
+ metric_bytes:inc(tonumber(ngx.var.request_length), {"request", "upstream/backend"})
+ metric_bytes:inc(tonumber(ngx.var.bytes_send), {"response", "upstream/backend"})
+ metric_requests:inc(1, {ngx.var.status, "upstream/backend"})
+ metric_latency:observe(tonumber(ngx.var.request_time), {"upstream/backend"})
+ }
+ }
+}
+```
+
+#### Nginx Service Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|-------------------------|------|-----------------------------------------------------------------------------------------------|---------|------------------------------------------------------|--------------------------------|
+| HTTP Request Trend | | meter_nginx_service_http_requests | Service | The increment rate of HTTP requests | nginx-lua-prometheus |
+| HTTP Latency | ms | meter_nginx_service_http_latency | Service | The increment rate of the latency of HTTP requests | nginx-lua-prometheus |
+| HTTP Bandwidth | KB | meter_nginx_service_bandwidth | Service | The increment rate of the bandwidth of HTTP requests | nginx-lua-prometheus |
+| HTTP Connections | | meter_nginx_service_http_connections | Service | The avg number of the connections | nginx-lua-prometheus |
+| HTTP Status Trend | | meter_nginx_service_http_status | Service | The increment rate of the status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 4xx Percent | % | meter_nginx_service_http_4xx_requests_increment / meter_nginx_service_http_requests_increment | Service | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 5xx Percent | % | meter_nginx_service_http_5xx_requests_increment / meter_nginx_service_http_requests_increment | Service | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+
+#### Nginx Instance Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|---------------------------|------|-------------------------------------------------------------------------------------------------|----------|------------------------------------------------------|--------------------------------|
+| HTTP Request Trend | | meter_nginx_instance_http_requests | Instance | The increment rate of HTTP requests | nginx-lua-prometheus |
+| HTTP Latency | ms | meter_nginx_instance_http_latency | Instance | The increment rate of the latency of HTTP requests | nginx-lua-prometheus |
+| HTTP Bandwidth | KB | meter_nginx_instance_bandwidth | Instance | The increment rate of the bandwidth of HTTP requests | nginx-lua-prometheus |
+| HTTP Connections | | meter_nginx_instance_http_connections | Instance | The avg number of the connections | nginx-lua-prometheus |
+| HTTP Status Trend | | meter_nginx_instance_http_status | Instance | The increment rate of the status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 4xx Percent | % | meter_nginx_instance_http_4xx_requests_increment / meter_nginx_instance_http_requests_increment | Instance | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 5xx Percent | % | meter_nginx_instance_http_5xx_requests_increment / meter_nginx_instance_http_requests_increment | Instance | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+
+#### Nginx Endpoint Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Catalog | Description | Data Source |
+|-------------------------|------|-------------------------------------------------------------------------------------------------|----------|------------------------------------------------------|----------------------|
+| HTTP Request Trend | | meter_nginx_endpoint_http_requests | Endpoint | The increment rate of HTTP requests | nginx-lua-prometheus |
+| HTTP Latency | ms | meter_nginx_endpoint_http_latency | Endpoint | The increment rate of the latency of HTTP requests | nginx-lua-prometheus |
+| HTTP Bandwidth | KB | meter_nginx_endpoint_bandwidth | Endpoint | The increment rate of the bandwidth of HTTP requests | nginx-lua-prometheus |
+| HTTP Status Trend | | meter_nginx_endpoint_http_status | Endpoint | The increment rate of the status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 4xx Percent | % | meter_nginx_endpoint_http_4xx_requests_increment / meter_nginx_endpoint_http_requests_increment | Endpoint | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+| HTTP Status 5xx Percent | % | meter_nginx_endpoint_http_5xx_requests_increment / meter_nginx_endpoint_http_requests_increment | Endpoint | The percentage of 4xx status of HTTP requests | nginx-lua-prometheus |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+
+The metrics definition and expression rules are found in `/config/otel-rules/nginx-service.yaml, /config/otel-rules/nginx-instance.yaml, /config/otel-rules/nginx-endpoint.yaml`.
+
+The Nginx dashboard panel configurations are found in `/config/ui-initialized-templates/nginx`.
+
+## Collect nginx access and error log
+SkyWalking leverages [fluentbit](https://fluentbit.io/) or other log agents for collecting access log and error log of Nginx.
+
+### Data flow
+1. fluentbit agent collects access log and error log from Nginx.
+2. fluentbit agent sends data to SkyWalking OAP Server using native meter APIs via HTTP.
+3. The SkyWalking OAP Server parses the expression with [LAL](../../concepts-and-designs/lal.md) to parse/extract and store the results.
+
+### Set up
+1. Install [fluentbit](https://docs.fluentbit.io/manual/installation/docker).
+2. Config fluent bit with fluent-bit.conf, refer to [here](../../../../test/e2e-v2/cases/nginx/fluent-bit.conf).
+
+### Error Log Monitoring
+Error Log monitoring provides monitoring of the error.log of the Nginx server.
+
+#### Supported Metrics
+| Monitoring Panel | Metric Name | Catalog | Description | Data Source |
+|--------------------------|--------------------------------------|----------|-------------------------------------------|-------------|
+| Service Error Log Count | meter_nginx_service_error_log_count | Service | The count of log level of nginx error.log | fluent bit |
+| Instance Error Log Count | meter_nginx_instance_error_log_count | Instance | The count of log level of nginx error.log | fluent bit |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+
+The log collect and analyse rules are found in `/config/lal/nginx.yaml`, `/config/log-mal-rules/nginx.yaml`.
+
+The Nginx dashboard panel configurations are found in `/config/ui-initialized-templates/nginx`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-postgresql-monitoring.md b/docs/en/setup/backend/backend-postgresql-monitoring.md
new file mode 100644
index 000000000000..4dd8bb322a2d
--- /dev/null
+++ b/docs/en/setup/backend/backend-postgresql-monitoring.md
@@ -0,0 +1,76 @@
+# PostgreSQL monitoring
+## PostgreSQL server performance from `postgres-exporter`
+SkyWalking leverages postgres-exporter for collecting metrics data from PostgreSQL. It leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. postgres-exporter collect metrics data from PostgreSQL.
+2. OpenTelemetry Collector fetches metrics from postgres-exporter via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Set up [postgres-exporter](https://github.com/prometheus-community/postgres_exporter#quick-start).
+2. Set up [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on Prometheus Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/postgresql/postgres-exporter/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### PostgreSQL Monitoring
+PostgreSQL cluster is cataloged as a `Layer: PostgreSQL` `Service` in OAP. Each PostgreSQL server is cataloged as an `Instance` in OAP.
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|-----|-----|
+| Shared Buffers | MB | meter_pg_shared_buffers | The number of shared memory buffers used by the server | postgres-exporter|
+| Effective Cache | GB | meter_pg_effective_cache | The planner's assumption about the total size of the data caches | postgres-exporter|
+| Maintenance Work Mem | MB | meter_pg_maintenance_work_mem | The maximum memory to be used for maintenance operations| postgres-exporter|
+| Seq Page Cost | | meter_pg_seq_page_cost | The planner's estimate of the cost of a sequentially fetched disk page.| postgres-exporter|
+| Random Page Cost| | meter_pg_random_page_cost | The planner's estimate of the cost of a nonsequentially fetched disk page. | postgres-exporter|
+| Max Worker Processes | | meter_pg_max_worker_processes | Maximum number of concurrent worker processes | postgres-exporter|
+| Max WAL Size | GB | meter_max_wal_size | The WAL size that triggers a checkpoint | postgres-exporter|
+| Max Parallel Workers | | meter_pg_max_parallel_workers | The maximum number of parallel processes per executor node| postgres-exporter|
+| Work Mem | MB | meter_pg_max_work_mem | The maximum memory to be used for query workspaces. | postgres-exporter|
+| Fetched Row Trend | | meter_pg_fetched_rows_rate | The trend of the number of rows fetched by queries in this database. | postgres-exporter|
+| Inserted Row Trend | | meter_pg_inserted_rows_rate | The trend of the number of rows inserted by queries in this database. | postgres-exporter|
+| Updated Row Trend | | meter_pg_updated_rows_rate | The trend of the number of rows updated by queries in this database. | postgres-exporter|
+| Deleted Row Trend | | meter_pg_deleted_rows_rate | The trend of the number of rows deleted by queries in this database. | postgres-exporter|
+| Returned Row Trend | | meter_pg_returned_rows_rate | The trend of the number of rows returned by queries in this database. | postgres-exporter|
+| Committed Transactions Trend | | meter_pg_committed_transactions_rate | The trend of the number of transactions in this database that have been committed | postgres-exporter|
+| Rolled Back Transactions Trend | | meter_pg_rolled_back_transactions_rate | The trend of the number of transactions in this database that have been rolled back | postgres-exporter|
+| Buffers Trend | | meter_pg_buffers_alloc meter_pg_buffers_checkpoint meter_pg_buffers_clean meter_pg_buffers_backend_fsync meter_pg_buffers_backend | The trend of the number of buffers | postgres-exporter|
+| Conflicts Trend | | meter_pg_conflicts_rate | The trend of the number of queries canceled due to conflicts with recovery in this database | postgres-exporter|
+| Deadlock Trend | | meter_pg_deadlocks_rate | The trend of the number of deadlocks detected in this database | postgres-exporter|
+| Cache Hit Rate | % | meter_pg_cache_hit_rate | The rate of cache hit | postgres-exporter|
+| Temporary Files Trend | | meter_pg_temporary_files_rate | The rate of total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the log_temp_files setting | postgres-exporter|
+| Checkpoint Stat Trend | | meter_pg_checkpoint_write_time_rate meter_pg_checkpoint_sync_time_rate meter_pg_checkpoint_req_rate meter_pg_checkpoint_timed_rate | The trend of checkpoint stat | postgres-exporter|
+| Active Sessions | | meter_pg_active_sessions | The number of connections which state is active | postgres-exporter|
+| Idle Sessions | | meter_pg_idle_sessions | The number of connections which state is idle,idle in transaction or idle in transaction (aborted) | postgres-exporter|
+| Locks Count | | meter_pg_locks_count | Number of locks | postgres-exporter|
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/postgresql`.
+The PostgreSQL dashboard panel configurations are found in `/config/ui-initialized-templates/postgresql`.
+
+## Collect sampled slow SQLs
+SkyWalking leverages [fluentbit](https://fluentbit.io/) or other log agents for collecting slow SQL statements from PostgreSQL.
+
+### Data flow
+1. fluentbit agent collects slow sql logs from PostgreSQL.
+2. fluentbit agent sends data to SkyWalking OAP Server using native log APIs via HTTP.
+3. The SkyWalking OAP Server parses the expression with [LAL](../../concepts-and-designs/lal.md) to parse/extract and store the results.
+
+### Set up
+1. Set up [fluentbit](https://docs.fluentbit.io/manual/installation/docker).
+2. Config [fluentbit](../../../../test/e2e-v2/cases/postgresql/postgres-exporter/fluent-bit.conf)
+3. Config PostgreSQL to enable slow log. [Example](../../../../test/e2e-v2/cases/postgresql/postgres-exporter/postgresql.conf).
+
+### Slow SQL Monitoring
+Slow SQL monitoring provides monitoring of the slow SQL statements of the PostgreSQL server. PostgreSQL Cluster is cataloged as a `Layer: POSTGRESQL` `Service` in OAP.
+Each PostgreSQL server is cataloged as an `Instance` in OAP.
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|-----|-----|
+|Slow Statements | ms | top_n_database_statement | The latency and statement of PostgreSQL slow SQLs | fluentbit|
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The slowsql expression rules are found in `/config/lal/pgsql-slowsql.yaml`
+The PostgreSQL dashboard panel configurations are found in `/config/ui-initialized-templates/postgresql`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-profile-thread-merging.md b/docs/en/setup/backend/backend-profile-thread-merging.md
new file mode 100644
index 000000000000..fa687c71fa33
--- /dev/null
+++ b/docs/en/setup/backend/backend-profile-thread-merging.md
@@ -0,0 +1,52 @@
+# Thread dump merging mechanism
+The performance profile is an enhancement feature in the APM system. We are using the thread dump to estimate the method execution time, rather than adding multiple local spans. In this way, the resource cost would be much less than using distributed tracing to locate slow method. This feature is suitable in the production environment. This document introduces how thread dumps are merged into the final report as a stack tree(s).
+
+## Thread analyst
+### Read data and transform
+Read the data from the database and convert it to a data structure in gRPC.
+```
+st=>start: Start
+e=>end: End
+op1=>operation: Load data using paging
+op2=>operation: Transform data using parallel
+
+st(right)->op1(right)->op2
+op2(right)->e
+```
+Copy the code and paste it into this [link](http://flowchart.js.org/) to generate flow chart.
+1. Use the stream to read data by page (50 records per page).
+2. Convert the data into gRPC data structures in the form of parallel streams.
+3. Merge into a list of data.
+### Data analysis
+Use the group-by and collector modes in the Java parallel stream to group according to the first stack element in the database records,
+and use the collector to perform data aggregation. Generate a multi-root tree.
+```
+st=>start: Start
+e=>end: End
+op1=>operation: Group by first stack element
+sup=>operation: Generate empty stack tree
+acc=>operation: Accumulator data to stack tree
+com=>operation: Combine stack trees
+fin=>operation: Calculate durations and build result
+
+st(right)->op1->sup(right)->acc
+acc(right)->com(right)->fin->e
+```
+Copy the code and paste it into this [link](http://flowchart.js.org/) to generate a flow chart.
+- **Group by first stack element**: Use the first level element in each stack to group, ensuring that the stacks have the same root node.
+- **Generate empty stack tree**: Generate multiple top-level empty trees to prepare for the following steps.
+The reason for generating multiple top-level trees is that original data can be added in parallel without generating locks.
+- **Accumulator data to stack tree**: Add every thread dump into the generated trees.
+ 1. Iterate through each element in the thread dump to find if there is any child element with the same code signature and same stack depth in the parent element.
+ If not, add this element.
+ 2. Keep the dump sequences and timestamps in each nodes from the source.
+- **Combine stack trees**: Combine all trees structures into one by using the same rules as the `Accumulator`.
+ 1. Use LDR to traverse the tree node. Use the `Stack` data structure to avoid recursive calls. Each stack element represents the node that needs to be merged.
+ 2. The task of merging two nodes is to merge the list of children nodes. If they have the same code signature and same parents, save the dump sequences and timestamps in this node. Otherwise, the node needs to be added into the target node as a new child.
+- **Calculate durations and build result**: Calculate relevant statistics and generate response.
+ 1. Use the same traversal node logic as in the `Combine stack trees` step. Convert to a GraphQL data structure, and put all nodes into a list for subsequent duration calculations.
+ 2. Calculate each node's duration in parallel. For each node, sort the sequences. If there are two continuous sequences, the duration should add the duration of these two seq's timestamp.
+ 3. Calculate each node execution in parallel. For each node, the duration of the current node should deduct the time consumed by all children.
+
+## Profile data debugging
+Please follow the [exporter tool](../../guides/backend-profile-export.md#export-using-command-line) to package profile data. Unzip the profile data and use [analyzer main function](../../../../oap-server/server-tools/profile-exporter/tool-profile-snapshot-bootstrap/src/test/java/org/apache/skywalking/oap/server/tool/profile/exporter/ProfileExportedAnalyze.java) to run it.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-pulsar-monitoring.md b/docs/en/setup/backend/backend-pulsar-monitoring.md
new file mode 100644
index 000000000000..ac8bec111c24
--- /dev/null
+++ b/docs/en/setup/backend/backend-pulsar-monitoring.md
@@ -0,0 +1,67 @@
+# Pulsar monitoring
+
+SkyWalking leverages OpenTelemetry Collector to collect metrics data in Prometheus format from the Pulsar and transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+Kafka entity as a `Service` in OAP and on the `Layer: PULSAR.
+
+## Data flow
+
+1. Pulsar exposes metrics through Prometheus endpoint.
+2. OpenTelemetry Collector fetches metrics from Pulsar cluster via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.`
+
+## Setup
+
+1. Set up [Pulsar Cluster](https://pulsar.apache.org/docs/3.1.x/getting-started-docker-compose/). (Pulsar cluster includes pulsar broker cluster and Bookkeeper bookie cluster.)
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). The example
+ for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/pulsar/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Pulsar Monitoring
+
+Pulsar monitoring provides multidimensional metrics monitoring of Pulsar cluster as `Layer: PULSAR` `Service` in
+the OAP. In each cluster, the nodes are represented as `Instance`.
+
+### Pulsar Cluster Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|----------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------|----------------|
+| Total Topics | meter_pulsar_total_topics | The number of Pulsar topics in this cluster. | Pulsar Cluster |
+| Total Subscriptions | meter_pulsar_total_subscriptions | The number of Pulsar subscriptions in this cluster. | Pulsar Cluster |
+| Total Producers | meter_pulsar_total_producers | The number of active producers connected to this cluster. | Pulsar Cluster |
+| Total Consumers | meter_pulsar_total_consumers | The number of active consumers connected to this cluster. | Pulsar Cluster |
+| Message Rate In | meter_pulsar_message_rate_in | The total message rate coming into this cluster (message per second). | Pulsar Cluster |
+| Message Rate Out | meter_pulsar_message_rate_out | The total message rate going out from this cluster (message per second). | Pulsar Cluster |
+| Throughput In | meter_pulsar_throughput_in | The total throughput coming into this cluster (byte per second). | Pulsar Cluster |
+| Throughput Out | meter_pulsar_throughput_out | The total throughput going out from this cluster (byte per second). | Pulsar Cluster |
+| Storage Size | meter_pulsar_storage_size | The total storage size of all topics in this broker (in bytes). | Pulsar Cluster |
+| Storage Logical Size | meter_pulsar_storage_logical_size | The storage size of all topics in this broker without replicas (in bytes). | Pulsar Cluster |
+| Storage Write Rate | meter_pulsar_storage_write_rate | The total message batches (entries) written to the storage for this broker (message batch per second). | Pulsar Cluster |
+| Storage Read Rate | meter_pulsar_storage_read_rate | The total message batches (entries) read from the storage for this broker (message batch per second). | Pulsar Cluster |
+
+
+### Pulsar Node Supported Metrics
+
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------|
+| Active Connections | meter_pulsar_broker_active_connections | The number of active connections. | Pulsar Broker |
+| Total Connections | meter_pulsar_broker_total_connections | The total number of connections. | Pulsar Broker |
+| Connection Create Success Count | meter_pulsar_broker_connection_create_success_count | The number of successfully created connections. | Pulsar Broker |
+| Connection Create Fail Count | meter_pulsar_broker_connection_create_fail_count | The number of failed connections. | Pulsar Broker |
+| Connection Closed Total Count | meter_pulsar_broker_connection_closed_total_count | The total number of closed connections. | Pulsar Broker |
+| JVM Buffer Pool Used | meter_pulsar_broker_jvm_buffer_pool_used_bytes | The usage of jvm buffer pool. | Pulsar Broker |
+| JVM Memory Pool Used | meter_pulsar_broker_jvm_memory_pool_used | The usage of jvm memory pool. | Pulsar Broker |
+| JVM Memory | meter_pulsar_broker_jvm_memory_init
meter_pulsar_broker_jvm_memory_used
meter_pulsar_broker_jvm_memory_committed | The usage of jvm memory. | Pulsar Broker |
+| JVM Threads | meter_pulsar_broker_jvm_threads_current
meter_pulsar_broker_jvm_threads_daemon
meter_pulsar_broker_jvm_threads_peak
meter_pulsar_broker_jvm_threads_deadlocked | The usage of jvm threads. | Pulsar Broker |
+| GC Time | meter_pulsar_broker_jvm_gc_collection_seconds_sum | Time spent in a given JVM garbage collector in seconds. | Pulsar Broker |
+| GC Count | meter_pulsar_broker_jvm_gc_collection_seconds_count | The count of a given JVM garbage collector. | Pulsar Broker |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `otel-rules/pulsar/pulsar-cluster.yaml, otel-rules/pulsar/pulsar-broker.yaml`.
+The Pulsar dashboard panel configurations are found in `ui-initialized-templates/pulsar`.
diff --git a/docs/en/setup/backend/backend-rabbitmq-monitoring.md b/docs/en/setup/backend/backend-rabbitmq-monitoring.md
new file mode 100644
index 000000000000..62ffc6a4e787
--- /dev/null
+++ b/docs/en/setup/backend/backend-rabbitmq-monitoring.md
@@ -0,0 +1,91 @@
+# RabbitMQ monitoring
+
+SkyWalking leverages `rabbitmq_prometheus` plugin for collecting metrics data from RabbitMQ. It leverages OpenTelemetry
+Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. The `rabbitmq_prometheus` plugin collect metrics data from RabbitMQ. Note: The RabbitMQ version is required to be
+ 3.8.0+.
+ The `rabbitmq_prometheus` plugin is built-in since RabbitMQ v3.8.0.
+2. OpenTelemetry Collector fetches metrics from `rabbitmq_prometheus` plugin via Prometheus Receiver and pushes metrics
+ to
+ SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Setup [rabbitmq_prometheus](https://www.rabbitmq.com/prometheus.html#installation).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes). The example
+ for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/rabbitmq/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## RabbitMQ Monitoring
+
+RabbitMQ monitoring provides multidimensional metrics monitoring of RabbitMQ cluster as `Layer: RABBITMQ` `Service` in
+the OAP. In each cluster, the nodes are represented as `Instance`.
+
+### RabbitMQ Cluster Supported Metrics
+
+| Monitoring Panel | Metric Name | Description | Data Source |
+|-----------------------------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| Memory Available Before Publishers Blocked (MB) | meter_rabbitmq_memory_available_before_publisher_blocked | If the value is zero or less, the memory alarm will be triggered and all publishing connections across all cluster nodes will be blocked. | rabbitmq_prometheus plugin |
+| Disk Space Available Before Publishers Blocked (GB) | meter_rabbitmq_disk_space_available_before_publisher_blocked | This metric is reported for the partition where the RabbitMQ data directory is stored. | rabbitmq_prometheus plugin |
+| File Descriptors Available | meter_rabbitmq_file_descriptors_available | When this value reaches zero, new connections will not be accepted and disk write operations may fail. | rabbitmq_prometheus plugin |
+| TCP Sockets Available | meter_rabbitmq_tcp_socket_available | When this value reaches zero, new connections will not be accepted. | rabbitmq_prometheus plugin |
+| Messages Ready To Be Delivered To Consumers | meter_rabbitmq_message_ready_delivered_consumers | Total number of ready messages ready to be delivered to consumers. | rabbitmq_prometheus plugin |
+| Messages Pending Consumer Acknowledgement | meter_rabbitmq_message_unacknowledged_delivered_consumers | The total number of messages that are either in-flight to consumers, currently being processed by consumers or simply waiting for the consumer acknowledgements to be processed by the queue. Until the queue processes the message acknowledgement, the message will remain unacknowledged. | rabbitmq_prometheus plugin |
+| Messages Published | meter_rabbitmq_messages_published | The incoming message rate before any routing rules are applied. | rabbitmq_prometheus plugin |
+| Messages Confirmed To Publishers | meter_rabbitmq_messages_confirmed | The rate of messages confirmed by the broker to publishers. Publishers must opt-in to receive message confirmations. | rabbitmq_prometheus plugin |
+| Messages Unconfirmed To Publishers | meter_rabbitmq_messages_unconfirmed | The rate of messages received from publishers that have publisher confirms enabled and the broker has not confirmed yet. | rabbitmq_prometheus plugin |
+| Messages Routed To Queues | meter_rabbitmq_messages_routed | The rate of messages received from publishers and successfully routed to the master queue replicas. | rabbitmq_prometheus plugin |
+| Unroutable Messages Returned To Publishers | meter_rabbitmq_messages_unroutable_returned | The rate of messages that cannot be routed and are returned back to publishers. | rabbitmq_prometheus plugin |
+| Unroutable Messages Dropped | meter_rabbitmq_messages_unroutable_dropped | The rate of messages that cannot be routed and are dropped. | rabbitmq_prometheus plugin |
+| Queues Total | meter_rabbitmq_queues | Total number of queue masters per node. | rabbitmq_prometheus plugin |
+| Queues Declared | meter_rabbitmq_queues_declared_total | The rate of queue declarations performed by clients. | rabbitmq_prometheus plugin |
+| Queues Created | meter_rabbitmq_queues_created_total | The rate of new queues created (as opposed to redeclarations). | rabbitmq_prometheus plugin |
+| Queues Deleted | meter_rabbitmq_queues_deleted_total | The rate of queues deleted. | rabbitmq_prometheus plugin |
+| Channels Total | meter_rabbitmq_channels | Total number of channels on all currently opened connections. | rabbitmq_prometheus plugin |
+| Channels Opened | meter_rabbitmq_channels_opened_total | The rate of new channels opened by applications across all connections. Channels are expected to be long-lived. | rabbitmq_prometheus plugin |
+| Channels Closed | meter_rabbitmq_channels_closed_total | The rate of channels closed by applications across all connections. Channels are expected to be long-lived. | rabbitmq_prometheus plugin |
+| Connections Total | meter_rabbitmq_connections | Total number of client connections. | rabbitmq_prometheus plugin |
+| Connections Opened | meter_rabbitmq_connections_opened_total | The rate of new connections opened by clients. Connections are expected to be long-lived. | rabbitmq_prometheus plugin |
+| Connections Closed | meter_rabbitmq_connections_closed_total | The rate of connections closed. Connections are expected to be long-lived. | rabbitmq_prometheus plugin |
+
+### RabbitMQ Node Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------|
+| Ready Messages | | meter_rabbitmq_node_queue_messages_ready | Total number of ready messages ready to be delivered to consumers. | rabbitmq_prometheus plugin |
+| Unacknowledged Messages | | meter_rabbitmq_node_unacknowledged_messages | Messages delivered to consumers but not yet acknowledged | rabbitmq_prometheus plugin |
+| Incoming Messages | | meter_rabbitmq_node_incoming_messages | The incoming message rate before any routing rules are applied. | rabbitmq_prometheus plugin |
+| Outgoing Messages | | meter_rabbitmq_node_outgoing_messages_total | The outgoing message rate before any routing rules are applied. | rabbitmq_prometheus plugin |
+| Publishers | | meter_rabbitmq_node_publisher_total | Publishers | rabbitmq_prometheus plugin |
+| Consumers | | meter_rabbitmq_node_consumer_total | Consumers currently connect | rabbitmq_prometheus plugin |
+| Collections | | meter_rabbitmq_node_connections_total | Connections currently open | rabbitmq_prometheus plugin |
+| Channels | | meter_rabbitmq_node_channel_total | Channels currently open | rabbitmq_prometheus plugin |
+| Queues | | meter_rabbitmq_node_queue_total | Queues available | rabbitmq_prometheus plugin |
+| Allocated Used | % | meter_rabbitmq_node_allocated_used_percent | Erlang VM memory utilisation from erts_alloc perspective | rabbitmq_prometheus plugin |
+| Allocated Unused | % | meter_rabbitmq_node_allocated_unused_percent | Erlang VM memory utilisation from erts_alloc perspective | rabbitmq_prometheus plugin |
+| Allocated Used | MB | meter_rabbitmq_node_allocated_used_bytes | Erlang VM memory utilisation from erts_alloc perspective | rabbitmq_prometheus plugin |
+| Allocated Unused | MB | meter_rabbitmq_node_allocated_unused_bytes | Erlang VM memory utilisation from erts_alloc perspective | rabbitmq_prometheus plugin |
+| Allocated Total | MB | meter_rabbitmq_node_allocated_total_bytes | Erlang VM memory utilisation from erts_alloc perspective | rabbitmq_prometheus plugin |
+| Resident Set Size | MB | meter_rabbitmq_node_process_resident_memory_bytes | Erlang VM Resident Set Size (RSS) As reported by the OS | rabbitmq_prometheus plugin |
+| Allocators | MB | meter_rabbitmq_node_allocated_unused_bytes
meter_rabbitmq_node_allocated_total_bytes
meter_rabbitmq_node_process_resident_memory_bytes | | rabbitmq_prometheus plugin |
+| Allocated By Type | MB | meter_rabbitmq_node_allocated_by_type | Allocated by allocator type | rabbitmq_prometheus plugin |
+| Multiblock Used | MB | meter_rabbitmq_node_allocated_multiblock_used | Multi block used | rabbitmq_prometheus plugin |
+| Multiblock Unused | MB | meter_rabbitmq_node_allocated_multiblock_unused | Multi block used | rabbitmq_prometheus plugin |
+| Multiblock Pool Used | MB | meter_rabbitmq_node_allocated_multiblock_pool_used | Multi block pool used | rabbitmq_prometheus plugin |
+| Multiblock Pool Unused | MB | meter_rabbitmq_node_allocated_multiblock_pool_unused | Multi block pool unused | rabbitmq_prometheus plugin |
+| Singleblock Used | MB | meter_rabbitmq_node_allocated_singleblock_used | Single block used | rabbitmq_prometheus plugin |
+| Singleblock Unused | MB | meter_rabbitmq_node_allocated_singleblock_unused | Single block unused | rabbitmq_prometheus plugin |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `/config/otel-rules/rabbitmq/rabbitmq-cluster.yaml, /config/otel-rules/rabbitmq/rabbitmq-node.yaml`.
+The RabbitMQ dashboard panel configurations are found in `/config/ui-initialized-templates/rabbitmq`.
diff --git a/docs/en/setup/backend/backend-redis-monitoring.md b/docs/en/setup/backend/backend-redis-monitoring.md
new file mode 100644
index 000000000000..bd20a9712025
--- /dev/null
+++ b/docs/en/setup/backend/backend-redis-monitoring.md
@@ -0,0 +1,71 @@
+# Redis monitoring
+## Redis server performance from `redis-exporter`
+SkyWalking leverages redis-exporter for collecting metrics data from Redis. It leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+### Data flow
+1. redis-exporter collect metrics data from Redis.
+2. OpenTelemetry Collector fetches metrics from redis-exporter via Prometheus Receiver and pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+### Set up
+1. Set up [redis-exporter](https://github.com/oliver006/redis_exporter#building-and-running-the-exporter).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#docker). For details on Redis Receiver in OpenTelemetry Collector, refer to [here](../../../../test/e2e-v2/cases/redis/redis-exporter/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+### Redis Monitoring
+Redis monitoring provides monitoring of the status and resources of the Redis server. Redis cluster is cataloged as a `Layer: REDIS` `Service` in OAP.
+Each Redis server is cataloged as an `Instance` in OAP.
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----------------------------------|--------|--------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------|
+| Uptime | day | meter_redis_uptime | The uptime of Redis. | redis-exporter |
+| Connected Clients | | meter_redis_connected_clients | The number of connected clients. | redis-exporter |
+| Blocked Clients | | meter_redis_blocked_clients | The number of blocked clients. | redis-exporter |
+| Memory Max Bytes | MB | meter_redis_memory_max_bytes | The max bytes of memory. | redis-exporter |
+| Hits Rate | % | meter_redis_hit_rate | Hit rate of redis when used as a cache. | redis-exporter |
+| Average Time Spend By Command | second | meter_redis_average_time_spent_by_command | Average time to execute various types of commands. | redis-exporter |
+| Total Commands Trend | | meter_redis_total_commands_rate | The Trend of total commands. | redis-exporter |
+| DB keys | | meter_redis_evicted_keys_total meter_redis_expired_keys_total meter_redis_db_keys | The number of Expired / Evicted / total keys. | redis-exporter |
+| Net Input/Output Bytes | KB | meter_redis_net_input_bytes meter_redis_net_output_bytes | Total bytes of input / output of redis net. | redis-exporter |
+| Memory Usage | % | meter_redis_memory_used_bytes meter_redis_memory_max_bytes | Percentage of used memory. | redis-exporter |
+| Total Time Spend By Command Trend | | meter_redis_commands_duration meter_redis_commands_total | The trend of total time spend by command | redis-exporter |
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/redis`.
+The Redis dashboard panel configurations are found in `/config/ui-initialized-templates/redis`.
+
+## Collect sampled slow commands
+SkyWalking leverages [fluentbit](https://fluentbit.io/) or other log agents for collecting slow commands from Redis.
+
+### Data flow
+1. Execute [commands](../../../../test/e2e-v2/cases/redis/redis-exporter/scripts/slowlog.sh) periodically to collect slow logs from Redis and save the result locally.
+2. Fluent-bit agent collects slow logs from local file.
+3. fluent-bit agent sends data to SkyWalking OAP Server using native meter APIs via HTTP.
+4. The SkyWalking OAP Server parses the expression with [LAL](../../concepts-and-designs/lal.md) to parse/extract and store the results.
+
+### Set up
+1. Set up [fluentbit](https://docs.fluentbit.io/manual/installation/docker).
+2. Config fluentbit from [here](../../../../test/e2e-v2/cases/redis/redis-exporter/fluent-bit.conf) for Redis.
+3. Config slow log from [here](../../../../test/e2e-v2/cases/redis/redis-exporter/redis.conf) for Redis.
+4. Periodically execute the [commands](../../../../test/e2e-v2/cases/redis/redis-exporter/scripts/slowlog.sh).
+
+**Notice:**
+
+1.The `slowlog-log-slower-than` and `slowlog-max-len` configuration items in the configuration file are for the slow log, the former indicating that execution time longer than the specified time (in milliseconds) will be logged to the slowlog, and the latter indicating the maximum number of slow logs that will be stored in the slow log file.
+2.In the e2e test, SkyWalking uses cron to periodically execute the redis command to fetch the slow logs and write them to a local file, which is then collected by fluent-bit to send the data to the OAP. You can see the relevant configuration files [here](../../../../test/e2e-v2/cases/redis/redis-exporter).You can also get slow logs periodically and send them to OAP in other ways than using cron and fluent-bit.
+
+### Slow Commands Monitoring
+Slow SQL monitoring provides monitoring of the slow commands of the Redis servers. Redis servers are cataloged as a `Layer: REDIS` `Service` in OAP.
+
+#### Supported Metrics
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|--------------------------------------------------|-----|
+|Slow Statements | ms | top_n_database_statement | The latency and statement of Redis slow commands | fluentbit|
+
+### Customizations
+You can customize your own metrics/expression/dashboard panel.
+The slowsql expression rules are found in `/config/lal/redis-slowsql.yaml`
+The Redis dashboard panel configurations are found in `/config/ui-initialized-templates/redis`.
+`
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-rocketmq-monitoring.md b/docs/en/setup/backend/backend-rocketmq-monitoring.md
new file mode 100644
index 000000000000..85c7137a64d5
--- /dev/null
+++ b/docs/en/setup/backend/backend-rocketmq-monitoring.md
@@ -0,0 +1,73 @@
+# RocketMQ monitoring
+
+SkyWalking leverages rocketmq-exporter for collecting metrics data from RocketMQ. It leverages OpenTelemetry
+Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+
+## Data flow
+
+1. The `rocketmq-exporter` (https://github.com/apache/rocketmq-exporter?tab=readme-ov-file#readme) collects metrics data from RocketMQ, The RocketMQ version is required to be 4.3.2+.
+2. OpenTelemetry Collector fetches metrics from rocketmq-exporter via Prometheus Receiver and pushes metrics to
+ SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to
+ filter/calculate/aggregate and store the results.
+
+## Setup
+
+1. Setup [rocketmq-exporter](https://github.com/apache/rocketmq-exporter).
+2. Set up [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#docker). The example for OpenTelemetry Collector configuration, refer
+ to [here](../../../../test/e2e-v2/cases/rocketmq/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## RocketMQ Monitoring
+
+RocketMQ monitoring provides multidimensional metrics monitoring of RocketMQ Exporter as `Layer: RocketMQ` `Service` in
+the OAP. In each cluster, the broker is represented as `Instance` and the topic is represented as `Endpoint`.
+
+### RocketMQ Cluster Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------|
+| Messages Produced Today | Count | meter_rocketmq_cluster_messages_produced_today | The number of cluster messages produced today. | RocketMQ Exporter |
+| Messages Consumed Today | Count | meter_rocketmq_cluster_messages_consumed_today | The number of cluster messages consumed today. | RocketMQ Exporter |
+| Total Producer Tps | Msg/sec | meter_rocketmq_cluster_total_producer_tps | The number of messages produced per second. | RocketMQ Exporter |
+| Total Consume Tps | Msg/sec | meter_rocketmq_cluster_total_consumer_tps | The number of messages consumed per second. | RocketMQ Exporter |
+| Producer Message Size | Bytes/sec | meter_rocketmq_cluster_producer_message_size | The max size of a message produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Bytes/sec | meter_rocketmq_cluster_consumer_message_size | The max size of the consumed message per second. | RocketMQ Exporter |
+| Messages Produced Until Yesterday | Count | meter_rocketmq_cluster_messages_produced_until_yesterday | The total number of messages put until 12 o'clock last night. | RocketMQ Exporter |
+| Messages Consumed Until Yesterday | Count | meter_rocketmq_cluster_messages_consumed_until_yesterday | The total number of messages read until 12 o'clock last night. | RocketMQ Exporter |
+| Max Consumer Latency | ms | meter_rocketmq_cluster_max_consumer_latency | The max number of consumer latency. | RocketMQ Exporter |
+| Max CommitLog Disk Ratio | % | meter_rocketmq_cluster_max_commitLog_disk_ratio | The max utilization ratio of the commit log disk. | RocketMQ Exporter |
+| CommitLog Disk Ratio | % | meter_rocketmq_cluster_commitLog_disk_ratio | The utilization ratio of the commit log disk per broker IP. | RocketMQ Exporter |
+| Pull ThreadPool Queue Head Wait Time | ms | meter_rocketmq_cluster_pull_threadPool_queue_head_wait_time | The wait time in milliseconds for pulling threadPool queue per broker IP. | RocketMQ Exporter |
+| Send ThreadPool Queue Head Wait Time | ms | meter_rocketmq_cluster_send_threadPool_queue_head_wait_time | The wait time in milliseconds for sending threadPool queue per broker IP. | RocketMQ Exporter |
+
+### RocketMQ Broker Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|----------------------------------------------------|-------------------|
+| Produce TPS | Msg/sec | meter_rocketmq_broker_produce_tps | The number of broker produces messages per second. | RocketMQ Exporter |
+| Consume QPS | Msg/sec | meter_rocketmq_broker_consume_qps | The number of broker consumes messages per second. | RocketMQ Exporter |
+| Producer Message Size | Bytes/sec | meter_rocketmq_broker_producer_message_size | The max size of the messages produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Bytes/sec | meter_rocketmq_broker_consumer_message_size | The max size of the messages consumed per second. | RocketMQ Exporter |
+
+### RocketMQ Topic Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------|
+| Max Producer Message Size | Byte | meter_rocketmq_topic_max_producer_message_size | The maximum number of messages produced. | RocketMQ Exporter |
+| Max Consumer Message Size | Byte | meter_rocketmq_topic_max_consumer_message_size | The maximum number of messages consumed. | RocketMQ Exporter |
+| Consumer Latency | ms | meter_rocketmq_topic_consumer_latency | Consumption delay time of a consumer group. | RocketMQ Exporter |
+| Producer Tps | Msg/sec | meter_rocketmq_topic_producer_tps | The number of messages produced per second. | RocketMQ Exporter |
+| Consumer Group Tps | Msg/sec | meter_rocketmq_topic_consumer_group_tps | The number of messages consumed per second per consumer group. | RocketMQ Exporter |
+| Producer Offset | Count | meter_rocketmq_topic_producer_offset | The max progress of a topic's production message. | RocketMQ Exporter |
+| Consumer Group Offset | Count | meter_rocketmq_topic_consumer_group_offset | The max progress of a topic's consumption message per consumer group. | RocketMQ Exporter |
+| Producer Message Size | Byte/sec | meter_rocketmq_topic_producer_message_size | The max size of messages produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Byte/sec | meter_rocketmq_topic_consumer_message_size | The max size of messages consumed per second. | RocketMQ Exporter |
+
+## Customizations
+
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found
+in `otel-rules/rocketmq/rocketmq-cluster.yaml, otel-rules/rocketmq/rocketmq-broker.yaml, otel-rules/rocketmq/rocketmq-topic.yaml`.
+The RocketMQ dashboard panel configurations are found in `ui-initialized-templates/rocketmq`.
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-setting-override.md b/docs/en/setup/backend/backend-setting-override.md
new file mode 100644
index 000000000000..bd9747444548
--- /dev/null
+++ b/docs/en/setup/backend/backend-setting-override.md
@@ -0,0 +1,48 @@
+# Setting Override
+SkyWalking backend supports setting overrides by system properties and system environment variables.
+You may override the settings in `application.yml`
+
+## System properties key rule
+**ModuleName**.**ProviderName**.**SettingKey**.
+
+- Example
+
+ Override `restHost` in this setting segment
+
+```yaml
+core:
+ default:
+ restHost: ${SW_CORE_REST_HOST:0.0.0.0}
+ restPort: ${SW_CORE_REST_PORT:12800}
+ restContextPath: ${SW_CORE_REST_CONTEXT_PATH:/}
+ gRPCHost: ${SW_CORE_GRPC_HOST:0.0.0.0}
+ gRPCPort: ${SW_CORE_GRPC_PORT:11800}
+```
+
+Use command arg
+```
+-Dcore.default.restHost=172.0.4.12
+```
+
+## System environment variables
+- Example
+
+ Override `restHost` in this setting segment through environment variables
+
+```yaml
+core:
+ default:
+ restHost: ${REST_HOST:0.0.0.0}
+ restPort: ${SW_CORE_REST_PORT:12800}
+ restContextPath: ${SW_CORE_REST_CONTEXT_PATH:/}
+ gRPCHost: ${SW_CORE_GRPC_HOST:0.0.0.0}
+ gRPCPort: ${SW_CORE_GRPC_PORT:11800}
+```
+
+If the `REST_HOST ` environment variable exists in your operating system and its value is `172.0.4.12`,
+then the value of `restHost` here will be overwritten to `172.0.4.12`; otherwise, it will be set to `0.0.0.0`.
+
+Placeholder nesting is also supported, like `${REST_HOST:${ANOTHER_REST_HOST:127.0.0.1}}`.
+In this case, if the `REST_HOST ` environment variable does not exist, but the ```REST_ANOTHER_REST_HOSTHOST```
+environment variable exists, and its value is `172.0.4.12`, then the value of `restHost` here will be overwritten to `172.0.4.12`;
+otherwise, it will be set to `127.0.0.1`.
diff --git a/docs/en/setup/backend/backend-setup.md b/docs/en/setup/backend/backend-setup.md
new file mode 100755
index 000000000000..8d95dcd732fe
--- /dev/null
+++ b/docs/en/setup/backend/backend-setup.md
@@ -0,0 +1,177 @@
+# Backend setup
+SkyWalking's backend distribution package consists of the following parts:
+
+1. **bin/cmd scripts**: Located in the `/bin` folder. Includes startup Linux shell and Windows cmd scripts for the backend server and UI startup.
+
+2. **Backend config**: Located in the `/config` folder. Includes settings files of the backend, which are:
+ * `application.yml`
+ * `log4j.xml`
+ * `alarm-settings.yml`
+
+3. **Libraries of backend**: Located in the `/oap-libs` folder. All dependencies of the backend can be found there.
+
+4. **Webapp env**: Located in the `webapp` folder. UI frontend jar file can be found here, together with its `webapp.yml` setting file.
+
+## Requirements and default settings
+
+Requirement: **Java 11/17/21**.
+
+You should set up the database ready before starting the backend. We recommend to use BanyanDB.
+If you want to use other databases, please read the [storage document](backend-storage.md).
+
+Use the docker mode to run BanyanDB containerized.
+```shell
+# The compatible version number could be found in /config/bydb.dependencies.properties
+export BYDB_VERSION=xxx
+
+docker pull apache/skywalking-banyandb:${BYDB_VERSION}
+
+docker run -d \
+ -p 17912:17912 \
+ -p 17913:17913 \
+ --name banyandb \
+ apache/skywalking-banyandb:${BYDB_VERSION} \
+ standalone
+```
+
+You can use `bin/startup.sh` (or cmd) to start up the OAP server and UI with their default settings,
+OAP listens on `0.0.0.0/11800` for gRPC APIs and `0.0.0.0/12800` for HTTP APIs.
+
+In Java, DotNetCore, Node.js, and Istio agents/probes, you should set the gRPC service address to `ip/host:11800`, and IP/host should be where your OAP is.
+
+UI listens on `8080` port and request `127.0.0.1/12800` to run a GraphQL query.
+
+### Interaction
+
+Before deploying Skywalking in your distributed environment, you should learn about how agents/probes, the backend, and the UI communicate with each other:
+
+
+
+- Most native agents and probes, including language-based or mesh probes, use gRPC service (`core/default/gRPC*` in `application.yml`) to report data to the backend. Also, the REST service is supported in JSON format.
+- UI uses GraphQL (HTTP) query to access the backend, also in REST service (`core/default/rest*` in `application.yml`).
+
+
+## Startup script
+The default startup scripts are `/bin/oapService.sh`(.bat).
+Read the [start up mode](backend-start-up-mode.md) document to learn other ways to start up the backend.
+
+
+### Key Parameters In The Booting Logs
+After the OAP booting process completed, you should be able to see all important parameters listed in the logs.
+
+```
+2023-11-06 21:10:45,988 org.apache.skywalking.oap.server.starter.OAPServerBootstrap 67 [main] INFO [] - The key booting parameters of Apache SkyWalking OAP are listed as following.
+
+Running Mode | null
+TTL.metrics | 7
+TTL.record | 3
+Version | 9.7.0-SNAPSHOT-92af797
+module.agent-analyzer.provider | default
+module.ai-pipeline.provider | default
+module.alarm.provider | default
+module.aws-firehose.provider | default
+module.cluster.provider | standalone
+module.configuration-discovery.provider | default
+module.configuration.provider | none
+module.core.provider | default
+module.envoy-metric.provider | default
+module.event-analyzer.provider | default
+module.log-analyzer.provider | default
+module.logql.provider | default
+module.promql.provider | default
+module.query.provider | graphql
+module.receiver-browser.provider | default
+module.receiver-clr.provider | default
+module.receiver-ebpf.provider | default
+module.receiver-event.provider | default
+module.receiver-jvm.provider | default
+module.receiver-log.provider | default
+module.receiver-meter.provider | default
+module.receiver-otel.provider | default
+module.receiver-profile.provider | default
+module.receiver-register.provider | default
+module.receiver-sharing-server.provider | default
+module.receiver-telegraf.provider | default
+module.receiver-trace.provider | default
+module.service-mesh.provider | default
+module.storage.provider | h2
+module.telemetry.provider | none
+oap.external.grpc.host | 0.0.0.0
+oap.external.grpc.port | 11800
+oap.external.http.host | 0.0.0.0
+oap.external.http.port | 12800
+oap.internal.comm.host | 0.0.0.0
+oap.internal.comm.port | 11800
+```
+
+- `oap.external.grpc.host`:`oap.external.grpc.port` is for reporting telemetry data through gRPC channel, including
+ native agents, OTEL.
+- `oap.external.http.host`:`oap.external.http.port` is for reporting telemetry data through HTTP channel and query,
+ including native GraphQL(UI), PromQL, LogQL.
+- `oap.internal.comm.host`:`oap.internal.comm.port` is for OAP cluster internal communication via gRPC/HTTP2 protocol.
+ The default host(`0.0.0.0`) is not suitable for the cluster mode, unless in k8s deployment. Please
+ read [Cluster Doc](backend-cluster.md) to understand how to set up the SkyWalking backend in the cluster mode.
+
+## application.yml
+SkyWalking backend startup behaviours are driven by `config/application.yml`. Understanding the settings file will help you read this document.
+
+The core concept behind this setting file is that the SkyWalking collector is based on a pure modular design.
+End-users can switch or assemble the collector features according to their unique requirements.
+
+In `application.yml`, there are three levels.
+1. **Level 1**: Module name. This means that this module is active in running mode.
+1. **Level 2**: Provider option list and provider selector. Available providers are listed here with a selector to indicate which one will actually take effect. If only one provider is listed, the `selector` is optional and can be omitted.
+1. **Level 3**. Settings of the chosen provider.
+
+Example:
+
+```yaml
+storage:
+ selector: banyandb # the banyandb storage will actually be activated.
+ mysql:
+ properties:
+ jdbcUrl: ${SW_JDBC_URL:"jdbc:mysql://localhost:3306/swtest?allowMultiQueries=true"}
+ dataSource.user: ${SW_DATA_SOURCE_USER:root}
+ dataSource.password: ${SW_DATA_SOURCE_PASSWORD:root@1234}
+ dataSource.cachePrepStmts: ${SW_DATA_SOURCE_CACHE_PREP_STMTS:true}
+ dataSource.prepStmtCacheSize: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_SIZE:250}
+ dataSource.prepStmtCacheSqlLimit: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_LIMIT:2048}
+ dataSource.useServerPrepStmts: ${SW_DATA_SOURCE_USE_SERVER_PREP_STMTS:true}
+ metadataQueryMaxSize: ${SW_STORAGE_MYSQL_QUERY_MAX_SIZE:5000}
+ banyandb:
+ targets: ${SW_STORAGE_BANYANDB_TARGETS:127.0.0.1:17912}
+ maxBulkSize: ${SW_STORAGE_BANYANDB_MAX_BULK_SIZE:10000}
+ flushInterval: ${SW_STORAGE_BANYANDB_FLUSH_INTERVAL:15}
+ flushTimeout: ${SW_STORAGE_BANYANDB_FLUSH_TIMEOUT:10}
+```
+
+1. **`storage`** is the module.
+1. **`selector`** selects one out of all providers listed below. The unselected ones take no effect as if they were deleted.
+1. **`default`** is the default implementor of the core module.
+1. `driver`, `url`, ... `metadataQueryMaxSize` are all setting items of the implementor.
+
+At the same time, there are two types of modules: required and optional. The required modules provide the skeleton of the backend.
+Even though their modular design supports pluggability, removing those modules does not serve any purpose. For optional modules, some of them have
+a provider implementation called `none`, meaning that it only provides a shell with no actual logic, typically such as telemetry.
+Setting `-` to the `selector` means that this whole module will be excluded at runtime.
+We advise against changing the APIs of those modules unless you understand the SkyWalking project and its codes very well.
+
+The required modules are listed here:
+1. **Core**. Provides the basic and major skeleton of all data analysis and stream dispatch.
+1. **Cluster**. Manages multiple backend instances in a cluster, which could provide high throughput process
+capabilities. See [**Cluster Management**](backend-cluster.md) for more details.
+1. **Storage**. Makes the analysis result persistent. See [**Choose storage**](backend-storage.md) for more details
+1. **Query**. Provides query interfaces to UI.
+1. **Receiver** and **Fetcher**. Expose the service to the agents and probes, or read telemetry data from a channel.
+
+## FAQs
+#### Why do we need to set the timezone? And when do we do it?
+SkyWalking provides downsampling time-series metrics features.
+Query and store at each time dimension (minute, hour, day, month metrics indexes)
+related to timezone when time formatting.
+
+For example, metrics time will be formatted like yyyyMMddHHmm in minute dimension metrics, which is timezone-related.
+
+By default, SkyWalking's OAP backend chooses the **OS default timezone**.
+Please follow the Java and OS documents if you want to override the timezone.
+
diff --git a/docs/en/setup/backend/backend-start-up-mode.md b/docs/en/setup/backend/backend-start-up-mode.md
new file mode 100644
index 000000000000..80432bf8873a
--- /dev/null
+++ b/docs/en/setup/backend/backend-start-up-mode.md
@@ -0,0 +1,19 @@
+# Start up mode
+You may need different startup modes in different deployment tools, such as k8s.
+We provide two additional optional startup modes.
+
+## Default mode
+The default mode carries out tasks to initialize as necessary, starts to listen, and provides services.
+
+Run `/bin/oapService.sh`(.bat) to start in this mode. This is also applicable when you're using `startup.sh`(.bat) to start.
+
+## Init mode
+In this mode, the OAP server starts up to carry out initialization and then exits.
+You could use this mode to initialize your storage (such as ElasticSearch indexes, MySQL, and TiDB tables) as well as your data.
+
+Run `/bin/oapServiceInit.sh`(.bat) to start in this mode.
+
+## No-init mode
+In this mode, the OAP server starts up without carrying out initialization. Rather, it watches out for the ElasticSearch indexes, MySQL, TiDB and other storage tables, starts listening and provides services. In other words, the OAP server would anticipate having another OAP server carrying out the initialization.
+
+Run `/bin/oapServiceNoInit.sh`(.bat) to start in this mode.
diff --git a/docs/en/setup/backend/backend-storage.md b/docs/en/setup/backend/backend-storage.md
new file mode 100644
index 000000000000..f878a3b7890a
--- /dev/null
+++ b/docs/en/setup/backend/backend-storage.md
@@ -0,0 +1,33 @@
+# Backend storage
+The SkyWalking storage is pluggable. We have provided the following storage solutions, which allow you to easily
+use one of them by specifying it as the `selector` in `application.yml`：
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:banyandb}
+```
+
+## BanyanDB - Native APM Database
+- [BanyanDB](storages/banyandb.md)
+
+BanyanDB is a native-built SkyWalking database, which can completely focus on SkyWalking use cases.
+It has demonstrated significant potential for performance improvement and reduced resource usage requirements. It indicates 5x less memory usage,
+1/5 disk IOPS, 1/4 disk throughput, and 30% less disk space, albeit with a slightly higher CPU trade-off, compared to Elasticsearch.
+
+## SQL database
+- [MySQL and its compatible databases](storages/mysql.md)
+- [PostgreSQL and its compatible databases](storages/postgresql.md)
+
+MySQL and PostgreSQL are recommended for production environments for medium-scale deployments, especially for low trace
+and log sampling rates. Some of their compatible databases may support larger scale better, such as TiDB and AWS Aurora.
+But the logs and traces performance could be significantly lower than BanyanDB and Elasticsearch, even more, their performance can't be improved linearly
+through scaling out nodes.
+
+## Elasticsearch+
+
+- [OpenSearch](storages/elasticsearch.md#opensearch)
+- [ElasticSearch 7 and 8](storages/elasticsearch.md#elasticsearch)
+
+Elasticsearch and OpenSearch are recommended for production environments, especially for large-scale deployments.
+OpenSearch derived from Elasticsearch 7.10.2 and iterates by its own roadmap. But notice, Elasticsearch cluster resource costs are high,
+due to its high requirement for memory and replication requirement to keep cluster robustness.
diff --git a/docs/en/setup/backend/backend-telemetry.md b/docs/en/setup/backend/backend-telemetry.md
new file mode 100644
index 000000000000..7308b79728ac
--- /dev/null
+++ b/docs/en/setup/backend/backend-telemetry.md
@@ -0,0 +1,144 @@
+# Telemetry for backend
+The OAP backend cluster itself is a distributed streaming process system. To assist the Ops team, we provide the telemetry for the OAP backend itself, also known as self-observability (so11y)
+
+By default, the telemetry is activated as setting `selector` to `prometheus`.
+
+```yaml
+telemetry:
+ selector: ${SW_TELEMETRY:prometheus}
+ none:
+ prometheus:
+ host: ${SW_TELEMETRY_PROMETHEUS_HOST:0.0.0.0}
+ port: ${SW_TELEMETRY_PROMETHEUS_PORT:1234}
+ sslEnabled: ${SW_TELEMETRY_PROMETHEUS_SSL_ENABLED:false}
+ sslKeyPath: ${SW_TELEMETRY_PROMETHEUS_SSL_KEY_PATH:""}
+ sslCertChainPath: ${SW_TELEMETRY_PROMETHEUS_SSL_CERT_CHAIN_PATH:""}
+```
+
+Besides the self observability, this supports [OAP circuit breaking](circuit-breaking.md) functionality.
+
+## Self Observability
+SkyWalking supports exposing telemetry data representing OAP running status through Prometheus endpoint.
+Users could set up OpenTelemetry collector to scrap and forward telemetry data to OAP server for further analysis,
+eventually showing up UI or GraphQL API.
+
+### Static IP or hostname
+Add the following configuration to enable self-observability-related modules.
+
+1. Set up prometheus telemetry.
+```yaml
+telemetry:
+ selector: ${SW_TELEMETRY:prometheus}
+ prometheus:
+ host: 127.0.0.1
+ port: 1543
+```
+
+2. Set up OpenTelemetry to scrape the metrics from OAP telemetry.
+
+Refer to [the E2E test case](../../../../test/e2e-v2/cases/so11y/otel-collector-config.yaml) as an example.
+
+For Kubernetes deployments, read the following section, otherwise you should be able to
+adjust the configurations below to fit your scenarios.
+
+### Service discovery on Kubernetes
+
+If you deploy an OAP server cluster on Kubernetes, the oap-server instance (pod) would not have a static IP or hostname. We can leverage [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/#kubernetes) to discover the oap-server instance, and scrape & transfer the metrics to OAP [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+On how to install SkyWalking on k8s, you can refer to [Apache SkyWalking Kubernetes](https://github.com/apache/skywalking-helm).
+
+Set this up following these steps:
+
+1. Set up oap-server.
+- Set the metrics port.
+ ```
+ prometheus-port: 1234
+ ```
+- Set environment variables.
+ ```
+ SW_TELEMETRY=prometheus
+ SW_OTEL_RECEIVER=default
+ SW_OTEL_RECEIVER_ENABLED_OTEL_METRICS_RULES=oap
+ ```
+
+ Here is an example to install by Apache SkyWalking Kubernetes:
+ ```
+ helm -n istio-system install skywalking skywalking \
+ --set elasticsearch.replicas=1 \
+ --set elasticsearch.minimumMasterNodes=1 \
+ --set elasticsearch.imageTag=7.5.1 \
+ --set oap.replicas=2 \
+ --set ui.image.repository=$HUB/skywalking-ui \
+ --set ui.image.tag=$TAG \
+ --set oap.image.tag=$TAG \
+ --set oap.image.repository=$HUB/skywalking-oap \
+ --set oap.storageType=elasticsearch \
+ --set oap.ports.prometheus-port=1234 \ # <<< Expose self observability metrics port
+ --set oap.env.SW_TELEMETRY=prometheus \
+ --set oap.env.SW_OTEL_RECEIVER=default \ # <<< Enable Otel receiver
+ --set oap.env.SW_OTEL_RECEIVER_ENABLED_OTEL_METRICS_RULES=oap # <<< Add oap analyzer for Otel metrics
+ ```
+2. Set up OpenTelemetry Collector and config a scrape job:
+``` yaml
+- job_name: 'skywalking-so11y' # make sure to use this in the so11y.yaml to filter only so11y metrics
+ metrics_path: '/metrics'
+ kubernetes_sd_configs:
+ - role: pod
+ relabel_configs:
+ - source_labels: [__meta_kubernetes_pod_container_name, __meta_kubernetes_pod_container_port_name]
+ action: keep
+ regex: oap;prometheus-port
+ - source_labels: []
+ target_label: service
+ replacement: oap-server
+ - source_labels: [__meta_kubernetes_pod_name]
+ target_label: host_name
+ regex: (.+)
+ replacement: $$1
+```
+For the full example for OpenTelemetry Collector configuration and recommended version, you can refer to [showcase](https://github.com/apache/skywalking-showcase/tree/main/deploy/platform/kubernetes/templates/feature-so11y).
+
+
+
+___
+
+Users also could leverage the Prometheus endpoint for their own Prometheus and Grafana.
+
+**NOTE**: Since Apr 21, 2021, the **Grafana** project has been relicensed to **AGPL-v3**, and is no longer licensed for Apache 2.0. Check the LICENSE details.
+The following Prometheus + Grafana solution is optional rather than recommended.
+
+## Prometheus
+Prometheus is supported as a telemetry implementor, which collects metrics from SkyWalking's backend.
+
+Set `prometheus` to provider. The endpoint opens at `http://0.0.0.0:1234/` and `http://0.0.0.0:1234/metrics`.
+```yaml
+telemetry:
+ selector: ${SW_TELEMETRY:prometheus}
+ prometheus:
+```
+
+Set host and port if needed.
+```yaml
+telemetry:
+ selector: ${SW_TELEMETRY:prometheus}
+ prometheus:
+ host: 127.0.0.1
+ port: 1543
+```
+
+Set relevant SSL settings to expose a secure endpoint. Note that the private key file and cert chain file could be uploaded once
+changes are applied to them.
+```yaml
+telemetry:
+ selector: ${SW_TELEMETRY:prometheus}
+ prometheus:
+ host: 127.0.0.1
+ port: 1543
+ sslEnabled: true
+ sslKeyPath: /etc/ssl/key.pem
+ sslCertChainPath: /etc/ssl/cert-chain.pem
+```
+
+### Grafana Visualization
+Provide the Grafana dashboard settings.
+Check [SkyWalking OAP Cluster Monitor Dashboard](grafana-cluster.json) config and [SkyWalking OAP Instance Monitor Dashboard](grafana-instance.json) config.
diff --git a/docs/en/setup/backend/backend-token-auth.md b/docs/en/setup/backend/backend-token-auth.md
new file mode 100644
index 000000000000..591e60dbb3ef
--- /dev/null
+++ b/docs/en/setup/backend/backend-token-auth.md
@@ -0,0 +1,42 @@
+# Token Authentication
+## Supported version
+7.0.0+
+
+## Why do we need token authentication after TLS?
+TLS is about transport security, ensuring a trusted network.
+On the other hand, token authentication is about monitoring **whether application data can be trusted**.
+
+## Token
+In the current version, a token is considered a simple string.
+
+### Set Token
+1. Set token in `agent.config` file
+```properties
+# Authentication active is based on backend setting, see application.yml for more details.
+agent.authentication = ${SW_AGENT_AUTHENTICATION:xxxx}
+```
+
+2. Set token in `application.yml` file
+```yaml
+······
+receiver-sharing-server:
+ default:
+ authentication: ${SW_AUTHENTICATION:""}
+······
+```
+
+## Authentication failure
+The Skywalking OAP verifies every request from the agent and only allows requests whose token matches the one configured in `application.yml` to pass through.
+
+If the token does not match, you will see the following log in the agent:
+```
+org.apache.skywalking.apm.dependencies.io.grpc.StatusRuntimeException: PERMISSION_DENIED
+```
+
+## FAQ
+### Can I use token authentication instead of TLS?
+No, you shouldn't. Of course, it's technically possible, but token and TLS are used for untrusted network environments. In these circumstances,
+TLS has a higher priority. Tokens can be trusted only under TLS protection, and they can be easily stolen if sent through a non-TLS network.
+
+### Do you support other authentication mechanisms, such as ak/sk?
+Not for now. But we welcome contributions to this feature.
diff --git a/docs/en/setup/backend/backend-trace-profiling.md b/docs/en/setup/backend/backend-trace-profiling.md
new file mode 100644
index 000000000000..4689e8582af4
--- /dev/null
+++ b/docs/en/setup/backend/backend-trace-profiling.md
@@ -0,0 +1,102 @@
+# Trace Profiling
+
+Trace Profiling is bound within the auto-instrument agent and corresponds to [In-Process Profiling](../../concepts-and-designs/profiling.md#in-process-profiling).
+
+It is delivered to the agent in the form of a task, allowing for dynamic enabling or disabling.
+Trace Profiling tasks can be created when an `endpoint` within a service experiences high latency.
+When the agent receives the task, it periodically samples the thread stack related to the endpoint when requested.
+Once the sampling is complete, the thread stack within the endpoint can be analyzed to determine the specific line of business code causing the performance issue.
+
+Lean more about the trace profiling, [please read this blog](../../concepts-and-designs/sdk-profiling.md).
+
+## Active in the OAP
+OAP and the agent use a brand-new protocol to exchange Trace Profiling data, so it is necessary to start OAP with the following configuration:
+
+```yaml
+receiver-profile:
+ selector: ${SW_RECEIVER_PROFILE:default}
+ default:
+```
+
+## Trace Profiling Task with Analysis
+
+To use the Trace Profiling feature, please follow these steps:
+
+1. **Create profiling task**: Use the UI or CLI tool to create a task.
+2. **Generate requests**: Ensure that the service has generated requests.
+3. **Query task details**: Check that the created task has Trace data generated.
+4. **Analyze the data**: Analyze the Trace data to determine where performance bottlenecks exist in the service.
+
+### Create profiling task
+
+Creating a Trace Profiling task is used to notify all agent nodes that execute the service entity which endpoint needs to perform the Trace Profiling feature.
+This Endpoint is typically an HTTP request or an RPC request address.
+
+When creating a task, the following configuration fields are required:
+
+1. **Service**: Which agent under the service needs to be monitored.
+2. **Endpoint**: The specific endpoint name, such as "POST:/path/to/request."
+3. **Start Time**: The start time of the task, which can be executed immediately or at a future time.
+4. **Duration**: The duration of the task execution.
+5. **Min Duration Threshold**: The monitoring will only be triggered when the specified endpoint's execution time exceeds this threshold. This effectively prevents the collection of ineffective data due to short execution times.
+6. **Dump Period**: The thread stack collection period, which will trigger thread sampling every specified number of milliseconds.
+7. **Max Sampling Count**: The maximum number of traces that can be collected in a task. This effectively prevents the program execution from being affected by excessive trace sampling, such as the Stop The World situation in Java.
+
+When the Agent receives a Trace Profiling task from OAP, it automatically generates a log to notify that the task has been acknowledged. The log contains the following field information:
+
+1. **Instance**: The name of the instance where the Agent is located.
+2. **Type**: Supports "NOTIFIED" and "EXECUTION_FINISHED", with the current log displaying "NOTIFIED".
+3. **Time**: The time when the Agent received the task.
+
+### Generate Requests
+
+At this point, Tracing requests matching the specified Endpoint and other conditions would undergo Profiling.
+
+Notice, whether profiling is thread sensitive, it relies on the agent side implementation. The Java Agent already supports cross-thread requests, so when a request involves cross-thread operations, it would also be periodically sampled for thread stack.
+
+### Query task details
+
+Once the Tracing request is completed, we can query the Tracing data associated with this Trace Profiling task, which includes the following information:
+
+1. **TraceId**: The Trace ID of the current request.
+2. **Instance**: The instance to which the current profiling data belongs.
+3. **Duration**: The total time taken by the current instance to process the Tracing request.
+4. **Spans**: The list of Spans associated with the current Tracing.
+ 1. **SpanId**: The ID of the current span.
+ 2. **Parent Span Id**: The ID of the parent span, allowing for a tree structure.
+ 3. **SegmentId**: The ID of the segment to which the span belongs.
+ 4. **Refs**: References of the current span, note that it only includes "CROSS_THREAD" type references.
+ 5. **Service**: The service entity information to which the current span belongs.
+ 6. **Instance**: The instance entity information to which the current span belongs.
+ 7. **Time**: The start and end time of the current span.
+ 8. **Endpoint Name**: The name of the current Span.
+ 9. **Type**: The type of the current span, either "Entry", "Local", or "Exit".
+ 10. **Peer**: The remote network address.
+ 11. **Component**: The name of the component used by the current span.
+ 12. **Layer**: The layer to which the current span belongs.
+ 13. **Tags**: The tags information contained in the current span.
+ 14. **Logs**: The log information in the current span.
+ 15. **Profiled**: Whether the current span supports Profiling data analysis.
+
+### Analyze the data
+
+Once we know which segments can be analyzed for profiling, we can then determine the time ranges available for thread stack analysis based on the "profiled" field in the span. Next, we can provide the following query content to analyze the data:
+
+1. **segmentId**: The segment to be analyzed. Segments are usually bound to individual threads, so we can determine which thread needs to be analyzed.
+2. **time range**: Includes the start and end time.
+
+By combining the segmentId with the time range, we can confirm the data for a specific thread during a specific time period.
+This allows us to merge the thread stack data from the specified thread and time range and analyze which lines of code take longer to execute.
+The following fields help you understand the program execution:
+1. **Id**: Used to identify the current thread stack frame.
+2. **Parent Id**: Combined with "id" to determine the hierarchical relationship.
+3. **Code Signature**: The method signature of the current thread stack frame.
+4. **Duration**: The total time consumed by the current thread stack frame.
+5. **Duration Child Excluded**: Excludes the child method calls of the current method, only obtaining the time consumed by the current method.
+6. **Count**: The number of times the current thread stack frame was sampled.
+
+If you want to learn more about the thread stack merging mechanism, please read [this documentation](backend-profile-thread-merging.md).
+
+## Exporter
+
+If you find that the results of profiling data are not correct, you can report an issue through [this documentation](../../guides/backend-profile-export.md).
\ No newline at end of file
diff --git a/docs/en/setup/backend/backend-vm-monitoring.md b/docs/en/setup/backend/backend-vm-monitoring.md
new file mode 100644
index 000000000000..cf0da6cf6b0f
--- /dev/null
+++ b/docs/en/setup/backend/backend-vm-monitoring.md
@@ -0,0 +1,57 @@
+# Linux Monitoring
+SkyWalking leverages Prometheus node-exporter to collect metrics data from the VMs and leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+VM entity as a `Service` in OAP and on the `Layer: OS_LINUX`.
+
+SkyWalking also provides InfluxDB Telegraf to receive VMs' metrics data by [Telegraf receiver](./telegraf-receiver.md).
+The telegraf receiver plugin receiver, process and convert the metrics, then it send converted metrics to [Meter System](./../../concepts-and-designs/mal.md).
+VM entity as a `Service` in OAP and on the `Layer: OS_LINUX`.
+
+## Data flow
+**For OpenTelemetry receiver:**
+1. The Prometheus node-exporter collects metrics data from the VMs.
+2. The OpenTelemetry Collector fetches metrics from node-exporter via Prometheus Receiver and pushes metrics to the SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+**For Telegraf receiver:**
+1. The InfluxDB Telegraf [input plugins](https://docs.influxdata.com/telegraf/v1.24/plugins/) collects various metrics data from the VMs.
+2. The cpu, mem, system, disk and diskio input plugins should be set in telegraf.conf file.
+2. The InfluxDB Telegraf send `JSON` format metrics by `HTTP` messages to Telegraf Receiver, then pushes converted metrics to the SkyWalking OAP Server [Meter System](./../../concepts-and-designs/mal.md).
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate ad store the results.
+4. The meter_vm_cpu_average_used metrics indicates the average usage of each CPU core for telegraf receiver.
+
+## Setup
+**For OpenTelemetry receiver:**
+1. Setup [Prometheus node-exporter](https://prometheus.io/docs/guides/node-exporter/).
+2. Setup [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/). This is an example for OpenTelemetry Collector configuration [otel-collector-config.yaml](../../../../test/e2e-v2/cases/vm/prometheus-node-exporter/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+**For Telegraf receiver:**
+1. Setup InfluxDB Telegraf's `telegraf.conf file` according to [Telegraf office document](https://docs.influxdata.com/telegraf/v1.24/).
+2. Setup InfluxDB Telegraf's `telegraf.conf file` specific rules according to [Telegraf receiver document](telegraf-receiver.md).
+3. Config SkyWalking [Telegraf receiver](telegraf-receiver.md).
+
+## Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------------------|------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------------------|
+| CPU Usage | % | meter_vm_cpu_total_percentage | The total percentage usage of the CPU core. If there are 2 cores, the maximum usage is 200%. | Prometheus node-exporter
Telegraf input plugin |
+| Memory RAM Usage | MB | meter_vm_memory_used | The total RAM usage | Prometheus node-exporter
Telegraf input plugin |
+| Memory Swap Usage | % | meter_vm_memory_swap_percentage | The percentage usage of swap memory | Prometheus node-exporter
Telegraf input plugin |
+| CPU Average Used | % | meter_vm_cpu_average_used | The percentage usage of the CPU core in each mode | Prometheus node-exporter
Telegraf input plugin |
+| CPU Load | | meter_vm_cpu_load1
meter_vm_cpu_load5
meter_vm_cpu_load15 | The CPU 1m / 5m / 15m average load | Prometheus node-exporter
Telegraf input plugin |
+| Memory RAM | MB | meter_vm_memory_total
meter_vm_memory_available
meter_vm_memory_used
meter_vm_memory_buff_cache | The RAM statistics, including Total / Available / Used / Buff-Cache | Prometheus node-exporter
Telegraf input plugin |
+| Memory Swap | MB | meter_vm_memory_swap_free
meter_vm_memory_swap_total | Swap memory statistics, including Free / Total | Prometheus node-exporter
Telegraf input plugin |
+| File System Mountpoint Usage | % | meter_vm_filesystem_percentage | The percentage usage of the file system at each mount point | Prometheus node-exporter
Telegraf input plugin |
+| Disk R/W | KB/s | meter_vm_disk_read
meter_vm_disk_written | The disk read and written | Prometheus node-exporter
Telegraf input plugin |
+| Network Bandwidth Usage | KB/s | meter_vm_network_receive
meter_vm_network_transmit | The network receive and transmit | Prometheus node-exporter
Telegraf input plugin |
+| Network Status | | meter_vm_tcp_curr_estab
meter_vm_tcp_tw
meter_vm_tcp_alloc
meter_vm_sockets_used
meter_vm_udp_inuse | The number of TCPs established / TCP time wait / TCPs allocated / sockets in use / UDPs in use | Prometheus node-exporter
Telegraf input plugin |
+| Filefd Allocated | | meter_vm_filefd_allocated | The number of file descriptors allocated | Prometheus node-exporter |
+
+## Customizing
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/vm.yaml` and `/config/telegraf-rules/vm.yaml`.
+The dashboard panel confirmations are found in `/config/ui-initialized-templates/os_linux`.
+
+## Blog
+For more details, see the blog article [SkyWalking 8.4 provides infrastructure monitoring](https://skywalking.apache.org/blog/2021-02-07-infrastructure-monitoring/).
diff --git a/docs/en/setup/backend/backend-win-monitoring.md b/docs/en/setup/backend/backend-win-monitoring.md
new file mode 100644
index 000000000000..b1392f3226d0
--- /dev/null
+++ b/docs/en/setup/backend/backend-win-monitoring.md
@@ -0,0 +1,34 @@
+# Windows Monitoring
+SkyWalking leverages Prometheus windows_exporter to collect metrics data from the Windows and leverages OpenTelemetry Collector to transfer the metrics to
+[OpenTelemetry receiver](opentelemetry-receiver.md) and into the [Meter System](./../../concepts-and-designs/mal.md).
+Windows entity as a `Service` in OAP and on the `Layer: OS_WINDOWS`.
+
+## Data flow
+**For OpenTelemetry receiver:**
+1. The Prometheus windows_exporter collects metrics data from the VMs.
+2. The OpenTelemetry Collector fetches metrics from windows_exporter via Prometheus Receiver and pushes metrics to the SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Setup
+**For OpenTelemetry receiver:**
+1. Setup [Prometheus windows_exporter](https://github.com/prometheus-community/windows_exporter).
+2. Setup [OpenTelemetry Collector ](https://opentelemetry.io/docs/collector/). This is an example for OpenTelemetry Collector configuration [otel-collector-config.yaml](../../../../test/e2e-v2/cases/win/prometheus-windows_exporter/otel-collector-config.yaml).
+3. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------------------|------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------------------|
+| CPU Usage | % | meter_win_cpu_total_percentage | The total percentage usage of the CPU core. If there are 2 cores, the maximum usage is 200%. | Prometheus windows_exporter |
+| Memory RAM Usage | MB | meter_win_memory_used | The total RAM usage | Prometheus windows_exporter |
+| Virtual-Memory Usage | % | meter_win_memory_virtual_memory_percentage | The percentage usage of virtual memeory memory | Prometheus windows_exporter |
+| CPU Average Used | % | meter_win_cpu_average_used | The percentage usage of the CPU core in each mode | Prometheus windows_exporter |
+| Memory RAM | MB | meter_win_memory_total
meter_win_memory_available
meter_win_memory_used | The RAM statistics, including Total / Available / Used | Prometheus windows_exporter |
+| Virtual-Memroy | MB | meter_win_memory_virtual_memory_free
meter_win_memory_virtual_memory_total | Virtual memory statistics, including Free / Total | Prometheus windows_exporter | | The percentage usage of the file system at each mount point | Prometheus windows_exporter |
+| Disk R/W | KB/s | meter_win_disk_read,meter_win_disk_written | The disk read and written | Prometheus windows_exporter |
+| Network Bandwidth Usage | KB/s | meter_win_network_receive
meter_win_network_transmit | The network receive and transmit | Prometheus windows_exporter | | The number of file descriptors allocated | Prometheus windows_exporter |
+
+## Customizing
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/otel-rules/windows.yaml`.
+The dashboard panel confirmations are found in `/config/ui-initialized-templates/os_windows`.
diff --git a/docs/en/setup/backend/backend-zabbix.md b/docs/en/setup/backend/backend-zabbix.md
new file mode 100644
index 000000000000..1ee46a092362
--- /dev/null
+++ b/docs/en/setup/backend/backend-zabbix.md
@@ -0,0 +1,77 @@
+# Zabbix Receiver
+The Zabbix receiver accepts metrics of [Zabbix Agent Active Checks protocol](https://www.zabbix.com/documentation/current/manual/appendix/items/activepassive#active_checks) format into the [Meter System](./../../concepts-and-designs/mal.md).
+Zabbix Agent is based on GPL-2.0 License, only version `6.x` and below are supported.
+
+## Module definition
+```yaml
+receiver-zabbix:
+ selector: ${SW_RECEIVER_ZABBIX:default}
+ default:
+ # Export tcp port, Zabbix agent could connected and transport data
+ port: 10051
+ # Bind to host
+ host: 0.0.0.0
+ # Enable config when receive agent request
+ activeFiles: agent
+```
+
+## Configuration file
+The Zabbix receiver is configured via a configuration file that defines everything related to receiving
+ from agents, as well as which rule files to load.
+
+The OAP can load the configuration at bootstrap. If the new configuration is not well-formed, the OAP fails to start up. The files
+are located at `$CLASSPATH/zabbix-rules`.
+
+The file is written in YAML format, defined by the scheme described below. Square brackets indicate that a parameter is optional.
+
+An example for Zabbix agent configuration could be found [here](../../../../test/e2e-v2/cases/vm/zabbix/zabbix_agentd.conf).
+You can find details on Zabbix agent items from [Zabbix Agent documentation](https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/zabbix_agent).
+
+### Configuration file
+
+```yaml
+# initExp is the expression that initializes the current configuration file
+initExp:
+# insert metricPrefix into metric name: _
+metricPrefix:
+# expPrefix is executed before the metrics executes other functions.
+expPrefix:
+# expSuffix is appended to all expression in this file.
+expSuffix:
+# Datasource from Zabbix Item keys.
+requiredZabbixItemKeys:
+ -
+# Support agent entities information.
+entities:
+ # Allow hostname patterns to build metrics.
+ hostPatterns:
+ -
+ # Customized metrics label before parse to meter system.
+ labels:
+ [- ]
+# Metrics rule allow you to recompute queries.
+metrics:
+ [ - ]
+```
+
+####
+
+```yaml
+# Define the label name. The label value must query from `value` or `fromItem` attribute.
+name:
+# Appoint value to label.
+[value: ]
+# Query label value from Zabbix Agent Item key.
+[fromItem: ]
+```
+
+####
+
+```yaml
+# The name of rule, which combinates with a prefix 'meter_' as the index/table name in storage.
+name:
+# MAL expression.
+exp:
+```
+
+For more on MAL, please refer to [mal.md](../../concepts-and-designs/mal.md).
diff --git a/docs/en/setup/backend/circuit-breaking.md b/docs/en/setup/backend/circuit-breaking.md
new file mode 100644
index 000000000000..fb687aeca0df
--- /dev/null
+++ b/docs/en/setup/backend/circuit-breaking.md
@@ -0,0 +1,20 @@
+# Circuit Breaking
+
+Circuit breaking is a mechanism used to detect failures and encapsulate the logic of preventing OAP node crashing. It is
+a key component of SkyWalking's resilience strategy. This approach protects the system from overload and ensures
+stability.
+
+Currently, there are two available strategies for circuit breaking: heap memory usage and direct memory pool size.
+
+```yaml
+# The int value of the max heap memory usage percent. The default value is 85%.
+maxHeapMemoryUsagePercent: ${SW_CORE_MAX_HEAP_MEMORY_USAGE_PERCENT:85}
+# The long value of the max direct memory usage. The default max value is -1, representing no limit. The unit is in bytes.
+maxDirectMemoryUsage: ${SW_CORE_MAX_DIRECT_MEMORY_USAGE:-1}
+```
+
+SkyWalking's circuit breaker mechanism actively rejects new telemetry data from gRPC.
+We keep HTTP services running to serve the UI and API, and Prometheus telemetry data is still available.
+
+Note, this feature relies on the `prometheus` provider in [Telemetry for backend](backend-telemetry.md) to monitor OAP
+server status.
\ No newline at end of file
diff --git a/docs/en/setup/backend/configuration-vocabulary.md b/docs/en/setup/backend/configuration-vocabulary.md
new file mode 100644
index 000000000000..6cea6ae44d54
--- /dev/null
+++ b/docs/en/setup/backend/configuration-vocabulary.md
@@ -0,0 +1,524 @@
+# Configuration Vocabulary
+
+The Configuration Vocabulary lists all available configurations provided by `application.yml`.
+
+## Main Configuration
+The main configuration is provided by `application.yml`.
+It divided into several modules, each of which has its own settings. The following table lists the modules and their settings.
+
+| Module | Provider | Settings | Value(s) and Explanation | System Environment Variable¹ | Default |
+|-------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------|
+| core | default | role | Option values: `Mixed/Receiver/Aggregator`. **Receiver** mode OAP opens the service to the agents, then analyzes and aggregates the results, and forwards the results for distributed aggregation. Aggregator mode OAP receives data from Mixer and Receiver role OAP nodes, and performs 2nd level aggregation. **Mixer** means both Receiver and Aggregator. | SW_CORE_ROLE | Mixed |
+| - | - | restHost | Binding IP of RESTful services. Services include GraphQL query and HTTP data report. | SW_CORE_REST_HOST | 0.0.0.0 |
+| - | - | restPort | Binding port of RESTful services. | SW_CORE_REST_PORT | 12800 |
+| - | - | restContextPath | Web context path of RESTful services. | SW_CORE_REST_CONTEXT_PATH | / |
+| - | - | restMaxThreads | Maximum thread number of RESTful services. | SW_CORE_REST_REST_MAX_THREADS | 200 |
+| - | - | restIdleTimeOut | Connector idle timeout of RESTful services (in milliseconds). | SW_CORE_REST_IDLE_TIMEOUT | 30000 |
+| - | - | restAcceptQueueSize | ServerSocketChannel Backlog of RESTful services. | SW_CORE_REST_QUEUE_SIZE | 0 |
+| - | - | httpMaxRequestHeaderSize | Maximum request header size accepted. | SW_CORE_HTTP_MAX_REQUEST_HEADER_SIZE | 8192 |
+| - | - | gRPCHost | Binding IP of gRPC services, including gRPC data report and internal communication among OAP nodes. | SW_CORE_GRPC_HOST | 0.0.0.0 |
+| - | - | gRPCPort | Binding port of gRPC services. | SW_CORE_GRPC_PORT | 11800 |
+| - | - | gRPCSslEnabled | Activates SSL for gRPC services. | SW_CORE_GRPC_SSL_ENABLED | false |
+| - | - | gRPCSslKeyPath | File path of gRPC SSL key. | SW_CORE_GRPC_SSL_KEY_PATH | - |
+| - | - | gRPCSslCertChainPath | File path of gRPC SSL cert chain. | SW_CORE_GRPC_SSL_CERT_CHAIN_PATH | - |
+| - | - | gRPCSslTrustedCAPath | File path of gRPC trusted CA. | SW_CORE_GRPC_SSL_TRUSTED_CA_PATH | - |
+| - | - | downsampling | Activated level of down sampling aggregation. | | Hour,Day |
+| - | - | enableDataKeeperExecutor | Controller of TTL scheduler. Once disabled, TTL wouldn't work. | SW_CORE_ENABLE_DATA_KEEPER_EXECUTOR | true |
+| - | - | dataKeeperExecutePeriod | Execution period of TTL scheduler (in minutes). Execution doesn't mean deleting data. The storage provider (e.g. ElasticSearch storage) could override this. | SW_CORE_DATA_KEEPER_EXECUTE_PERIOD | 5 |
+| - | - | recordDataTTL | The lifecycle of record data (in days). Record data includes traces, top N sample records, and logs. Minimum value is 2. | SW_CORE_RECORD_DATA_TTL | 3 |
+| - | - | metricsDataTTL | The lifecycle of metrics data (in days), including metadata. We recommend setting metricsDataTTL >= recordDataTTL. Minimum value is 2. | SW_CORE_METRICS_DATA_TTL | 7 |
+| - | - | l1FlushPeriod | The period of L1 aggregation flush to L2 aggregation (in milliseconds). | SW_CORE_L1_AGGREGATION_FLUSH_PERIOD | 500 |
+| - | - | storageSessionTimeout | The threshold of session time (in milliseconds). Default value is 70000. | SW_CORE_STORAGE_SESSION_TIMEOUT | 70000 |
+| - | - | persistentPeriod | The period of doing data persistence. Unit is second.Default value is 25s | SW_CORE_PERSISTENT_PERIOD | 25 |
+| - | - | topNReportPeriod | The execution period (in minutes) of top N sampler, which saves sampled data into the storage. | SW_CORE_TOPN_REPORT_PERIOD | 10 |
+| - | - | activeExtraModelColumns | Appends entity names (e.g. service names) into metrics storage entities. | SW_CORE_ACTIVE_EXTRA_MODEL_COLUMNS | false |
+| - | - | serviceNameMaxLength | Maximum length limit of service names. | SW_SERVICE_NAME_MAX_LENGTH | 70 |
+| - | - | instanceNameMaxLength | Maximum length limit of service instance names. The maximum length of service + instance names should be less than 200. | SW_INSTANCE_NAME_MAX_LENGTH | 70 |
+| - | - | endpointNameMaxLength | Maximum length limit of endpoint names. The maximum length of service + endpoint names should be less than 240. | SW_ENDPOINT_NAME_MAX_LENGTH | 150 |
+| - | - | searchableTracesTags | Defines a set of span tag keys which are searchable through GraphQL. Multiple values are separated by commas. The max length of key=value should be less than 256 or will be dropped. | SW_SEARCHABLE_TAG_KEYS | http.method,http.status_code,rpc.status_code,db.type,db.instance,mq.queue,mq.topic,mq.broker |
+| - | - | searchableLogsTags | Defines a set of log tag keys which are searchable through GraphQL. Multiple values are separated by commas. The max length of key=value should be less than 256 or will be dropped. | SW_SEARCHABLE_LOGS_TAG_KEYS | level |
+| - | - | searchableAlarmTags | Defines a set of alarm tag keys which are searchable through GraphQL. Multiple values are separated by commas. The max length of key=value should be less than 256 or will be dropped. | SW_SEARCHABLE_ALARM_TAG_KEYS | level |
+| - | - | autocompleteTagKeysQueryMaxSize | The max size of tags keys for autocomplete select. | SW_AUTOCOMPLETE_TAG_KEYS_QUERY_MAX_SIZE | 100 |
+| - | - | autocompleteTagValuesQueryMaxSize | The max size of tags values for autocomplete select. | SW_AUTOCOMPLETE_TAG_VALUES_QUERY_MAX_SIZE | 100 |
+| - | - | gRPCThreadPoolSize | Pool size of gRPC server. | SW_CORE_GRPC_THREAD_POOL_SIZE | Default to gRPC's implementation, which is a cached thread pool that can grow infinitely. |
+| - | - | maxConcurrentCallsPerConnection | The maximum number of concurrent calls permitted for each incoming connection. Defaults to no limit. | SW_CORE_GRPC_MAX_CONCURRENT_CALL | - |
+| - | - | maxMessageSize | Sets the maximum message size allowed to be received on the server. Empty means 4 MiB. | SW_CORE_GRPC_MAX_MESSAGE_SIZE | 52428800 (50MB) |
+| - | - | remoteTimeout | Timeout for cluster internal communication (in seconds). | - | 20 |
+| - | - | maxSizeOfNetworkAddressAlias | The maximum size of network address detected in the system being monitored. | - | 1_000_000 |
+| - | - | maxPageSizeOfQueryProfileSnapshot | The maximum size for snapshot analysis in an OAP query. | - | 500 |
+| - | - | maxSizeOfAnalyzeProfileSnapshot | The maximum number of snapshots analyzed by the OAP. | - | 12000 |
+| - | - | prepareThreads | The number of threads used to prepare metrics data to the storage. | SW_CORE_PREPARE_THREADS | 2 |
+| - | - | enableEndpointNameGroupingByOpenapi | Automatically groups endpoints by the given OpenAPI definitions. | SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI | true |
+| - | - | maxDurationOfQueryEBPFProfilingData | The maximum duration(in second) of query the eBPF profiling data from database. | - | 30 |
+| - | - | maxThreadCountOfQueryEBPFProfilingData | The maximum thread count of query the eBPF profiling data from database. | - | System CPU core size |
+| - | - | uiMenuRefreshInterval | The period(in seconds) of refreshing the status of all UI menu items. | - | 20 |
+| - | - | serviceCacheRefreshInterval | The period(in seconds) of refreshing the service cache. | SW_SERVICE_CACHE_REFRESH_INTERVAL | 10 |
+| - | - | enableHierarchy | If disable the hierarchy, the service and instance hierarchy relation will not be built. And the query of hierarchy will return empty result. All the hierarchy relations are defined in the `hierarchy-definition.yml`. Notice: some of the configurations only available for kubernetes environments. | SW_CORE_ENABLE_HIERARCHY | true |
+| - | - | maxHeapMemoryUsagePercent | The int value of the max heap memory usage percent. | SW_CORE_MAX_HEAP_MEMORY_USAGE_PERCENT | 96 (96%) |
+| - | - | maxDirectMemoryUsage | The long value of the max direct memory usage. The default max value is -1, representing no limit. The unit is in bytes. | SW_CORE_MAX_DIRECT_MEMORY_USAGE | -1 |
+| cluster | standalone | - | Standalone is not suitable for running on a single node running. No configuration available. | - | - |
+| - | zookeeper | namespace | The namespace, represented by root path, isolates the configurations in Zookeeper. | SW_NAMESPACE | `/`, root path |
+| - | - | hostPort | Hosts and ports of Zookeeper Cluster. | SW_CLUSTER_ZK_HOST_PORT | localhost:2181 |
+| - | - | baseSleepTimeMs | The period of Zookeeper client between two retries (in milliseconds). | SW_CLUSTER_ZK_SLEEP_TIME | 1000 |
+| - | - | maxRetries | The maximum retry time. | SW_CLUSTER_ZK_MAX_RETRIES | 3 |
+| - | - | enableACL | Opens ACL using `schema` and `expression`. | SW_ZK_ENABLE_ACL | false |
+| - | - | schema | Schema for the authorization. | SW_ZK_SCHEMA | digest |
+| - | - | expression | Expression for the authorization. | SW_ZK_EXPRESSION | skywalking:skywalking |
+| - | - | internalComHost | The hostname registered in Zookeeper for the internal communication of OAP cluster. | SW_CLUSTER_INTERNAL_COM_HOST | - |
+| - | - | internalComPort | The port registered in Zookeeper for the internal communication of OAP cluster. | SW_CLUSTER_INTERNAL_COM_PORT | -1 |
+| - | kubernetes | namespace | Namespace deployed by SkyWalking in k8s. | SW_CLUSTER_K8S_NAMESPACE | default |
+| - | - | labelSelector | Labels used for filtering OAP deployment in k8s. | SW_CLUSTER_K8S_LABEL | app=collector,release=skywalking |
+| - | - | uidEnvName | Environment variable name for reading uid. | SW_CLUSTER_K8S_UID | SKYWALKING_COLLECTOR_UID |
+| - | consul | serviceName | Service name for SkyWalking cluster. | SW_SERVICE_NAME | SkyWalking_OAP_Cluster |
+| - | - | hostPort | Hosts and ports for Consul cluster. | SW_CLUSTER_CONSUL_HOST_PORT | localhost:8500 |
+| - | - | aclToken | ACL Token of Consul. Empty string means `without ALC token`. | SW_CLUSTER_CONSUL_ACLTOKEN | - |
+| - | - | internalComHost | The hostname registered in Consul for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_HOST | - |
+| - | - | internalComPort | The port registered in Consul for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_PORT | -1 |
+| - | etcd | serviceName | Service name for SkyWalking cluster. | SW_CLUSTER_ETCD_SERVICE_NAME | SkyWalking_OAP_Cluster |
+| - | - | endpoints | Hosts and ports for etcd cluster. | SW_CLUSTER_ETCD_ENDPOINTS | localhost:2379 |
+| - | - | namespace | Namespace for SkyWalking cluster. | SW_CLUSTER_ETCD_NAMESPACE | /skywalking |
+| - | - | authentication | Indicates whether there is authentication. | SW_CLUSTER_ETCD_AUTHENTICATION | false |
+| - | - | user | Etcd auth username. | SW_CLUSTER_ETCD_USER | |
+| - | - | password | Etcd auth password. | SW_CLUSTER_ETCD_PASSWORD | |
+| - | - | internalComHost | The hostname registered in etcd for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_HOST | - |
+| - | - | internalComPort | The port registered in etcd for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_PORT | -1 |
+| - | Nacos | serviceName | Service name for SkyWalking cluster. | SW_SERVICE_NAME | SkyWalking_OAP_Cluster |
+| - | - | hostPort | Hosts and ports for Nacos cluster. | SW_CLUSTER_NACOS_HOST_PORT | localhost:8848 |
+| - | - | namespace | Namespace used by SkyWalking node coordination. | SW_CLUSTER_NACOS_NAMESPACE | public |
+| - | - | internalComHost | The hostname registered in Nacos for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_HOST | - |
+| - | - | internalComPort | The port registered in Nacos for internal communications of the OAP cluster. | SW_CLUSTER_INTERNAL_COM_PORT | -1 |
+| - | - | contextPath | Nacos set contextPath. | SW_CLUSTER_NACOS_CONTEXT_PATH | - |
+| - | - | username | Nacos Auth username. | SW_CLUSTER_NACOS_USERNAME | - |
+| - | - | password | Nacos Auth password. | SW_CLUSTER_NACOS_PASSWORD | - |
+| - | - | accessKey | Nacos Auth accessKey. | SW_CLUSTER_NACOS_ACCESSKEY | - |
+| - | - | secretKey | Nacos Auth secretKey. | SW_CLUSTER_NACOS_SECRETKEY | - |
+| - | - | syncPeriodHttpUriRecognitionPattern | The period of HTTP URI recognition pattern synchronization (in seconds). | SW_CORE_SYNC_PERIOD_HTTP_URI_RECOGNITION_PATTERN | 10 |
+| - | - | trainingPeriodHttpUriRecognitionPattern | The period of HTTP URI recognition pattern training (in seconds). | SW_CORE_TRAINING_PERIOD_HTTP_URI_RECOGNITION_PATTERN | 60 |
+| - | - | maxHttpUrisNumberPerService | The maximum number of HTTP URIs per service. | SW_MAX_HTTP_URIS_NUMBER_PER_SERVICE | 3000 | |
+| storage | elasticsearch | - | ElasticSearch (and OpenSearch) storage implementation. | - | - |
+| - | - | namespace | Prefix of indexes created and used by SkyWalking. | SW_NAMESPACE | - |
+| - | - | clusterNodes | ElasticSearch cluster nodes for client connection. | SW_STORAGE_ES_CLUSTER_NODES | localhost |
+| - | - | protocol | HTTP or HTTPs. | SW_STORAGE_ES_HTTP_PROTOCOL | HTTP |
+| - | - | connectTimeout | Connect timeout of ElasticSearch client (in milliseconds). | SW_STORAGE_ES_CONNECT_TIMEOUT | 3000 |
+| - | - | socketTimeout | Socket timeout of ElasticSearch client (in milliseconds). | SW_STORAGE_ES_SOCKET_TIMEOUT | 30000 |
+| - | - | responseTimeout | Response timeout of ElasticSearch client (in milliseconds), `0` disables the timeout. | SW_STORAGE_ES_RESPONSE_TIMEOUT | 15000 |
+| - | - | numHttpClientThread | The number of threads for the underlying HTTP client to perform socket I/O. If the value is <= 0, the number of available processors will be used. | SW_STORAGE_ES_NUM_HTTP_CLIENT_THREAD | 0 |
+| - | - | user | Username of ElasticSearch cluster. | SW_ES_USER | - |
+| - | - | password | Password of ElasticSearch cluster. | SW_ES_PASSWORD | - |
+| - | - | trustStorePath | Trust JKS file path. Only works when username and password are enabled. | SW_STORAGE_ES_SSL_JKS_PATH | - |
+| - | - | trustStorePass | Trust JKS file password. Only works when username and password are enabled. | SW_STORAGE_ES_SSL_JKS_PASS | - |
+| - | - | secretsManagementFile | Secrets management file in the properties format, including username and password, which are managed by a 3rd party tool. Capable of being updated them at runtime. | SW_ES_SECRETS_MANAGEMENT_FILE | - |
+| - | - | dayStep | Represents the number of days in the one-minute/hour/day index. | SW_STORAGE_DAY_STEP | 1 |
+| - | - | indexShardsNumber | Shard number of new indexes. | SW_STORAGE_ES_INDEX_SHARDS_NUMBER | 1 |
+| - | - | indexReplicasNumber | Replicas number of new indexes. | SW_STORAGE_ES_INDEX_REPLICAS_NUMBER | 0 |
+| - | - | specificIndexSettings | Specify the settings for each index individually. If configured, this setting has the highest priority and overrides the generic settings. | SW_STORAGE_ES_SPECIFIC_INDEX_SETTINGS | - |
+| - | - | superDatasetDayStep | Represents the number of days in the super size dataset record index. Default value is the same as dayStep when the value is less than 0. | SW_STORAGE_ES_SUPER_DATASET_DAY_STEP | -1 |
+| - | - | superDatasetIndexShardsFactor | Super dataset is defined in the code (e.g. trace segments). This factor provides more shards for the super dataset: shards number = indexShardsNumber * superDatasetIndexShardsFactor. This factor also affects Zipkin and Jaeger traces. | SW_STORAGE_ES_SUPER_DATASET_INDEX_SHARDS_FACTOR | 5 |
+| - | - | superDatasetIndexReplicasNumber | Represents the replicas number in the super size dataset record index. | SW_STORAGE_ES_SUPER_DATASET_INDEX_REPLICAS_NUMBER | 0 |
+| - | - | indexTemplateOrder | The order of index template. | SW_STORAGE_ES_INDEX_TEMPLATE_ORDER | 0 |
+| - | - | bulkActions | Async bulk size of the record data batch execution. | SW_STORAGE_ES_BULK_ACTIONS | 5000 |
+| - | - | batchOfBytes | A threshold to control the max body size of ElasticSearch Bulk flush. | SW_STORAGE_ES_BATCH_OF_BYTES | 10485760 (10m) |
+| - | - | flushInterval | Period of flush (in seconds). Does not matter whether `bulkActions` is reached or not. | SW_STORAGE_ES_FLUSH_INTERVAL | 5 |
+| - | - | concurrentRequests | The number of concurrent requests allowed to be executed. | SW_STORAGE_ES_CONCURRENT_REQUESTS | 2 |
+| - | - | resultWindowMaxSize | The maximum size of dataset when the OAP loads cache, such as network aliases. | SW_STORAGE_ES_QUERY_MAX_WINDOW_SIZE | 10000 |
+| - | - | metadataQueryMaxSize | The maximum size of metadata per query. | SW_STORAGE_ES_QUERY_MAX_SIZE | 10000 |
+| - | - | scrollingBatchSize | The batch size of metadata per iteration when `metadataQueryMaxSize` or `resultWindowMaxSize` is too large to be retrieved in a single query. | SW_STORAGE_ES_SCROLLING_BATCH_SIZE | 5000 |
+| - | - | segmentQueryMaxSize | The maximum size of trace segments per query. | SW_STORAGE_ES_QUERY_SEGMENT_SIZE | 200 |
+| - | - | profileTaskQueryMaxSize | The maximum size of profile task per query. | SW_STORAGE_ES_QUERY_PROFILE_TASK_SIZE | 200 |
+| - | - | asyncProfilerTaskQueryMaxSize | The maximum size of async-profiler task per query. | SW_STORAGE_ES_QUERY_ASYNC_PROFILER_TASK_SIZE | 200 |
+| - | - | profileDataQueryScrollBatchSize | The batch size of query profiling data. | SW_STORAGE_ES_QUERY_PROFILE_DATA_BATCH_SIZE | 100 |
+| - | - | advanced | All settings of ElasticSearch index creation. The value should be in JSON format. | SW_STORAGE_ES_ADVANCED | - |
+| - | - | logicSharding | Shard metrics and records indices into multi-physical indices, one index template per metric/meter aggregation function or record. | SW_STORAGE_ES_LOGIC_SHARDING | false |
+| - | mysql | - | MySQL Storage. The MySQL JDBC Driver is not in the dist. Please copy it into the oap-lib folder manually. | - | - |
+| - | - | properties | Hikari connection pool configurations. | - | Listed in the `application.yaml`. |
+| - | - | metadataQueryMaxSize | The maximum size of metadata per query. | SW_STORAGE_MYSQL_QUERY_MAX_SIZE | 5000 |
+| - | - | maxSizeOfBatchSql | The maximum size of batch size of SQL execution | SW_STORAGE_MAX_SIZE_OF_BATCH_SQL | 2000 |
+| - | - | asyncBatchPersistentPoolSize | async flush data into database thread size | SW_STORAGE_ASYNC_BATCH_PERSISTENT_POOL_SIZE | 4 |
+| - | postgresql | - | PostgreSQL storage. | - | - |
+| - | - | properties | Hikari connection pool configurations. | - | Listed in the `application.yaml`. |
+| - | - | metadataQueryMaxSize | The maximum size of metadata per query. | SW_STORAGE_MYSQL_QUERY_MAX_SIZE | 5000 |
+| - | - | maxSizeOfBatchSql | The maximum size of batch size of SQL execution | SW_STORAGE_MAX_SIZE_OF_BATCH_SQL | 2000 |
+| - | - | asyncBatchPersistentPoolSize | async flush data into database thread size | SW_STORAGE_ASYNC_BATCH_PERSISTENT_POOL_SIZE | 4 |
+| - | banyandb | - | BanyanDB storage, since 10.2.0, the [banyandb configuration](#banyandb-configuration) is separated to an independent configuration file: `bydb.yaml`. | - | - |
+| agent-analyzer | default | Agent Analyzer. | SW_AGENT_ANALYZER | default | |
+| - | - | traceSamplingPolicySettingsFile | The sampling policy including `sampling rate` and `the threshold of trace segment latency` can be configured by the `traceSamplingPolicySettingsFile` file. | SW_TRACE_SAMPLING_POLICY_SETTINGS_FILE | `trace-sampling-policy-settings.yml` |
+| - | - | slowDBAccessThreshold | The slow database access threshold (in milliseconds). | SW_SLOW_DB_THRESHOLD | default:200,mongodb:100 |
+| - | - | forceSampleErrorSegment | When sampling mechanism is activated, this config samples the error status segment and ignores the sampling rate. | SW_FORCE_SAMPLE_ERROR_SEGMENT | true |
+| - | - | segmentStatusAnalysisStrategy | Determines the final segment status from span status. Available values are `FROM_SPAN_STATUS` , `FROM_ENTRY_SPAN`, and `FROM_FIRST_SPAN`. `FROM_SPAN_STATUS` indicates that the segment status would be error if any span has an error status. `FROM_ENTRY_SPAN` means that the segment status would only be determined by the status of entry spans. `FROM_FIRST_SPAN` means that the segment status would only be determined by the status of the first span. | SW_SEGMENT_STATUS_ANALYSIS_STRATEGY | FROM_SPAN_STATUS |
+| - | - | noUpstreamRealAddressAgents | Exit spans with the component in the list would not generate client-side instance relation metrics, since some tracing plugins (e.g. Nginx-LUA and Envoy) can't collect the real peer IP address. | SW_NO_UPSTREAM_REAL_ADDRESS | 6000,9000 |
+| - | - | meterAnalyzerActiveFiles | Indicates which files could be instrumented and analyzed. Multiple files are split by ",". | SW_METER_ANALYZER_ACTIVE_FILES | | |
+| - | - | slowCacheWriteThreshold | The threshold of slow command which is used for writing operation (in milliseconds). | SW_SLOW_CACHE_WRITE_THRESHOLD | `default:20,redis:10` |
+| - | - | slowCacheReadThreshold | The threshold of slow command which is used for reading (getting) operation (in milliseconds). | SW_SLOW_CACHE_READ_THRESHOLD | `default:20,redis:10` |
+| receiver-sharing-server | default | Sharing server provides new gRPC and restful servers for data collection. Ana designates that servers in the core module are to be used for internal communication only. | - | - | |
+| - | - | restHost | Binding IP of RESTful services. Services include GraphQL query and HTTP data report. | SW_RECEIVER_SHARING_REST_HOST | - |
+| - | - | restPort | Binding port of RESTful services. | SW_RECEIVER_SHARING_REST_PORT | - |
+| - | - | restContextPath | Web context path of RESTful services. | SW_RECEIVER_SHARING_REST_CONTEXT_PATH | - |
+| - | - | restMaxThreads | Maximum thread number of RESTful services. | SW_RECEIVER_SHARING_REST_MAX_THREADS | 200 |
+| - | - | restIdleTimeOut | Connector idle timeout of RESTful services (in milliseconds). | SW_RECEIVER_SHARING_REST_IDLE_TIMEOUT | 30000 |
+| - | - | restAcceptQueueSize | ServerSocketChannel backlog of RESTful services. | SW_RECEIVER_SHARING_REST_QUEUE_SIZE | 0 |
+| - | - | httpMaxRequestHeaderSize | Maximum request header size accepted. | SW_RECEIVER_SHARING_HTTP_MAX_REQUEST_HEADER_SIZE | 8192 |
+| - | - | gRPCHost | Binding IP of gRPC services. Services include gRPC data report and internal communication among OAP nodes. | SW_RECEIVER_GRPC_HOST | 0.0.0.0. Not Activated |
+| - | - | gRPCPort | Binding port of gRPC services. | SW_RECEIVER_GRPC_PORT | Not Activated |
+| - | - | gRPCThreadPoolSize | Pool size of gRPC server. | SW_RECEIVER_GRPC_THREAD_POOL_SIZE | Default to gRPC's implementation, which is a cached thread pool that can grow infinitely. |
+| - | - | gRPCSslEnabled | Activates SSL for gRPC services. | SW_RECEIVER_GRPC_SSL_ENABLED | false |
+| - | - | gRPCSslKeyPath | File path of gRPC SSL key. | SW_RECEIVER_GRPC_SSL_KEY_PATH | - |
+| - | - | gRPCSslCertChainPath | File path of gRPC SSL cert chain. | SW_RECEIVER_GRPC_SSL_CERT_CHAIN_PATH | - |
+| - | - | maxConcurrentCallsPerConnection | The maximum number of concurrent calls permitted for each incoming connection. Defaults to no limit. | SW_RECEIVER_GRPC_MAX_CONCURRENT_CALL | - |
+| - | - | maxMessageSize | Sets the maximum message size allowed to be received on the server. Empty means 4 MiB. | SW_RECEIVER_GRPC_MAX_MESSAGE_SIZE | 52428800 (50MB) |
+| - | - | authentication | The token text for authentication. Works for gRPC connection only. Once this is set, the client is required to use the same token. | SW_AUTHENTICATION | - |
+| log-analyzer | default | Log Analyzer. | SW_LOG_ANALYZER | default | |
+| - | - | lalFiles | The LAL configuration file names (without file extension) to be activated. Read [LAL](../../concepts-and-designs/lal.md) for more details. | SW_LOG_LAL_FILES | default |
+| - | - | malFiles | The MAL configuration file names (without file extension) to be activated. Read [LAL](../../concepts-and-designs/lal.md) for more details. | SW_LOG_MAL_FILES | "" |
+| event-analyzer | default | Event Analyzer. | SW_EVENT_ANALYZER | default | |
+| receiver-register | default | gRPC and HTTPRestful services that provide service, service instance and endpoint register. | - | - | |
+| receiver-trace | default | gRPC and HTTPRestful services that accept SkyWalking format traces. | - | - | |
+| receiver-jvm | default | gRPC services that accept JVM metrics data. | - | - | |
+| receiver-clr | default | gRPC services that accept .Net CLR metrics data. | - | - | |
+| receiver-profile | default | gRPC services that accept profile task status and snapshot reporter. | - | - | |
+| receiver-zabbix | default | TCP receiver accepts Zabbix format metrics. | - | - | |
+| - | - | port | Exported TCP port. Zabbix agent could connect and transport data. | SW_RECEIVER_ZABBIX_PORT | 10051 |
+| - | - | host | Binds to host. | SW_RECEIVER_ZABBIX_HOST | 0.0.0.0 |
+| - | - | activeFiles | Enables config when agent request is received. | SW_RECEIVER_ZABBIX_ACTIVE_FILES | agent |
+| service-mesh | default | gRPC services that accept data from inbound mesh probes. | - | - | |
+| envoy-metric | default | Envoy `metrics_service` and `ALS(access log service)` are supported by this receiver. The OAL script supports all GAUGE type metrics. | - | - | |
+| - | - | acceptMetricsService | Starts Envoy Metrics Service analysis. | SW_ENVOY_METRIC_SERVICE | true |
+| - | - | alsHTTPAnalysis | Starts Envoy HTTP Access Log Service analysis. Value = `k8s-mesh` means starting the analysis. | SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS | - |
+| - | - | alsTCPAnalysis | Starts Envoy TCP Access Log Service analysis. Value = `k8s-mesh` means starting the analysis. | SW_ENVOY_METRIC_ALS_TCP_ANALYSIS | - |
+| - | - | k8sServiceNameRule | `k8sServiceNameRule` allows you to customize the service name in ALS via Kubernetes metadata. The available variables are `pod` and `service`. E.g. you can use `${service.metadata.name}-${pod.metadata.labels.version}` to append the version number to the service name. Note that when using environment variables to pass this configuration, use single quotes(`''`) to avoid being evaluated by the shell. | K8S_SERVICE_NAME_RULE | ${pod.metadata.labels.(service.istio.io/canonical-name)}.${pod.metadata.namespace} |
+| - | - | istioServiceNameRule | `istioServiceNameRule` allows you to customize the service name in ALS via Kubernetes metadata. The available variables are `serviceEntry`. E.g. you can use `${serviceEntry.metadata.name}-${serviceEntry.metadata.labels.version}` to append the version number to the service name. Note that when using environment variables to pass this configuration, use single quotes(`''`) to avoid being evaluated by the shell. | ISTIO_SERVICE_NAME_RULE | ${serviceEntry.metadata.name}.${serviceEntry.metadata.namespace} |
+| - | - | istioServiceEntryIgnoredNamespaces | When looking up service informations from the Istio ServiceEntries, some of the ServiceEntries might be created in several namespaces automatically by some components, and OAP will randomly pick one of them to build the service name, users can use this config to exclude ServiceEntries that they don't want to be used. Comma separated. | SW_ISTIO_SERVICE_ENTRY_IGNORED_NAMESPACES | - |
+| - | - | gRPCHost | Binding IP of gRPC service for Envoy access log service. | SW_ALS_GRPC_HOST | 0.0.0.0. Not Activated |
+| - | - | gRPCPort | Binding port of gRPC service for Envoy access log service. | SW_ALS_GRPC_PORT | Not Activated |
+| - | - | gRPCThreadPoolSize | Pool size of gRPC server. | SW_ALS_GRPC_THREAD_POOL_SIZE | Default to gRPC's implementation, which is a cached thread pool that can grow infinitely. |
+| - | - | gRPCSslEnabled | Activates SSL for gRPC services. | SW_ALS_GRPC_SSL_ENABLED | false |
+| - | - | gRPCSslKeyPath | File path of gRPC SSL key. | SW_ALS_GRPC_SSL_KEY_PATH | - |
+| - | - | gRPCSslCertChainPath | File path of gRPC SSL cert chain. | SW_ALS_GRPC_SSL_CERT_CHAIN_PATH | - |
+| - | - | maxConcurrentCallsPerConnection | The maximum number of concurrent calls permitted for each incoming connection. Defaults to no limit. | SW_ALS_GRPC_MAX_CONCURRENT_CALL | - |
+| - | - | maxMessageSize | Sets the maximum message size allowed to be received on the server. Empty means 4 MiB. | SW_ALS_GRPC_MAX_MESSAGE_SIZE | 4M(based on Netty) |
+| receiver-otel | default | A receiver for analyzing metrics data from OpenTelemetry. | - | - | |
+| - | - | enabledHandlers | Enabled handlers for otel. | SW_OTEL_RECEIVER_ENABLED_HANDLERS | - |
+| - | - | enabledOtelMetricsRules | Enabled metric rules for OTLP handler. | SW_OTEL_RECEIVER_ENABLED_OTEL_METRICS_RULES | - |
+| receiver-zipkin | default | A receiver for Zipkin traces. | - | - | |
+| - | - | sampleRate | The sample rate precision is 1/10000, should be between 0 and 10000 | SW_ZIPKIN_SAMPLE_RATE | 10000 |
+| - | - | searchableTracesTags | Defines a set of span tag keys which are searchable. Multiple values are separated by commas. The max length of key=value should be less than 256 or will be dropped. | SW_ZIPKIN_SEARCHABLE_TAG_KEYS | http.method |
+| - | - | enableHttpCollector | Enable Http Collector. | SW_ZIPKIN_HTTP_COLLECTOR_ENABLED | true |
+| - | - | restHost | Binding IP of RESTful services. | SW_RECEIVER_ZIPKIN_REST_HOST | 0.0.0.0 |
+| - | - | restPort | Binding port of RESTful services. | SW_RECEIVER_ZIPKIN_REST_PORT | 9411 |
+| - | - | restContextPath | Web context path of RESTful services. | SW_RECEIVER_ZIPKIN_REST_CONTEXT_PATH | / |
+| - | - | restMaxThreads | Maximum thread number of RESTful services. | SW_RECEIVER_ZIPKIN_REST_MAX_THREADS | 200 |
+| - | - | restIdleTimeOut | Connector idle timeout of RESTful services (in milliseconds). | SW_RECEIVER_ZIPKIN_REST_IDLE_TIMEOUT | 30000 |
+| - | - | restAcceptQueueSize | Maximum request header size accepted. | SW_RECEIVER_ZIPKIN_REST_QUEUE_SIZE | 0 |
+| - | - | enableKafkaCollector | Enable Kafka Collector. | SW_ZIPKIN_KAFKA_COLLECTOR_ENABLED | false |
+| - | - | kafkaBootstrapServers | Kafka ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG. | SW_ZIPKIN_KAFKA_SERVERS | localhost:9092 |
+| - | - | kafkaGroupId | Kafka ConsumerConfig.GROUP_ID_CONFIG. | SW_ZIPKIN_KAFKA_GROUP_ID | zipkin |
+| - | - | kafkaTopic | Kafka Topics. | SW_ZIPKIN_KAFKA_TOPIC | zipkin |
+| - | - | kafkaConsumerConfig | Kafka consumer config, JSON format as Properties. If it contains the same key with above, would override. | SW_ZIPKIN_KAFKA_CONSUMER_CONFIG | "{\"auto.offset.reset\":\"earliest\",\"enable.auto.commit\":true}" |
+| - | - | kafkaConsumers | The number of consumers to create. | SW_ZIPKIN_KAFKA_CONSUMERS | 1 |
+| - | - | kafkaHandlerThreadPoolSize | Pool size of Kafka message handler executor. | SW_ZIPKIN_KAFKA_HANDLER_THREAD_POOL_SIZE | CPU core * 2 |
+| - | - | kafkaHandlerThreadPoolQueueSize | Queue size of Kafka message handler executor. | SW_ZIPKIN_KAFKA_HANDLER_THREAD_POOL_QUEUE_SIZE | 10000 |
+| kafka-fetcher | default | Read SkyWalking's native metrics/logs/traces through Kafka server. | - | - | |
+| - | - | bootstrapServers | A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. | SW_KAFKA_FETCHER_SERVERS | localhost:9092 |
+| - | - | namespace | Namespace aims to isolate multi OAP cluster when using the same Kafka cluster. If you set a namespace for Kafka fetcher, OAP will add a prefix to topic name. You should also set namespace in `agent.config`. The property is named `plugin.kafka.namespace`. | SW_NAMESPACE | - |
+| - | - | groupId | A unique string that identifies the consumer group to which this consumer belongs. | - | skywalking-consumer |
+| - | - | partitions | The number of partitions for the topic being created. | SW_KAFKA_FETCHER_PARTITIONS | 3 |
+| - | - | consumers | The number of consumers to create. | SW_KAFKA_FETCHER_CONSUMERS | 1 |
+| - | - | enableNativeProtoLog | Enables fetching and handling native proto log data. | SW_KAFKA_FETCHER_ENABLE_NATIVE_PROTO_LOG | true |
+| - | - | enableNativeJsonLog | Enables fetching and handling native json log data. | SW_KAFKA_FETCHER_ENABLE_NATIVE_JSON_LOG | true |
+| - | - | replicationFactor | The replication factor for each partition in the topic being created. | SW_KAFKA_FETCHER_PARTITIONS_FACTOR | 2 |
+| - | - | kafkaHandlerThreadPoolSize | Pool size of Kafka message handler executor. | SW_KAFKA_HANDLER_THREAD_POOL_SIZE | CPU core * 2 |
+| - | - | kafkaHandlerThreadPoolQueueSize | Queue size of Kafka message handler executor. | SW_KAFKA_HANDLER_THREAD_POOL_QUEUE_SIZE | 10000 |
+| - | - | topicNameOfMeters | Kafka topic name for meter system data. | - | skywalking-meters |
+| - | - | topicNameOfMetrics | Kafka topic name for JVM metrics data. | - | skywalking-metrics |
+| - | - | topicNameOfProfiling | Kafka topic name for profiling data. | - | skywalking-profilings |
+| - | - | topicNameOfTracingSegments | Kafka topic name for tracing data. | - | skywalking-segments |
+| - | - | topicNameOfManagements | Kafka topic name for service instance reporting and registration. | - | skywalking-managements |
+| - | - | topicNameOfLogs | Kafka topic name for native proto log data. | - | skywalking-logs |
+| - | - | topicNameOfJsonLogs | Kafka topic name for native json log data. | - | skywalking-logs-json |
+| cilium-fetcher | default | Read Cilium Observe protocol data to collect Cilium Service status. | - | - | |
+| - | - | peerHost | The Cilium Peer Service Host. | SW_CILIUM_FETCHER_PEER_HOST | hubble-peer.kube-system.svc.cluster.local |
+| - | - | peerPort | The Cilium Peer Service Port. | SW_CILIUM_FETCHER_PEER_PORT | 80 |
+| - | - | fetchFailureRetrySecond | The Cilium fetch observe data failure retry interval(second). | SW_CILIUM_FETCHER_FETCH_FAILURE_RETRY_SECOND | 10 |
+| - | - | sslConnection | The Cilium fetch protocol is TLS enabled or not. | eSW_CILIUM_FETCHER_SSL_CONNECTION | false |
+| - | - | sslPrivateKeyFile | The Cilium TLS fetch private key file path. | SW_CILIUM_FETCHER_PRIVATE_KEY_FILE_PATH | "" |
+| - | - | sslCertChainFile | The Cilium TLS fetch cert chain file path. | SW_CILIUM_FETCHER_CERT_CHAIN_FILE_PATH | "" |
+| - | - | sslCaFile | The Cilium TLS fetch rot CA Certification file path. | SW_CILIUM_FETCHER_CA_FILE_PATH | "" |
+| - | - | convertClientAsServerTraffic | The Cilium flow data should convert client to the server side not. If convert, then the server side flow would be ignored. | SW_CILIUM_FETCHER_CONVERT_CLIENT_AS_SERVER_TRAFFIC | true |
+| receiver-browser | default | gRPC services that accept browser performance data and error log. | - | - | - |
+| - | - | sampleRate | Sampling rate for receiving trace. Precise to 1/10000. 10000 means sampling rate of 100% by default. | SW_RECEIVER_BROWSER_SAMPLE_RATE | 10000 |
+| query | graphql | - | GraphQL query implementation. | - | |
+| - | - | enableLogTestTool | Enable the log testing API to test the LAL. **NOTE**: This API evaluates untrusted code on the OAP server. A malicious script can do significant damage (steal keys and secrets, remove files and directories, install malware, etc). As such, please enable this API only when you completely trust your users. | SW_QUERY_GRAPHQL_ENABLE_LOG_TEST_TOOL | false |
+| - | - | maxQueryComplexity | Maximum complexity allowed for the GraphQL query that can be used to abort a query if the total number of data fields queried exceeds the defined threshold. | SW_QUERY_MAX_QUERY_COMPLEXITY | 3000 |
+| - | - | enableUpdateUITemplate | Allow user add，disable and update UI template. | SW_ENABLE_UPDATE_UI_TEMPLATE | false |
+| - | - | enableOnDemandPodLog | Ondemand Pod log: fetch the Pod logs on users' demand, the logs are fetched and displayed in real time, and are not persisted in any kind. This is helpful when users want to do some experiments and monitor the logs and see what's happing inside the service. Note: if you print secrets in the logs, they are also visible to the UI, so for the sake of security, this feature is disabled by default, please set this configuration to enable the feature manually. | SW_ENABLE_ON_DEMAND_POD_LOG | false |
+| query-zipkin | default | - | This module is for Zipkin query API and support zipkin-lens UI | - | |
+| - | - | restHost | Binding IP of RESTful services. | SW_QUERY_ZIPKIN_REST_HOST | 0.0.0.0 |
+| - | - | restPort | Binding port of RESTful services. | SW_QUERY_ZIPKIN_REST_PORT | 9412 |
+| - | - | restContextPath | Web context path of RESTful services. | SW_QUERY_ZIPKIN_REST_CONTEXT_PATH | zipkin |
+| - | - | restMaxThreads | Maximum thread number of RESTful services. | SW_QUERY_ZIPKIN_REST_MAX_THREADS | 200 |
+| - | - | restIdleTimeOut | Connector idle timeout of RESTful services (in milliseconds). | SW_QUERY_ZIPKIN_REST_IDLE_TIMEOUT | 30000 |
+| - | - | restAcceptQueueSize | Maximum request header size accepted. | SW_QUERY_ZIPKIN_REST_QUEUE_SIZE | 0 |
+| - | - | lookback | Default look back for traces and autocompleteTags, 1 day in millis | SW_QUERY_ZIPKIN_LOOKBACK | 86400000 |
+| - | - | namesMaxAge | The Cache-Control max-age (seconds) for serviceNames, remoteServiceNames and spanNames | SW_QUERY_ZIPKIN_NAMES_MAX_AGE | 300 |
+| - | - | uiQueryLimit | Default traces query max size | SW_QUERY_ZIPKIN_UI_QUERY_LIMIT | 10 |
+| - | - | uiDefaultLookback | Default look back on the UI for search traces, 15 minutes in millis | SW_QUERY_ZIPKIN_UI_DEFAULT_LOOKBACK | 900000 |
+| promql | default | - | This module is for PromQL API. | - | |
+| - | - | restHost | Binding IP of RESTful services. | SW_PROMQL_REST_HOST | 0.0.0.0 |
+| - | - | restPort | Binding port of RESTful services. | SW_PROMQL_REST_PORT | 9090 |
+| - | - | restContextPath | Web context path of RESTful services. | SW_PROMQL_REST_CONTEXT_PATH | / |
+| - | - | restMaxThreads | Maximum thread number of RESTful services. | SW_PROMQL_REST_MAX_THREADS | 200 |
+| - | - | restIdleTimeOut | Connector idle timeout of RESTful services (in milliseconds). | SW_PROMQL_REST_IDLE_TIMEOUT | 30000 |
+| - | - | restAcceptQueueSize | Maximum request header size accepted. | SW_PROMQL_REST_QUEUE_SIZE | 0 |
+| - | - | buildInfoVersion | Mock version for API buildInfo | SW_PROMQL_BUILD_INFO_VERSION | 2.45.0 |
+| - | - | buildInfoRevision | Mock revision for API buildInfo | SW_PROMQL_BUILD_INFO_REVISION | |
+| - | - | buildInfoBranch | Mock branch for API buildInfo | SW_PROMQL_BUILD_INFO_BRANCH | |
+| - | - | buildInfoBuildUser | Mock build user for API buildInfo | SW_PROMQL_BUILD_INFO_BUILD_USER | |
+| - | - | buildInfoBuildDate | Mock build date for API buildInfo | SW_PROMQL_BUILD_INFO_BUILD_DATE | |
+| - | - | buildInfoGoVersion | Mock go version for API buildInfo | SW_PROMQL_BUILD_INFO_GO_VERSION | |
+| alarm | default | - | Read [alarm doc](backend-alarm.md) for more details. | - | |
+| telemetry | - | - | Read [telemetry doc](backend-telemetry.md) for more details. | - | |
+| - | none | - | No op implementation. | - | |
+| - | prometheus | host | Binding host for Prometheus server fetching data. | SW_TELEMETRY_PROMETHEUS_HOST | 0.0.0.0 |
+| - | - | port | Binding port for Prometheus server fetching data. | SW_TELEMETRY_PROMETHEUS_PORT | 1234 |
+| configuration | - | - | Read [dynamic configuration doc](dynamic-config.md) for more details. | - | |
+| - | grpc | host | DCS server binding hostname. | SW_DCS_SERVER_HOST | - |
+| - | - | port | DCS server binding port. | SW_DCS_SERVER_PORT | 80 |
+| - | - | clusterName | Cluster name when reading the latest configuration from DSC server. | SW_DCS_CLUSTER_NAME | SkyWalking |
+| - | - | period | The period of reading data from DSC server by the OAP (in seconds). | SW_DCS_PERIOD | 20 |
+| - | - | maxInboundMessageSize | The max inbound message size of gRPC. | SW_DCS_MAX_INBOUND_MESSAGE_SIZE | 4194304 |
+| - | apollo | apolloMeta | `apollo.meta` in Apollo. | SW_CONFIG_APOLLO | http://localhost:8080 |
+| - | - | apolloCluster | `apollo.cluster` in Apollo. | SW_CONFIG_APOLLO_CLUSTER | default |
+| - | - | apolloEnv | `env` in Apollo. | SW_CONFIG_APOLLO_ENV | - |
+| - | - | appId | `app.id` in Apollo. | SW_CONFIG_APOLLO_APP_ID | skywalking |
+| - | zookeeper | namespace | The namespace (represented by root path) that isolates the configurations in the Zookeeper. | SW_CONFIG_ZK_NAMESPACE | `/`, root path |
+| - | - | hostPort | Hosts and ports of Zookeeper Cluster. | SW_CONFIG_ZK_HOST_PORT | localhost:2181 |
+| - | - | baseSleepTimeMs | The period of Zookeeper client between two retries (in milliseconds). | SW_CONFIG_ZK_BASE_SLEEP_TIME_MS | 1000 |
+| - | - | maxRetries | The maximum retry time. | SW_CONFIG_ZK_MAX_RETRIES | 3 |
+| - | - | period | The period of data sync (in seconds). | SW_CONFIG_ZK_PERIOD | 60 |
+| - | etcd | endpoints | Hosts and ports for etcd cluster (separated by commas if multiple). | SW_CONFIG_ETCD_ENDPOINTS | http://localhost:2379 |
+| - | - | namespace | Namespace for SkyWalking cluster. | SW_CONFIG_ETCD_NAMESPACE | /skywalking |
+| - | - | authentication | Indicates whether there is authentication. | SW_CONFIG_ETCD_AUTHENTICATION | false |
+| - | - | user | Etcd auth username. | SW_CONFIG_ETCD_USER | |
+| - | - | password | Etcd auth password. | SW_CONFIG_ETCD_PASSWORD | |
+| - | - | period | The period of data sync (in seconds). | SW_CONFIG_ZK_PERIOD | 60 |
+| - | consul | hostPort | Hosts and ports for Consul cluster. | SW_CONFIG_CONSUL_HOST_AND_PORTS | localhost:8500 |
+| - | - | aclToken | ACL Token of Consul. Empty string means `without ACL token`. | SW_CONFIG_CONSUL_ACL_TOKEN | - |
+| - | - | period | The period of data sync (in seconds). | SW_CONFIG_CONSUL_PERIOD | 60 |
+| - | k8s-configmap | namespace | Deployment namespace of the config map. | SW_CLUSTER_K8S_NAMESPACE | default |
+| - | - | labelSelector | Labels for locating configmap. | SW_CLUSTER_K8S_LABEL | app=collector,release=skywalking |
+| - | - | period | The period of data sync (in seconds). | SW_CONFIG_ZK_PERIOD | 60 |
+| - | nacos | serverAddr | Nacos Server Host. | SW_CONFIG_NACOS_SERVER_ADDR | 127.0.0.1 |
+| - | - | port | Nacos Server Port. | SW_CONFIG_NACOS_SERVER_PORT | 8848 |
+| - | - | group | Nacos Configuration namespace. | SW_CONFIG_NACOS_SERVER_NAMESPACE | - |
+| - | - | period | The period of data sync (in seconds). | SW_CONFIG_CONFIG_NACOS_PERIOD | 60 |
+| - | - | username | Nacos Auth username. | SW_CONFIG_NACOS_USERNAME | - |
+| - | - | password | Nacos Auth password. | SW_CONFIG_NACOS_PASSWORD | - |
+| - | - | accessKey | Nacos Auth accessKey. | SW_CONFIG_NACOS_ACCESSKEY | - |
+| - | - | secretKey | Nacos Auth secretKey. | SW_CONFIG_NACOS_SECRETKEY | - |
+| exporter | default | enableGRPCMetrics | Enable gRPC metrics exporter. | SW_EXPORTER_ENABLE_GRPC_METRICS | false |
+| - | - | gRPCTargetHost | The host of target gRPC server for receiving export data | SW_EXPORTER_GRPC_HOST | 127.0.0.1 |
+| - | - | gRPCTargetPort | The port of target gRPC server for receiving export data. | SW_EXPORTER_GRPC_PORT | 9870 |
+| - | - | enableKafkaTrace | Enable Kafka trace exporter. | SW_EXPORTER_ENABLE_KAFKA_TRACE | false |
+| - | - | enableKafkaLog | Enable Kafka log exporter. | SW_EXPORTER_ENABLE_KAFKA_LOG | false |
+| - | - | kafkaBootstrapServers | A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. | SW_EXPORTER_KAFKA_SERVERS | localhost:9092 |
+| - | - | kafkaProducerConfig | Kafka producer config, JSON format as Properties. | SW_EXPORTER_KAFKA_PRODUCER_CONFIG | - |
+| - | - | kafkaTopicTrace | Kafka topic name for trace. | SW_EXPORTER_KAFKA_TOPIC_TRACE | skywalking-export-trace |
+| - | - | kafkaTopicLog | Kafka topic name for log. | SW_EXPORTER_KAFKA_TOPIC_LOG | skywalking-export-log |
+| - | - | exportErrorStatusTraceOnly | Export error status trace segments through the Kafka channel. | SW_EXPORTER_KAFKA_TRACE_FILTER_ERROR | false |
+| health-checker | default | checkIntervalSeconds | The period of checking OAP internal health status (in seconds). | SW_HEALTH_CHECKER_INTERVAL_SECONDS | 5 |
+| status-query | default | | | | |
+| - | - | keywords4MaskingSecretsOfConfig | Include the list of keywords to filter configurations including secrets. Separate keywords by a comma. | SW_DEBUGGING_QUERY_KEYWORDS_FOR_MASKING_SECRETS | user,password,token,accessKey,secretKey,authentication |
+| configuration-discovery | default | disableMessageDigest | If true, agent receives the latest configuration every time, even without making any changes. By default, OAP uses the SHA512 message digest mechanism to detect changes in configuration. | SW_DISABLE_MESSAGE_DIGEST | false |
+| receiver-event | default | gRPC services that handle events data. | - | - | |
+| aws-firehose-receiver | default | host | Binding IP of HTTP server | SW_RECEIVER_AWS_FIREHOSE_HTTP_HOST | 0.0.0.0 |
+| - | - | port | Binding port of HTTP server | SW_RECEIVER_AWS_FIREHOSE_HTTP_PORT | 12801 |
+| - | - | contextPath | Context path of HTTP server | SW_RECEIVER_AWS_FIREHOSE_HTTP_CONTEXT_PATH | / |
+| - | - | maxThreads | Max Thread number of HTTP server | SW_RECEIVER_AWS_FIREHOSE_HTTP_MAX_THREADS | 200 |
+| - | - | idleTimeOut | Idle timeout of a connection for keep-alive. | SW_RECEIVER_AWS_FIREHOSE_HTTP_IDLE_TIME_OUT | 30000 |
+| - | - | acceptQueueSize | Maximum allowed number of open connections | SW_RECEIVER_AWS_FIREHOSE_HTTP_ACCEPT_QUEUE_SIZE | 0 |
+| - | - | maxRequestHeaderSize | Maximum length of all headers in an HTTP/1 response | SW_RECEIVER_AWS_FIREHOSE_HTTP_MAX_REQUEST_HEADER_SIZE | 8192 |
+| - | - | firehoseAccessKey | The AccessKey of AWS firhose | SW_RECEIVER_AWS_FIREHOSE_ACCESS_KEY | |
+| - | - | enableTLS | Indicate if enable HTTPS for the server | SW_RECEIVER_AWS_FIREHOSE_HTTP_ENABLE_TLS | false |
+| - | - | tlsKeyPath | TLS key path | SW_RECEIVER_AWS_FIREHOSE_HTTP_TLS_KEY_PATH | |
+| - | - | tlsCertChainPath | TLS certificate chain path | SW_RECEIVER_AWS_FIREHOSE_HTTP_TLS_CERT_CHAIN_PATH | |
+| ai-pipeline | default | | | |
+| - | - | uriRecognitionServerAddr | The address of the URI recognition server. | SW_AI_PIPELINE_URI_RECOGNITION_SERVER_ADDR | - |
+| - | - | uriRecognitionServerPort | The port of the URI recognition server. | SW_AI_PIPELINE_URI_RECOGNITION_SERVER_PORT | 17128 |
+| - | - | baselineServerAddr | The address of the Baseline server. | SW_API_PIPELINE_BASELINE_SERVICE_HOST | - |
+| - | - | baselineServerPort | The port of the Baseline server. | SW_API_PIPELINE_BASELINE_SERVICE_PORT | 17128 |
+| receiver-async-profiler | default | gRPC services that accept async-profiler task status and data reporter. | - | - | |
+| - | - | jfrMaxSize | Used to manage the maximum size of the jfr file that can be received, the unit is Byte, default is 30M. | SW_RECEIVER_ASYNC_PROFILER_JFR_MAX_SIZE | 31457280 |
+| - | - | memoryParserEnabled | Used to determine whether to receive jfr in memory file or physical file mode. | SW_RECEIVER_ASYNC_PROFILER_MEMORY_PARSER_ENABLED | true |
+
+## BanyanDB Configuration
+
+Since 10.2.0, the banyandb configuration is separated to an independent configuration file: `bydb.yaml`.
+The following table lists the configuration items:
+
+### Global Configuration
+The global settings for the whole BanyanDB:
+
+| Settings | Value(s) and Explanation | System Environment Variable¹ | Default |
+|---------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------|
+| targets | Hosts with ports of the BanyanDB. | SW_STORAGE_BANYANDB_TARGETS | 127.0.0.1:17912 |
+| maxBulkSize | The maximum size of write entities in a single batch write call. | SW_STORAGE_BANYANDB_MAX_BULK_SIZE | 10000 |
+| flushInterval | Period of flush interval. In the timeunit of seconds. | SW_STORAGE_BANYANDB_FLUSH_INTERVAL | 15 |
+| flushTimeout | The timeout seconds of a bulk flush. | SW_STORAGE_BANYANDB_FLUSH_TIMEOUT | 10 |
+| concurrentWriteThreads | Concurrent consumer threads for batch writing. | SW_STORAGE_BANYANDB_CONCURRENT_WRITE_THREADS | 15 |
+| profileTaskQueryMaxSize | Max size of ProfileTask to be fetched. | SW_STORAGE_BANYANDB_PROFILE_TASK_QUERY_MAX_SIZE | 200 |
+| resultWindowMaxSize | The maximum size of dataset when the OAP loads cache, such as network aliases. | SW_STORAGE_BANYAND_QUERY_MAX_WINDOW_SIZE | 10000 |
+| metadataQueryMaxSize | The maximum size of metadata per query. | SW_STORAGE_BANYAND_QUERY_MAX_SIZE | 10000 |
+| segmentQueryMaxSize | The maximum size of trace segments per query. | SW_STORAGE_BANYAND_QUERY_SEGMENT_SIZE | 200 |
+| asyncProfilerTaskQueryMaxSize | Max size of AsyncProfilerTask to be fetched. | SW_STORAGE_BANYANDB_ASYNC_PROFILER_TASK_QUERY_MAX_SIZE | 200 |
+| profileDataQueryScrollBatchSize | The batch size of query profiling data. | SW_STORAGE_BANYAND_QUERY_PROFILE_DATA_BATCH_SIZE | 100 |
+| sslTrustCAPath | If the BanyanDB server is configured with TLS, config the TLS cert file path and open tls connection. | SW_STORAGE_BANYANDB_SSL_TRUST_CA_PATH | - |
+| cleanupUnusedTopNRules | Cleanup TopN rules in BanyanDB server that are not configured in the bydb-topn.yml config. | SW_STORAGE_BANYANDB_CLEANUP_UNUSED_TOPN_RULES | true |
+
+### Group Configuration
+The settings for each group:
+The `hot` stage is enabled by default for all groups.
+If the `warm` stage is enabled, the data will be moved to the `warm` stage after the TTL of the `hot` stage.
+If the `cold` stage is enabled and `warm` stage is disabled, the data will be moved to the `cold` stage after the TTL of the `hot` stage.
+If both `warm` and `cold` stages are enabled, the data will be moved to the `warm` stage after the TTL of the `hot` stage, and then to the `cold` stage after the TTL of the `warm` stage.
+OAP will query the data from the "hot and warm" stage by default if the "warm" stage is enabled.
+
+| Group | Settings | Stage Settings | Value(s) and Explanation | System Environment Variable¹ | Default |
+|------------------------|-----------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-----------|
+| records | - | - | The group for records not specified. Each normal dataset will be grouped under a single group named `records`. | - | - |
+| - | shardNum | - | Shards Number for normal records group. | SW_STORAGE_BANYANDB_RECORDS_SHARD_NUM | 1 |
+| - | segmentInterval | - | Segment Interval Days for normal records group. | SW_STORAGE_BANYANDB_RECORDS_SI_DAYS | 1 |
+| - | ttl | - | TTL Days for normal records group. | SW_STORAGE_BANYANDB_RECORDS_TTL_DAYS | 3 |
+| - | enableWarmStage | - | Activate warm stage for normal records group. | SW_STORAGE_BANYANDB_RECORDS_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage for normal records group. | SW_STORAGE_BANYANDB_RECORDS_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_RECORDS_WARM_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_RECORDS_WARM_SI_DAYS | 2 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_RECORDS_WARM_TTL_DAYS | 7 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_RECORDS_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_RECORDS_COLD_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_RECORDS_COLD_SI_DAYS | 3 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_RECORDS_COLD_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_RECORDS_COLD_NODE_SELECTOR | type=cold |
+| recordsTrace | - | - | | - | - |
+| - | shardNum | - | Shards Number for SkyWalking trace records group. | SW_STORAGE_BANYANDB_TRACE_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days. | SW_STORAGE_BANYANDB_TRACE_SI_DAYS | 1 |
+| - | ttl | - | TTL Days. | SW_STORAGE_BANYANDB_TRACE_TTL_DAYS | 3 |
+| - | enableWarmStage | - | Activate warm stage. | SW_STORAGE_BANYANDB_TRACE_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage. | SW_STORAGE_BANYANDB_TRACE_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_TRACE_WARM_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_TRACE_WARM_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_TRACE_WARM_TTL_DAYS | 7 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_TRACE_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_TRACE_COLD_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_TRACE_COLD_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_TRACE_COLD_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_TRACE_COLD_NODE_SELECTOR | type=cold |
+| recordsZipkinTrace | - | - | | - | - |
+| - | shardNum | - | Shards Number for Zipkin trace records group. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_SI_DAYS | 1 |
+| - | ttl | - | TTL Days. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_TTL_DAYS | 3 |
+| - | enableWarmStage | - | Activate warm stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_TTL_DAYS | 7 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_NODE_SELECTOR | type=cold |
+| recordsLog | - | - | | - | - |
+| - | shardNum | - | Shards Number. | SW_STORAGE_BANYANDB_LOG_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days. | SW_STORAGE_BANYANDB_LOG_SI_DAYS | 1 |
+| - | ttl | - | TTL Days. | SW_STORAGE_BANYANDB_LOG_TTL_DAYS | 3 |
+| - | enableWarmStage | - | Activate warm stage. | SW_STORAGE_BANYANDB_LOG_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage. | SW_STORAGE_BANYANDB_LOG_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_LOG_WARM_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_LOG_WARM_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_LOG_WARM_TTL_DAYS | 7 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_LOG_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_LOG_COLD_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_LOG_COLD_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_LOG_COLD_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_LOG_COLD_NODE_SELECTOR | type=cold |
+| recordsBrowserErrorLog | - | - | | - | - |
+| - | shardNum | - | Shards Number. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_SI_DAYS | 1 |
+| - | ttl | - | TTL Days. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_TTL_DAYS | 3 |
+| - | enableWarmStage | - | Activate warm stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_TTL_DAYS | 7 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_SI_DAYS | 1 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_NODE_SELECTOR | type=cold |
+| metricsMinute | - | - | The group for minute granularity metrics group. | - | - |
+| - | shardNum | - | Shards Number for minute granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_MINUTE_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days for minute granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_MINUTE_SI_DAYS | 1 |
+| - | ttl | - | TTL Days for minute granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_MINUTE_TTL_DAYS | 7 |
+| - | enableWarmStage | - | Activate warm stage for minute granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_MINUTE_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage for minute granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_MINUTE_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_SI_DAYS | 3 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_TTL_DAYS | 15 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_SHARD_NUM | 2 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_SI_DAYS | 5 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_TTL_DAYS | 60 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_NODE_SELECTOR | type=cold |
+| metricsHour | - | - | The group for hour granularity metrics. | - | - |
+| - | shardNum | - | Shards Number for hour granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_HOUR_SHARD_NUM | 1 |
+| - | segmentInterval | - | Segment Interval Days for hour granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_HOUR_SI_DAYS | 5 |
+| - | ttl | - | TTL Days for hour granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_HOUR_TTL_DAYS | 15 |
+| - | enableWarmStage | - | Activate warm stage for hour granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_HOUR_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage for hour granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_HOUR_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_SI_DAYS | 7 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_SI_DAYS | 15 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_TTL_DAYS | 120 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_NODE_SELECTOR | type=cold |
+| metricsDay | - | - | The group for day granularity metrics. | - | - |
+| - | shardNum | - | Shards Number for day granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_DAY_SHARD_NUM | 1 |
+| - | segmentInterval | - | Segment Interval Days for day granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_DAY_SI_DAYS | 15 |
+| - | ttl | - | TTL Days for day granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_DAY_TTL_DAYS | 15 |
+| - | enableWarmStage | - | Activate warm stage for day granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_DAY_ENABLE_WARM_STAGE | false |
+| - | enableColdStage | - | Activate cold stage for day granularity metrics group. | SW_STORAGE_BANYANDB_METRICS_DAY_ENABLE_COLD_STAGE | false |
+| - | warm | - | The warm stage settings. | - | - |
+| - | - | shardNum | Shards Number for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_WARM_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_WARM_SI_DAYS | 15 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_WARM_TTL_DAYS | 30 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_WARM_NODE_SELECTOR | type=warm |
+| - | cold | - | The cold stage settings. | - | - |
+| - | - | shardNum | Shards Number for for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_COLD_SHARD_NUM | 1 |
+| - | - | segmentInterval | Segment Interval Days for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_COLD_SI_DAYS | 15 |
+| - | - | ttl | TTL Days for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_COLD_TTL_DAYS | 120 |
+| - | - | nodeSelector | Specifying target nodes for this stage. | SW_STORAGE_BANYANDB_METRICS_DAY_COLD_NODE_SELECTOR | type=cold |
+| metadata | - | - | The `metadata` group is designed to store metrics that are used for indexing without value columns. Such as `service_traffic`, `network_address_alias`, etc. Since BanyanDB *0.8.0*. | - | - |
+| - | shardNum | - | Shards Number for metadata `index` group. | SW_STORAGE_BANYANDB_METADATA_SHARD_NUM | 2 |
+| - | segmentInterval | - | Segment Interval Days for metadata `index` group. | SW_STORAGE_BANYANDB_METADATA_SI_DAYS | 15 |
+| - | ttl | - | TTL Days for metadata `index` group. | SW_STORAGE_BANYANDB_METADATA_TTL_DAYS | 15 |
+| property | - | - | The group settings of property, such as UI and profiling. | - | - |
+| - | shardNum | - | Shards Number for property group. | SW_STORAGE_BANYANDB_PROPERTY_SHARD_NUM | 1 |
+
+## Note
+
+¹ System Environment Variable name could be declared and changed in `application.yml/bydb.yaml`. The names listed here are simply
+provided in the default `application.yml/bydb.yaml` file.
diff --git a/docs/en/setup/backend/dashboards-so11y-go-agent.md b/docs/en/setup/backend/dashboards-so11y-go-agent.md
new file mode 100644
index 000000000000..a7f4d82e533e
--- /dev/null
+++ b/docs/en/setup/backend/dashboards-so11y-go-agent.md
@@ -0,0 +1,32 @@
+# Go Agent self observability dashboard
+
+SkyWalking go agent reports its metrics using Meter APIS to measure tracing performance.
+it also provides a dashboard to visualize the agent metrics.
+
+## Data flow
+1. SkyWalking go agent reports metrics data internally and automatically.
+2. SkyWalking OAP receives these meters through native protocols.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Set up
+Go Agent so11y is a build-in feature, it reports meters automatically after boot.
+
+## Self observability monitoring
+Self observability monitoring provides monitoring of the runtime performance of the go agent itself. `agent.service_name` is a `Service` in Agent so11y, and land on the `Layer: SO11Y_GO_AGENT`.
+
+### Self observability metrics
+
+| Unit | Metric Name | Description | Data Source |
+|------------------|-------------------------------------------------------|---------------------------------------------|---------------------|
+| Count Per Minute | meter_sw_go_created_tracing_context_count | Created Tracing Context Count (Per Minute) | SkyWalking Go Agent |
+| Count Per Minute | meter_sw_go_finished_tracing_context_count | Finished Tracing Context Count (Per Minute) | SkyWalking Go Agent |
+| Count Per Minute | meter_sw_go_created_ignored_context_count | Created Ignored Context Count (Per Minute) | SkyWalking Go Agent |
+| Count Per Minute | meter_sw_go_finished_ignored_context_count | Finished Ignored Context Count (Per Minute) | SkyWalking Go Agent |
+| Count Per Minute | meter_sw_go_possible_leaked_context_count | Possible Leak Context Count (Per Minute) | SkyWalking Go Agent |
+| Count Per Minute | meter_sw_go_interceptor_error_count | Interceptor Error Count (Per Minute) | SkyWalking Go Agent |
+| ns | meter_sw_go_tracing_context_execution_time_percentile | Tracing Context Execution Time (ns) | SkyWalking Go Agent |
+
+## Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/meter-analyzer-config/go-agent.yaml`
+The self observability dashboard panel configurations are found in `/config/ui-initialized-templates/so11y_go_agent`.
diff --git a/docs/en/setup/backend/dashboards-so11y-java-agent.md b/docs/en/setup/backend/dashboards-so11y-java-agent.md
new file mode 100644
index 000000000000..45a584a86dda
--- /dev/null
+++ b/docs/en/setup/backend/dashboards-so11y-java-agent.md
@@ -0,0 +1,32 @@
+# Java Agent self observability dashboard
+
+SkyWalking java agent reports itself metrics by Meter APIS in order to measure tracing performance.
+it also provides a dashboard to visualize the agent metrics.
+
+## Data flow
+1. SkyWalking java agent reports metrics data internally and automatically.
+2. SkyWalking OAP accept these meters through native protocols.
+3. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Set up
+Java Agent so11y is a build-in feature, it reports meters automatically after boot.
+
+## Self observability monitoring
+Self observability monitoring provides monitoring of the runtime performance of the java agent itself. `agent.service_name` is a `Service` in Agent so11y, and land on the `Layer: SO11Y_JAVA_AGENT`.
+
+### Self observability metrics
+
+| Unit | Metric Name | Description | Data Source |
+|-------------------|----------------------------------------------------------------|---------------------------------------------|-----------------------|
+| Count Per Minute | meter_java_agent_created_tracing_context_count | Created Tracing Context Count (Per Minute) | SkyWalking Java Agent |
+| Count Per Minute | meter_java_agent_finished_tracing_context_count | Finished Tracing Context Count (Per Minute) | SkyWalking Java Agent |
+| Count Per Minute | meter_java_agent_created_ignored_context_count | Created Ignored Context Count (Per Minute) | SkyWalking Java Agent |
+| Count Per Minute | meter_java_agent_finished_ignored_context_count | Finished Ignored Context Count (Per Minute) | SkyWalking Java Agent |
+| Count Per Minute | meter_java_agent_possible_leaked_context_count | Possible Leak Context Count (Per Minute) | SkyWalking Java Agent |
+| Count Per Minute | meter_java_agent_interceptor_error_count | Interceptor Error Count (Per Minute) | SkyWalking Java Agent |
+| ns | meter_java_agent_tracing_context_execution_time_percentile | Tracing Context Execution Time (ns) | SkyWalking Java Agent |
+
+## Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/meter-analyzer-config/java-agent.yaml`
+The self observability dashboard panel configurations are found in `/config/ui-initialized-templates/so11y_java_agent`.
diff --git a/docs/en/setup/backend/dashboards-so11y-satellite.md b/docs/en/setup/backend/dashboards-so11y-satellite.md
new file mode 100644
index 000000000000..824002ef59fc
--- /dev/null
+++ b/docs/en/setup/backend/dashboards-so11y-satellite.md
@@ -0,0 +1,31 @@
+# Satellite self observability dashboard
+
+SkyWalking Satellite collects and exports metrics in Prometheus format and SkyWalking metrics service protobuffer format for consuming,
+it also provides a dashboard to visualize the Satellite metrics.
+
+## Data flow
+1. SkyWalking Satellite collects metrics data internally and pushes the metrics to SkyWalking OAP.
+2. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Set up
+1. Set up [SkyWalking Satellite Telemetry Exporter](https://github.com/apache/skywalking-satellite/blob/1987e1d566ac90f6b58a45fd9bfa27bf8faad635/docs/en/setup/examples/feature/telemetry-exporter/README.md).
+2. Config SkyWalking [OpenTelemetry receiver](opentelemetry-receiver.md).
+
+## Self observability monitoring
+Self observability monitoring provides monitoring of the status and resources of the OAP server itself. `oap-server` is a `Service` in OAP, and land on the `Layer: SO11Y_OAP`.
+
+### Self observability metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-----|------|-----|-----|-----|
+| | Count | satellite_service_grpc_connect_count | Connection Count | SkyWalking Satellite |
+| | Percentage | satellite_service_server_cpu_utilization | CPU (%) | SkyWalking Satellite |
+| | Count | satellite_service_queue_used_count | The used count of queue of pipeline | SkyWalking Satellite |
+| | Count | satellite_service_receive_event_count | Receive count of event from downstream | SkyWalking Satellite |
+| | Count | satellite_service_fetch_event_count | Fetch count of event from downstream | SkyWalking Satellite |
+| | Count | satellite_service_queue_input_count | The event count of push to the queue | SkyWalking Satellite |
+| | Count | satellite_service_send_event_count | The event count of push data to the upstream | SkyWalking Satellite |
+
+## Customizations
+You can customize your own metrics/expression/dashboard panel.
+The self observability dashboard panel configurations are found in `/config/ui-initialized-templates/so11y_satellite/so11y-root.json`.
diff --git a/docs/en/setup/backend/dashboards-so11y.md b/docs/en/setup/backend/dashboards-so11y.md
new file mode 100644
index 000000000000..2c9cfe33d0a9
--- /dev/null
+++ b/docs/en/setup/backend/dashboards-so11y.md
@@ -0,0 +1,53 @@
+# OAP self observability dashboard
+
+SkyWalking itself collects and exports metrics in Prometheus format for consuming,
+it also provides a dashboard to visualize the self-observability metrics.
+
+## Data flow
+1. SkyWalking OAP collects metrics data internally and exposes a Prometheus http endpoint to retrieve the metrics.
+2. SkyWalking OAP itself (or OpenTelemetry Collector, prefered in Kubernetes scenarios) fetches metrics from the Prometheus endpoint in step (1).
+3. OAP (or OpenTelemetry Collector) pushes metrics to SkyWalking OAP Server via OpenTelemetry gRPC exporter.
+4. The SkyWalking OAP Server parses the expression with [MAL](../../concepts-and-designs/mal.md) to filter/calculate/aggregate and store the results.
+
+## Set up
+Follow [OAP Self Observability Telemetry doc](backend-telemetry.md) to set up OAP and OpenTelemetry Collector.
+
+## Self observability monitoring
+Self observability monitoring provides monitoring of the status and resources of the OAP server itself. `oap-server` is a `Service` in OAP, and land on the `Layer: SO11Y_OAP`.
+
+### Self observability metrics
+
+| Unit | Metric Name | Description | Data Source |
+|------|---------------------------------------------------|-----|-----|
+| Count Per Minute | meter_oap_instance_jvm_gc_count | GC Count | oap self observability |
+| MB | meter_oap_instance_jvm_memory_bytes_used | Memory | oap self observability |
+| ms / min | meter_oap_instance_jvm_young_gc_time | GC Time (ms / min) | oap self observability |
+| ms / min | meter_oap_instance_jvm_old_gc_time | GC Time (ms / min) | oap self observability |
+| Count Per Minute | meter_oap_instance_mesh_count | Mesh Analysis Count (Per Minute) | oap self observability |
+| Count Per Minute | meter_oap_instance_mesh_analysis_error_count | Mesh Analysis Count (Per Minute) | oap self observability |
+| ms | meter_oap_instance_trace_latency_percentile | Trace Analysis Latency (ms) | oap self observability |
+| Count | meter_oap_jvm_class_loaded_count | Class Count | oap self observability |
+| Count | meter_oap_jvm_class_total_unloaded_count | Class Count | oap self observability |
+| Count | meter_oap_jvm_class_total_loaded_count | Class Count | oap self observability |
+| Count | meter_oap_instance_persistence_prepare_count | Persistence Count (Per 5 Minutes) | oap self observability |
+| Count | meter_oap_instance_persistence_execute_count | Persistence Count (Per 5 Minutes) | oap self observability |
+| Count | meter_oap_jvm_thread_live_count | Thread Count | oap self observability |
+| Count | meter_oap_jvm_thread_peak_count | Thread Count | oap self observability |
+| Count | meter_oap_jvm_thread_daemon_count | Thread Count | oap self observability |
+| ms | meter_oap_instance_persistence_execute_percentile | Persistence Execution Latency Per Metric Type (ms) | oap self observability |
+| ms | meter_oap_instance_persistence_prepare_percentile | Persistence Preparing Latency Per Metric Type (ms) | oap self observability |
+| Count | meter_oap_jvm_thread_runnable_count | Thread State Count | oap self observability |
+| Count | meter_oap_jvm_thread_timed_waiting_count | Thread State Count | oap self observability |
+| Count | meter_oap_jvm_thread_blocked_count | Thread State Count | oap self observability |
+| Count | meter_oap_jvm_thread_waiting_count | Thread State Count | oap self observability |
+| Count per minute | meter_oap_instance_metrics_aggregation | Aggregation (Per Minute) | oap self observability |
+| ms | meter_oap_instance_mesh_latency_percentile | Mesh Analysis Latency (ms) | oap self observability |
+| Count per minute | meter_oap_instance_trace_count | Trace Analysis Count (Per Minute) | oap self observability |
+| Count per minute | meter_oap_instance_trace_analysis_error_count | Trace Analysis Count (Per Minute) | oap self observability |
+| Percentage | meter_oap_instance_cpu_percentage | CPU (%) | oap self observability |
+| Count | meter_oap_instance_metrics_persistent_cache | count of metrics cache hit and no-hit |oap self observability|
+
+## Customizations
+You can customize your own metrics/expression/dashboard panel.
+The metrics definition and expression rules are found in `/config/fetcher-prom-rules/self.yaml` and `config/otel-rules/oap.yaml`.
+The self observability dashboard panel configurations are found in `/config/ui-initialized-templates/so11y_oap`.
diff --git a/docs/en/setup/backend/dynamic-config-apollo.md b/docs/en/setup/backend/dynamic-config-apollo.md
new file mode 100755
index 000000000000..be206fb87217
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-apollo.md
@@ -0,0 +1,56 @@
+# Dynamic Configuration Apollo Implementation
+
+[Apollo](https://github.com/ctripcorp/apollo/) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:apollo}
+ apollo:
+ apolloMeta: ${SW_CONFIG_APOLLO:http://localhost:8080}
+ apolloCluster: ${SW_CONFIG_APOLLO_CLUSTER:default}
+ apolloEnv: ${SW_CONFIG_APOLLO_ENV:""}
+ appId: ${SW_CONFIG_APOLLO_APP_ID:skywalking}
+```
+
+## Config Storage
+### Single Config
+Single configs in Apollo are key/value pairs:
+
+| Key | Value |
+|-----|-----|
+| configKey | configValue |
+
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+The config in Apollo is:
+
+| Key | Value |
+|-----|-----|
+| agent-analyzer.default.slowDBAccessThreshold | default:200,mongodb:50 |
+| ... | ... |
+
+
+### Group Config
+Group config in Apollo are key/value pairs as well, and the key is composited by configKey and subItemKey with `.`.
+
+| Key | Value |
+|-----|-----|
+| configKey.subItemkey1 | subItemValue1 |
+| configKey.subItemkey2 | subItemValue2 |
+| ... | ... |
+
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+The config in Apollo is:
+
+| Key | Value |
+|-----|-----|
+| core.default.endpoint-name-grouping-openapi.customerAPI-v1 | value of customerAPI-v1 |
+| core.default.endpoint-name-grouping-openapi.productAPI-v1 | value of productAPI-v1 |
+| core.default.endpoint-name-grouping-openapi.productAPI-v2 | value of productAPI-v2 |
\ No newline at end of file
diff --git a/docs/en/setup/backend/dynamic-config-configmap.md b/docs/en/setup/backend/dynamic-config-configmap.md
new file mode 100755
index 000000000000..a597168594e0
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-configmap.md
@@ -0,0 +1,111 @@
+# Dynamic Configuration Kubernetes Configmap Implementation
+
+[configmap](https://kubernetes.io/docs/concepts/configuration/configmap/) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:k8s-configmap}
+ # [example] (../../../../oap-server/server-configuration/configuration-k8s-configmap/src/test/resources/skywalking-dynamic-configmap.example.yaml)
+ k8s-configmap:
+ # Sync period in seconds. Defaults to 60 seconds.
+ period: ${SW_CONFIG_CONFIGMAP_PERIOD:60}
+ # Which namespace is configmap deployed in.
+ namespace: ${SW_CLUSTER_K8S_NAMESPACE:default}
+ # Labelselector is used to locate specific configmap
+ labelSelector: ${SW_CLUSTER_K8S_LABEL:app=collector,release=skywalking}
+```
+`{namespace}` is the k8s namespace to which the configmap belongs.
+`{labelSelector}` is used to identify which configmaps would be selected.
+
+e.g. These 2 configmaps would be selected by the above config:
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: skywalking-dynamic-config
+ namespace: default
+ labels:
+ app: collector
+ release: skywalking
+data:
+ configKey1: configValue1
+ configKey2: configValue2
+ ...
+```
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: skywalking-dynamic-config2
+ namespace: default
+ labels:
+ app: collector
+ release: skywalking
+data:
+ configKey3: configValue3
+ ...
+```
+
+## Config Storage
+The configs are configmap data items, as the above example shows. we can organize the configs in 1 or more configmap files.
+### Single Config
+Under configmap.data:
+```
+ configKey: configValue
+```
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+The config in configmap is:
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: skywalking-dynamic-config
+ namespace: default
+ labels:
+ app: collector
+ release: skywalking
+data:
+ agent-analyzer.default.slowDBAccessThreshold: default:200,mongodb:50
+```
+### Group Config
+The `data key` is composited by configKey and subItemKey to identify it is a group config:
+```
+configKey.subItemKey1: subItemValue1
+configKey.subItemKey2: subItemValue2
+...
+```
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+The config can separate into 2 configmaps is:
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: skywalking-dynamic-config
+ namespace: default
+ labels:
+ app: collector
+ release: skywalking
+data:
+ core.default.endpoint-name-grouping-openapi.customerAPI-v1: value of customerAPI-v1
+ core.default.endpoint-name-grouping-openapi.productAPI-v1: value of productAPI-v1
+```
+```
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: skywalking-dynamic-config2
+ namespace: default
+ labels:
+ app: collector
+ release: skywalking
+data:
+ core.default.endpoint-name-grouping-openapi.productAPI-v2: value of productAPI-v2
+```
\ No newline at end of file
diff --git a/docs/en/setup/backend/dynamic-config-consul.md b/docs/en/setup/backend/dynamic-config-consul.md
new file mode 100755
index 000000000000..71e364c7b3df
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-consul.md
@@ -0,0 +1,65 @@
+# Dynamic Configuration Consul Implementation
+
+[Consul](https://github.com/rickfast/consul-client) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:consul}
+ consul:
+ # Consul host and ports, separated by comma, e.g. 1.2.3.4:8500,2.3.4.5:8500
+ hostAndPorts: ${SW_CONFIG_CONSUL_HOST_AND_PORTS:1.2.3.4:8500}
+ # Sync period in seconds. Defaults to 60 seconds.
+ period: ${SW_CONFIG_CONSUL_PERIOD:1}
+ # Consul aclToken
+ aclToken: ${SW_CONFIG_CONSUL_ACL_TOKEN:""}
+```
+
+## Config Storage
+### Single Config
+Single configs in Consul are key/value pairs:
+
+| Key | Value |
+|-----|-----|
+| configKey | configValue |
+
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+The config in Consul is:
+
+| Key | Value |
+|-----|-----|
+| agent-analyzer.default.slowDBAccessThreshold | default:200,mongodb:50 |
+| ... | ... |
+
+
+### Group Config
+Group config in Consul are key/value pairs as well, but according to the level keys organized by `/`.
+
+| Key | Value |
+|-----|-----|
+| configKey/subItemkey1 | subItemValue1 |
+| configKey/subItemkey2 | subItemValue2 |
+| ... | ... |
+
+If we use Consul UI, we can see keys organized like a folder:
+```
+configKey
+ -- subItemkey1
+ -- subItemkey2
+...
+```
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+The config in Consul is:
+
+| Key | Value |
+|-----|-----|
+| core.default.endpoint-name-grouping-openapi/customerAPI-v1 | value of customerAPI-v1 |
+| core.default.endpoint-name-grouping-openapi/productAPI-v1 | value of productAPI-v1 |
+| core.default.endpoint-name-grouping-openapi/productAPI-v2 | value of productAPI-v2 |
diff --git a/docs/en/setup/backend/dynamic-config-etcd.md b/docs/en/setup/backend/dynamic-config-etcd.md
new file mode 100755
index 000000000000..7ff8ea207deb
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-etcd.md
@@ -0,0 +1,60 @@
+# Dynamic Configuration Etcd Implementation
+
+[Etcd](https://github.com/etcd-io/etcd) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:etcd}
+ etcd:
+ period: ${SW_CONFIG_ETCD_PERIOD:60} # Unit seconds, sync period. Default fetch every 60 seconds.
+ endpoints: ${SW_CONFIG_ETCD_ENDPOINTS:http://localhost:2379}
+ namespace: ${SW_CONFIG_ETCD_NAMESPACE:/skywalking}
+ authentication: ${SW_CONFIG_ETCD_AUTHENTICATION:false}
+ user: ${SW_CONFIG_ETCD_USER:}
+ password: ${SW_CONFIG_ETCD_password:}
+```
+
+**NOTE**: Since 8.7.0, only the v3 protocol is supported.
+
+## Config Storage
+### Single Config
+Single configs in etcd are key/value pairs:
+
+| Key | Value |
+|-----|-----|
+| {namespace}/configKey | configValue |
+
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+If `namespace = /skywalking` the config in etcd is:
+
+| Key | Value |
+|-----|-----|
+| /skywalking/agent-analyzer.default.slowDBAccessThreshold | default:200,mongodb:50 |
+| ... | ... |
+
+
+### Group Config
+Group config in etcd are key/value pairs as well, and the key is composited by configKey and subItemKey with `/`.
+
+| Key | Value |
+|-----|-----|
+| {namespace}/configKey/subItemkey1 | subItemValue1 |
+| {namespace}/configKey/subItemkey2 | subItemValue2 |
+| ... | ... |
+
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+If `namespace = /skywalking` the config in etcd is:
+
+| Key | Value |
+|-----|-----|
+| /skywalking/core.default.endpoint-name-grouping-openapi/customerAPI-v1 | value of customerAPI-v1 |
+| /skywalking/core.default.endpoint-name-grouping-openapi/productAPI-v1 | value of productAPI-v1 |
+| /skywalking/core.default.endpoint-name-grouping-openapi/productAPI-v2 | value of productAPI-v2 |
diff --git a/docs/en/setup/backend/dynamic-config-nacos.md b/docs/en/setup/backend/dynamic-config-nacos.md
new file mode 100755
index 000000000000..4d33c7ab701f
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-nacos.md
@@ -0,0 +1,82 @@
+# Dynamic Configuration Nacos Implementation
+
+[Nacos](https://github.com/alibaba/nacos) 2.x is also supported as a Dynamic Configuration Center (DCC).
+
+To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:nacos}
+ nacos:
+ # Nacos Server Host
+ serverAddr: ${SW_CONFIG_NACOS_SERVER_ADDR:127.0.0.1}
+ # Nacos Server Port
+ port: ${SW_CONFIG_NACOS_SERVER_PORT:8848}
+ # Nacos Configuration Group
+ group: ${SW_CONFIG_NACOS_SERVER_GROUP:skywalking}
+ # Nacos Configuration namespace
+ namespace: ${SW_CONFIG_NACOS_SERVER_NAMESPACE:}
+ # Unit seconds, sync period. Default fetch every 60 seconds.
+ period: ${SW_CONFIG_NACOS_PERIOD:60}
+ # the name of current cluster, set the name if you want to upstream system known.
+ clusterName: ${SW_CONFIG_NACOS_CLUSTER_NAME:default}
+```
+
+## Config Storage
+### Single Config
+
+| Data Id | Group | Config Value |
+|-----|-----|-----|
+| configKey | {group} | configValue |
+
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+If `group = skywalking`, the config in Nacos is:
+
+| Data Id | Group | Config Value |
+|-----|-----|-----|
+| agent-analyzer.default.slowDBAccessThreshold | skywalking | default:200,mongodb:50 |
+
+### Group Config
+
+| Data Id | Group | Config Value | Config Type |
+|-----|-----|-----|-----|
+| configKey | {group} | subItemkey1subItemkey2... | TEXT |
+| subItemkey1 | {group} | subItemValue1 |
+| subItemkey2 | {group} | subItemValue2 |
+| ... | ... | ... |
+
+Notice: If you add/remove a subItem, you need to add/remove the subItemKey from the group to which the subItem belongs:
+
+| Data Id | Group | Config Value | Config Type |
+|-----|-----|-----|-----|
+| configKey | {group} | subItemkey1subItemkey2... | TEXT |
+
+We separate subItemkeys by `\n` or `\r\n`, trim leading and trailing whitespace; if you set the config by `Nacos UI`, each subItemkey should be in a new line:
+```
+subItemValue1
+subItemValue2
+...
+
+```
+If you set the config by `API`, each subItemkey should be separated by `\n` or `\r\n`:
+```
+configService.publishConfig("test-module.default.testKeyGroup", "skywalking", "subItemkey1\n subItemkey2"));
+```
+
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+If `group = skywalking`, the config in Nacos is:
+
+| Data Id | Group | Config Value | Config Type |
+|-----|-----|-----|-----|
+| core.default.endpoint-name-grouping-openapi | skywalking | customerAPI-v1productAPI-v1productAPI-v2 | TEXT |
+| customerAPI-v1 | skywalking | value of customerAPI-v1 |
+| productAPI-v1 | skywalking | value of productAPI-v1 |
+| productAPI-v2 | skywalking | value of productAPI-v2 |
diff --git a/docs/en/setup/backend/dynamic-config-service.md b/docs/en/setup/backend/dynamic-config-service.md
new file mode 100755
index 000000000000..90279e59e385
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-service.md
@@ -0,0 +1,67 @@
+# Dynamic Configuration Service, DCS
+[Dynamic Configuration Service](../../../../oap-server/server-configuration/grpc-configuration-sync/src/main/proto/configuration-service.proto)
+is a gRPC service which requires implementation of the upstream system.
+The SkyWalking OAP fetches the configuration from the implementation (any system) after you open the implementation like this:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:grpc}
+ grpc:
+ host: ${SW_DCS_SERVER_HOST:""}
+ port: ${SW_DCS_SERVER_PORT:80}
+ clusterName: ${SW_DCS_CLUSTER_NAME:SkyWalking}
+ period: ${SW_DCS_PERIOD:20}
+```
+
+## Config Server Response
+`uuid`: To identify whether the config data changed, if `uuid` is the same, it is not required to respond to the config data.
+### Single Config
+Implement:
+```
+rpc call (ConfigurationRequest) returns (ConfigurationResponse) { }
+```
+
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+The response `configTable` is:
+```
+configTable {
+ name: "agent-analyzer.default.slowDBAccessThreshold"
+ value: "default:200,mongodb:50"
+}
+```
+
+### Group Config
+Implement:
+```
+rpc callGroup (ConfigurationRequest) returns (GroupConfigurationResponse) {}
+```
+Respond config data `GroupConfigItems groupConfigTable`
+
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+The response `groupConfigTable` is:
+
+```
+groupConfigTable {
+ groupName: "core.default.endpoint-name-grouping-openapi"
+ items {
+ name: "customerAPI-v1"
+ value: "value of customerAPI-v1"
+ }
+ items {
+ name: "productAPI-v1"
+ value: "value of productAPI-v1"
+ }
+ items {
+ name: "productAPI-v2"
+ value: "value of productAPI-v2"
+ }
+}
+```
diff --git a/docs/en/setup/backend/dynamic-config-zookeeper.md b/docs/en/setup/backend/dynamic-config-zookeeper.md
new file mode 100755
index 000000000000..db8ace032a19
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config-zookeeper.md
@@ -0,0 +1,61 @@
+# Dynamic Configuration Zookeeper Implementation
+[Zookeeper](https://github.com/apache/zookeeper) is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows:
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:zookeeper}
+ zookeeper:
+ period: ${SW_CONFIG_ZK_PERIOD:60} # Unit seconds, sync period. Default fetch every 60 seconds.
+ namespace: ${SW_CONFIG_ZK_NAMESPACE:/default}
+ hostPort: ${SW_CONFIG_ZK_HOST_PORT:localhost:2181}
+ # Retry Policy
+ baseSleepTimeMs: ${SW_CONFIG_ZK_BASE_SLEEP_TIME_MS:1000} # initial amount of time to wait between retries
+ maxRetries: ${SW_CONFIG_ZK_MAX_RETRIES:3} # max number of times to retry
+```
+
+The **namespace** is the ZooKeeper path. The config key and value are the properties of the `namespace` folder.
+
+## Config Storage
+### Single Config
+```
+znode.path = {namespace}/configKey
+configValue = znode.data
+```
+e.g. The config is:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+If `namespace = /default` the config in zookeeper is:
+```
+znode.path = /default/agent-analyzer.default.slowDBAccessThreshold
+znode.data = default:200,mongodb:50
+```
+
+### Group Config
+```
+znode.path = {namespace}/configKey
+znode.child1.path = {znode.path}/subItemkey1
+znode.child2.path = {znode.path}/subItemkey2
+...
+subItemValue1 = znode.child1.data
+subItemValue2 = znode.child2.data
+...
+```
+e.g. The config is:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+```
+If `namespace = /default` the config in zookeeper is:
+```
+znode.path = /default/core.default.endpoint-name-grouping-openapi
+znode.customerAPI-v1.path = /default/core.default.endpoint-name-grouping-openapi/customerAPI-v1
+znode.productAPI-v1.path = /default/core.default.endpoint-name-grouping-openapi/productAPI-v1
+znode.productAPI-v2.path = /default/core.default.endpoint-name-grouping-openapi/productAPI-v2
+
+znode.customerAPI-v1.data = value of customerAPI-v1
+znode.productAPI-v1.data = value of productAPI-v1
+znode.productAPI-v2.data = value of productAPI-v2
+
+```
\ No newline at end of file
diff --git a/docs/en/setup/backend/dynamic-config.md b/docs/en/setup/backend/dynamic-config.md
new file mode 100755
index 000000000000..4de75d7bd504
--- /dev/null
+++ b/docs/en/setup/backend/dynamic-config.md
@@ -0,0 +1,72 @@
+# Dynamic Configuration
+SkyWalking Configurations are mostly set through `application.yml` and OS system environment variables.
+
+At the same time, some of them support dynamic settings from an upstream management system.
+
+Currently, SkyWalking supports two types of dynamic configurations: Single and Group.
+
+This feature depends on upstream service, so it is **DISABLED** by default.
+
+```yaml
+configuration:
+ selector: ${SW_CONFIGURATION:none}
+ none:
+ grpc:
+ host: ${SW_DCS_SERVER_HOST:""}
+ port: ${SW_DCS_SERVER_PORT:80}
+ clusterName: ${SW_DCS_CLUSTER_NAME:SkyWalking}
+ period: ${SW_DCS_PERIOD:20}
+ # ... other implementations
+```
+## Single Configuration
+Single Configuration is a config key that corresponds to a specific config value. The logic structure is:
+```
+{configKey}:{configValue}
+```
+For example:
+```
+{agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50}
+```
+Supported configurations are as follows:
+
+| Config Key | Value Description | Value Format Example |
+|:----:|:----:|:----:|
+|agent-analyzer.default.slowDBAccessThreshold| Thresholds of slow Database statement. Overrides `agent-analyzer/default/slowDBAccessThreshold` of `application.yml`. | default:200,mongodb:50|
+|agent-analyzer.default.uninstrumentedGateways| The uninstrumented gateways. Overrides `gateways.yml`. | Same as [`gateways.yml`](uninstrumented-gateways.md#configuration-format). |
+|alarm.default.alarm-settings| The alarm settings. Overrides `alarm-settings.yml`. | Same as [`alarm-settings.yml`](backend-alarm.md). |
+|core.default.apdexThreshold| The apdex threshold settings. Overrides `service-apdex-threshold.yml`. | Same as [`service-apdex-threshold.yml`](apdex-threshold.md). |
+|core.default.endpoint-name-grouping| The endpoint name grouping setting. Overrides `endpoint-name-grouping.yml`. | Same as [`endpoint-name-grouping.yml`](endpoint-grouping-rules.md). |
+|core.default.log4j-xml| The log4j xml configuration. Overrides `log4j2.xml`. | Same as [`log4j2.xml`](dynamical-logging.md). |
+|core.default.searchableTracesTags| The searchableTracesTags configuration. Override `core/default/searchableTracesTags` in the `application.yml`. | http.method,http.status_code,rpc.status_code,db.type,db.instance,mq.queue,mq.topic,mq.broker |
+|agent-analyzer.default.traceSamplingPolicy| The sampling policy for default and service dimension, override `trace-sampling-policy-settings.yml`. | same as [`trace-sampling-policy-settings.yml`](trace-sampling.md) |
+|configuration-discovery.default.agentConfigurations| The ConfigurationDiscovery settings. | See [`configuration-discovery.md`](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/configuration-discovery/). |
+
+## Group Configuration
+Group Configuration is a config key corresponding to a group sub config item. A sub config item is a key-value pair. The logic structure is:
+```
+{configKey}: |{subItemkey1}:{subItemValue1}
+ |{subItemkey2}:{subItemValue2}
+ |{subItemkey3}:{subItemValue3}
+ ...
+```
+For example:
+```
+{core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1}
+ |{productAPI-v1}:{value of productAPI-v1}
+ |{productAPI-v2}:{value of productAPI-v2}
+
+```
+Supported configurations are as follows:
+
+| Config Key | SubItem Key Description | Value Description | Value Format Example |
+|:----:|:----:|:----:|:----:|
+|core.default.endpoint-name-grouping-openapi|The serviceName relevant to openAPI definition file. eg. `serviceA`. If the serviceName relevant to multiple files should add subItems for each files, and each subItem key should split serviceName and fileName with `.` eg. `serviceA.API-file1`,`serviceA.API-file2` |The openAPI definitions file contents(yaml format) for create endpoint name grouping rules.|Same as [`productAPI-v2.yaml`](endpoint-grouping-rules.md)|
+
+## Dynamic Configuration Implementations
+- [Dynamic Configuration Service, DCS](./dynamic-config-service.md)
+- [Zookeeper Implementation](./dynamic-config-zookeeper.md)
+- [Etcd Implementation](./dynamic-config-etcd.md)
+- [Consul Implementation](./dynamic-config-consul.md)
+- [Apollo Implementation](./dynamic-config-apollo.md)
+- [Kubernetes Configmap Implementation](./dynamic-config-configmap.md)
+- [Nacos Implementation](./dynamic-config-nacos.md)
diff --git a/docs/en/setup/backend/dynamical-logging.md b/docs/en/setup/backend/dynamical-logging.md
new file mode 100644
index 000000000000..bdcf0877e553
--- /dev/null
+++ b/docs/en/setup/backend/dynamical-logging.md
@@ -0,0 +1,48 @@
+# Dynamical Logging
+
+The OAP server leverages `log4j2` to manage the logging system. `log4j2` supports changing the configuration
+at runtime, but you have to manually update the XML configuration file, which could be time-consuming and prone to man-made mistakes.
+
+Dynamical logging, which depends on dynamic configuration, provides us with an agile way to update all OAP `log4j`
+configurations through a single operation.
+
+The key of the configuration item is `core.default.log4j-xml`, and you can select any of the configuration implements
+to store the content of `log4j.xml`. In the booting phase, once the core module gets started, `core.default.log4j-xml`
+would come into the OAP log4j context.
+
+If the configuration is changed after the OAP startup, you have to wait for a while for the changes to be applied. The default value is `60` seconds, which you could change through `configuration..period` in `application.yaml`.
+
+If you remove `core.default.log4j-xml` from the configuration center or disable the configuration module, `log4j.xml` in the `config` directory would be affected.
+
+> Caveat: The OAP only supports the XML configuration format.
+
+This is an example of configuring dynamical logging through a ConfigMap in a Kubernetes cluster. You may set up other configuration
+clusters following the same procedures.
+
+```yaml
+apiVersion: v1
+data:
+ core.default.log4j-xml: |-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+kind: ConfigMap
+metadata:
+ labels:
+ app: collector
+ release: skywalking
+ name: skywalking-oap
+ namespace: default
+```
diff --git a/docs/en/setup/backend/endpoint-grouping-rules.md b/docs/en/setup/backend/endpoint-grouping-rules.md
new file mode 100644
index 000000000000..f8b894963782
--- /dev/null
+++ b/docs/en/setup/backend/endpoint-grouping-rules.md
@@ -0,0 +1,307 @@
+# Group Parameterized Endpoints
+In most cases, endpoints are detected automatically through language agents, service mesh observability solutions,
+or meter system configurations.
+
+There are some special cases, especially when REST-style URI is used, where the application codes include the parameter in the endpoint name,
+such as putting order ID in the URI. Examples are `/prod/ORDER123` and `/prod/ORDER456`. But logically, most would expect to
+have an endpoint name like `prod/{order-id}`. This is a specially designed feature in parameterized endpoint grouping.
+
+If the incoming endpoint name accords with the rules, SkyWalking will group the endpoint by rules.
+
+There are two approaches in which SkyWalking supports endpoint grouping:
+1. Endpoint name grouping by OpenAPI definitions.
+2. Endpoint name grouping by custom configurations.
+
+Both grouping approaches can work together in sequence.
+
+## Endpoint name grouping by OpenAPI definitions
+The OpenAPI definitions are documents based on the [OpenAPI Specification (OAS)](https://www.openapis.org/), which is used to define a standard, language-agnostic interface for HTTP APIs.
+
+SkyWalking now supports `OAS v2.0+`. It could parse the documents `(yaml)` and build grouping rules from them automatically.
+
+
+### How to use
+1. Add `Specification Extensions` for SkyWalking config in the OpenAPI definition documents; otherwise, all configs are default:
+ `${METHOD}` is a reserved placeholder which represents the HTTP method, e.g. `POST/GET...`
.
+ `${PATH}` is a reserved placeholder which represents the path, e.g. `/products/{id}`.
+
+ | Extension Name | Required | Description | Default Value |
+ |-----|-----|-----|-----|
+ | x-sw-service-name | false | The service name to which these endpoints belong. | The directory name to which the OpenAPI definition documents belong. |
+ | x-sw-endpoint-name-match-rule | false | The rule used to match the endpoint. | `${METHOD}:${PATH}` |
+ | x-sw-endpoint-name-format | false | The endpoint name after grouping. | `${METHOD}:${PATH}` |
+
+ These extensions are under `OpenAPI Object`. For example, the document below has a full custom config:
+
+``` yaml
+openapi: 3.0.0
+x-sw-service-name: serviceB
+x-sw-endpoint-name-match-rule: "${METHOD}:${PATH}"
+x-sw-endpoint-name-format: "${METHOD}:${PATH}"
+
+info:
+ description: OpenAPI definition for SkyWalking test.
+ version: v2
+ title: Product API
+ ...
+```
+
+ We highly recommend using the default config. The custom config (`x-sw-endpoint-name-match-rule/x-sw-endpoint-name-format`) is considered part of the match rules (regex pattern).
+ We have provided some use cases in `org.apache.skywalking.oap.server.core.config.group.openapi.EndpointGroupingRuleReader4OpenapiTest`. You may validate your custom config as well.
+
+2. All OpenAPI definition documents are located in the `openapi-definitions` directory, with directories having at most two levels. We recommend using the service name as the subDirectory name, as you will then not be required to set `x-sw-service-name`. For example:
+ ```
+├── openapi-definitions
+│ ├── serviceA
+│ │ ├── customerAPI-v1.yaml
+│ │ └── productAPI-v1.yaml
+│ └── serviceB
+│ └── productAPI-v2.yaml
+```
+3. The feature is enabled by default. You can disable it by setting the `Core Module` configuration `${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI:false}`.
+
+### Rules match priority
+We recommend designing the API path as clearly as possible. If the API path is fuzzy and an endpoint name matches multiple paths, SkyWalking would select a path according to the match priority set out below:
+1. The exact path is matched.
+ E.g. `/products or /products/inventory`
+2. The path with fewer variables.
+ E.g. In the case of `/products/{var1}/{var2} and /products/{var1}/abc`, endpoint name `/products/123/abc` will match the second one.
+3. If the paths have the same number of variables, the longest path is matched, and the vars are considered to be `1`.
+ E.g. In the case of `/products/abc/{var1} and products/{var12345}/ef`, endpoint name `/products/abc/ef` will match the first one, because `length("abc") = 3` is larger than `length("ef") = 2`.
+### Examples
+If we have an OpenAPI definition doc `productAPI-v2.yaml` in directory `serviceB`, it will look like this:
+```yaml
+
+openapi: 3.0.0
+
+info:
+ description: OpenAPI definition for SkyWalking test.
+ version: v2
+ title: Product API
+
+tags:
+ - name: product
+ description: product
+ - name: relatedProducts
+ description: Related Products
+
+paths:
+ /products:
+ get:
+ tags:
+ - product
+ summary: Get all products list
+ description: Get all products list.
+ operationId: getProducts
+ responses:
+ "200":
+ description: Success
+ content:
+ application/json:
+ schema:
+ type: array
+ items:
+ $ref: "#/components/schemas/Product"
+ /products/{region}/{country}:
+ get:
+ tags:
+ - product
+ summary: Get products regional
+ description: Get products regional with the given id.
+ operationId: getProductRegional
+ parameters:
+ - name: region
+ in: path
+ description: Products region
+ required: true
+ schema:
+ type: string
+ - name: country
+ in: path
+ description: Products country
+ required: true
+ schema:
+ type: string
+ responses:
+ "200":
+ description: successful operation
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/Product"
+ "400":
+ description: Invalid parameters supplied
+ /products/{id}:
+ get:
+ tags:
+ - product
+ summary: Get product details
+ description: Get product details with the given id.
+ operationId: getProduct
+ parameters:
+ - name: id
+ in: path
+ description: Product id
+ required: true
+ schema:
+ type: integer
+ format: int64
+ responses:
+ "200":
+ description: successful operation
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/ProductDetails"
+ "400":
+ description: Invalid product id
+ post:
+ tags:
+ - product
+ summary: Update product details
+ description: Update product details with the given id.
+ operationId: updateProduct
+ parameters:
+ - name: id
+ in: path
+ description: Product id
+ required: true
+ schema:
+ type: integer
+ format: int64
+ - name: name
+ in: query
+ description: Product name
+ required: true
+ schema:
+ type: string
+ responses:
+ "200":
+ description: successful operation
+ delete:
+ tags:
+ - product
+ summary: Delete product details
+ description: Delete product details with the given id.
+ operationId: deleteProduct
+ parameters:
+ - name: id
+ in: path
+ description: Product id
+ required: true
+ schema:
+ type: integer
+ format: int64
+ responses:
+ "200":
+ description: successful operation
+ /products/{id}/relatedProducts:
+ get:
+ tags:
+ - relatedProducts
+ summary: Get related products
+ description: Get related products with the given product id.
+ operationId: getRelatedProducts
+ parameters:
+ - name: id
+ in: path
+ description: Product id
+ required: true
+ schema:
+ type: integer
+ format: int64
+ responses:
+ "200":
+ description: successful operation
+ content:
+ application/json:
+ schema:
+ $ref: "#/components/schemas/RelatedProducts"
+ "400":
+ description: Invalid product id
+
+components:
+ schemas:
+ Product:
+ type: object
+ description: Product id and name
+ properties:
+ id:
+ type: integer
+ format: int64
+ description: Product id
+ name:
+ type: string
+ description: Product name
+ required:
+ - id
+ - name
+ ProductDetails:
+ type: object
+ description: Product details
+ properties:
+ id:
+ type: integer
+ format: int64
+ description: Product id
+ name:
+ type: string
+ description: Product name
+ description:
+ type: string
+ description: Product description
+ required:
+ - id
+ - name
+ RelatedProducts:
+ type: object
+ description: Related Products
+ properties:
+ id:
+ type: integer
+ format: int32
+ description: Product id
+ relatedProducts:
+ type: array
+ description: List of related products
+ items:
+ $ref: "#/components/schemas/Product"
+
+
+```
+
+Here are some use cases:
+
+ | Incoming Endpoint | Incoming Service | x-sw-service-name | x-sw-endpoint-name-match-rule | x-sw-endpoint-name-format | Matched | Grouping Result |
+ |-----|-----|-----|-----|-----|-----|-----|
+ | `GET:/products` | serviceB | default | default | default | true | `GET:/products` |
+ | `GET:/products/asia/cn` | serviceB | default | default | default | true | `GET:/products/{region}/{country}` |
+ | `GET:/products/123` | serviceB | default | default | default | true | `GET:/products{id}` |
+ | `GET:/products/123/abc/efg` | serviceB | default | default | default | false | `GET:/products/123/abc/efg` |
+ | `:/products/123` | serviceB | default | default | default | false | `:/products/123`|
+ | `GET:/products/123` | serviceC | default | default | default | false | `GET:/products/123` |
+ | `GET:/products/123` | serviceC | serviceC | default | default | true | `GET:/products/123` |
+ | `:/products/123` | serviceB | default | `<${METHOD}>:${PATH}` | `<${METHOD}>:${PATH}` | true | `:/products/{id}` |
+ | `GET:/products/123` | serviceB | default | default | `${PATH}:<${METHOD}>` | true | `/products/{id}:` |
+ | `/products/123:` | serviceB | default | `${PATH}:<${METHOD}>` | default | true | `GET:/products/{id}` |
+
+### Initialize and update the OpenAPI definitions dynamically
+Use [Dynamic Configuration](dynamic-config.md) to initialize and update OpenAPI definitions, the endpoint grouping rules from OpenAPI
+will re-create by the new config.
+
+
+## Endpoint name grouping by custom configuration
+Currently, a user could set up grouping rules through the static YAML file named `endpoint-name-grouping.yml`,
+or use [Dynamic Configuration](dynamic-config.md) to initialize and update endpoint grouping rules.
+
+### Configuration Format
+Both the static local file and dynamic configuration value share the same YAML format.
+
+```yaml
+grouping:
+ # Endpoint of the service would follow the following rules
+ - service-name: serviceA
+ rules:
+ # {var} represents any variable string in the URI.
+ - /prod/{var}
+```
diff --git a/docs/en/setup/backend/exporter.md b/docs/en/setup/backend/exporter.md
new file mode 100644
index 000000000000..fd68a4cb019c
--- /dev/null
+++ b/docs/en/setup/backend/exporter.md
@@ -0,0 +1,128 @@
+# Exporter
+SkyWalking provides the essential functions of observability, including metrics aggregation, trace, log, alerting, and profiling.
+In many real-world scenarios, users may want to forward their data to a 3rd party system for further in-depth analysis.
+**Exporter** has made that possible.
+
+The exporter is an independent module that has to be manually activated.
+
+Right now, we provide the following exporting channels:
+1. gRPC Exporter
+- [Metrics](#metrics-grpc-exporter)
+
+2. Kafka Exporter
+- [Trace](#trace-kafka-exporter)
+- [Log](#log-kafka-exporter)
+
+## gRPC Exporter
+### Metrics gRPC Exporter
+Metrics gRPC exporter uses SkyWalking's native export service definition. Here is the proto definition: [metric-exporter.proto](https://github.com/apache/skywalking/blob/master/oap-server/exporter/src/main/proto/metric-exporter.proto).
+```proto
+service MetricExportService {
+ rpc export (stream ExportMetricValue) returns (ExportResponse) {
+ }
+
+ rpc subscription (SubscriptionReq) returns (SubscriptionsResp) {
+ }
+}
+```
+
+To activate the exporter, you should set `${SW_EXPORTER:default}` and `${SW_EXPORTER_ENABLE_GRPC_METRICS:true}`, configure the target gRPC server address.
+```yaml
+exporter:
+ selector:${SW_EXPORTER:default}
+ default:
+ # gRPC exporter
+ enableGRPCMetrics: ${SW_EXPORTER_ENABLE_GRPC_METRICS:true}
+ gRPCTargetHost: ${SW_EXPORTER_GRPC_HOST:127.0.0.1}
+ gRPCTargetPort: ${SW_EXPORTER_GRPC_PORT:9870}
+ ...
+```
+
+- `gRPCTargetHost`:`gRPCTargetPort` is the expected target service address. You could set any gRPC server to receive the data.
+- Target gRPC service needs to go on standby; otherwise, the OAP startup may fail.
+
+#### Target exporter service
+1. Subscription implementation.
+Return the expected metrics name list with event type (incremental or total). All names must match the OAL/MAL script definition.
+Return empty list, if you want to export all metrics in the incremental event type.
+
+2. Export implementation.
+Stream service. All subscribed metrics will be sent here based on the OAP core schedule. Also, if the OAP is deployed as a cluster,
+this method will be called concurrently.
+
+## Kafka Exporter
+### Trace Kafka Exporter
+Trace kafka exporter pushes messages to the Kafka Broker and Topic `skywalking-export-trace` to export the trace. Here is the message:
+```
+ProducerRecord
+Key: TraceSegmentId
+Value: Bytes of SegmentObject
+```
+
+The `SegmentObject` definition follows the protocol:
+[SkyWalking data collect protocol#Tracing.proto](https://github.com/apache/skywalking-data-collect-protocol/blob/master/language-agent/Tracing.proto).
+```proto
+// The segment is a collection of spans. It includes all collected spans in a simple one request context, such as a HTTP request process.
+message SegmentObject {
+ string traceId = 1;
+ string traceSegmentId = 2;
+ repeated SpanObject spans = 3;
+ string service = 4;
+ string serviceInstance = 5;
+ bool isSizeLimited = 6;
+}
+```
+
+To activate the exporter, you should set `${SW_EXPORTER:default}` and `${SW_EXPORTER_ENABLE_KAFKA_TRACE:true}`, configure the Kafka server addresses.
+```yaml
+exporter:
+ selector:${SW_EXPORTER:default}
+ default:
+ # Kafka exporter
+ enableKafkaTrace: ${SW_EXPORTER_ENABLE_KAFKA_TRACE:true}
+ kafkaBootstrapServers: ${SW_EXPORTER_KAFKA_SERVERS:localhost:9092}
+ # Kafka producer config, JSON format as Properties.
+ kafkaProducerConfig: ${SW_EXPORTER_KAFKA_PRODUCER_CONFIG:""}
+ kafkaTopicTrace: ${SW_EXPORTER_KAFKA_TOPIC_TRACE:skywalking-export-trace}
+ exportErrorStatusTraceOnly: ${SW_EXPORTER_KAFKA_TRACE_FILTER_ERROR:false}
+ ...
+```
+
+- `exportErrorStatusTraceOnly=true` represents that only export the error status trace segments through the Kafka channel.
+
+### Log Kafka Exporter
+Log kafka exporter pushes messages to the Kafka Broker and Topic `skywalking-export-log` to export the log. Here is the message:
+```
+ProducerRecord
+Key: LogRecordId
+Value: Bytes of LogData
+```
+
+The `LogData` definition follows the protocol:
+[SkyWalking data collect protocol#Logging.proto](https://github.com/apache/skywalking-data-collect-protocol/blob/master/logging/Logging.proto).
+```proto
+message LogData {
+ int64 timestamp = 1;
+ string service = 2;
+ string serviceInstance = 3;
+ string endpoint = 4;
+ LogDataBody body = 5;
+ TraceContext traceContext = 6;
+ LogTags tags = 7;
+ string layer = 8;
+}
+```
+
+To activate the exporter, you should set `${SW_EXPORTER:default}` and `${SW_EXPORTER_ENABLE_KAFKA_LOG:true}`, configure the Kafka server addresses.
+```yaml
+exporter:
+ selector:${SW_EXPORTER:default}
+ default:
+ # Kafka exporter
+ enableKafkaLog: ${SW_EXPORTER_ENABLE_KAFKA_LOG:true}
+ kafkaBootstrapServers: ${SW_EXPORTER_KAFKA_SERVERS:localhost:9092}
+ # Kafka producer config, JSON format as Properties.
+ kafkaProducerConfig: ${SW_EXPORTER_KAFKA_PRODUCER_CONFIG:""}
+ kafkaTopicLog: ${SW_EXPORTER_KAFKA_TOPIC_LOG:skywalking-export-log}
+ ...
+```
diff --git a/docs/en/setup/backend/filelog-native.md b/docs/en/setup/backend/filelog-native.md
new file mode 100644
index 000000000000..1e7d61e0be69
--- /dev/null
+++ b/docs/en/setup/backend/filelog-native.md
@@ -0,0 +1,40 @@
+# Collecting File Log
+
+Application's logs are important data for troubleshooting, usually they are persistent through local or network file
+system.
+SkyWalking provides ways to collect logs from those files by leveraging popular open-source tools.
+
+## Log files collector
+
+You can use [Filebeat](https://www.elastic.co/cn/beats/filebeat), [Fluentd](https://www.fluentd.org/)
+and [FluentBit](http://fluentbit.io) to collect logs, and then transport the logs to SkyWalking OAP through Kafka or
+HTTP protocol, with the formats [Kafka JSON](../../api/log-data-protocol.md#native-kafka-protocol)
+or [HTTP JSON array](../../api/log-data-protocol.md#http-api).
+
+### Filebeat
+
+Filebeat supports using Kafka to transport logs. Open [kafka-fetcher](kafka-fetcher.md#kafka-fetcher) and enable
+configs `enableNativeJsonLog`.
+
+Take the following Filebeat config YAML as an example to set up Filebeat:
+
+- [filebeat.yml](../../../../test/e2e-v2/cases/kafka/log/filebeat.yml)
+
+### Fluentd
+
+Fluentd supports using Kafka to transport logs. Open [kafka-fetcher](kafka-fetcher.md#kafka-fetcher) and enable
+configs `enableNativeJsonLog`.
+
+Take the following fluentd config file as an example to set up Fluentd:
+
+- [fluentd.conf](../../../../test/e2e-v2/cases/kafka/log/fluentd.conf)
+
+### Fluent-bit
+
+Fluent-bit sends logs to OAP directly through HTTP(rest port).
+Point the output address to `restHost`:`restPort` of `receiver-sharing-server` or `core`(if `receiver-sharing-server` is
+inactivated)
+
+Take the following fluent-bit config files as an example to set up Fluent-bit:
+
+- [fluent-bit.conf](../../../../test/e2e-v2/cases/log/fluent-bit/fluent-bit.conf)
\ No newline at end of file
diff --git a/docs/en/setup/backend/grafana-cluster.json b/docs/en/setup/backend/grafana-cluster.json
new file mode 100644
index 000000000000..01c119ba493f
--- /dev/null
+++ b/docs/en/setup/backend/grafana-cluster.json
@@ -0,0 +1,4726 @@
+{
+ "__inputs": [
+ {
+ "name": "DS_PROMETHEUS-SW",
+ "label": "prometheus-sw",
+ "description": "",
+ "type": "datasource",
+ "pluginId": "prometheus",
+ "pluginName": "Prometheus"
+ }
+ ],
+ "annotations": {
+ "list": [
+ {
+ "builtIn": 1,
+ "datasource": "${DS_PROMETHEUS-SW}",
+ "enable": true,
+ "hide": true,
+ "iconColor": "rgba(0, 211, 255, 1)",
+ "name": "Annotations & Alerts",
+ "type": "dashboard"
+ }
+ ]
+ },
+ "description": "SkyWalking OAP Cluster Monitor Dashboard",
+ "editable": true,
+ "gnetId": null,
+ "graphTooltip": 0,
+ "id": null,
+ "iteration": 1705281849017,
+ "links": [],
+ "panels": [
+ {
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 0
+ },
+ "id": 37,
+ "title": "Basic Info",
+ "type": "row"
+ },
+ {
+ "cacheTimeout": null,
+ "colorBackground": false,
+ "colorValue": false,
+ "colors": [
+ "#299c46",
+ "rgba(237, 129, 40, 0.89)",
+ "#d44a3a"
+ ],
+ "datasource": "$datasource",
+ "format": "none",
+ "gauge": {
+ "maxValue": 100,
+ "minValue": 0,
+ "show": false,
+ "thresholdLabels": false,
+ "thresholdMarkers": true
+ },
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 1
+ },
+ "id": 13,
+ "interval": null,
+ "links": [],
+ "mappingType": 1,
+ "mappingTypes": [
+ {
+ "name": "value to text",
+ "value": 1
+ },
+ {
+ "name": "range to text",
+ "value": 2
+ }
+ ],
+ "maxDataPoints": 100,
+ "nullPointMode": "connected",
+ "nullText": null,
+ "options": {},
+ "postfix": "",
+ "postfixFontSize": "50%",
+ "prefix": "",
+ "prefixFontSize": "50%",
+ "rangeMaps": [
+ {
+ "from": "null",
+ "text": "N/A",
+ "to": "null"
+ }
+ ],
+ "sparkline": {
+ "fillColor": "rgba(31, 118, 189, 0.18)",
+ "full": false,
+ "lineColor": "rgb(31, 120, 193)",
+ "show": false
+ },
+ "tableColumn": "",
+ "targets": [
+ {
+ "expr": "count(uptime{job=\"$job\"})",
+ "refId": "A"
+ }
+ ],
+ "thresholds": "",
+ "title": "Instances Number",
+ "type": "singlestat",
+ "valueFontSize": "80%",
+ "valueMaps": [
+ {
+ "op": "=",
+ "text": "N/A",
+ "value": "null"
+ }
+ ],
+ "valueName": "current"
+ },
+ {
+ "cacheTimeout": null,
+ "columns": [
+ {
+ "text": "Current",
+ "value": "current"
+ }
+ ],
+ "datasource": "$datasource",
+ "fontSize": "100%",
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 1
+ },
+ "id": 38,
+ "links": [],
+ "options": {},
+ "pageSize": null,
+ "showHeader": true,
+ "sort": {
+ "col": 1,
+ "desc": false
+ },
+ "styles": [
+ {
+ "alias": "",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Metric",
+ "thresholds": [],
+ "type": "string",
+ "unit": "short"
+ },
+ {
+ "alias": "",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Current",
+ "thresholds": [],
+ "type": "date",
+ "unit": "short"
+ }
+ ],
+ "targets": [
+ {
+ "expr": "process_start_time_seconds{job=\"$job\"}*1000",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "title": "Instances Start Time",
+ "transform": "timeseries_aggregations",
+ "type": "table"
+ },
+ {
+ "cacheTimeout": null,
+ "columns": [
+ {
+ "text": "Current",
+ "value": "current"
+ }
+ ],
+ "datasource": "$datasource",
+ "fontSize": "100%",
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 1
+ },
+ "id": 39,
+ "links": [],
+ "options": {},
+ "pageSize": null,
+ "showHeader": true,
+ "sort": {
+ "col": 1,
+ "desc": false
+ },
+ "styles": [
+ {
+ "alias": "",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Metric",
+ "thresholds": [],
+ "type": "string",
+ "unit": "short"
+ },
+ {
+ "alias": "",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Current",
+ "thresholds": [],
+ "type": "number",
+ "unit": "s"
+ }
+ ],
+ "targets": [
+ {
+ "expr": "time() - process_start_time_seconds{job=\"$job\"}",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "title": "Instances Run Time",
+ "transform": "timeseries_aggregations",
+ "type": "table"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 7
+ },
+ "hiddenSeries": false,
+ "id": 20,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(process_cpu_seconds_total{job=\"$job\"}[1m]) * 100 / 60",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "CPU * Cores number",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "percent",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 7
+ },
+ "hiddenSeries": false,
+ "id": 22,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_memory_bytes_used{job=\"$job\",area=\"heap\"}",
+ "legendFormat": "{{instance}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_memory_bytes_committed{job=\"$job\",area=\"heap\"}",
+ "legendFormat": "{{instance}}-committed",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_memory_bytes_max{job=\"$job\",area=\"heap\"}",
+ "legendFormat": "{{instance}}-max",
+ "refId": "C"
+ },
+ {
+ "expr": "jvm_memory_bytes_init{job=\"$job\",area=\"heap\"}",
+ "legendFormat": "{{instance}}-init",
+ "refId": "D"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Heap Memory",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 7
+ },
+ "hiddenSeries": false,
+ "id": 21,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(jvm_gc_collection_seconds_sum{job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{instance}}-{{gc}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "GC Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 13
+ },
+ "hiddenSeries": false,
+ "id": 27,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_memory_pool_bytes_used{job=\"$job\"}",
+ "legendFormat": "{{instance}}-{{pool}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_committed{job=\"$job\"}",
+ "legendFormat": "{{instance}}-{{pool}}-committed",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_max{job=\"$job\"}",
+ "legendFormat": "{{instance}}-{{pool}}-max",
+ "refId": "C"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_init{job=\"$job\"}",
+ "legendFormat": "{{instance}}-{{pool}}-init",
+ "refId": "D"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Memory Pool",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 13
+ },
+ "hiddenSeries": false,
+ "id": 26,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_memory_bytes_used{job=\"$job\",area=\"nonheap\"}",
+ "legendFormat": "{{instance}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_memory_bytes_committed{job=\"$job\",area=\"nonheap\"}",
+ "legendFormat": "{{instance}}-committed",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_memory_bytes_max{job=\"$job\",area=\"nonheap\"}",
+ "legendFormat": "{{instance}}-max",
+ "refId": "C"
+ },
+ {
+ "expr": "jvm_memory_bytes_init{job=\"$job\",area=\"nonheap\"}",
+ "legendFormat": "{{instance}}-init",
+ "refId": "D"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Nonheap Memory",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 13
+ },
+ "hiddenSeries": false,
+ "id": 33,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(jvm_gc_collection_seconds_count{job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{instance}}-{{gc}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "GC Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 19
+ },
+ "hiddenSeries": false,
+ "id": 40,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_threads_current{job=\"$job\"}",
+ "legendFormat": "{{instance}}-Current",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_threads_daemon{job=\"$job\"}",
+ "legendFormat": "{{instance}}-Daemon",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_threads_peak{job=\"$job\"}",
+ "legendFormat": "{{instance}}-Peak",
+ "refId": "C"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Thread Count",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 19
+ },
+ "hiddenSeries": false,
+ "id": 41,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_threads_state{job=\"$job\"}",
+ "legendFormat": "{{instance}}-{{state}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Thread State",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 19
+ },
+ "hiddenSeries": false,
+ "id": 42,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_classes_loaded{job=\"$job\"}",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Class Loaded",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 25
+ },
+ "id": 35,
+ "panels": [],
+ "title": "OAP Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 26
+ },
+ "hiddenSeries": false,
+ "id": 2,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(trace_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "B"
+ },
+ {
+ "expr": "rate(trace_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 26
+ },
+ "hiddenSeries": false,
+ "id": 6,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(trace_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 26
+ },
+ "hiddenSeries": false,
+ "id": 11,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(trace_analysis_error_count{job=\"$job\"}[1m]) ",
+ "interval": "1m",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 32
+ },
+ "hiddenSeries": false,
+ "id": 24,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(mesh_analysis_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(mesh_analysis_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 32
+ },
+ "hiddenSeries": false,
+ "id": 25,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(mesh_analysis_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 32
+ },
+ "hiddenSeries": false,
+ "id": 28,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(mesh_analysis_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 38
+ },
+ "hiddenSeries": false,
+ "id": 69,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(k8s_als_in_count{job=\"$job\"}[1m]))",
+ "interval": "",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(k8s_als_in_count{job=\"$job\"}[1m])",
+ "hide": false,
+ "interval": "",
+ "legendFormat": "{{instance}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "K8S ALS Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 38
+ },
+ "hiddenSeries": false,
+ "id": 71,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(k8s_als_in_latency_sum{job=\"$job\"}[1m])",
+ "interval": "",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "K8S ALS Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 38
+ },
+ "hiddenSeries": false,
+ "id": 73,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(k8s_als_drop_count{job=\"$job\"}[1m]) ",
+ "interval": "",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "K8S ALS Drop Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 44
+ },
+ "hiddenSeries": false,
+ "id": 50,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(meter_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(meter_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 44
+ },
+ "hiddenSeries": false,
+ "id": 51,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(meter_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 44
+ },
+ "hiddenSeries": false,
+ "id": 52,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(meter_analysis_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 50
+ },
+ "hiddenSeries": false,
+ "id": 53,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(log_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(log_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 50
+ },
+ "hiddenSeries": false,
+ "id": 54,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(log_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 50
+ },
+ "hiddenSeries": false,
+ "id": 55,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(log_analysis_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 56
+ },
+ "hiddenSeries": false,
+ "id": 56,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(event_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(event_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 56
+ },
+ "hiddenSeries": false,
+ "id": 57,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(event_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 56
+ },
+ "hiddenSeries": false,
+ "id": 58,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(event_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 62
+ },
+ "hiddenSeries": false,
+ "id": 59,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(browser_perf_data_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(browser_perf_data_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 62
+ },
+ "hiddenSeries": false,
+ "id": 60,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_perf_data_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 62
+ },
+ "hiddenSeries": false,
+ "id": 61,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_perf_data_analysis_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 68
+ },
+ "hiddenSeries": false,
+ "id": 62,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(browser_error_log_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(browser_error_log_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 68
+ },
+ "hiddenSeries": false,
+ "id": 63,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_error_log_in_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 68
+ },
+ "hiddenSeries": false,
+ "id": 64,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_error_log_analysis_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}-{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 74
+ },
+ "hiddenSeries": false,
+ "id": 65,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(metrics_fetcher_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(metrics_fetcher_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 74
+ },
+ "hiddenSeries": false,
+ "id": 66,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(metrics_fetcher_latency_sum{job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 74
+ },
+ "hiddenSeries": false,
+ "id": 67,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(metrics_fetcher_error_count{job=\"$job\"}[1m]) ",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 80
+ },
+ "hiddenSeries": false,
+ "id": 49,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 1,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",protocol=~\"kafka-fetcher|grpc\"}[1h]))",
+ "interval": "1h",
+ "legendFormat": "Current Week",
+ "refId": "B"
+ },
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",protocol=~\"kafka-fetcher|grpc\"}[1h] offset 1w))",
+ "interval": "1h",
+ "legendFormat": "Last Week",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": "1d",
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Hour",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": false
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 80
+ },
+ "hiddenSeries": false,
+ "id": 48,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",protocol=~\"kafka-fetcher|grpc\"}[1d]))",
+ "interval": "1d",
+ "legendFormat": "Current Week",
+ "refId": "B"
+ },
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",protocol=~\"kafka-fetcher|grpc\"}[1d] offset 1w))",
+ "interval": "1d",
+ "legendFormat": "Last Week",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": "7d",
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Day",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": false
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 80
+ },
+ "hiddenSeries": false,
+ "id": 23,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(metrics_aggregation{job=\"$job\"}[1m])) by (level)",
+ "interval": "1m",
+ "legendFormat": "Level{{level}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Aggregation (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "description": "",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 86
+ },
+ "hiddenSeries": false,
+ "id": 29,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(remote_out_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(remote_out_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}} -> {{dest}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Remote Out Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 86
+ },
+ "hiddenSeries": false,
+ "id": 30,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(rate(remote_in_latency_count{job=\"$job\"}[1m]))",
+ "legendFormat": "total",
+ "refId": "A"
+ },
+ {
+ "expr": "rate(remote_in_latency_count{job=\"$job\"}[1m])",
+ "legendFormat": "{{instance}}",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Remote In Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "cacheTimeout": null,
+ "columns": [
+ {
+ "text": "Current",
+ "value": "current"
+ }
+ ],
+ "datasource": "$datasource",
+ "fontSize": "100%",
+ "gridPos": {
+ "h": 12,
+ "w": 8,
+ "x": 16,
+ "y": 86
+ },
+ "id": 47,
+ "links": [],
+ "options": {},
+ "pageSize": null,
+ "showHeader": true,
+ "sort": {
+ "col": 1,
+ "desc": true
+ },
+ "styles": [
+ {
+ "alias": "Metric Name",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Metric",
+ "thresholds": [],
+ "type": "string",
+ "unit": "short"
+ },
+ {
+ "alias": "Total Count",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "decimals": 2,
+ "mappingType": 1,
+ "pattern": "Current",
+ "thresholds": [],
+ "type": "number",
+ "unit": "short"
+ }
+ ],
+ "targets": [
+ {
+ "expr": "sum(metrics_aggregation{job=\"$job\"}) by (metricName)",
+ "format": "time_series",
+ "legendFormat": "{{metricName}}",
+ "refId": "A"
+ }
+ ],
+ "title": "Metrics Aggregation Total Count",
+ "transform": "timeseries_aggregations",
+ "type": "table"
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 92
+ },
+ "hiddenSeries": false,
+ "id": 18,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_prepare_latency_count{job=\"$job\"}[1m])",
+ "instant": false,
+ "interval": "1m",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Prepare Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 92
+ },
+ "hiddenSeries": false,
+ "id": 31,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_prepare_latency_sum{job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Prepare Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 98
+ },
+ "hiddenSeries": false,
+ "id": 32,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_execute_latency_count{job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Execution Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 98
+ },
+ "hiddenSeries": false,
+ "id": 16,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_execute_latency_sum{job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Execution Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 98
+ },
+ "hiddenSeries": false,
+ "id": 46,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_error_count{job=\"$job\"}[1m])",
+ "instant": false,
+ "interval": "1m",
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ }
+ ],
+ "refresh": false,
+ "schemaVersion": 21,
+ "style": "dark",
+ "tags": [
+ "skywalking"
+ ],
+ "templating": {
+ "list": [
+ {
+ "current": {
+ "text": "prometheus-sw",
+ "value": "prometheus-sw"
+ },
+ "hide": 0,
+ "includeAll": false,
+ "label": null,
+ "multi": false,
+ "name": "datasource",
+ "options": [],
+ "query": "prometheus",
+ "refresh": 1,
+ "regex": "",
+ "skipUrlSync": false,
+ "type": "datasource"
+ },
+ {
+ "allValue": null,
+ "current": {},
+ "datasource": "$datasource",
+ "definition": "label_values(job)",
+ "hide": 0,
+ "includeAll": false,
+ "label": null,
+ "multi": false,
+ "name": "job",
+ "options": [],
+ "query": "label_values(job)",
+ "refresh": 1,
+ "regex": "",
+ "skipUrlSync": false,
+ "sort": 0,
+ "tagValuesQuery": "",
+ "tags": [],
+ "tagsQuery": "",
+ "type": "query",
+ "useTags": false
+ }
+ ]
+ },
+ "time": {
+ "from": "now-5m",
+ "to": "now"
+ },
+ "timepicker": {
+ "refresh_intervals": [
+ "5s",
+ "10s",
+ "30s",
+ "1m",
+ "5m",
+ "15m",
+ "30m",
+ "1h",
+ "2h",
+ "1d"
+ ],
+ "time_options": [
+ "5m",
+ "15m",
+ "1h",
+ "6h",
+ "12h",
+ "24h",
+ "2d",
+ "7d",
+ "30d"
+ ]
+ },
+ "timezone": "",
+ "title": "SkyWalking OAP Cluster Monitor Dashboard",
+ "uid": "7NEmel8mkc",
+ "version": 41
+}
\ No newline at end of file
diff --git a/docs/en/setup/backend/grafana-instance.json b/docs/en/setup/backend/grafana-instance.json
new file mode 100644
index 000000000000..530c995b9534
--- /dev/null
+++ b/docs/en/setup/backend/grafana-instance.json
@@ -0,0 +1,5326 @@
+{
+ "__inputs": [
+ {
+ "name": "DS_PROMETHEUS-SW",
+ "label": "prometheus-sw",
+ "description": "",
+ "type": "datasource",
+ "pluginId": "prometheus",
+ "pluginName": "Prometheus"
+ }
+ ],
+ "annotations": {
+ "list": [
+ {
+ "builtIn": 1,
+ "datasource": "${DS_PROMETHEUS-SW}",
+ "enable": true,
+ "hide": true,
+ "iconColor": "rgba(0, 211, 255, 1)",
+ "name": "Annotations & Alerts",
+ "type": "dashboard"
+ }
+ ]
+ },
+ "description": "SkyWalking OAP Instance Monitor Dashboard",
+ "editable": true,
+ "gnetId": null,
+ "graphTooltip": 0,
+ "id": null,
+ "iteration": 1705280937759,
+ "links": [],
+ "panels": [
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 0
+ },
+ "id": 67,
+ "panels": [],
+ "title": "Basic Info",
+ "type": "row"
+ },
+ {
+ "cacheTimeout": null,
+ "colorBackground": false,
+ "colorValue": false,
+ "colors": [
+ "#299c46",
+ "rgba(237, 129, 40, 0.89)",
+ "#d44a3a"
+ ],
+ "datasource": "$datasource",
+ "decimals": null,
+ "format": "dateTimeAsIso",
+ "gauge": {
+ "maxValue": 100,
+ "minValue": 0,
+ "show": false,
+ "thresholdLabels": false,
+ "thresholdMarkers": true
+ },
+ "gridPos": {
+ "h": 3,
+ "w": 8,
+ "x": 0,
+ "y": 1
+ },
+ "id": 31,
+ "interval": null,
+ "links": [],
+ "mappingType": 1,
+ "mappingTypes": [
+ {
+ "name": "value to text",
+ "value": 1
+ },
+ {
+ "name": "range to text",
+ "value": 2
+ }
+ ],
+ "maxDataPoints": 100,
+ "nullPointMode": "connected",
+ "nullText": null,
+ "options": {},
+ "postfix": "",
+ "postfixFontSize": "50%",
+ "prefix": "",
+ "prefixFontSize": "50%",
+ "rangeMaps": [
+ {
+ "from": "null",
+ "text": "N/A",
+ "to": "null"
+ }
+ ],
+ "sparkline": {
+ "fillColor": "rgba(31, 118, 189, 0.18)",
+ "full": false,
+ "lineColor": "rgb(31, 120, 193)",
+ "show": false,
+ "ymax": null,
+ "ymin": null
+ },
+ "tableColumn": "",
+ "targets": [
+ {
+ "expr": "process_start_time_seconds{job=\"$job\",instance=\"$instance\"}*1000",
+ "legendFormat": "",
+ "refId": "A"
+ }
+ ],
+ "thresholds": "",
+ "timeFrom": null,
+ "timeShift": null,
+ "title": "Start Time",
+ "type": "singlestat",
+ "valueFontSize": "80%",
+ "valueMaps": [
+ {
+ "op": "=",
+ "text": "N/A",
+ "value": "null"
+ }
+ ],
+ "valueName": "avg"
+ },
+ {
+ "cacheTimeout": null,
+ "colorBackground": false,
+ "colorValue": false,
+ "colors": [
+ "#299c46",
+ "rgba(237, 129, 40, 0.89)",
+ "#d44a3a"
+ ],
+ "datasource": "$datasource",
+ "format": "s",
+ "gauge": {
+ "maxValue": 100,
+ "minValue": 0,
+ "show": false,
+ "thresholdLabels": false,
+ "thresholdMarkers": true
+ },
+ "gridPos": {
+ "h": 3,
+ "w": 8,
+ "x": 8,
+ "y": 1
+ },
+ "id": 69,
+ "interval": null,
+ "links": [],
+ "mappingType": 1,
+ "mappingTypes": [
+ {
+ "name": "value to text",
+ "value": 1
+ },
+ {
+ "name": "range to text",
+ "value": 2
+ }
+ ],
+ "maxDataPoints": 100,
+ "nullPointMode": "connected",
+ "nullText": null,
+ "options": {},
+ "postfix": "",
+ "postfixFontSize": "50%",
+ "prefix": "",
+ "prefixFontSize": "50%",
+ "rangeMaps": [
+ {
+ "from": "null",
+ "text": "N/A",
+ "to": "null"
+ }
+ ],
+ "sparkline": {
+ "fillColor": "rgba(31, 118, 189, 0.18)",
+ "full": false,
+ "lineColor": "rgb(31, 120, 193)",
+ "show": false,
+ "ymax": null,
+ "ymin": null
+ },
+ "tableColumn": "",
+ "targets": [
+ {
+ "expr": "time() - process_start_time_seconds{job=\"$job\",instance=\"$instance\"}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": "",
+ "timeFrom": null,
+ "timeShift": null,
+ "title": "Run Time",
+ "type": "singlestat",
+ "valueFontSize": "80%",
+ "valueMaps": [
+ {
+ "op": "=",
+ "text": "N/A",
+ "value": "null"
+ }
+ ],
+ "valueName": "avg"
+ },
+ {
+ "cacheTimeout": null,
+ "colorBackground": false,
+ "colorValue": false,
+ "colors": [
+ "#299c46",
+ "rgba(237, 129, 40, 0.89)",
+ "#d44a3a"
+ ],
+ "datasource": "$datasource",
+ "format": "none",
+ "gauge": {
+ "maxValue": 100,
+ "minValue": 0,
+ "show": false,
+ "thresholdLabels": false,
+ "thresholdMarkers": true
+ },
+ "gridPos": {
+ "h": 3,
+ "w": 8,
+ "x": 16,
+ "y": 1
+ },
+ "id": 91,
+ "interval": null,
+ "links": [],
+ "mappingType": 1,
+ "mappingTypes": [
+ {
+ "name": "value to text",
+ "value": 1
+ },
+ {
+ "name": "range to text",
+ "value": 2
+ }
+ ],
+ "maxDataPoints": 100,
+ "nullPointMode": "connected",
+ "nullText": null,
+ "options": {},
+ "postfix": "",
+ "postfixFontSize": "50%",
+ "prefix": "",
+ "prefixFontSize": "50%",
+ "rangeMaps": [
+ {
+ "from": "null",
+ "text": "N/A",
+ "to": "null"
+ }
+ ],
+ "sparkline": {
+ "fillColor": "rgba(31, 118, 189, 0.18)",
+ "full": false,
+ "lineColor": "rgb(31, 120, 193)",
+ "show": false,
+ "ymax": null,
+ "ymin": null
+ },
+ "tableColumn": "jdk",
+ "targets": [
+ {
+ "expr": "label_join(jvm_info{job=\"$job\",instance=\"$instance\"}, \"jdk\", \", \", \"vendor\", \"runtime\", \"version\")",
+ "format": "table",
+ "instant": true,
+ "refId": "A"
+ }
+ ],
+ "thresholds": "",
+ "timeFrom": null,
+ "timeShift": null,
+ "title": "JVM Info",
+ "type": "singlestat",
+ "valueFontSize": "80%",
+ "valueMaps": [
+ {
+ "op": "=",
+ "text": "N/A",
+ "value": "null"
+ }
+ ],
+ "valueName": "first"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 4
+ },
+ "hiddenSeries": false,
+ "id": 25,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(process_cpu_seconds_total{instance=\"$instance\",job=\"$job\"}[1m]) * 100 / 60",
+ "legendFormat": "CPU",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "CPU * Cores number",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "percent",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 4
+ },
+ "hiddenSeries": false,
+ "id": 87,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "process_resident_memory_bytes{job=\"$job\",instance=\"$instance\"}",
+ "legendFormat": "Resident",
+ "refId": "A"
+ },
+ {
+ "expr": "process_virtual_memory_bytes{job=\"$job\",instance=\"$instance\"}",
+ "legendFormat": "Virtual",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Memory",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "cacheTimeout": null,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 4
+ },
+ "hiddenSeries": false,
+ "id": 35,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pluginVersion": "6.5.2",
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "process_open_fds{job=\"$job\",instance=\"$instance\"}",
+ "legendFormat": "Current",
+ "refId": "A"
+ },
+ {
+ "expr": "process_max_fds{job=\"$job\",instance=\"$instance\"}",
+ "legendFormat": "Max",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Open File Descriptors",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 10
+ },
+ "id": 65,
+ "panels": [],
+ "title": "Thread Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 11
+ },
+ "hiddenSeries": false,
+ "id": 43,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_threads_current{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "Current",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_threads_daemon{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "Daemon",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_threads_peak{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "Peak",
+ "refId": "C"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Thread Count",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 11
+ },
+ "hiddenSeries": false,
+ "id": 73,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_threads_state{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{state}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Thread State",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 11
+ },
+ "hiddenSeries": false,
+ "id": 79,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_threads_started_total{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "Started Total",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "JVM Thread Started Total",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 17
+ },
+ "id": 63,
+ "panels": [],
+ "title": "Memory Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 18
+ },
+ "hiddenSeries": false,
+ "id": 29,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_memory_bytes_used{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{area}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_memory_bytes_committed{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{area}}-committed",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_memory_bytes_max{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{area}}-max",
+ "refId": "C"
+ },
+ {
+ "expr": "jvm_memory_bytes_init{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{area}}-init",
+ "refId": "D"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Heap/Nonheap",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "percentunit",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 18
+ },
+ "hiddenSeries": false,
+ "id": 75,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_memory_pool_bytes_used{instance=\"$instance\",job=\"$job\"}",
+ "intervalFactor": 1,
+ "legendFormat": "{{pool}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_committed{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}-committed",
+ "refId": "B"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_max{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}-max",
+ "refId": "C"
+ },
+ {
+ "expr": "jvm_memory_pool_bytes_init{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}-init",
+ "refId": "D"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Memory Pool Used",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 18
+ },
+ "hiddenSeries": false,
+ "id": 77,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(jvm_memory_pool_allocated_bytes_total{instance=\"$instance\",job=\"$job\"}[1m])",
+ "legendFormat": "{{pool}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Memory Pool Allocated",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 24
+ },
+ "id": 61,
+ "panels": [],
+ "title": "GC Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 25
+ },
+ "hiddenSeries": false,
+ "id": 27,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(jvm_gc_collection_seconds_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{gc}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "GC Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 25
+ },
+ "hiddenSeries": false,
+ "id": 81,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(jvm_gc_collection_seconds_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "interval": "1m",
+ "legendFormat": "{{gc}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "GC Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 31
+ },
+ "id": 59,
+ "panels": [],
+ "title": "Classes Loaded Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 32
+ },
+ "hiddenSeries": false,
+ "id": 41,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_classes_loaded{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "jvm_classes_loaded",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Classes Loaded",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "cacheTimeout": null,
+ "colorBackground": false,
+ "colorValue": false,
+ "colors": [
+ "#299c46",
+ "rgba(237, 129, 40, 0.89)",
+ "#d44a3a"
+ ],
+ "datasource": "$datasource",
+ "format": "none",
+ "gauge": {
+ "maxValue": 100,
+ "minValue": 0,
+ "show": false,
+ "thresholdLabels": false,
+ "thresholdMarkers": true
+ },
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 32
+ },
+ "id": 83,
+ "interval": null,
+ "links": [],
+ "mappingType": 1,
+ "mappingTypes": [
+ {
+ "name": "value to text",
+ "value": 1
+ },
+ {
+ "name": "range to text",
+ "value": 2
+ }
+ ],
+ "maxDataPoints": 100,
+ "nullPointMode": "connected",
+ "nullText": null,
+ "options": {},
+ "postfix": "",
+ "postfixFontSize": "50%",
+ "prefix": "",
+ "prefixFontSize": "50%",
+ "rangeMaps": [
+ {
+ "from": "null",
+ "text": "N/A",
+ "to": "null"
+ }
+ ],
+ "sparkline": {
+ "fillColor": "rgba(31, 118, 189, 0.18)",
+ "full": false,
+ "lineColor": "rgb(31, 120, 193)",
+ "show": false,
+ "ymax": null,
+ "ymin": null
+ },
+ "tableColumn": "",
+ "targets": [
+ {
+ "expr": "jvm_classes_unloaded_total{instance=\"$instance\",job=\"$job\"}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": "",
+ "timeFrom": null,
+ "timeShift": null,
+ "title": "Classes Unloaded",
+ "type": "singlestat",
+ "valueFontSize": "80%",
+ "valueMaps": [
+ {
+ "op": "=",
+ "text": "N/A",
+ "value": "null"
+ }
+ ],
+ "valueName": "avg"
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 38
+ },
+ "id": 57,
+ "panels": [],
+ "title": "Buffer Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 39
+ },
+ "hiddenSeries": false,
+ "id": 33,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_buffer_pool_used_bytes{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}-used",
+ "refId": "A"
+ },
+ {
+ "expr": "jvm_buffer_pool_capacity_bytes{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}-capacity",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Buffer Pool Bytes",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "decbytes",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 39
+ },
+ "hiddenSeries": false,
+ "id": 85,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "jvm_buffer_pool_used_buffers{instance=\"$instance\",job=\"$job\"}",
+ "legendFormat": "{{pool}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Buffer Pool Buffers",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "collapsed": false,
+ "datasource": null,
+ "gridPos": {
+ "h": 1,
+ "w": 24,
+ "x": 0,
+ "y": 45
+ },
+ "id": 53,
+ "panels": [],
+ "title": "OAP Info",
+ "type": "row"
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 46
+ },
+ "hiddenSeries": false,
+ "id": 2,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(trace_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 46
+ },
+ "hiddenSeries": false,
+ "id": 6,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(trace_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 46
+ },
+ "hiddenSeries": false,
+ "id": 11,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(trace_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 52
+ },
+ "hiddenSeries": false,
+ "id": 92,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(mesh_analysis_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 52
+ },
+ "hiddenSeries": false,
+ "id": 93,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(mesh_analysis_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 52
+ },
+ "hiddenSeries": false,
+ "id": 94,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(mesh_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Mesh Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 58
+ },
+ "hiddenSeries": false,
+ "id": 123,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(k8s_als_in_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "interval": "",
+ "legendFormat": "",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeRegions": [],
+ "title": "K8S ALS Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 58
+ },
+ "hiddenSeries": false,
+ "id": 125,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(k8s_als_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "interval": "",
+ "legendFormat": "",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeRegions": [],
+ "title": "K8S ALS Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": null,
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 58
+ },
+ "hiddenSeries": false,
+ "id": 127,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(k8s_als_drop_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "interval": "",
+ "legendFormat": "",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeRegions": [],
+ "title": "K8S ALS Drop Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 64
+ },
+ "hiddenSeries": false,
+ "id": 101,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(meter_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 64
+ },
+ "hiddenSeries": false,
+ "id": 102,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(meter_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 64
+ },
+ "hiddenSeries": false,
+ "id": 103,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(meter_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Meter Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 70
+ },
+ "hiddenSeries": false,
+ "id": 104,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(log_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 70
+ },
+ "hiddenSeries": false,
+ "id": 105,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(log_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 70
+ },
+ "hiddenSeries": false,
+ "id": 106,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(log_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Log Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 76
+ },
+ "hiddenSeries": false,
+ "id": 107,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(event_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 76
+ },
+ "hiddenSeries": false,
+ "id": 108,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(event_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 76
+ },
+ "hiddenSeries": false,
+ "id": 109,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(event_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Event Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 82
+ },
+ "hiddenSeries": false,
+ "id": 110,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(browser_perf_data_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 82
+ },
+ "hiddenSeries": false,
+ "id": 111,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_perf_data_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 82
+ },
+ "hiddenSeries": false,
+ "id": 112,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_perf_data_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Perf Data Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 88
+ },
+ "hiddenSeries": false,
+ "id": 113,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(browser_error_log_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Received Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 88
+ },
+ "hiddenSeries": false,
+ "id": 114,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_error_log_in_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Analysis Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 88
+ },
+ "hiddenSeries": false,
+ "id": 115,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(browser_error_log_analysis_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{protocol}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Browser Error Log Analysis Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 94
+ },
+ "hiddenSeries": false,
+ "id": 116,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(metrics_fetcher_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 94
+ },
+ "hiddenSeries": false,
+ "id": 117,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(metrics_fetcher_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "instant": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 94
+ },
+ "hiddenSeries": false,
+ "id": 118,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(metrics_fetcher_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Fetcher Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 100
+ },
+ "hiddenSeries": false,
+ "id": 119,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 1,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",instance=\"$instance\",protocol=~\"kafka-fetcher|grpc\"}[1h]))",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1h",
+ "intervalFactor": 1,
+ "legendFormat": "Current Week",
+ "refId": "A"
+ },
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",instance=\"$instance\",protocol=~\"kafka-fetcher|grpc\"}[1h] offset 1w))",
+ "interval": "1h",
+ "legendFormat": "Last Week",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": "1d",
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Hour",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": false
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 100
+ },
+ "hiddenSeries": false,
+ "id": 120,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",instance=\"$instance\",protocol=~\"kafka-fetcher|grpc\"}[1d]))",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1d",
+ "intervalFactor": 1,
+ "legendFormat": "Current Week",
+ "refId": "A"
+ },
+ {
+ "expr": "sum(increase(trace_in_latency_count{job=\"$job\",instance=\"$instance\",protocol=~\"kafka-fetcher|grpc\"}[1d] offset 1w))",
+ "interval": "1d",
+ "legendFormat": "Last Week",
+ "refId": "B"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": "7d",
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Trace Segment Received Count / Day",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": false
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 100
+ },
+ "hiddenSeries": false,
+ "id": 23,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "sum(increase(metrics_aggregation {instance=\"$instance\",job=\"$job\"} [1m])) by (level)",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Level{{level}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Metrics Aggregation (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 106
+ },
+ "hiddenSeries": false,
+ "id": 95,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(remote_out_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}} -> {{dest}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Remote Out Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 106
+ },
+ "hiddenSeries": false,
+ "id": 96,
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "rate(remote_in_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{instance}}",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Remote In Count / Second",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "columns": [
+ {
+ "text": "Current",
+ "value": "current"
+ }
+ ],
+ "datasource": "$datasource",
+ "fontSize": "100%",
+ "gridPos": {
+ "h": 12,
+ "w": 8,
+ "x": 16,
+ "y": 106
+ },
+ "id": 121,
+ "links": [],
+ "options": {},
+ "pageSize": null,
+ "showHeader": true,
+ "sort": {
+ "col": 0,
+ "desc": true
+ },
+ "styles": [
+ {
+ "alias": "Metric Name",
+ "dateFormat": "YYYY-MM-DD HH:mm:ss",
+ "mappingType": 1,
+ "pattern": "Metric",
+ "type": "string"
+ },
+ {
+ "alias": "Total Count",
+ "colorMode": null,
+ "colors": [
+ "rgba(245, 54, 54, 0.9)",
+ "rgba(237, 129, 40, 0.89)",
+ "rgba(50, 172, 45, 0.97)"
+ ],
+ "decimals": 2,
+ "pattern": "Current",
+ "thresholds": [],
+ "type": "number",
+ "unit": "short"
+ }
+ ],
+ "targets": [
+ {
+ "expr": "sum(metrics_aggregation{instance=\"$instance\",job=\"$job\"}) by (metricName)",
+ "format": "time_series",
+ "hide": false,
+ "intervalFactor": 1,
+ "legendFormat": "{{metricName}}",
+ "refId": "A"
+ }
+ ],
+ "timeFrom": null,
+ "timeShift": null,
+ "title": "Metrics Aggregation Total Count",
+ "transform": "timeseries_aggregations",
+ "type": "table"
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 112
+ },
+ "hiddenSeries": false,
+ "id": 18,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_prepare_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Prepare Count",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Prepare Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 112
+ },
+ "hiddenSeries": false,
+ "id": 98,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_prepare_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Prepare Time",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Prepare Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 0,
+ "y": 118
+ },
+ "hiddenSeries": false,
+ "id": 97,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 2,
+ "points": true,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_execute_latency_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Execution Count",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Execution Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": false,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 8,
+ "y": 118
+ },
+ "hiddenSeries": false,
+ "id": 99,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": true,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_execute_latency_sum{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Execution Time",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Execution Time (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "s",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ },
+ {
+ "aliasColors": {},
+ "bars": true,
+ "dashLength": 10,
+ "dashes": false,
+ "datasource": "$datasource",
+ "fill": 1,
+ "fillGradient": 0,
+ "gridPos": {
+ "h": 6,
+ "w": 8,
+ "x": 16,
+ "y": 118
+ },
+ "hiddenSeries": false,
+ "id": 100,
+ "interval": "1m",
+ "legend": {
+ "avg": false,
+ "current": false,
+ "max": false,
+ "min": false,
+ "show": true,
+ "total": false,
+ "values": false
+ },
+ "lines": false,
+ "linewidth": 1,
+ "links": [],
+ "nullPointMode": "null",
+ "options": {
+ "dataLinks": []
+ },
+ "percentage": false,
+ "pointradius": 5,
+ "points": false,
+ "renderer": "flot",
+ "seriesOverrides": [],
+ "spaceLength": 10,
+ "stack": false,
+ "steppedLine": false,
+ "targets": [
+ {
+ "expr": "increase(persistence_timer_bulk_error_count{instance=\"$instance\",job=\"$job\"}[1m])",
+ "format": "time_series",
+ "hide": false,
+ "interval": "1m",
+ "intervalFactor": 1,
+ "legendFormat": "Bulk Error Count",
+ "refId": "A"
+ }
+ ],
+ "thresholds": [],
+ "timeFrom": null,
+ "timeRegions": [],
+ "timeShift": null,
+ "title": "Persistence Error Count (Increment) / Minute",
+ "tooltip": {
+ "shared": true,
+ "sort": 0,
+ "value_type": "individual"
+ },
+ "type": "graph",
+ "xaxis": {
+ "buckets": null,
+ "mode": "time",
+ "name": null,
+ "show": true,
+ "values": []
+ },
+ "yaxes": [
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ },
+ {
+ "format": "short",
+ "label": null,
+ "logBase": 1,
+ "max": null,
+ "min": null,
+ "show": true
+ }
+ ],
+ "yaxis": {
+ "align": false,
+ "alignLevel": null
+ }
+ }
+ ],
+ "refresh": "",
+ "schemaVersion": 27,
+ "style": "dark",
+ "tags": [
+ "skywalking"
+ ],
+ "templating": {
+ "list": [
+ {
+ "current": {
+ "text": "prometheus-sw",
+ "value": "prometheus-sw"
+ },
+ "hide": 0,
+ "includeAll": false,
+ "label": null,
+ "multi": false,
+ "name": "datasource",
+ "options": [],
+ "query": "prometheus",
+ "refresh": 1,
+ "regex": "",
+ "skipUrlSync": false,
+ "type": "datasource"
+ },
+ {
+ "allValue": null,
+ "current": {},
+ "datasource": "$datasource",
+ "definition": "label_values(job)",
+ "hide": 0,
+ "includeAll": false,
+ "label": null,
+ "multi": false,
+ "name": "job",
+ "options": [],
+ "query": "label_values(job)",
+ "refresh": 1,
+ "regex": "",
+ "skipUrlSync": false,
+ "sort": 0,
+ "tagValuesQuery": "",
+ "tags": [],
+ "tagsQuery": "",
+ "type": "query",
+ "useTags": false
+ },
+ {
+ "allValue": null,
+ "current": {},
+ "datasource": "${DS_PROMETHEUS-SW}",
+ "definition": "label_values(process_cpu_seconds_total{job=\"$job\"},instance)",
+ "hide": 0,
+ "includeAll": false,
+ "label": "instance",
+ "multi": false,
+ "name": "instance",
+ "options": [],
+ "query": "label_values(process_cpu_seconds_total{job=\"$job\"},instance)",
+ "refresh": 1,
+ "regex": "",
+ "skipUrlSync": false,
+ "sort": 0,
+ "tagValuesQuery": "",
+ "tags": [],
+ "tagsQuery": "",
+ "type": "query",
+ "useTags": false
+ }
+ ]
+ },
+ "time": {
+ "from": "now-5m",
+ "to": "now"
+ },
+ "timepicker": {
+ "refresh_intervals": [
+ "5s",
+ "10s",
+ "30s",
+ "1m",
+ "5m",
+ "15m",
+ "30m",
+ "1h",
+ "2h",
+ "1d"
+ ],
+ "time_options": [
+ "5m",
+ "15m",
+ "1h",
+ "6h",
+ "12h",
+ "24h",
+ "2d",
+ "7d",
+ "30d"
+ ]
+ },
+ "timezone": "",
+ "title": "SkyWalking OAP Instance Monitor Dashboard",
+ "uid": "7NEmel8mki",
+ "version": 30
+}
\ No newline at end of file
diff --git a/docs/en/setup/backend/grpc-security.md b/docs/en/setup/backend/grpc-security.md
new file mode 100644
index 000000000000..d5dae1984524
--- /dev/null
+++ b/docs/en/setup/backend/grpc-security.md
@@ -0,0 +1,91 @@
+# gRPC SSL transportation support for OAP server
+
+For OAP communication, we are currently using gRPC, a multi-platform RPC framework that uses protocol buffers for message serialization. The nice part about gRPC is that it promotes the use of SSL/TLS to authenticate and encrypt exchanges. Now OAP supports enabling SSL transportation for gRPC receivers. Since 8.8.0, OAP supports enabling mutual TLS authentication between probes and OAP servers.
+
+To enable this feature, follow the steps below.
+
+## Preparation
+
+
+By default, the communication between OAP nodes and the communication between receiver and probe share the same gRPC server. Its configuration is in `application.yml/core/default` section.
+
+The advanced gRPC receiver is only for communication with the probes. This configuration is in `application.yml/receiver-sharing-server/default` section.
+
+
+The first step is to generate certificates and private key files for encrypting communication.
+
+### Creating SSL/TLS Certificates
+
+The first step is to generate certificates and key files for encrypting communication. This is fairly straightforward: use `openssl` from the command line.
+
+Use this [script](../../../../tools/TLS/tls_key_generate.sh) if you are not familiar with how to generate key files.
+
+We need the following files:
+
+* `ca.crt`: A certificate authority public key for a client to validate the server's certificate.
+* `server.pem`, `client.pem`: A private RSA key to sign and authenticate the public key. It's either a PKCS#8(PEM) or PKCS#1(DER).
+* `server.crt`, `client.crt`: Self-signed X.509 public keys for distribution.
+
+## TLS on OAP servers
+
+By default, the communication between OAP nodes and the communication between receiver and probe share the same gRPC server. That means once you enable SSL for receivers and probes, the OAP nodes will enable it too.
+
+
+**NOTE**: SkyWalking **does not** support enabling mTLS on `OAP server nodes communication`. That means you have to enable `receiver-sharing-server` for enabling mTLS on communication between probes and OAP servers. More details see [Enable mTLS mode on gRPC receiver](#enable-mtls-mode-on-grpc-receiver).
+
+
+You can enable gRPC SSL by adding the following lines to `application.yml/core/default`.
+
+```yaml
+gRPCSslEnabled: true
+gRPCSslKeyPath: /path/to/server.pem
+gRPCSslCertChainPath: /path/to/server.crt
+gRPCSslTrustedCAPath: /path/to/ca.crt
+```
+
+`gRPCSslKeyPath` and `gRPCSslCertChainPath` are loaded by the OAP server to encrypt communication. `gRPCSslTrustedCAPath`
+helps the gRPC client to verify server certificates in cluster mode.
+
+> There is a gRPC client and server in every OAP server node. The gRPC client communicates with OAP servers in cluster mode. They are sharing the core module configuration.
+
+**When new files are in place, they can be loaded dynamically, and you won't have to restart an OAP instance.**
+
+
+## Enable TLS on independent gRPC receiver
+
+If you enable `receiver-sharing-server` to ingest data from an external source, add the following lines to `application.yml/receiver-sharing-server/default`:
+
+```yaml
+gRPCPort: ${SW_RECEIVER_GRPC_PORT:"changeMe"}
+gRPCSslEnabled: true
+gRPCSslKeyPath: /path/to/server.pem
+gRPCSslCertChainPath: /path/to/server.crt
+```
+
+Since `receiver-sharing-server` only receives data from an external source, it doesn't need a CA at all. But you have to configure the CA for the clients, such as [Java agent](http://github.com/apache/skywalking-java), [Satellite](http://github.com/apache/skywalking-satellite). If you port to the Java agent, refer to [the Java agent repo](http://github.com/apache/skywalking-java) to configure the Java agent and enable TLS.
+
+**NOTE**: change the `SW_RECEIVER_GRPC_PORT` as non-zero to enable `receiver-sharing-server`. And the port is open for the clients.
+
+### Enable mTLS mode on gRPC receiver
+
+Since 8.8.0, SkyWalking has supported mutual TLS authentication for transporting between clients and OAP servers. Enable `mTLS` mode for the gRPC channel requires [Sharing gRPC Server](backend-expose.md) enabled, as the following configuration.
+
+```yaml
+receiver-sharing-server:
+ selector: ${SW_RECEIVER_SHARING_SERVER:default}
+ default:
+ # For gRPC server
+ gRPCHost: ${SW_RECEIVER_GRPC_HOST:0.0.0.0}
+ gRPCPort: ${SW_RECEIVER_GRPC_PORT:"changeMe"}
+ maxConcurrentCallsPerConnection: ${SW_RECEIVER_GRPC_MAX_CONCURRENT_CALL:0}
+ maxMessageSize: ${SW_RECEIVER_GRPC_MAX_MESSAGE_SIZE:52428800} #50MB
+ gRPCThreadPoolSize: ${SW_RECEIVER_GRPC_THREAD_POOL_SIZE:0}
+ gRPCSslEnabled: ${SW_RECEIVER_GRPC_SSL_ENABLED:true}
+ gRPCSslKeyPath: ${SW_RECEIVER_GRPC_SSL_KEY_PATH:"/path/to/server.pem"}
+ gRPCSslCertChainPath: ${SW_RECEIVER_GRPC_SSL_CERT_CHAIN_PATH:"/path/to/server.crt"}
+ gRPCSslTrustedCAsPath: ${SW_RECEIVER_GRPC_SSL_TRUSTED_CAS_PATH:"/path/to/ca.crt"}
+ authentication: ${SW_AUTHENTICATION:""}
+```
+
+You can still use this [script](../../../../tools/TLS/tls_key_generate.sh) to generate CA certificate and the key files of server-side(for OAP Server) and client-side(for Agent/Satellite).
+You have to notice the keys, including server and client-side, are from the same CA certificate.
diff --git a/docs/en/setup/backend/kafka-fetcher.md b/docs/en/setup/backend/kafka-fetcher.md
new file mode 100644
index 000000000000..f86e6c95c74d
--- /dev/null
+++ b/docs/en/setup/backend/kafka-fetcher.md
@@ -0,0 +1,50 @@
+# Kafka Fetcher
+
+The Kafka Fetcher pulls messages from the Kafka Broker to learn about what agents have delivered. Check the agent documentation for details on how to enable the Kafka reporter. Typically, tracing segments, service/instance properties, JVM metrics, and meter system data are supported (depending on the agent implementation). Kafka Fetcher can work with gRPC/HTTP Receivers simultaneously for adopting different transport protocols.
+
+Kafka Fetcher is disabled by default. To enable it, configure it as follows.
+
+Namespace aims to isolate multi OAP clusters when using the same Kafka cluster.
+If you set a namespace for Kafka fetcher, the OAP will add a prefix to the topic name. You should also set the namespace in the property named `plugin.kafka.namespace` in `agent.config`.
+
+```yaml
+kafka-fetcher:
+ selector: ${SW_KAFKA_FETCHER:default}
+ default:
+ bootstrapServers: ${SW_KAFKA_FETCHER_SERVERS:localhost:9092}
+ namespace: ${SW_NAMESPACE:""}
+```
+
+`skywalking-segments`, `skywalking-metrics`, `skywalking-profilings`, `skywalking-managements`, `skywalking-meters`, `skywalking-logs`
+and `skywalking-logs-json` topics are required by `kafka-fetcher`.
+If they do not exist, Kafka Fetcher will create them by default. Also, you can create them by yourself before the OAP server starts.
+
+When using the OAP server automatic creation mechanism, you could modify the number of partitions and replications of the topics using the following configurations:
+
+```yaml
+kafka-fetcher:
+ selector: ${SW_KAFKA_FETCHER:default}
+ default:
+ bootstrapServers: ${SW_KAFKA_FETCHER_SERVERS:localhost:9092}
+ namespace: ${SW_NAMESPACE:""}
+ partitions: ${SW_KAFKA_FETCHER_PARTITIONS:3}
+ replicationFactor: ${SW_KAFKA_FETCHER_PARTITIONS_FACTOR:2}
+ consumers: ${SW_KAFKA_FETCHER_CONSUMERS:1}
+```
+
+When using Kafka MirrorMaker 2.0 to replicate topics between Kafka clusters, you can set the source Kafka Cluster alias (mm2SourceAlias) and separator (mm2SourceSeparator) according to your Kafka MirrorMaker [config](https://github.com/apache/kafka/tree/trunk/connect/mirror#remote-topics).
+```yaml
+kafka-fetcher:
+ selector: ${SW_KAFKA_FETCHER:default}
+ default:
+ bootstrapServers: ${SW_KAFKA_FETCHER_SERVERS:localhost:9092}
+ namespace: ${SW_NAMESPACE:""}
+ partitions: ${SW_KAFKA_FETCHER_PARTITIONS:3}
+ replicationFactor: ${SW_KAFKA_FETCHER_PARTITIONS_FACTOR:2}
+ consumers: ${SW_KAFKA_FETCHER_CONSUMERS:1}
+ mm2SourceAlias: ${SW_KAFKA_MM2_SOURCE_ALIAS:""}
+ mm2SourceSeparator: ${SW_KAFKA_MM2_SOURCE_SEPARATOR:""}
+ kafkaConsumerConfig:
+ enable.auto.commit: true
+ ...
+```
diff --git a/docs/en/setup/backend/log-agent-native.md b/docs/en/setup/backend/log-agent-native.md
new file mode 100644
index 000000000000..a3c41207595f
--- /dev/null
+++ b/docs/en/setup/backend/log-agent-native.md
@@ -0,0 +1,49 @@
+# Collecting Logs by Agents
+
+Some of SkyWalking native agents support collecting logs and sending them to OAP server without local files and/or file
+agents, which are listed in [here](filelog-native.md).
+
+## Java agent's toolkits
+
+Java agent provides toolkits for
+[log4j](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-log4j-1.x/),
+[log4j2](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-log4j-2.x/),
+and
+[logback](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-logback-1.x/)
+to report logs through gRPC with automatically injected trace context.
+
+[SkyWalking Satellite sidecar](https://github.com/apache/skywalking-satellite) is a recommended proxy/side that
+forwards logs (including the use of Kafka MQ to transport logs). When using this,
+open [kafka-fetcher](kafka-fetcher.md#kafka-fetcher)
+and enable configs `enableNativeProtoLog`.
+
+Java agent provides toolkits for
+[log4j](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-log4j-1.x/#print-skywalking-context-in-your-logs),
+[log4j2](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-log4j-2.x/#print-skywalking-context-in-your-logs),
+and
+[logback](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-logback-1.x/#print-skywalking-context-in-your-logs)
+to report logs through files with automatically injected trace context.
+
+Log framework config examples:
+
+- [log4j1.x fileAppender](../../../../test/e2e-v2/java-test-service/e2e-service-provider/src/main/resources/log4j.properties)
+- [log4j2.x fileAppender](../../../../test/e2e-v2/java-test-service/e2e-service-provider/src/main/resources/log4j2.xml)
+- [logback fileAppender](../../../../test/e2e-v2/java-test-service/e2e-service-provider/src/main/resources/logback.xml)
+
+## Python agent log reporter
+
+[SkyWalking Python Agent](https://github.com/apache/skywalking-python) implements a log reporter for the [logging
+module](https://docs.python.org/3/library/logging.html) with functionalities aligning with the Java toolkits.
+
+To explore how to enable the reporting features for your use cases, please refer to the
+[Log Reporter Doc](https://skywalking.apache.org/docs/skywalking-python/next/en/setup/advanced/logreporter/) for a
+detailed guide.
+
+## Golang agent log reporter
+
+[SkyWalking Golang Agent](https://github.com/apache/skywalking-go) implements a log reporter for the logging module
+with functionality is similar to that of the Java toolkits.
+
+To explore how to enable the reporting features for your use cases, please refer to the
+[Log Reporter Doc](https://skywalking.apache.org/docs/skywalking-go/next/en/advanced-features/manual-apis/toolkit-log/) for a
+detailed guide.
diff --git a/docs/en/setup/backend/log-analyzer.md b/docs/en/setup/backend/log-analyzer.md
new file mode 100644
index 000000000000..07b797b84931
--- /dev/null
+++ b/docs/en/setup/backend/log-analyzer.md
@@ -0,0 +1,17 @@
+# Log Analysis
+
+Log analyzer of OAP server supports native log data. OAP could use Log Analysis Language to
+structure log content through parsing, extracting and saving logs.
+The analyzer also uses Meter Analysis Language Engine for further metrics calculation.
+
+```yaml
+log-analyzer:
+ selector: ${SW_LOG_ANALYZER:default}
+ default:
+ lalFiles: ${SW_LOG_LAL_FILES:default}
+ malFiles: ${SW_LOG_MAL_FILES:""}
+```
+
+Read the doc on [Log Analysis Language(LAL)](../../concepts-and-designs/lal.md) for more on log structuring and metrics analysis.
+The [LAL's `metrics` extracts](../../concepts-and-designs/lal.md#extractor) provide the capabilities to generate new metrics
+from the raw log text for further calculation.
diff --git a/docs/en/setup/backend/log-otlp.md b/docs/en/setup/backend/log-otlp.md
new file mode 100644
index 000000000000..77c56daa9427
--- /dev/null
+++ b/docs/en/setup/backend/log-otlp.md
@@ -0,0 +1,55 @@
+# OpenTelemetry Logging Format
+
+SkyWalking can receive logs exported from OpenTelemetry collector, the data flow is:
+
+```mermaid
+graph LR
+ B[OpenTelemetry SDK 1]
+ C[FluentBit/FluentD, etc.]
+ K[Other sources that OpenTelemetry supports ...]
+ D[OpenTelemetry Collector]
+ E[SkyWalking OAP Server]
+ B --> D
+ C --> D
+ K --> D
+ D -- exporter --> E
+```
+
+Recommend to use [OpenTelemetry OTLP Exporter](#opentelemetry-otlp-exporter) to forward collected logs to OAP server in OTLP
+format, and SkyWalking OAP is responsible for transforming the data format into native log format with analysis support
+powered by [LAL script](../../concepts-and-designs/lal.md).
+
+___
+Deprecated: unmaintained and not recommended to use, will be removed.
+
+[OpenTelemetry SkyWalking Exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/5133f4ccd69fa40d016c5b7f2198fb6ac61007b4/exporter/skywalkingexporter) was first added into `open-telemetry/opentelemetry-collector-contrib` before
+OAP OTLP support. It transforms the logs to SkyWalking format before sending them to SkyWalking OAP. Currently, from OTLP
+community, it is not well maintained, and already being marked as `unmaintained`, and may be removed in 2024.
+___
+
+## OpenTelemetry OTLP Exporter
+
+By using this exporter, you can send any log data to SkyWalking OAP as long as the data is in OTLP format, no matter
+where the data is generated.
+
+To enable this exporter, make sure the `receiver-otel` is enabled and the `otlp-logs` value is in
+the `receiver-otel/default/enabledHandlers` configuration section:
+
+```yaml
+receiver-otel:
+ selector: ${SW_OTEL_RECEIVER:default}
+ default:
+ enabledHandlers: ${SW_OTEL_RECEIVER_ENABLED_HANDLERS:"otlp-metrics,otlp-logs"}
+```
+
+Also, because most of the language SDKs of OpenTelemetry do not support logging feature (yet) or the logging feature is
+experimental, it's your responsibility to make sure the reported log data contains the following attributes, otherwise
+SkyWalking is not able to consume them:
+
+- `service.name`: the name of the service that generates the log data.
+
+And several attributes are optional as add-on information for the logs before analyzing.
+- `service.layer`: the layer of the service that generates the logs. The default value is `GENERAL` layer, which is 100% sampled defined by [LAL general rule](https://github.com/apache/skywalking/blob/master/oap-server/server-starter/src/main/resources/lal/default.yaml)
+- `service.instance`: the instance name that generates the logs. The default value is empty.
+
+Note, that these attributes should be set manually through OpenTelemetry SDK or through [attribute#insert in OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/attributesprocessor/README.md).
diff --git a/docs/en/setup/backend/logs-template.json b/docs/en/setup/backend/logs-template.json
new file mode 100644
index 000000000000..28308b32db55
--- /dev/null
+++ b/docs/en/setup/backend/logs-template.json
@@ -0,0 +1,83 @@
+{
+ "timestamp": {
+ "type": "sequence",
+ "min": "1649643929000",
+ "max": "1649653929000"
+ },
+ "serviceName": {
+ "type": "randomString",
+ "length": "20",
+ "prefix": "test_svc_name_",
+ "letters": true,
+ "numbers": true
+ },
+ "serviceInstanceName": {
+ "type": "randomString",
+ "length": "20",
+ "prefix": "test_svc_inst_name_",
+ "letters": true,
+ "numbers": true
+ },
+ "endpointName": {
+ "type": "randomString",
+ "length": "20",
+ "prefix": "test_endpoint_",
+ "letters": true,
+ "numbers": true
+ },
+ "traceId": {
+ "type": "randomString",
+ "length": "20",
+ "prefix": "test_trace_id_",
+ "letters": true,
+ "numbers": true
+ },
+ "traceSegmentId": {
+ "type": "randomString",
+ "length": "20",
+ "prefix": "test",
+ "letters": true,
+ "numbers": true
+ },
+ "spanId": {
+ "type": "randomInt",
+ "min": "0",
+ "max": "5"
+ },
+ "contentType": {
+ "type": "randomInt",
+ "min": 1,
+ "max": 1
+ },
+ "content": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test",
+ "letters": true,
+ "numbers": true
+ },
+ "error": {
+ "type": "randomBool"
+ },
+ "tags": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "key": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ },
+ "value": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test",
+ "letters": true,
+ "numbers": true
+ }
+ }
+ }
+}
diff --git a/docs/en/setup/backend/marketplace.md b/docs/en/setup/backend/marketplace.md
new file mode 100644
index 000000000000..7a398b339796
--- /dev/null
+++ b/docs/en/setup/backend/marketplace.md
@@ -0,0 +1,12 @@
+# Marketplace
+
+**Marketplace** is the first UI menu on the SkyWalking native UI.
+
+The native out-of-box features are listed in the marketplace. Follow the `Documentation` guidance to set up the required components.
+Once SkyWalking detects the services of those layers, the relative menu will show up on the left automatically.
+
+If you prefer to have a custom dashboard to visualize your metrics, logs, and traces in your private setup, you need to
+1. Follow Tracing, Logging, and Metrics documentation to set up codes.
+2. Follow Customization documentation to add analysis pipeline.
+3. Follow [UI Customization Setup documentation](../../ui/README.md) to set up new UI dashboards.
+
diff --git a/docs/en/setup/backend/metrics-exporter.md b/docs/en/setup/backend/metrics-exporter.md
new file mode 100644
index 000000000000..aa0dfcd87973
--- /dev/null
+++ b/docs/en/setup/backend/metrics-exporter.md
@@ -0,0 +1 @@
+All SkyWalking exporter(metrics, trace, log) instructions had been moved [here](exporter.md).
diff --git a/docs/en/setup/backend/micrometer-observations.md b/docs/en/setup/backend/micrometer-observations.md
new file mode 100644
index 000000000000..dd2982df5603
--- /dev/null
+++ b/docs/en/setup/backend/micrometer-observations.md
@@ -0,0 +1,40 @@
+# MicroMeter Observations setup
+
+Micrometer Observation is part of the Micrometer project and contains the Observation API.
+SkyWalking integrates its MicroMeter 1.10 APIs so that it can send metrics to the SkyWalking [Meter System](./../../concepts-and-designs/mal.md).
+
+Follow Java agent [Observations docs](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-micrometer-1.10/) to set up agent in the Spring first.
+
+## Set up backend receiver
+
+1. Make sure to enable meter receiver in `application.yml`.
+```yaml
+receiver-meter:
+ selector: ${SW_RECEIVER_METER:default}
+ default:
+```
+
+2. Configure the meter config file. It already has the [spring sleuth meter config](../../../../oap-server/server-starter/src/main/resources/meter-analyzer-config/spring-micrometer.yaml).
+ If you have a customized meter at the agent side, please configure the meter using the steps set out in the [meter document](backend-meter.md#manual-meter-api).
+
+3. Enable Spring sleuth config in `application.yml`.
+```yaml
+agent-analyzer:
+ selector: ${SW_AGENT_ANALYZER:default}
+ default:
+ meterAnalyzerActiveFiles: ${SW_METER_ANALYZER_ACTIVE_FILES:spring-micrometer}
+```
+
+## Dashboard configuration
+
+SkyWalking provides the Spring Sleuth dashboard by default under the general service instance, which contains the metrics provided by Spring Sleuth by default.
+Once you have added customized metrics in the application and configuration the meter config file in the backend. Please following
+the [customized dashboard documentation](../../ui/README.md#metrics) to add the metrics in the dashboard.
+
+## Supported meter
+
+Three types of information are supported: Application, System, and JVM.
+
+1. Application: HTTP request count and duration, JDBC max/idle/active connection count, and Tomcat session active/reject count.
+1. System: CPU system/process usage, OS system load, and OS process file count.
+1. JVM: GC pause count and duration, memory max/used/committed size, thread peak/live/daemon count, and classes loaded/unloaded count.
diff --git a/docs/en/setup/backend/mq.md b/docs/en/setup/backend/mq.md
new file mode 100644
index 000000000000..553835979b08
--- /dev/null
+++ b/docs/en/setup/backend/mq.md
@@ -0,0 +1,14 @@
+# Message Queue performance and consuming latency monitoring
+
+Message Queue server plays an essential role in today's distributed system to reduce the length and latency of
+blocking RPC and eventually improve user experience. But in this async way, the measure for queue consuming traffic and
+latency becomes significant.
+
+Since 8.9.0, SkyWalking leverages native tracing agent and [**Extension Header
+Item** of SkyWalking Cross Process Propagation Headers Protocol v3](../../api/x-process-propagation-headers-v3.md#extension-header-item)
+To provide performance monitoring for the Message Queue systems.
+
+In default, we provide `Message Queue Consuming Count` and `Message Queue Avg Consuming Latency` metrics for service and
+endpoint levels.
+
+More metrics could be added through `core.oal`.
diff --git a/docs/en/setup/backend/on-demand-pod-log.md b/docs/en/setup/backend/on-demand-pod-log.md
new file mode 100644
index 000000000000..0b6b745ec8b6
--- /dev/null
+++ b/docs/en/setup/backend/on-demand-pod-log.md
@@ -0,0 +1,23 @@
+# On Demand Pod Logs
+
+This feature is to fetch the Pod logs on users' demand, the logs are fetched and displayed in real time,
+and are not persisted in any kind. This is helpful when users want to do some experiments and monitor the
+logs and see what's happing inside the service.
+
+Note: if you print secrets in the logs, they are also visible to the UI, so for the sake of security, this
+feature is disabled by default, please read the configuration documentation to enable this feature manually.
+
+## How it works
+
+As the name indicates, this feature only works for Kubernetes Pods.
+
+SkyWalking OAP collects and saves the service instance's namespace and Pod name in the service instance's
+properties, named `namespace` and `pod`, users can select the same and UI should fetch the logs by service
+instance in a given interval and display the logs in UI, OAP receives the query and checks the instance's
+properties and use the `namespace` and `pod` to locate the Pod and query the logs.
+
+If you want to register a service instance that has on demand logs available, you should add `namespace`
+and `pod` in the service instance properties, so that you can query the real time logs from that Pod.
+
+That said, in order to make this feature work properly, you should in advance configure the cluster role for
+OAP to list/get namespaces, services, pods and pods/log.
diff --git a/docs/en/setup/backend/opentelemetry-receiver.md b/docs/en/setup/backend/opentelemetry-receiver.md
new file mode 100644
index 000000000000..6e60c866b2e0
--- /dev/null
+++ b/docs/en/setup/backend/opentelemetry-receiver.md
@@ -0,0 +1,66 @@
+# OpenTelemetry Metrics Format
+
+The OpenTelemetry receiver supports ingesting agent metrics by meter-system. The OAP can load the configuration at bootstrap.
+If the new configuration is not well-formed, the OAP may fail to start up. The files are located at `$CLASSPATH/otel-rules`.
+
+Supported handlers:
+
+* `otlp`: [OpenTelemetry](https://github.com/open-telemetry/opentelemetry-collector/tree/1c217b366fbdb209044d8f4c3fece079ae23bd3b/exporter/otlpexporter) gRPC service handler.
+
+**Notice:** Set `SW_OTEL_RECEIVER=default` through system environment or change `receiver-otel/selector=${SW_OTEL_RECEIVER:default}` to activate the OpenTelemetry receiver.
+
+The rule file should be in YAML format, defined by the scheme described in [MAL](../../concepts-and-designs/mal.md).
+Note: `receiver-otel` only supports the `group`, `defaultMetricLevel`, and `metricsRules` nodes of the scheme due to its push mode.
+
+To activate the `otlp` handler and relevant rules of `istio`:
+
+```yaml
+receiver-otel:
+ selector: ${SW_OTEL_RECEIVER:default}
+ default:
+ enabledHandlers: ${SW_OTEL_RECEIVER_ENABLED_HANDLERS:"otlp-metrics"}
+ enabledOtelMetricsRules: ${SW_OTEL_RECEIVER_ENABLED_OTEL_METRICS_RULES:"istio-controlplane"}
+```
+
+The receiver adds label with key `node_identifier_host_name` to the collected data samples,
+and its value is from `net.host.name` (or `host.name` for some OTLP versions) resource attributes defined in OpenTelemetry proto,
+for identification of the metric data.
+
+**Notice:** In the resource scope, dots (.) in the attributes' key names are converted to underscores (_), whereas in the metrics scope, they are not converted.
+
+| Description | Configuration File | Data Source |
+|-----------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
+| Metrics of Istio Control Plane | otel-rules/istio-controlplane.yaml | Istio Control Plane -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of SkyWalking OAP server itself | otel-rules/oap.yaml | SkyWalking OAP Server(SelfObservability) -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Linux OS | otel-rules/vm.yaml | prometheus/node_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Windows OS | otel-rules/windows.yaml | prometheus-community/windows_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of K8s cluster | otel-rules/k8s/k8s-cluster.yaml | K8s kube-state-metrics -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of K8s cluster | otel-rules/k8s/k8s-node.yaml | cAdvisor & K8s kube-state-metrics -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of K8s cluster | otel-rules/k8s/k8s-service.yaml | cAdvisor & K8s kube-state-metrics -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of MYSQL | otel-rules/mysql/mysql-instance.yaml | prometheus/mysqld_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of MYSQL | otel-rules/mysql/mysql-service.yaml | prometheus/mysqld_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of PostgreSQL | otel-rules/postgresql/postgresql-instance.yaml | prometheus-community/postgres_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of PostgreSQL | otel-rules/postgresql/postgresql-service.yaml | prometheus-community/postgres_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Apache APISIX | otel-rules/apisix.yaml | apisix prometheus plugin -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of AWS Cloud EKS | otel-rules/aws-eks/eks-cluster.yaml | AWS Container Insights Receiver -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of AWS Cloud EKS | otel-rules/aws-eks/eks-service.yaml | AWS Container Insights Receiver -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of AWS Cloud EKS | otel-rules/aws-eks/eks-node.yaml | AWS Container Insights Receiver -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Elasticsearch | otel-rules/elasticsearch/elasticsearch-cluster.yaml | prometheus-community/elasticsearch_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Elasticsearch | otel-rules/elasticsearch/elasticsearch-index.yaml | prometheus-community/elasticsearch_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Elasticsearch | otel-rules/elasticsearch/elasticsearch-node.yaml | prometheus-community/elasticsearch_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Redis | otel-rules/redis/redis-service.yaml | oliver006/redis_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Redis | otel-rules/redis/redis-instance.yaml | oliver006/redis_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of RabbitMQ | otel-rules/rabbitmq/rabbitmq-cluster.yaml | rabbitmq-prometheus -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of RabbitMQ | otel-rules/rabbitmq/rabbitmq-node.yaml | rabbitmq-prometheus -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of MongoDB | otel-rules/mongodb/mongodb-cluster.yaml | percona/mongodb_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of MongoDB | otel-rules/mongodb/mongodb-node.yaml | percona/mongodb_exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Kafka | otel-rules/kafka/kafka-cluster.yaml | prometheus/jmx_exporter/jmx_prometheus_javaagent -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Kafka | otel-rules/kafka/kafka-broker.yaml | prometheus/jmx_exporter/jmx_prometheus_javaagent -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of ClickHouse | otel-rules/clickhouse/clickhouse-instance.yaml | ClickHouse(embedded prometheus endpoint) -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of ClickHouse | otel-rules/clickhouse/clickhouse-service.yaml | ClickHouse(embedded prometheus endpoint) -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of RocketMQ | otel-rules/rocketmq/rocketmq-cluster.yaml | rocketmq-exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of RocketMQ | otel-rules/rocketmq/rocketmq-broker.yaml | rocketmq-exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of RocketMQ | otel-rules/rocketmq/rocketmq-topic.yaml | rocketmq-exporter -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Flink | otel-rules/flink/flink-jobManager.yaml | flink jobManager -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Flink | otel-rules/flink/flink-taskManager.yaml | flink taskManager -> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
+| Metrics of Flink | otel-rules/flink/flink-job.yaml | flink jobManager & flink taskManager-> OpenTelemetry Collector -- OTLP exporter --> SkyWalking OAP Server |
diff --git a/docs/en/setup/backend/otlp-trace.md b/docs/en/setup/backend/otlp-trace.md
new file mode 100644
index 000000000000..6afd5f984ad6
--- /dev/null
+++ b/docs/en/setup/backend/otlp-trace.md
@@ -0,0 +1,22 @@
+# OpenTelemetry Trace Format
+
+SkyWalking can receive traces from Traces in OTLP format and convert them to Zipkin Trace format eventually.
+For data analysis and queries related to Zipkin Trace, please [refer to the relevant documentation](./zipkin-trace.md#zipkin-query).
+
+OTLP Trace handler references the [Zipkin Exporter in the OpenTelemetry Collector](https://opentelemetry.io/docs/specs/otel/trace/sdk_exporters/zipkin/#summary) to convert the data format.
+
+## Set up backend receiver
+
+1. Make sure to enable **otlp-traces** handler in OTLP receiver of `application.yml`.
+```yaml
+receiver-otel:
+ selector: default
+ default:
+ enabledHandlers: otlp-traces
+```
+
+2. Make sure to enable zipkin receiver and zipkin query in `application.yml` for config the zipkin.
+
+## Setup Query and Lens UI
+
+Please read [deploy Lens UI documentation](./zipkin-trace.md#lens-ui) for query OTLP traces.
\ No newline at end of file
diff --git a/docs/en/setup/backend/segment-template.json b/docs/en/setup/backend/segment-template.json
new file mode 100644
index 000000000000..c07a98f382aa
--- /dev/null
+++ b/docs/en/setup/backend/segment-template.json
@@ -0,0 +1,106 @@
+{
+ "traceId": {
+ "type": "uuid",
+ "changingFrequency": "1"
+ },
+ "serviceInstanceName": {
+ "type": "randomString",
+ "length": "10",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ },
+ "serviceName": {
+ "type": "fixedString",
+ "value": "service_"
+ },
+ "segments": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "endpointName": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ },
+ "error": {
+ "type": "randomInt",
+ "min": 1,
+ "max": 1
+ },
+ "tags": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "key": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_tag_",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 5
+ },
+ "value": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_value_",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ }
+ }
+ },
+ "spans": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "latency": {
+ "type": "randomInt",
+ "min": 100,
+ "max": 1000
+ },
+ "operationName": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_endpoint_",
+ "letters": true,
+ "numbers": true
+ },
+ "componentId": {
+ "type": "randomInt",
+ "min": "0",
+ "max": "4"
+ },
+ "error": {
+ "type": "randomBool",
+ "possibility": "0.2"
+ },
+ "tags": {
+ "type": "randomList",
+ "size": 5,
+ "item": {
+ "key": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_tag_key_",
+ "letters": true,
+ "numbers": true,
+ "domainSize": 10
+ },
+ "value": {
+ "type": "randomString",
+ "length": "10",
+ "prefix": "test_tag_val_",
+ "letters": true,
+ "numbers": true
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/docs/en/setup/backend/service-auto-grouping.md b/docs/en/setup/backend/service-auto-grouping.md
new file mode 100644
index 000000000000..a0d493f82cbf
--- /dev/null
+++ b/docs/en/setup/backend/service-auto-grouping.md
@@ -0,0 +1,15 @@
+# Service Auto Grouping
+SkyWalking supports various default and customized dashboard templates.
+Each template provides an appropriate layout for services in a particular field.
+For example, the metrics for services with language agents installed
+may be different from that of services detected by the service mesh observability solution as well as SkyWalking's self-observability metrics dashboard.
+
+Therefore, since version 8.3.0, the SkyWalking OAP has generated the groups based on this simple naming format:
+
+### ${service name} = [${group name}::]${logic name}
+
+If the service name includes double colons (`::`), the literal string before the colons is taken as the group name.
+In the latest GraphQL query, the group name has been provided as an optional parameter.
+> getAllServices(duration: Duration!, group: String): [Service!]!
+
+RocketBot UI dashboards (`Standard` type) support the `group name` for default and custom configurations.
diff --git a/docs/en/setup/backend/slow-cache-command.md b/docs/en/setup/backend/slow-cache-command.md
new file mode 100644
index 000000000000..29f8e252d284
--- /dev/null
+++ b/docs/en/setup/backend/slow-cache-command.md
@@ -0,0 +1,15 @@
+# Slow Cache Command
+Slow Cache command are sensitive for you to identify bottlenecks of a system which relies on cache system.
+
+Slow Cache command are based on sampling. Right now, the core samples are the top 50 slowest every 10 minutes.
+Note that the duration of these command must be slower than the threshold.
+
+Here's the format of the settings (in milliseconds):
+> cache-type:thresholdValue,cache-type2:thresholdValue2
+
+The default settings are `default:20,redis:10`. `Reserved Cache type` is **default**, which is the default threshold for all
+cache types, unless set explicitly.
+
+**Note**:
+1. The threshold should not be set too small, like `1ms`. Although it works in theory, OAP performance issues may arise if your system statement access time is usually more than 1ms.
+2. The OAP server would run statistic per service and only persistent the top 50 every 10(controlled by `topNReportPeriod: ${SW_CORE_TOPN_REPORT_PERIOD:10}`) minutes by default.
\ No newline at end of file
diff --git a/docs/en/setup/backend/slow-db-statement.md b/docs/en/setup/backend/slow-db-statement.md
new file mode 100644
index 000000000000..240fe935c641
--- /dev/null
+++ b/docs/en/setup/backend/slow-db-statement.md
@@ -0,0 +1,16 @@
+# Slow Database Statement
+Slow Database statements are crucial for you to identify bottlenecks of a system which relies on databases.
+
+Slow DB statements are based on sampling. Right now, the core samples are the top 50 slowest every 10 minutes.
+Note that the duration of these statements must be slower than the threshold.
+
+Here's the format of the settings (in milliseconds):
+> database-type:thresholdValue,database-type2:thresholdValue2
+
+The default settings are `default:200,mongodb:100`. `Reserved DB type` is **default**, which is the default threshold for all
+database types, unless set explicitly.
+
+**Note**:
+1. The threshold should not be set too small, like `1ms`. Although it works in theory, OAP performance issues may arise if your system statement access time is usually more than 1ms.
+2. The OAP server would run statistic per service and only persistent the top 50 every 10(controlled by `topNReportPeriod: ${SW_CORE_TOPN_REPORT_PERIOD:10}`) minutes by default.
+
diff --git a/docs/en/setup/backend/storages/banyandb.md b/docs/en/setup/backend/storages/banyandb.md
new file mode 100644
index 000000000000..5624f1125229
--- /dev/null
+++ b/docs/en/setup/backend/storages/banyandb.md
@@ -0,0 +1,356 @@
+## BanyanDB
+
+[BanyanDB](https://github.com/apache/skywalking-banyandb) is a dedicated storage implementation developed by the SkyWalking Team and the community. Activate BanyanDB as the storage by setting the storage provider to **banyandb**.
+
+The BanyanDB server compatibility relies on API and release versions, which are defined in `bydb.dependencies.properties`
+```shell
+# BanyanDB version is the version number of BanyanDB Server release.
+# This is the bundled and tested BanyanDB release version
+bydb.version=x.y
+# BanyanDB API version is the version number of the BanyanDB query APIs
+# OAP server has bundled implementation of BanyanDB Java client.
+# Please check BanyanDB documentation for the API version compatibility.
+# https://skywalking.apache.org/docs/skywalking-banyandb/next/installation/versions
+# Each `bydb.api.version` could have multiple compatible release version(`bydb.version`).
+bydb.api.version=x.y
+```
+
+If the BanyanDB server API version is not compatible with the OAP server, the OAP server will not start, and the following error message will be displayed:
+```shell
+... ERROR [] - ... Incompatible BanyanDB server API version: 0.x. But accepted versions: 0.y
+org.apache.skywalking.oap.server.library.module.ModuleStartException: Incompatible BanyanDB server API version...
+```
+
+### Configuration
+In the `application.yml` file, select the BanyanDB storage provider:
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:banyandb}
+```
+
+Since 10.2.0, the banyandb configuration is separated to an independent configuration file: `bydb.yaml`:
+
+```yaml
+global:
+ # Targets is the list of BanyanDB servers, separated by commas.
+ # Each target is a BanyanDB server in the format of `host:port`.
+ # If BanyanDB is deployed as a standalone server, the target should be the IP address or domain name and port of the BanyanDB server.
+ # If BanyanDB is deployed in a cluster, the targets should be the IP address or domain name and port of the `liaison` nodes, separated by commas.
+ targets: ${SW_STORAGE_BANYANDB_TARGETS:127.0.0.1:17912}
+ # The maximum number of records in a bulk write request.
+ # A larger value can improve write performance but also increases OAP and BanyanDB Server memory usage.
+ maxBulkSize: ${SW_STORAGE_BANYANDB_MAX_BULK_SIZE:10000}
+ # The minimum seconds between two bulk flushes.
+ # If the data in a bulk is less than maxBulkSize, the data will be flushed after this period.
+ # If the data in a bulk exceeds maxBulkSize, the data will be flushed immediately.
+ # A larger value can reduce write pressure on BanyanDB Server but increase data latency.
+ flushInterval: ${SW_STORAGE_BANYANDB_FLUSH_INTERVAL:15}
+ # The timeout in seconds for a bulk flush.
+ flushTimeout: ${SW_STORAGE_BANYANDB_FLUSH_TIMEOUT:10}
+ # The number of threads that write data to BanyanDB concurrently.
+ # A higher value can improve write performance but also increases CPU usage on both OAP and BanyanDB Server.
+ concurrentWriteThreads: ${SW_STORAGE_BANYANDB_CONCURRENT_WRITE_THREADS:15}
+ # The maximum size of the dataset when the OAP loads cache, such as network aliases.
+ resultWindowMaxSize: ${SW_STORAGE_BANYANDB_QUERY_MAX_WINDOW_SIZE:10000}
+ # The maximum size of metadata per query.
+ metadataQueryMaxSize: ${SW_STORAGE_BANYANDB_QUERY_MAX_SIZE:10000}
+ # The maximum number of trace segments per query.
+ segmentQueryMaxSize: ${SW_STORAGE_BANYANDB_QUERY_SEGMENT_SIZE:200}
+ # The maximum number of profile task queries in a request.
+ profileTaskQueryMaxSize: ${SW_STORAGE_BANYANDB_QUERY_PROFILE_TASK_SIZE:200}
+ # The batch size for querying profile data.
+ profileDataQueryBatchSize: ${SW_STORAGE_BANYANDB_QUERY_PROFILE_DATA_BATCH_SIZE:100}
+ asyncProfilerTaskQueryMaxSize: ${SW_STORAGE_BANYANDB_ASYNC_PROFILER_TASK_QUERY_MAX_SIZE:200}
+ # If the BanyanDB server is configured with TLS, configure the TLS cert file path and enable TLS connection.
+ sslTrustCAPath: ${SW_STORAGE_BANYANDB_SSL_TRUST_CA_PATH:""}
+
+groups:
+ # The group settings of record.
+ # - "ShardNum": Number of shards in the group. Shards are the basic units of data storage in BanyanDB. Data is distributed across shards based on the hash value of the series ID.
+ # Refer to the [BanyanDB Shard](https://skywalking.apache.org/docs/skywalking-banyandb/latest/concept/clustering/#52-data-sharding) documentation for more details.
+ # - "SIDays": Interval in days for creating a new segment. Segments are time-based, allowing efficient data retention and querying. `SI` stands for Segment Interval.
+ # - "TTLDays": Time-to-live for the data in the group, in days. Data exceeding the TTL will be deleted.
+ #
+ # For more details on setting `segmentIntervalDays` and `ttlDays`, refer to the [BanyanDB TTL](https://skywalking.apache.org/docs/main/latest/en/banyandb/ttl) documentation.
+
+ # The "records" section defines settings for normal datasets not specified in records.
+ # Each dataset will be grouped under a single group named "records".
+ records:
+ # The settings for the default "hot" stage.
+ shardNum: ${SW_STORAGE_BANYANDB_RECORDS_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_RECORDS_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_RECORDS_TTL_DAYS:3}
+ # If the "warm" stage is enabled, the data will be moved to the "warm" stage after the TTL of the "hot" stage.
+ # If the "cold" stage is enabled and "warm" stage is disabled, the data will be moved to the "cold" stage after the TTL of the "hot" stage.
+ # If both "warm" and "cold" stages are enabled, the data will be moved to the "warm" stage after the TTL of the "hot" stage, and then to the "cold" stage after the TTL of the "warm" stage.
+ # OAP will query the data from the "hot and warm" stage by default if the "warm" stage is enabled.
+ enableWarmStage: ${SW_STORAGE_BANYANDB_RECORDS_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_RECORDS_ENABLE_COLD_STAGE:false}
+ # The settings for the "warm" stage.
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_RECORDS_WARM_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_RECORDS_WARM_SI_DAYS:2}
+ ttl: ${SW_STORAGE_BANYANDB_RECORDS_WARM_TTL_DAYS:7}
+ nodeSelector: ${SW_STORAGE_BANYANDB_RECORDS_WARM_NODE_SELECTOR:"type=warm"}
+ # The settings for the "cold" stage.
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_RECORDS_COLD_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_RECORDS_COLD_SI_DAYS:3}
+ ttl: ${SW_STORAGE_BANYANDB_RECORDS_COLD_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_RECORDS_COLD_NODE_SELECTOR:"type=cold"}
+ # The group settings of super datasets.
+ # Super datasets are used to store trace or log data that is too large for normal datasets.
+ recordsTrace:
+ shardNum: ${SW_STORAGE_BANYANDB_TRACE_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_TRACE_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_TRACE_TTL_DAYS:3}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_TRACE_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_TRACE_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_TRACE_WARM_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_TRACE_WARM_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_TRACE_WARM_TTL_DAYS:7}
+ nodeSelector: ${SW_STORAGE_BANYANDB_TRACE_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_TRACE_COLD_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_TRACE_COLD_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_TRACE_COLD_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_TRACE_COLD_NODE_SELECTOR:"type=cold"}
+ recordsZipkinTrace:
+ shardNum: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_TTL_DAYS:3}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_TTL_DAYS:7}
+ nodeSelector: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_ZIPKIN_TRACE_COLD_NODE_SELECTOR:"type=cold"}
+ recordsLog:
+ shardNum: ${SW_STORAGE_BANYANDB_LOG_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_LOG_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_LOG_TTL_DAYS:3}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_LOG_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_LOG_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_LOG_WARM_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_LOG_WARM_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_LOG_WARM_TTL_DAYS:7}
+ nodeSelector: ${SW_STORAGE_BANYANDB_LOG_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_LOG_COLD_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_LOG_COLD_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_LOG_COLD_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_LOG_COLD_NODE_SELECTOR:"type=cold"}
+ recordsBrowserErrorLog:
+ shardNum: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_TTL_DAYS:3}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_TTL_DAYS:7}
+ nodeSelector: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_COLD_NODE_SELECTOR:"type=cold"}
+ # The group settings of metrics.
+ #
+ # OAP stores metrics based its granularity.
+ # Valid values are "day", "hour", and "minute". That means metrics will be stored in the three separate groups.
+ # Non-"minute" are governed by the "core.downsampling" setting.
+ # For example, if "core.downsampling" is set to "hour", the "hour" will be used, while "day" are ignored.
+ metricsMinute:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_SI_DAYS:1}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_TTL_DAYS:7}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_SI_DAYS:3}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_TTL_DAYS:15}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_SI_DAYS:5}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_TTL_DAYS:60}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_MINUTE_COLD_NODE_SELECTOR:"type=cold"}
+ metricsHour:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_HOUR_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_HOUR_SI_DAYS:5}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_HOUR_TTL_DAYS:15}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_METRICS_HOUR_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_METRICS_HOUR_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_SI_DAYS:7}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_HOUR_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_SI_DAYS:15}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_TTL_DAYS:120}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_HOUR_COLD_NODE_SELECTOR:"type=cold"}
+ metricsDay:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_DAY_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_DAY_SI_DAYS:15}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_DAY_TTL_DAYS:15}
+ enableWarmStage: ${SW_STORAGE_BANYANDB_METRICS_DAY_ENABLE_WARM_STAGE:false}
+ enableColdStage: ${SW_STORAGE_BANYANDB_METRICS_DAY_ENABLE_COLD_STAGE:false}
+ warm:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_DAY_WARM_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_DAY_WARM_SI_DAYS:15}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_DAY_WARM_TTL_DAYS:30}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_DAY_WARM_NODE_SELECTOR:"type=warm"}
+ cold:
+ shardNum: ${SW_STORAGE_BANYANDB_METRICS_DAY_COLD_SHARD_NUM:1}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METRICS_DAY_COLD_SI_DAYS:15}
+ ttl: ${SW_STORAGE_BANYANDB_METRICS_DAY_COLD_TTL_DAYS:120}
+ nodeSelector: ${SW_STORAGE_BANYANDB_METRICS_DAY_COLD_NODE_SELECTOR:"type=cold"}
+ # If the metrics is marked as "index_mode", the metrics will be stored in the "metadata" group.
+ # The "metadata" group is designed to store metrics that are used for indexing without value columns.
+ # Such as `service_traffic`, `network_address_alias`, etc.
+ # "index_mode" requires BanyanDB *0.8.0* or later.
+ metadata:
+ shardNum: ${SW_STORAGE_BANYANDB_METADATA_SHARD_NUM:2}
+ segmentInterval: ${SW_STORAGE_BANYANDB_METADATA_SI_DAYS:15}
+ ttl: ${SW_STORAGE_BANYANDB_METADATA_TTL_DAYS:15}
+
+ # The group settings of property, such as UI and profiling.
+ property:
+ shardNum: ${SW_STORAGE_BANYANDB_PROPERTY_SHARD_NUM:1}
+
+```
+### TopN Rules Configuration
+The BanyanDB storage supports TopN pre-aggregation in the BanyanDB server side, which trades off more disk_volume for pre-aggregation to save CPU cost, and perform faster query in the query stage.
+You can define the TopN rules for different metrics. The configuration is defined in the `bydb-topn.yaml` file:
+
+```yaml
+# This file is used to configure the TopN rules for BanyanDB in SkyWalking OAP server.
+# The rules define how to aggregate and sort `metrics (Measure)` for services, endpoints, and instances.
+#
+# - name: Required. The name of the TopN rule, uniquely identifies the rule.
+# - metricName: Required. The name of the metric to be aggregated.
+# - groupByTagNames: Optional, default `[]`. The tag names to group the metrics by. If not specified, the metrics will sort without grouped.
+# - countersNumber: Optional, default `1000`. The max size of entries in a time window for the pre-aggregation.
+
+# The size of LRU determines the maximally tolerated time range.
+# The buffers in the time range are kept in the memory so that
+# the data in [T - lruSize * n, T] would be accepted in the pre-aggregation process.
+# T = the current time in the current dimensionality.
+# n = interval in the current dimensionality.
+# - lruSizeMinute: Optional, default `10`. Defines how many time_buckets are held in the memory for minute-level metrics.
+# - lruSizeHourDay: Optional, default `2`. Defines how many time_buckets are held in the memory for hour and day-level metrics.
+
+# - sort: Optional, default `all`. The sorting order for the metrics, asc, des or all(include both asc and des).
+
+TopN-Rules:
+ # endpoint metrics
+ # `attr0` is defined in the `EndpointDecorator` as the Layer.
+ - name: endpoint_cpm
+ metricName: endpoint_cpm
+ sort: des
+ - name: endpoint_cpm-layer
+ metricName: endpoint_cpm
+ groupByTagNames:
+ - attr0
+ sort: des
+ - name: endpoint_cpm-service
+ metricName: endpoint_cpm
+ groupByTagNames:
+ - service_id
+ sort: des
+ - name: endpoint_sla
+ metricName: endpoint_sla
+ sort: asc
+ - name: endpoint_sla-layer
+ metricName: endpoint_sla
+ groupByTagNames:
+ - attr0
+ sort: asc
+ - name: endpoint_sla-service
+ metricName: endpoint_sla
+ groupByTagNames:
+ - service_id
+ sort: asc
+ - name: endpoint_resp_time
+ metricName: endpoint_resp_time
+ sort: des
+ - name: endpoint_resp_time-layer
+ metricName: endpoint_resp_time
+ groupByTagNames:
+ - attr0
+ sort: des
+ - name: endpoint_resp_time-service
+ metricName: endpoint_resp_time
+ groupByTagNames:
+ - service_id
+ sort: des
+ # browser_app_page_pv metrics
+ - name: browser_app_page_pv-service
+ metricName: browser_app_page_pv
+ groupByTagNames:
+ - service_id
+ sort: des
+ - name: browser_app_page_error_sum-service
+ metricName: browser_app_page_error_sum
+ groupByTagNames:
+ - service_id
+ sort: des
+ - name: browser_app_page_error_rate-service
+ metricName: browser_app_page_error_rate
+ groupByTagNames:
+ - service_id
+ sort: des
+```
+
+### Installation Modes
+
+BanyanDB Server supports two installation modes:
+
+- **Standalone Mode**: Suitable for small-scale deployments.
+ - **Configuration**: `targets` is the IP address/hostname and port of the BanyanDB server.
+
+Use the docker mode to run BanyanDB containerized.
+```shell
+# The compatible version number could be found in /config/bydb.dependencies.properties
+export BYDB_VERSION=xxx
+
+docker pull apache/skywalking-banyandb:${BYDB_VERSION}
+
+docker run -d \
+ -p 17912:17912 \
+ -p 17913:17913 \
+ --name banyandb \
+ apache/skywalking-banyandb:${BYDB_VERSION} \
+ standalone
+```
+
+Or use the development builds for latest and unreleased features, all versions are available [here](https://github.com/apache/skywalking-banyandb/pkgs/container/skywalking-banyandb).
+```shell
+docker pull apache/skywalking-banyandb:latest
+
+docker run -d \
+ -p 17912:17912 \
+ -p 17913:17913 \
+ --name banyandb \
+ ghcr.io/apache/skywalking-banyandb:xxxxxx \
+ standalone
+```
+
+- **Cluster Mode**: Suitable for large-scale deployments.
+ - **Configuration**: `targets` is the IP address/hostname and port of the `liaison` nodes, separated by commas. `Liaison` nodes are the entry points of the BanyanDB cluster.
+
+For more details, refer to the documentation of [BanyanDB](https://skywalking.apache.org/docs/skywalking-banyandb/latest/readme/) and the [BanyanDB Java Client](https://github.com/apache/skywalking-banyandb-java-client) subprojects.
diff --git a/docs/en/setup/backend/storages/elasticsearch.md b/docs/en/setup/backend/storages/elasticsearch.md
new file mode 100644
index 000000000000..a2d60a5a731f
--- /dev/null
+++ b/docs/en/setup/backend/storages/elasticsearch.md
@@ -0,0 +1,222 @@
+# Elasticsearch and OpenSearch
+Elasticsearch and OpenSearch are supported as storage. The storage provider is **elasticsearch**.
+This storage option is recommended for a large scale production environment, such as more than 1000 services, 10000 endpoints, and 100000 traces per minute,
+and plan to 100% sampling rate for the persistent in the storage.
+
+## OpenSearch
+
+OpenSearch is a fork from ElasticSearch 7.11 but licensed in Apache 2.0.
+OpenSearch storage shares the same configurations as ElasticSearch.
+In order to activate OpenSearch as storage, set the storage provider to **elasticsearch**.
+
+We support and tested the following versions of OpenSearch:
+
+- 1.1.0, 1.3.10
+- 2.4.0, 2.8.0, 3.0.0
+
+## Elasticsearch
+
+**NOTE:** Elastic announced through their blog that Elasticsearch will be moving over to a Server Side Public
+License (SSPL) and/or Elastic License 2.0(ELv2), since Feb. 2021, which is **incompatible with Apache License 2.0**.
+Both of these licenses are not OSS licenses approved by the Open Source Initiative (OSI).
+This license change is effective from Elasticsearch version 7.11.
+So please choose the suitable ElasticSearch version according to your usage.
+If you have concerns about SSPL/ELv2, choose the versions before 7.11 or switch to OpenSearch.
+
+By default, SkyWalking uses following indices for various telemetry data.
+
+* sw_management (All SkyWalking management data, e.g. UI dashboard settings, UI Menu, Continuous profiling policy)
+* sw_metrics-all-`${day-format}` (All metrics/meters generated through MAL and OAL engines, and metadata of service/instance/endpoint)
+* sw_log-`${day-format}` (Collected logs, exclude browser logs)
+* sw_segment-`${day-format}` (Native trace segments)
+* sw_browser_error_log-`${day-format}` (Collected browser logs)
+* sw_zipkin_span-`${day-format}` (Zipkin trace spans)
+* sw_records-all-`${day-format}` (All sampled records, e.g. slow SQLs, agent profiling, and ebpf profiling)
+
+SkyWalking rebuilds the ElasticSearch client on top of ElasticSearch REST API and automatically picks up
+correct request formats according to the server-side version, hence you don't need to download different binaries
+and don't need to configure different storage selectors for different ElasticSearch server-side versions anymore.
+
+For now, SkyWalking supports ElasticSearch 7.x, ElasticSearch 8.x, and OpenSearch 1.x, their
+configurations are as follows:
+
+_Notice, ElasticSearch 6 worked and is not promised due to end of life officially._
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:elasticsearch}
+ elasticsearch:
+ namespace: ${SW_NAMESPACE:""}
+ clusterNodes: ${SW_STORAGE_ES_CLUSTER_NODES:localhost:9200}
+ protocol: ${SW_STORAGE_ES_HTTP_PROTOCOL:"http"}
+ trustStorePath: ${SW_STORAGE_ES_SSL_JKS_PATH:""}
+ trustStorePass: ${SW_STORAGE_ES_SSL_JKS_PASS:""}
+ user: ${SW_ES_USER:""}
+ password: ${SW_ES_PASSWORD:""}
+ secretsManagementFile: ${SW_ES_SECRETS_MANAGEMENT_FILE:""} # Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
+ dayStep: ${SW_STORAGE_DAY_STEP:1} # Represent the number of days in the one minute/hour/day index.
+ indexShardsNumber: ${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1} # Shard number of new indexes
+ indexReplicasNumber: ${SW_STORAGE_ES_INDEX_REPLICAS_NUMBER:1} # Replicas number of new indexes
+ # Specify the settings for each index individually.
+ # If configured, this setting has the highest priority and overrides the generic settings.
+ specificIndexSettings: ${SW_STORAGE_ES_SPECIFIC_INDEX_SETTINGS:""}
+ # Super data set has been defined in the codes, such as trace segments.The following 3 config would be improve es performance when storage super size data in es.
+ superDatasetDayStep: ${SW_STORAGE_ES_SUPER_DATASET_DAY_STEP:-1} # Represent the number of days in the super size dataset record index, the default value is the same as dayStep when the value is less than 0
+ superDatasetIndexShardsFactor: ${SW_STORAGE_ES_SUPER_DATASET_INDEX_SHARDS_FACTOR:5} # This factor provides more shards for the super data set, shards number = indexShardsNumber * superDatasetIndexShardsFactor. Also, this factor effects Zipkin traces.
+ superDatasetIndexReplicasNumber: ${SW_STORAGE_ES_SUPER_DATASET_INDEX_REPLICAS_NUMBER:0} # Represent the replicas number in the super size dataset record index, the default value is 0.
+ indexTemplateOrder: ${SW_STORAGE_ES_INDEX_TEMPLATE_ORDER:0} # the order of index template
+ bulkActions: ${SW_STORAGE_ES_BULK_ACTIONS:1000} # Execute the async bulk record data every ${SW_STORAGE_ES_BULK_ACTIONS} requests
+ flushInterval: ${SW_STORAGE_ES_FLUSH_INTERVAL:10} # flush the bulk every 10 seconds whatever the number of requests
+ concurrentRequests: ${SW_STORAGE_ES_CONCURRENT_REQUESTS:2} # the number of concurrent requests
+ resultWindowMaxSize: ${SW_STORAGE_ES_QUERY_MAX_WINDOW_SIZE:10000}
+ metadataQueryMaxSize: ${SW_STORAGE_ES_QUERY_MAX_SIZE:5000}
+ segmentQueryMaxSize: ${SW_STORAGE_ES_QUERY_SEGMENT_SIZE:200}
+ profileTaskQueryMaxSize: ${SW_STORAGE_ES_QUERY_PROFILE_TASK_SIZE:200}
+ profileDataQueryScrollBatchSize: ${SW_STORAGE_ES_QUERY_PROFILE_DATA_SCROLLING_BATCH_SIZE:100}
+ oapAnalyzer: ${SW_STORAGE_ES_OAP_ANALYZER:"{\"analyzer\":{\"oap_analyzer\":{\"type\":\"stop\"}}}"} # the oap analyzer.
+ oapLogAnalyzer: ${SW_STORAGE_ES_OAP_LOG_ANALYZER:"{\"analyzer\":{\"oap_log_analyzer\":{\"type\":\"standard\"}}}"} # the oap log analyzer. It could be customized by the ES analyzer configuration to support more language log formats, such as Chinese log, Japanese log and etc.
+ advanced: ${SW_STORAGE_ES_ADVANCED:""}
+ # Set it to `true` could shard metrics indices into multi-physical indices
+ # as same as the versions(one index template per metric/meter aggregation function) before 9.2.0.
+ logicSharding: ${SW_STORAGE_ES_LOGIC_SHARDING:false}
+ # Custom routing can reduce the impact of searches. Instead of having to fan out a search request to all the shards in an index, the request can be sent to just the shard that matches the specific routing value (or values).
+ enableCustomRouting: ${SW_STORAGE_ES_ENABLE_CUSTOM_ROUTING:false}
+```
+
+### ElasticSearch With Https SSL Encrypting communications.
+
+Example:
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:elasticsearch}
+ elasticsearch:
+ namespace: ${SW_NAMESPACE:""}
+ user: ${SW_ES_USER:""} # User needs to be set when Http Basic authentication is enabled
+ password: ${SW_ES_PASSWORD:""} # Password to be set when Http Basic authentication is enabled
+ clusterNodes: ${SW_STORAGE_ES_CLUSTER_NODES:localhost:443}
+ trustStorePath: ${SW_STORAGE_ES_SSL_JKS_PATH:"../es_keystore.jks"}
+ trustStorePass: ${SW_STORAGE_ES_SSL_JKS_PASS:""}
+ protocol: ${SW_STORAGE_ES_HTTP_PROTOCOL:"https"}
+ ...
+```
+- File at `trustStorePath` is being monitored. Once it is changed, the ElasticSearch client will reconnect.
+- `trustStorePass` could be changed in the runtime through [**Secrets Management File Of ElasticSearch Authentication**](#secrets-management-file-of-elasticsearch-authentication).
+
+### Daily Index Step
+Daily index step(`storage/elasticsearch/dayStep`, default 1) represents the index creation period. In this period, metrics for several days (dayStep value) are saved.
+
+In most cases, users don't need to change the value manually, as SkyWalking is designed to observe large-scale distributed systems.
+But in some cases, users may want to set a long TTL value, such as more than 60 days. However, their ElasticSearch cluster may not be powerful enough due to low traffic in the production environment.
+This value could be increased to 5 (or more) if users could ensure a single index could support the metrics and traces for these days (5 in this case).
+
+For example, if dayStep == 11,
+1. Data in [2000-01-01, 2000-01-11] will be merged into the index-20000101.
+1. Data in [2000-01-12, 2000-01-22] will be merged into the index-20000112.
+
+`storage/elasticsearch/superDatasetDayStep` overrides the `storage/elasticsearch/dayStep` if the value is positive.
+This would affect the record-related entities, such as trace segments. In some cases, the size of metrics is much smaller than the record (trace). This would improve the shards balance in the ElasticSearch cluster.
+
+NOTE: TTL deletion would be affected by these steps. You should set an extra dayStep in your TTL. For example, if you want to have TTL == 30 days and dayStep == 10, you are recommended to set TTL = 40.
+
+### Secrets Management File Of ElasticSearch Authentication
+The value of `secretsManagementFile` should point to the secrets management file absolute path.
+The file includes the username, password, and JKS password of the ElasticSearch server in the properties format.
+```properties
+user=xxx
+password=yyy
+trustStorePass=zzz
+```
+
+The major difference between using `user, password, trustStorePass` configs in the `application.yaml` file is that the **Secrets Management File** is being watched by the OAP server.
+Once it is changed manually or through a 3rd party tool, such as [Vault](https://github.com/hashicorp/vault),
+the storage provider will use the new username, password, and JKS password to establish the connection and close the old one. If the information exists in the file,
+the `user/password` will be overridden.
+
+
+### Index Settings
+The following settings control the number of shards and replicas for new and existing index templates. The update only got applied after OAP reboots.
+```yaml
+storage:
+ elasticsearch:
+ # ......
+ indexShardsNumber: ${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1}
+ indexReplicasNumber: ${SW_STORAGE_ES_INDEX_REPLICAS_NUMBER:1}
+ specificIndexSettings: ${SW_STORAGE_ES_SPECIFIC_INDEX_SETTINGS:""}
+ superDatasetIndexShardsFactor: ${SW_STORAGE_ES_SUPER_DATASET_INDEX_SHARDS_FACTOR:5}
+ superDatasetIndexReplicasNumber: ${SW_STORAGE_ES_SUPER_DATASET_INDEX_REPLICAS_NUMBER:0}
+```
+The following table shows the relationship between those config items and Elasticsearch `index number_of_shards/number_of_replicas`.
+And also you can [specify the settings for each index individually.](#specify-settings-for-each-elasticsearch-index-individually)
+
+| index | number_of_shards | number_of_replicas |
+|--------------------------------------|------------------|----------------------|
+| sw_ui_template | indexShardsNumber | indexReplicasNumber |
+| sw_metrics-all-`${day-format}` | indexShardsNumber | indexReplicasNumber |
+| sw_log-`${day-format}` | indexShardsNumber * superDatasetIndexShardsFactor | superDatasetIndexReplicasNumber |
+| sw_segment-`${day-format}` | indexShardsNumber * superDatasetIndexShardsFactor | superDatasetIndexReplicasNumber |
+| sw_browser_error_log-`${day-format}` | indexShardsNumber * superDatasetIndexShardsFactor | superDatasetIndexReplicasNumber |
+| sw_zipkin_span-`${day-format}` | indexShardsNumber * superDatasetIndexShardsFactor | superDatasetIndexReplicasNumber |
+| sw_records-all-`${day-format}` | indexShardsNumber | indexReplicasNumber |
+
+#### Advanced Configurations For Elasticsearch Index
+You can add advanced configurations in `JSON` format to set `ElasticSearch index settings` by following [ElasticSearch doc](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html)
+
+For example, set [translog](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-translog.html) settings:
+
+```yaml
+storage:
+ elasticsearch:
+ # ......
+ advanced: ${SW_STORAGE_ES_ADVANCED:"{\"index.translog.durability\":\"request\",\"index.translog.sync_interval\":\"5s\"}"}
+```
+
+#### Specify Settings For Each Elasticsearch Index Individually
+You can specify the settings for one or more indexes individually by using `SW_STORAGE_ES_SPECIFIC_INDEX_SETTINGS`.
+
+**NOTE:**
+Supported settings:
+- number_of_shards
+- number_of_replicas
+
+**NOTE:** These settings have the highest priority and will override the existing
+generic settings mentioned in [index settings doc](#index-settings).
+
+The settings are in `JSON` format. The index name here is logic entity name, which should exclude the `${SW_NAMESPACE}` which is `sw` by default, e.g.
+```json
+{
+ "metrics-all":{
+ "number_of_shards":"3",
+ "number_of_replicas":"2"
+ },
+ "segment":{
+ "number_of_shards":"6",
+ "number_of_replicas":"1"
+ }
+}
+```
+
+This configuration in the YAML file is like this,
+```yaml
+storage:
+ elasticsearch:
+ # ......
+ specificIndexSettings: ${SW_STORAGE_ES_SPECIFIC_INDEX_SETTINGS:"{\"metrics-all\":{\"number_of_shards\":\"3\",\"number_of_replicas\":\"2\"},\"segment\":{\"number_of_shards\":\"6\",\"number_of_replicas\":\"1\"}}"}
+```
+
+### Recommended ElasticSearch server-side configurations
+You could add the following configuration to `elasticsearch.yml`, and set the value based on your environment.
+
+```yml
+# In tracing scenario, consider to set more than this at least.
+thread_pool.index.queue_size: 1000 # Only suitable for ElasticSearch 6
+thread_pool.write.queue_size: 1000 # Suitable for ElasticSearch 6 and 7
+
+# When you face a query error on the traces page, remember to check this.
+index.max_result_window: 1000000
+```
+
+We strongly recommend that you read more about these configurations from ElasticSearch's official documentation since they directly impact the performance of ElasticSearch.
+
+### About Namespace
+When a namespace is set, all index names in ElasticSearch will use it as the prefix.
diff --git a/docs/en/setup/backend/storages/mysql.md b/docs/en/setup/backend/storages/mysql.md
new file mode 100644
index 000000000000..11e28296261d
--- /dev/null
+++ b/docs/en/setup/backend/storages/mysql.md
@@ -0,0 +1,28 @@
+# MySQL
+Activate MySQL as storage, and set storage provider to **mysql**.
+
+**NOTE:** MySQL driver is NOT allowed in Apache official distribution and source codes.
+Please download the MySQL driver on your own. Copy the connection driver jar to `oap-libs`.
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:mysql}
+ mysql:
+ properties:
+ jdbcUrl: ${SW_JDBC_URL:"jdbc:mysql://localhost:3306/swtest?rewriteBatchedStatements=true&allowMultiQueries=true"}
+ dataSource.user: ${SW_DATA_SOURCE_USER:root}
+ dataSource.password: ${SW_DATA_SOURCE_PASSWORD:root@1234}
+ dataSource.cachePrepStmts: ${SW_DATA_SOURCE_CACHE_PREP_STMTS:true}
+ dataSource.prepStmtCacheSize: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_SIZE:250}
+ dataSource.prepStmtCacheSqlLimit: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_LIMIT:2048}
+ dataSource.useServerPrepStmts: ${SW_DATA_SOURCE_USE_SERVER_PREP_STMTS:true}
+ metadataQueryMaxSize: ${SW_STORAGE_MYSQL_QUERY_MAX_SIZE:5000}
+ maxSizeOfBatchSql: ${SW_STORAGE_MAX_SIZE_OF_BATCH_SQL:2000}
+ asyncBatchPersistentPoolSize: ${SW_STORAGE_ASYNC_BATCH_PERSISTENT_POOL_SIZE:4}
+```
+All connection-related settings, including URL link, username, and password, are found in `application.yml`.
+Only part of the settings is listed here. See the [HikariCP](https://github.com/brettwooldridge/HikariCP) connection pool document for full settings.
+To understand the function of the parameter `rewriteBatchedStatements=true` in MySQL, see the MySQL official document for more details.
+
+In theory, all other databases that are compatible with MySQL protocol should be able to use this storage plugin,
+such as TiDB. Please compose the JDBC URL according to the database's documentation.
diff --git a/docs/en/setup/backend/storages/postgresql.md b/docs/en/setup/backend/storages/postgresql.md
new file mode 100644
index 000000000000..f1b0e8d90666
--- /dev/null
+++ b/docs/en/setup/backend/storages/postgresql.md
@@ -0,0 +1,24 @@
+# PostgreSQL
+PostgreSQL JDBC driver uses version 42.3.2. It supports PostgreSQL 8.2 or newer.
+Activate PostgreSQL as storage, and set storage provider to **postgresql**.
+
+```yaml
+storage:
+ selector: ${SW_STORAGE:postgresql}
+ postgresql:
+ properties:
+ jdbcUrl: ${SW_JDBC_URL:"jdbc:postgresql://localhost:5432/skywalking"}
+ dataSource.user: ${SW_DATA_SOURCE_USER:postgres}
+ dataSource.password: ${SW_DATA_SOURCE_PASSWORD:123456}
+ dataSource.cachePrepStmts: ${SW_DATA_SOURCE_CACHE_PREP_STMTS:true}
+ dataSource.prepStmtCacheSize: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_SIZE:250}
+ dataSource.prepStmtCacheSqlLimit: ${SW_DATA_SOURCE_PREP_STMT_CACHE_SQL_LIMIT:2048}
+ dataSource.useServerPrepStmts: ${SW_DATA_SOURCE_USE_SERVER_PREP_STMTS:true}
+ metadataQueryMaxSize: ${SW_STORAGE_MYSQL_QUERY_MAX_SIZE:5000}
+ maxSizeOfArrayColumn: ${SW_STORAGE_MAX_SIZE_OF_ARRAY_COLUMN:20}
+ numOfSearchableValuesPerTag: ${SW_STORAGE_NUM_OF_SEARCHABLE_VALUES_PER_TAG:2}
+ maxSizeOfBatchSql: ${SW_STORAGE_MAX_SIZE_OF_BATCH_SQL:2000}
+ asyncBatchPersistentPoolSize: ${SW_STORAGE_ASYNC_BATCH_PERSISTENT_POOL_SIZE:4}
+```
+All connection-related settings, including URL link, username, and password, are found in `application.yml`.
+Only part of the settings is listed here. Please follow [HikariCP](https://github.com/brettwooldridge/HikariCP) connection pool document for full settings.
diff --git a/docs/en/setup/backend/telegraf-receiver.md b/docs/en/setup/backend/telegraf-receiver.md
new file mode 100644
index 000000000000..9512ee87046b
--- /dev/null
+++ b/docs/en/setup/backend/telegraf-receiver.md
@@ -0,0 +1,45 @@
+# Telegraf receiver
+
+The Telegraf receiver supports receiving InfluxDB Telegraf's metrics by meter-system.
+The OAP can load the configuration at bootstrap. The files are located at `$CLASSPATH/telegraf-rules`.
+If the new configuration is not well-formed, the OAP may fail to start up.
+
+This is the [InfluxDB Telegraf](https://docs.influxdata.com/telegraf/v1.24/) Document,
+the Telegraf receiver can handle Telegraf's [CPU Input Plugin](https://github.com/influxdata/telegraf/blob/release-1.24/plugins/inputs/cpu/README.md),
+[Memory Input Plugin](https://github.com/influxdata/telegraf/blob/release-1.24/plugins/inputs/mem/README.md).
+
+There are many other telegraf input plugins, users can customize different input plugins' rule files.
+The rule file should be in YAML format, defined by the scheme described in [MAL](../../concepts-and-designs/mal.md).
+Please see the [telegraf plugin directory](https://docs.influxdata.com/telegraf/v1.24/plugins/) for more input plugins information.
+
+**Notice:**
+* The Telegraf receiver module uses `HTTP` to receive telegraf's metrics,
+so the outputs method should be set `[[outputs.http]]` in telegraf.conf file.
+Please see the [http outputs](https://github.com/influxdata/telegraf/blob/release-1.24/plugins/outputs/http/README.md)
+for more details.
+
+* The Telegraf receiver module **only** process telegraf's `JSON` metrics format,
+the data format should be set `data_format = "json"` in telegraf.conf file.
+Please see the [JSON data format](https://docs.influxdata.com/telegraf/v1.24/data_formats/output/json/)
+for more details.
+
+* The default `json_timestamp_units` is second in JSON output,
+and the Telegraf receiver module **only** process `second` timestamp unit.
+If users configure `json_timestamp_units` in telegraf.conf file, `json_timestamp_units = "1s"` is feasible.
+Please see the [JSON data format](https://docs.influxdata.com/telegraf/v1.24/data_formats/output/json/)
+for more details.
+
+The following is the default telegraf receiver YAML rule file in the `application.yml`,
+Set `SW_RECEIVER_TELEGRAF:default` through system environment or change `SW_RECEIVER_TELEGRAF_ACTIVE_FILES:vm`
+to activate the OpenTelemetry receiver with `vm.yml` in telegraf-rules.
+```yaml
+receiver-telegraf:
+ selector: ${SW_RECEIVER_TELEGRAF:default}
+ default:
+ activeFiles: ${SW_RECEIVER_TELEGRAF_ACTIVE_FILES:vm}
+```
+
+| Rule Name | Description | Configuration File | Data Source |
+|-----------|----------------|------------------------|-------------------------------------------------------------------------|
+| vm | Metrics of VMs | telegraf-rules/vm.yaml | Telegraf inputs plugins --> Telegraf Receiver --> SkyWalking OAP Server |
+
diff --git a/docs/en/setup/backend/trace-sampling.md b/docs/en/setup/backend/trace-sampling.md
new file mode 100644
index 000000000000..c27efc60ed63
--- /dev/null
+++ b/docs/en/setup/backend/trace-sampling.md
@@ -0,0 +1,61 @@
+# Trace Sampling at server side
+An advantage of a distributed tracing system is that detailed information from the traces can be obtained. However, the downside is that these traces use up a lot of storage.
+
+If you enable the trace sampling mechanism at the **server-side**, you will find that the service metrics, service instance, endpoint, and topology all have the same accuracy as before. The only difference is that they do not save all traces in storage.
+
+Of course, even if you enable sampling, the traces will be kept as consistent as possible. Being **consistent** means that once the trace
+segments have been collected and reported by agents, the backend would make its best effort not to split the traces. See our [recommendation](#recommendation)
+to understand why you should keep the traces as consistent as possible and try not to split them.
+
+## Set the sample rate
+In the **agent-analyzer** module, you will find the `sampleRate` setting by the configuration `traceSamplingPolicySettingsFile`.
+
+```yaml
+agent-analyzer:
+ default:
+ ...
+ # The default sampling rate and the default trace latency time configured by the 'traceSamplingPolicySettingsFile' file.
+ traceSamplingPolicySettingsFile: ${SW_TRACE_SAMPLING_POLICY_SETTINGS_FILE:trace-sampling-policy-settings.yml}
+ forceSampleErrorSegment: ${SW_FORCE_SAMPLE_ERROR_SEGMENT:true} # When sampling mechanism activated, this config would make the error status segment sampled, ignoring the sampling rate.
+```
+
+The default `trace-sampling-policy-settings.yml` uses the following format. Could use [dynamic configuration](dynamic-config.md) to update the settings in the runtime.
+```yaml
+default:
+ # Default sampling rate that replaces the 'agent-analyzer.default.sampleRate'
+ # The sample rate precision is 1/10000. 10000 means 100% sample in default.
+ rate: 10000
+ # Default trace latency time that replaces the 'agent-analyzer.default.slowTraceSegmentThreshold'
+ # Setting this threshold about the latency would make the slow trace segments sampled if they cost more time, even the sampling mechanism is activated. The default value is `-1`, which would not sample slow traces. Unit, millisecond.
+ duration: -1
+#services:
+# - name: serverName
+# rate: 1000 # Sampling rate of this specific service
+# duration: 10000 # Trace latency threshold for trace sampling for this specific service
+```
+
+`duration.rate` allows you to set the sample rate to this backend.
+The sample rate precision is 1/10000. 10000 means 100% sample by default.
+
+`forceSampleErrorSegment` allows you to save all error segments when the sampling mechanism is activated.
+This config will cause the error status segment to be sampled when the sampling mechanism is activated, ignoring the sampling rate.
+
+`default.duration` allows you to save all slow trace segments when the sampling mechanism is activated.
+Setting this threshold on latency (in milliseconds) would cause slow trace segments to be sampled if they use up more time, even if the sampling mechanism is activated. The default value is `-1`, which means that slow traces would not be sampled.
+
+**Note:**
+`services.[].rate` and `services.[].duration` has a higher priority than `default.rare` and `default.duration`.
+
+# Recommendation
+You may choose to set different backend instances with different `sampleRate` values, although we recommend that you set the values to be the same.
+
+When you set the different rates, let's say:
+* Backend-Instance**A**.sampleRate = 35
+* Backend-Instance**B**.sampleRate = 55
+
+Assume the agents have reported all trace segments to the backend. 35% of the traces at the global level will be collected and saved in storage consistently/completely together with all spans. 20% of the trace segments reported to Backend-Instance **B** will be saved in storage, whereas some trace segments may be missed, as they are reported to Backend-Instance**A** and ignored.
+
+# Note
+When you enable sampling, the actual sample rate may exceed sampleRate. The reason is that currently, all error/slow segments will be saved; meanwhile, the upstream and downstream may not be sampled. This feature ensures that you have the error/slow stacks and segments, although it is not guaranteed that you would have the whole traces.
+
+Note that if most of the accesses have failed or are slow, the sampling rate would be close to 100%. This may cause the backend or storage clusters to crash.
diff --git a/docs/en/setup/backend/ttl.md b/docs/en/setup/backend/ttl.md
new file mode 100644
index 000000000000..1513880a7806
--- /dev/null
+++ b/docs/en/setup/backend/ttl.md
@@ -0,0 +1,22 @@
+# Data Lifecycle. Time To Live (TTL)
+Time To Live (TTL) is a mechanism to automatically delete data that is older than the specified time.
+
+In SkyWalking, there are two types of observability data:
+1. Records include traces, logs, topN sampled statements and alarm. `recordDataTTL` applies to **record** data.
+1. Metrics include all metrics for service, instance, endpoint, and topology map. Metadata(lists of services, instances, or endpoints) also belongs to metrics. `metricsDataTTL` applies to **Metrics** data.
+
+These are the settings for the different types:
+```yaml
+ # Set a timeout on metrics data. After the timeout has expired, the metrics data will automatically be deleted.
+ recordDataTTL: ${SW_CORE_RECORD_DATA_TTL:3} # Unit is day
+ metricsDataTTL: ${SW_CORE_METRICS_DATA_TTL:7} # Unit is day
+```
+
+## BanyanDB TTL
+
+BanyanDB has a TTL mechanism to automatically delete data that is older than the specified time. When you use BanyanDB
+as the storage backend, `recordDataTTL` and `metricsDataTTL` are not used. Instead, you should configure the TTL
+settings in `storage.banyandb`.
+
+Please refer to the [Storage BanyanDB](storages/banyandb.md) and [BanyanDB's Progressive TTL](../../banyandb/ttl.md)
+documents for more information.
diff --git a/docs/en/setup/backend/ui-grafana.md b/docs/en/setup/backend/ui-grafana.md
new file mode 100644
index 000000000000..45392ea07452
--- /dev/null
+++ b/docs/en/setup/backend/ui-grafana.md
@@ -0,0 +1,125 @@
+# Use Grafana As The UI
+SkyWalking provide [PromQL Service](../../api/promql-service.md) since 9.4.0 and [LogQL Service](../../api/logql-service.md) since 9.6.0. You can choose [Grafana](https://grafana.com/)
+as the SkyWalking UI. About the installation and how to use please refer to the [official document](https://grafana.com/docs/grafana/v9.3/).
+
+Notice <1>, Gafana is [AGPL-3.0 license](https://github.com/grafana/grafana/blob/main/LICENSE), which is very different from Apache 2.0.
+Please follow AGPL 3.0 license requirements.
+
+Notice <2>, SkyWalking always uses its native UI as first class. All visualization features are only available on native UI.
+Grafana UI is an extension on our support of PromQL APIs. We don't maintain or promise the complete Grafana UI dashboard setup.
+
+## Configure Data Source
+### Prometheus Data Source
+In the data source config panel, chose the `Prometheus` and set the url to the OAP server address, the default port is `9090`.
+
+
+### SkyWalking Data Source
+Before you start, please install the [SkyWalking data source plugin](https://github.com/apache/skywalking-grafana-plugins).
+In the data source config panel, chose the `SkyWalking` and set the url to the OAP server `graphql` service address, the default port is `12800`.
+
+
+### Loki Data Source
+In the data source config panel, chose the `Loki` and set the url to the OAP server address, the default port is `3100`.
+
+
+## Configure Metric Dashboards
+
+### Dashboards Settings
+The following steps are the example of config a `General Service` dashboard:
+1. Create a dashboard named `General Service`. A [layer](../../../../oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/Layer.java) is recommended as a dashboard.
+2. Configure variables for the dashboard:
+
+After configure, you can select the service/instance/endpoint on the top of the dashboard:
+
+
+### Add Panels
+The following contents show how to add several typical metrics panels.
+General settings:
+1. Chose the metrics and chart.
+2. Set `Query options --> Min interval = 1m`, because the metrics min time bucket in SkyWalking is 1m.
+3. Add PromQL expressions, use the variables configured above for the labels then you can select the labels value from top.
+ **Note: Some metrics values may be required calculations to match units.**
+4. Select the returned labels you want to show on panel.
+5. Test query and save the panel.
+
+#### Common Value Metrics
+1. For example `service_apdex` and `Time series chart`.
+2. Add PromQL expression, the metric scope is `Service`, so add labels `service` and `layer` for match.
+3. Set `Connect null values --> Always` and `Show points --> Always` because when the query interval > 1hour or 1day SkyWalking return
+ the hour/day step metrics values.
+
+#### Labeled Value Metrics
+1. For example `service_percentile` and `Time series chart`.
+2. Add PromQL expressions, the metric scope is `Service`, add labels `service` and `layer` for match.
+ And it's a labeled value metric, add `labels='0,1,2,3,4'` filter the result label, and add`relabels='P50,P75,P90,P95,P99'` rename the result label.
+3. Set `Connect null values --> Always` and `Show points --> Always` because when the query interval > 1hour or 1day SkyWalking return
+ the hour/day step metrics values.
+
+
+#### Sort Metrics
+1. For example `service_instance_cpm` and `Bar gauge chart`.
+2. Add PromQL expressions, add labels `parent_service` and `layer` for match, add `top_n='10'` and `order='DES'` filter the result.
+3. Set the `Calculation --> Latest*`.
+
+
+#### Sampled Records
+Same as the Sort Metrics.
+
+## Configure Topology Dashboards
+
+### Dashboards Settings
+For now, SkyWalking support `General Service` and `Service Mesh` topology dashboards, the layer is `GENERAL` and `MESH` respectively.
+The following configuration can reuse the above `General Service` dashboard and add a new variable `Plugin_SkyWalking` for the dashboard:
+
+
+### Add Topology Panel
+1. Chose the Node Graph chart.
+2. Set `Layer` and `Service` by the variables. If you want to show all services in this layer, set `Service` empty.
+3. Set `Node Metrics` and `Edge Metrics` which you want to show on the topology.
+
+
+## Configure Log Dashboard
+### Dashboards Settings
+The following steps are the example of config a log dashboard:
+1. Create a dashboard named `Log`.
+2. Configure variables for the dashboard:
+
+3. Please make sure `service_instance` and `endpoint` variable enabled `Include All` option and set `Custom all value` to * or blank (typed by space button on the keyboard):
+
+4. `Tags` variable is a little different from others, for more details, please refer [Ad hoc filters](https://grafana.com/docs/grafana/latest/dashboards/variables/add-template-variables/#add-ad-hoc-filters):
+
+5. After configure, you can select log query variables on the top of the dashboard:
+
+
+### Add Log Panel
+The following steps show how to add a log panel.
+1. Choose `Logs` chart.
+2. Set the `Line limit` value (The max number of logs to return in a query) and `Order` value (Determines the sort order of logs).
+3. Add LogQL expressions, use the variables configured above for the labels and searching keyword.
+`service_instance` & `endpoint` variable ref should use raw [variable-format-options](https://grafana.com/docs/grafana/latest/dashboards/variables/variable-syntax/#advanced-variable-format-options)
+to prevent it value be escaped.
+4. Test query and save the panel.
+
+
+## Configure Relation Dashboards
+### Dashboards Settings
+The following steps are the example of config a `General Relation` dashboard:
+1. Create a dashboard named `General Relation`.
+2. Configure variables for the dashboard:
+ 
+ After configure, you can select the service/instance/endpoint and the dest service/instance/endpoint on the top of the dashboard:
+ 
+### Add Relation Metrics Panel
+The following contents show how to add relation metric panels.
+1. Chose the metrics and chart.
+2. Set `Query options`, `Connect null values`, `Show points` and `Returned Labels`. Please refer `Configure Metric Dashboards` part.
+3. Add PromQL expression, For all scopes, set `Layer`, `Dest Layer`, `Service` and `Dest Service` by the variables. For service instance relation scope, extra set `Service Instance` and `Dest Service Instance`.
+For endpoint relation scope, extra set `Endpoint` and `Dest Endpoint`.
+4. Test query and save the panel.
+
+
+## Preview on demo.skywalking.a.o
+SkyWalking community provides a preview site for services of `General` and `Service Mesh` layers from the demo environment.
+You could take a glance through [**Preview metrics on Grafana**](https://skywalking.apache.org/#demo) of the demo deployment.
+
+Notice, we don't provide all setups due to our monitoring target expanding fast. This demo is for helping you understand the above documents only.
diff --git a/docs/en/setup/backend/ui-setup.md b/docs/en/setup/backend/ui-setup.md
new file mode 100644
index 000000000000..18f5e3534309
--- /dev/null
+++ b/docs/en/setup/backend/ui-setup.md
@@ -0,0 +1,40 @@
+# UI
+SkyWalking UI distribution is already included in our Apache official release.
+
+## Startup
+Startup script is also in `/bin/webappService.sh`(.bat). UI runs as a Java process, powered-by Armeria.
+
+## Settings
+The settings file of UI is `webapp/webapp.yml` in the distribution package. It has three parts.
+
+1. Listening port.
+1. Backend connect info.
+
+```yaml
+serverPort: ${SW_SERVER_PORT:-8080}
+
+# Comma separated list of OAP addresses, with `http://` or `https://` prefix.
+oapServices: ${SW_OAP_ADDRESS:-http://localhost:12800}
+zipkinServices: ${SW_ZIPKIN_ADDRESS:http://localhost:9412}
+```
+
+## Start with Docker Image
+
+Start a container to connect OAP server whose address is `http://oap:12800`.
+
+```shell
+export version=9.0.0
+docker run --name oap --restart always -d -e SW_OAP_ADDRESS=http://oap:12800 -e SW_ZIPKIN_ADDRESS=http://oap:9412 apache/skywalking-ui:$version
+```
+
+### Configuration
+
+We could set up environment variables to configure this image.
+
+### SW_OAP_ADDRESS
+
+The address of your OAP server. The default value is `http://127.0.0.1:12800`.
+
+### SW_ZIPKIN_ADDRESS
+
+The address of your Zipkin server. The default value is `http://127.0.0.1:9412`.
diff --git a/docs/en/setup/backend/uninstrumented-gateways.md b/docs/en/setup/backend/uninstrumented-gateways.md
new file mode 100755
index 000000000000..4f46b04e45f9
--- /dev/null
+++ b/docs/en/setup/backend/uninstrumented-gateways.md
@@ -0,0 +1,22 @@
+# Uninstrumented Gateways/Proxies
+
+The uninstrumented gateways are not instrumented by the SkyWalking agent plugin when they start,
+but they can be configured in `gateways.yml` file or via [Dynamic Configuration](dynamic-config.md). The reason why they can't register
+to backend automatically is that there are no suitable agent plugins. For example, there are no agent plugins for Nginx, HAProxy, etc.
+So to visualize the real topology, we provide a way to configure the gateways/proxies manually.
+
+## Configuration Format
+
+The configuration content includes gateway names and their instances:
+
+```yml
+gateways:
+ - name: proxy0 # the name is not used for now
+ instances:
+ - host: 127.0.0.1 # the host/IP of this gateway instance
+ port: 9099 # the port of this gateway instance defaults to 80
+```
+
+**Note**: The `host` of the instance must be the one that is actually used on the client-side. For example,
+if instance `proxyA` has 2 IPs, say `192.168.1.110` and `192.168.1.111`, both of which delegate the target service,
+and the client connects to `192.168.1.110`, then configuring `192.168.1.111` as the `host` won't work properly.
diff --git a/docs/en/setup/backend/zipkin-trace.md b/docs/en/setup/backend/zipkin-trace.md
new file mode 100644
index 000000000000..9932e147992d
--- /dev/null
+++ b/docs/en/setup/backend/zipkin-trace.md
@@ -0,0 +1,74 @@
+## Zipkin receiver
+The Zipkin receiver makes the OAP server work as an alternative Zipkin server implementation for collecting traces.
+It supports Zipkin v1/v2 formats through the HTTP collector and Kafka collector.
+
+**NOTICE, Zipkin trace would not be analyzed like SkyWalking native trace format.**
+
+Use the following config to activate it.
+Set `enableHttpCollector` to enable HTTP collector and `enableKafkaCollector` to enable Kafka collector.
+
+```yaml
+receiver-zipkin:
+ selector: ${SW_RECEIVER_ZIPKIN:default}
+ default:
+ # Defines a set of span tag keys which are searchable.
+ # The max length of key=value should be less than 256 or will be dropped.
+ searchableTracesTags: ${SW_ZIPKIN_SEARCHABLE_TAG_KEYS:http.method}
+ # The sample rate precision is 1/10000, should be between 0 and 10000
+ sampleRate: ${SW_ZIPKIN_SAMPLE_RATE:10000}
+ ## The below configs are for OAP collect zipkin trace from HTTP
+ enableHttpCollector: ${SW_ZIPKIN_HTTP_COLLECTOR_ENABLED:true}
+ restHost: ${SW_RECEIVER_ZIPKIN_REST_HOST:0.0.0.0}
+ restPort: ${SW_RECEIVER_ZIPKIN_REST_PORT:9411}
+ restContextPath: ${SW_RECEIVER_ZIPKIN_REST_CONTEXT_PATH:/}
+ restMaxThreads: ${SW_RECEIVER_ZIPKIN_REST_MAX_THREADS:200}
+ restIdleTimeOut: ${SW_RECEIVER_ZIPKIN_REST_IDLE_TIMEOUT:30000}
+ restAcceptQueueSize: ${SW_RECEIVER_ZIPKIN_REST_QUEUE_SIZE:0}
+ ## The below configs are for OAP collect zipkin trace from kafka
+ enableKafkaCollector: ${SW_ZIPKIN_KAFKA_COLLECTOR_ENABLED:true}
+ kafkaBootstrapServers: ${SW_ZIPKIN_KAFKA_SERVERS:localhost:9092}
+ kafkaGroupId: ${SW_ZIPKIN_KAFKA_Group_Id:zipkin}
+ kafkaTopic: ${SW_ZIPKIN_KAFKA_TOPIC:zipkin}
+ # Kafka consumer config, JSON format as Properties. If it contains the same key with above, would override.
+ kafkaConsumerConfig: ${SW_ZIPKIN_KAFKA_CONSUMER_CONFIG:"{\"auto.offset.reset\":\"earliest\",\"enable.auto.commit\":true}"}
+ # The Count of the topic consumers
+ kafkaConsumers: ${SW_ZIPKIN_KAFKA_CONSUMERS:1}
+ kafkaHandlerThreadPoolSize: ${SW_ZIPKIN_KAFKA_HANDLER_THREAD_POOL_SIZE:-1}
+ kafkaHandlerThreadPoolQueueSize: ${SW_ZIPKIN_KAFKA_HANDLER_THREAD_POOL_QUEUE_SIZE:-1}
+
+```
+
+## Zipkin query
+The Zipkin receiver makes the OAP server work as an alternative Zipkin server implementation for query traces.
+It implemented `ZipkinQueryApiV2` through the HTTP service, supporting Zipkin-lens UI.
+
+Use the following config to activate it.
+
+```yaml
+query-zipkin:
+ selector: ${SW_QUERY_ZIPKIN:default}
+ default:
+ # For HTTP server
+ restHost: ${SW_QUERY_ZIPKIN_REST_HOST:0.0.0.0}
+ restPort: ${SW_QUERY_ZIPKIN_REST_PORT:9412}
+ restContextPath: ${SW_QUERY_ZIPKIN_REST_CONTEXT_PATH:/zipkin}
+ restMaxThreads: ${SW_QUERY_ZIPKIN_REST_MAX_THREADS:200}
+ restIdleTimeOut: ${SW_QUERY_ZIPKIN_REST_IDLE_TIMEOUT:30000}
+ restAcceptQueueSize: ${SW_QUERY_ZIPKIN_REST_QUEUE_SIZE:0}
+ # Default look back for serviceNames, remoteServiceNames and spanNames, 1 day in millis
+ lookback: ${SW_QUERY_ZIPKIN_LOOKBACK:86400000}
+ # The Cache-Control max-age (seconds) for serviceNames, remoteServiceNames and spanNames
+ namesMaxAge: ${SW_QUERY_ZIPKIN_NAMES_MAX_AGE:300}
+ ## The below config are OAP support for zipkin-lens UI
+ # Default traces query max size
+ uiQueryLimit: ${SW_QUERY_ZIPKIN_UI_QUERY_LIMIT:10}
+ # Default look back for search traces, 15 minutes in millis
+ uiDefaultLookback: ${SW_QUERY_ZIPKIN_UI_DEFAULT_LOOKBACK:900000}
+```
+
+## Lens UI
+Lens UI is Zipkin native UI. SkyWalking webapp has bundled it in the binary distribution.
+`{webapp IP}:{webapp port}/zipkin` is exposed and accessible for the browser.
+Meanwhile, `Iframe` UI component could be used to host Zipkin Lens UI on the SkyWalking booster UI dashboard.(link=/zipkin)
+
+Zipkin Lens UI source codes could be found [here](https://github.com/openzipkin/zipkin/tree/master/zipkin-lens).
\ No newline at end of file
diff --git a/docs/en/setup/envoy/als_setting.md b/docs/en/setup/envoy/als_setting.md
new file mode 100644
index 000000000000..28cb19640a39
--- /dev/null
+++ b/docs/en/setup/envoy/als_setting.md
@@ -0,0 +1,110 @@
+# Observe Service Mesh through ALS
+
+[Envoy Access Log Service (ALS)](https://www.envoyproxy.io/docs/envoy/v1.18.2/api-v2/service/accesslog/v2/als.proto) provides
+full logs on routed RPC, including HTTP and TCP.
+
+## Background
+
+The solution was initialized and first implemented by [Sheng Wu](https://github.com/wu-sheng), [Hongtao Gao](https://github.com/hanahmily), [Lizan Zhou](https://github.com/lizan),
+and [Dhi Aurrahman](https://github.com/dio) on May 17, 2019, and was presented at [KubeCon China 2019](https://kccncosschn19eng.sched.com/event/NroB/observability-in-service-mesh-powered-by-envoy-and-apache-skywalking-sheng-wu-lizan-zhou-tetrate).
+Here is a [video recording of the presentation](https://www.youtube.com/watch?v=tERm39ju9ew).
+
+SkyWalking is the first open-source project that introduced an ALS-based solution to the world. This solution provides a new take on observability with a lightweight payload on the service mesh.
+
+## Enable ALS and SkyWalking Receiver
+
+You need the following steps to set up ALS.
+
+- Enable [`envoyAccessLogService` in ProxyConfig](https://istio.io/docs/reference/config/istio.mesh.v1alpha1/#ProxyConfig) and set the ALS address to where the SkyWalking OAP listens.
+In Istio version 1.6.0+, if Istio is installed with [`demo` profile](https://istio.io/latest/docs/setup/additional-setup/config-profiles/), you can enable ALS with this command:
+
+ ```shell
+ istioctl manifest apply \
+ --set profile=demo \
+ --set meshConfig.enableEnvoyAccessLogService=true \
+ --set meshConfig.defaultConfig.envoyAccessLogService.address=
+ ```
+
+ Note: Replace `` with the real address where SkyWalking OAP is deployed.
+
+- Activate SkyWalking Envoy Receiver. (activated in default)
+
+```yaml
+envoy-metric:
+ selector: ${SW_ENVOY_METRIC:default}
+```
+
+- Choose an ALS analyzer. There are two available analyzers for both HTTP access logs and TCP access logs: `k8s-mesh` and `mx-mesh`.
+ Set the system environment variables **SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS** and **SW_ENVOY_METRIC_ALS_TCP_ANALYSIS**,
+ such as `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=mx-mesh` and `SW_ENVOY_METRIC_ALS_TCP_ANALYSIS=mx-mesh`, or in `application.yaml` to activate the analyzers. For more about the analyzers, see [SkyWalking ALS Analyzers](#skywalking-als-analyzers).
+
+ ```yaml
+ envoy-metric:
+ selector: ${SW_ENVOY_METRIC:default}
+ default:
+ acceptMetricsService: ${SW_ENVOY_METRIC_SERVICE:true}
+ alsHTTPAnalysis: ${SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS:""} # Setting the system env variable would override this.
+ alsTCPAnalysis: ${SW_ENVOY_METRIC_ALS_TCP_ANALYSIS:""}
+ ```
+
+ To use multiple analyzers as a fallback, please use `,` to concatenate.
+
+## Example
+
+Here's an example of installing Istio and deploying SkyWalking by Helm chart.
+
+```shell
+istioctl install \
+ --set profile=demo \
+ --set meshConfig.enableEnvoyAccessLogService=true \
+ --set meshConfig.defaultConfig.envoyAccessLogService.address=skywalking-oap.istio-system:11800
+
+git clone https://github.com/apache/skywalking-helm.git
+cd skywalking-helm/chart
+
+helm repo add elastic https://helm.elastic.co
+
+helm dep up skywalking
+
+helm install 8.1.0 skywalking -n istio-system \
+ --set oap.env.SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=mx-mesh \
+ --set oap.env.SW_ENVOY_METRIC_ALS_TCP_ANALYSIS=mx-mesh \
+ --set fullnameOverride=skywalking \
+ --set oap.envoy.als.enabled=true
+```
+
+You can use `kubectl -n istio-system logs -l app=skywalking | grep "K8sALSServiceMeshHTTPAnalysis"` to ensure that OAP ALS `mx-mesh` analyzer has been activated.
+
+## SkyWalking ALS Analyzers
+
+There are several available analyzers: `k8s-mesh`, `mx-mesh`, and `persistence`. You can specify one or more
+analyzers to analyze the access logs. When multiple analyzers are specified, it acts as a fast-success mechanism:
+SkyWalking loops over the analyzers and use them to analyze the logs. Once there is an analyzer that is able to produce a
+result, it stops the loop.
+
+### `k8s-mesh`
+
+`k8s-mesh` uses the metadata from Kubernetes clusters, hence in this analyzer, OAP needs access roles to `Pod`, `Service`, and `Endpoints`.
+
+The [blog](https://skywalking.apache.org/blog/2020-12-03-obs-service-mesh-with-sw-and-als/) illustrates the details of how it works and a step-by-step tutorial to apply it to the `bookinfo` application.
+
+### `mx-mesh`
+
+`mx-mesh` uses the Envoy metadata exchange mechanism to get the service name, etc.
+This analyzer requires Istio to enable the metadata exchange plugin (you can enable it by `--set values.telemetry.v2.enabled=true`,
+or if you're using Istio 1.7+ and installing it with profile `demo`/`preview`, it should already be enabled).
+
+The [blog](https://skywalking.apache.org/blog/obs-service-mesh-vm-with-sw-and-als/) illustrates the details of how it works and a step-by-step tutorial on applying it to the [Online Boutique](https://github.com/GoogleCloudPlatform/microservices-demo) system.
+
+### `persistence`
+
+`persistence` analyzer adapts the Envoy access log format to
+SkyWalking's [native log format](https://github.com/apache/skywalking-data-collect-protocol/blob/master/logging/Logging.proto), and forwards the formatted logs to [LAL](../../concepts-and-designs/lal.md), where you can configure persistent
+conditions, such as `sampler`, only persist error logs, etc. SkyWalking provides a default configuration
+file [`envoy-als.yaml`](../../../../oap-server/server-starter/src/main/resources/lal/envoy-als.yaml) that you can
+adjust as per your needs. Please make sure to activate this rule via adding the rule name `envoy-als`
+into config item `log-analyzer/default/lalFiles` (or environment variable `SW_LOG_LAL_FILES`,
+e.g. `SW_LOG_LAL_FILES=envoy-als`).
+
+**Attention**: Since the `persistence` analyzer also needs a mechanism to map the logs into responding services, you need to configure at least one of `k8s-mesh` or `mx-mesh` as its antecedent so that `persistence` analyzer knows which service the logs belong to. For example, you should set `envoy-metric/default/alsHTTPAnalysis` (or environment
+variable `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS`) to something like `k8s-mesh,persistence`, `mx-mesh,persistence`, or `mx-mesh,k8s-mesh,persistence`.
diff --git a/docs/en/setup/envoy/config.yaml b/docs/en/setup/envoy/config.yaml
new file mode 100644
index 000000000000..7037f2a72bcd
--- /dev/null
+++ b/docs/en/setup/envoy/config.yaml
@@ -0,0 +1,108 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+admin:
+ access_log_path: /tmp/admin_access.log
+ address:
+ socket_address:
+ protocol: TCP
+ address: 127.0.0.1
+ port_value: 9901
+
+stats_sinks:
+ - name: envoy.metrics_service
+ config:
+ grpc_service:
+ envoy_grpc:
+ cluster_name: service_skywalking
+
+node:
+ id: ingress
+ cluster: card-api-cluster
+ locality:
+ region: ap-southeast-1
+ zone: zone1
+ sub_zone: subzone1
+ metadata:
+ skywalking: iscool
+ envoy: isawesome
+ LABELS:
+ app: test-app
+ NAME: service-instance-name
+
+static_resources:
+ listeners:
+ - name: listener_0
+ address:
+ socket_address:
+ protocol: TCP
+ address: 0.0.0.0
+ port_value: 10000
+ filter_chains:
+ - filters:
+ - name: envoy.http_connection_manager
+ typed_config:
+ "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
+ stat_prefix: ingress_http
+ route_config:
+ name: local_route
+ virtual_hosts:
+ - name: local_service
+ domains: ["*"]
+ routes:
+ - match:
+ prefix: "/"
+ route:
+ host_rewrite: www.google.com
+ cluster: service_google
+ http_filters:
+ - name: envoy.router
+ clusters:
+ - name: service_skywalking
+ connect_timeout: 5s
+ type: LOGICAL_DNS
+ http2_protocol_options: {}
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_skywalking
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: skywalking
+ # This is the port where SkyWalking serving the Envoy Metrics Service gRPC stream.
+ port_value: 11800
+
+ - name: service_google
+ connect_timeout: 5s
+ type: LOGICAL_DNS
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_google
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: www.google.com
+ port_value: 443
+ tls_context:
+ sni: www.google.com
diff --git a/docs/en/setup/envoy/examples/metrics/Makefile b/docs/en/setup/envoy/examples/metrics/Makefile
new file mode 100644
index 000000000000..da68d6304792
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/Makefile
@@ -0,0 +1,23 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+up:
+ docker-compose up -d
+
+down:
+ docker-compose down
+
+.PHONY: up down
diff --git a/docs/en/setup/envoy/examples/metrics/README.md b/docs/en/setup/envoy/examples/metrics/README.md
new file mode 100644
index 000000000000..eb8ae15b7c45
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/README.md
@@ -0,0 +1,114 @@
+# Sending Envoy Metrics to SkyWalking OAP Server Example
+
+This is an example of sending [Envoy Stats](https://www.envoyproxy.io/docs/envoy/v1.19.1/intro/arch_overview/observability/statistics) to the SkyWalking OAP server
+through Metric Service [v2](https://www.envoyproxy.io/docs/envoy/v1.18.2/api-v2/config/metrics/v2/metrics_service.proto) and [v3](https://www.envoyproxy.io/docs/envoy/v1.19.1/api-v3/config/metrics/v3/metrics_service.proto).
+
+## Running the example
+
+The example requires `docker` and `docker-compose` to be installed in your local system. It fetches images from Docker Hub.
+
+Note that in this setup, we override the [`log4j2.xml`](log4j2.xml) config to set the `org.apache.skywalking.oap.server.receiver.envoy` logger level to `DEBUG`. This enables us to see the messages sent by Envoy to the SkyWalking OAP server.
+
+You can also find the Envoy Metric Service V3 API example in [docker-compose-envoy-v3-api.yaml](./docker-compose-envoy-v3-api.yaml)
+```
+$ make up
+$ docker-compose logs -f skywalking
+$ # Please wait for a moment until SkyWalking is ready and Envoy starts sending the stats. You will see similar messages like the following:
+skywalking_1 | 2021-07-23 13:25:30,683 - org.apache.skywalking.oap.server.receiver.envoy.MetricServiceGRPCHandler -19437 [grpcServerPool-1-thread-2] DEBUG [] - Received msg identifier {
+skywalking_1 | node {
+skywalking_1 | id: "ingress"
+skywalking_1 | cluster: "envoy-proxy"
+skywalking_1 | metadata {
+skywalking_1 | fields {
+skywalking_1 | key: "LABELS"
+skywalking_1 | value {
+skywalking_1 | struct_value {
+skywalking_1 | fields {
+skywalking_1 | key: "app"
+skywalking_1 | value {
+skywalking_1 | string_value: "test-app"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "NAME"
+skywalking_1 | value {
+skywalking_1 | string_value: "service-instance-name"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "envoy"
+skywalking_1 | value {
+skywalking_1 | string_value: "isawesome"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "skywalking"
+skywalking_1 | value {
+skywalking_1 | string_value: "iscool"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | locality {
+skywalking_1 | region: "ap-southeast-1"
+skywalking_1 | zone: "zone1"
+skywalking_1 | sub_zone: "subzone1"
+skywalking_1 | }
+skywalking_1 | user_agent_name: "envoy"
+skywalking_1 | user_agent_build_version {
+skywalking_1 | version {
+skywalking_1 | major_number: 1
+skywalking_1 | minor_number: 19
+skywalking_1 | }
+skywalking_1 | metadata {
+skywalking_1 | fields {
+skywalking_1 | key: "build.type"
+skywalking_1 | value {
+skywalking_1 | string_value: "RELEASE"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "revision.sha"
+skywalking_1 | value {
+skywalking_1 | string_value: "68fe53a889416fd8570506232052b06f5a531541"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "revision.status"
+skywalking_1 | value {
+skywalking_1 | string_value: "Clean"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | fields {
+skywalking_1 | key: "ssl.version"
+skywalking_1 | value {
+skywalking_1 | string_value: "BoringSSL"
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | extensions {
+skywalking_1 | name: "composite-action"
+skywalking_1 | category: "envoy.matching.action"
+skywalking_1 | }
+ ......
+skywalking_1 | }
+skywalking_1 | }
+skywalking_1 | envoy_metrics {
+skywalking_1 | name: "cluster.service_google.update_no_rebuild"
+skywalking_1 | type: COUNTER
+skywalking_1 | metric {
+skywalking_1 | counter {
+skywalking_1 | value: 1.0
+skywalking_1 | }
+skywalking_1 | timestamp_ms: 1627046729718
+skywalking_1 | }
+ ......
+skywalking_1 | }
+...
+
+$ # To tear down:
+$ make down
+```
diff --git a/docs/en/setup/envoy/examples/metrics/docker-compose-envoy-v3-api.yaml b/docs/en/setup/envoy/examples/metrics/docker-compose-envoy-v3-api.yaml
new file mode 100644
index 000000000000..58d0382dbfa1
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/docker-compose-envoy-v3-api.yaml
@@ -0,0 +1,34 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+version: "3"
+services:
+ envoy19:
+ image: envoyproxy/envoy-alpine:v1.19-latest
+ command: /usr/local/bin/envoy -c /etc/envoy.yaml --service-cluster envoy-proxy
+ ports:
+ - 10001:10000
+ depends_on:
+ - skywalking
+ volumes:
+ - ./envoy-v1.19.yaml:/etc/envoy.yaml
+
+ skywalking:
+ image: apache/skywalking-oap-server:latest
+ volumes:
+ - ./log4j2.xml:/skywalking/config/log4j2.xml
+ expose:
+ - "11800"
diff --git a/docs/en/setup/envoy/examples/metrics/docker-compose.yaml b/docs/en/setup/envoy/examples/metrics/docker-compose.yaml
new file mode 100644
index 000000000000..a5873b998fb8
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/docker-compose.yaml
@@ -0,0 +1,34 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+version: "3"
+services:
+ envoy16:
+ image: envoyproxy/envoy-alpine:v1.16.2
+ command: /usr/local/bin/envoy -c /etc/envoy.yaml --service-cluster envoy-proxy
+ ports:
+ - 10000:10000
+ depends_on:
+ - skywalking
+ volumes:
+ - ./envoy-v1.16.yaml:/etc/envoy.yaml
+
+ skywalking:
+ image: apache/skywalking-oap-server:latest
+ volumes:
+ - ./log4j2.xml:/skywalking/config/log4j2.xml
+ expose:
+ - "11800"
diff --git a/docs/en/setup/envoy/examples/metrics/envoy-v1.16.yaml b/docs/en/setup/envoy/examples/metrics/envoy-v1.16.yaml
new file mode 100644
index 000000000000..9d3caec766b1
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/envoy-v1.16.yaml
@@ -0,0 +1,107 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+admin:
+ access_log_path: /tmp/admin_access.log
+ address:
+ socket_address:
+ protocol: TCP
+ address: 127.0.0.1
+ port_value: 9901
+
+stats_sinks:
+ - name: envoy.metrics_service
+ config:
+ grpc_service:
+ envoy_grpc:
+ cluster_name: service_skywalking
+
+node:
+ id: ingress-v1
+ cluster: card-api-cluster-v1
+ locality:
+ region: ap-southeast-1
+ zone: zone1
+ sub_zone: subzone1
+ metadata:
+ skywalking: iscool
+ envoy: isawesome
+ LABELS:
+ app: test-app-v1
+ NAME: service-instance-name-v1
+
+static_resources:
+ listeners:
+ - name: listener_0
+ address:
+ socket_address:
+ protocol: TCP
+ address: 0.0.0.0
+ port_value: 10000
+ filter_chains:
+ - filters:
+ - name: envoy.http_connection_manager
+ typed_config:
+ "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
+ stat_prefix: ingress_http
+ route_config:
+ name: local_route
+ virtual_hosts:
+ - name: local_service
+ domains: ["*"]
+ routes:
+ - match:
+ prefix: "/"
+ route:
+ host_rewrite: www.google.com
+ cluster: service_google
+ http_filters:
+ - name: envoy.router
+ clusters:
+ - name: service_skywalking
+ connect_timeout: 5s
+ type: STRICT_DNS
+ http2_protocol_options: {}
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_skywalking
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: skywalking
+ port_value: 11800
+
+ - name: service_google
+ connect_timeout: 5s
+ type: STRICT_DNS
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_google
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: www.google.com
+ port_value: 443
+ tls_context:
+ sni: www.google.com
diff --git a/docs/en/setup/envoy/examples/metrics/envoy-v1.19.yaml b/docs/en/setup/envoy/examples/metrics/envoy-v1.19.yaml
new file mode 100644
index 000000000000..1c7169c8ae7a
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/envoy-v1.19.yaml
@@ -0,0 +1,116 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+admin:
+ access_log_path: /tmp/admin_access.log
+ address:
+ socket_address:
+ protocol: TCP
+ address: 127.0.0.1
+ port_value: 9901
+
+stats_sinks:
+ - name: envoy.stat_sinks.metrics_service
+ typed_config:
+ "@type": type.googleapis.com/envoy.config.metrics.v3.MetricsServiceConfig
+ transport_api_version: V3
+ grpc_service:
+ envoy_grpc:
+ cluster_name: service_skywalking
+
+node:
+ id: ingress-v2
+ cluster: card-api-cluster-v2
+ locality:
+ region: ap-southeast-1
+ zone: zone1
+ sub_zone: subzone1
+ metadata:
+ skywalking: iscool
+ envoy: isawesome
+ LABELS:
+ app: test-app-v2
+ NAME: service-instance-name-v2
+
+static_resources:
+ listeners:
+ - name: listener_0
+ address:
+ socket_address:
+ protocol: TCP
+ address: 0.0.0.0
+ port_value: 10000
+ filter_chains:
+ - filters:
+ - name: envoy.filters.network.http_connection_manager
+ typed_config:
+ "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
+ codec_type: auto
+ stat_prefix: ingress_http
+ route_config:
+ name: local_route
+ virtual_hosts:
+ - name: local_service
+ domains: ["*"]
+ routes:
+ - match:
+ prefix: "/"
+ route:
+ host_rewrite_literal: www.google.com
+ cluster: service_google
+ http_filters:
+ - name: envoy.filters.http.router
+ clusters:
+ - name: service_skywalking
+ connect_timeout: 5s
+ type: LOGICAL_DNS
+ typed_extension_protocol_options:
+ envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
+ "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
+ explicit_http_config:
+ http2_protocol_options: {}
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_skywalking
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: skywalking
+ port_value: 11800
+
+ - name: service_google
+ connect_timeout: 5s
+ type: STRICT_DNS
+ # Comment out the following line to test on v6 networks
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_google
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: www.google.com
+ port_value: 443
+ transport_socket:
+ name: envoy.transport_sockets.tls
+ typed_config:
+ "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
diff --git a/docs/en/setup/envoy/examples/metrics/log4j2.xml b/docs/en/setup/envoy/examples/metrics/log4j2.xml
new file mode 100644
index 000000000000..55dd9fe6572d
--- /dev/null
+++ b/docs/en/setup/envoy/examples/metrics/log4j2.xml
@@ -0,0 +1,36 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/en/setup/envoy/identify.json b/docs/en/setup/envoy/identify.json
new file mode 100644
index 000000000000..f0a1ecefc37a
--- /dev/null
+++ b/docs/en/setup/envoy/identify.json
@@ -0,0 +1,366 @@
+{
+ "identifier": {
+ "node": {
+ "id": "ingress",
+ "cluster": "envoy-proxy",
+ "metadata": {
+ "envoy": "isawesome",
+ "skywalking": "iscool"
+ },
+ "locality": {
+ "region": "ap-southeast-1",
+ "zone": "zone1",
+ "subZone": "subzone1"
+ },
+ "buildVersion": "caf7ab123964cedd172a2d4cb29b2f2e05ca9156/1.10.0-dev/Clean/RELEASE/BoringSSL"
+ }
+ },
+ "envoyMetrics": [
+ {
+ "name": "cluster.service_stats.update_attempt",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_change",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.update_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.update_attempt",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.update_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_change",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.listener_added",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.listener_create_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.cluster_added",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "runtime.deprecated_feature_use",
+ "metric": [
+ {
+ "counter": {
+ "value": 18
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_healthy",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_degraded",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_total",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_total",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_degraded",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_healthy",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.parent_connections",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.live",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.total_listeners_active",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.memory_heap_size",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 3145728
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.uptime",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 5
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.days_until_first_cert_expiring",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 2147483647
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.concurrency",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.total_connections",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.hot_restart_epoch",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.memory_allocated",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1704824
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.active_clusters",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 2
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "server.version",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 13301675
+ },
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.total_listeners_warming",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "runtime.num_keys",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.warming_clusters",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781658343"
+ }
+ ]
+ }
+ ]
+}
diff --git a/docs/en/setup/envoy/metrics.json b/docs/en/setup/envoy/metrics.json
new file mode 100644
index 000000000000..218f51ad3049
--- /dev/null
+++ b/docs/en/setup/envoy/metrics.json
@@ -0,0 +1,545 @@
+{
+ "envoyMetrics": [
+ {
+ "name": "cluster.service_stats.upstream_cx_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_rq_pending_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.update_attempt",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_tx_bytes_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 2185
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_rx_bytes_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 48
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_change",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_rq_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_http2_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.update_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.update_attempt",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.update_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_change",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "http.async-client.rq_total",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.listener_added",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.listener_create_success",
+ "metric": [
+ {
+ "counter": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.cluster_added",
+ "metric": [
+ {
+ "counter": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "runtime.deprecated_feature_use",
+ "metric": [
+ {
+ "counter": {
+ "value": 18
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_healthy",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_rq_pending_active",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_degraded",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.membership_total",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_rx_bytes_buffered",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 39
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.circuit_breakers.default.rq_pending_open",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_rq_active",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_active",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.circuit_breakers.default.rq_open",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_total",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_degraded",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_google.membership_healthy",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.parent_connections",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.live",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.total_listeners_active",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.memory_heap_size",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 3145728
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.uptime",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 10
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.days_until_first_cert_expiring",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 2147483647
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.concurrency",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.total_connections",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.hot_restart_epoch",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.memory_allocated",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 1767200
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.active_clusters",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 2
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "server.version",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {
+ "value": 13301675
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "listener_manager.total_listeners_warming",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "runtime.num_keys",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster_manager.warming_clusters",
+ "type": "GAUGE",
+ "metric": [
+ {
+ "gauge": {},
+ "timestampMs": "1551781663344"
+ }
+ ]
+ },
+ {
+ "name": "cluster.service_stats.upstream_cx_connect_ms",
+ "type": "SUMMARY",
+ "metric": [
+ {
+ "summary": {
+ "quantile": [
+ {
+ "value": 1
+ },
+ {
+ "quantile": 0.25,
+ "value": 1.025
+ },
+ {
+ "quantile": 0.5,
+ "value": 1.05
+ },
+ {
+ "quantile": 0.75,
+ "value": 1.075
+ },
+ {
+ "quantile": 0.9,
+ "value": 1.09
+ },
+ {
+ "quantile": 0.95,
+ "value": 1.095
+ },
+ {
+ "quantile": 0.99,
+ "value": 1.099
+ },
+ {
+ "quantile": 0.995,
+ "value": 1.0995
+ },
+ {
+ "quantile": 0.999,
+ "value": 1.0999
+ },
+ {
+ "quantile": 1,
+ "value": 1.1
+ }
+ ]
+ },
+ "timestampMs": "1551781663344"
+ }
+ ]
+ }
+ ]
+}
diff --git a/docs/en/setup/envoy/metrics_service_setting.md b/docs/en/setup/envoy/metrics_service_setting.md
new file mode 100644
index 000000000000..f4b9df61d046
--- /dev/null
+++ b/docs/en/setup/envoy/metrics_service_setting.md
@@ -0,0 +1,114 @@
+# Send Envoy metrics to SkyWalking with/without Istio
+
+Envoy defines a gRPC service to emit metrics, and whatever is used to implement this protocol can be used to receive the metrics.
+SkyWalking has a built-in receiver that implements this protocol, so you can configure Envoy to emit its metrics to SkyWalking.
+
+As an APM system, SkyWalking not only receives and stores the metrics emitted by Envoy but also analyzes the topology of services and service instances.
+
+**Attention:** There are two versions of the Envoy metrics service protocol currently:
+[v2](https://www.envoyproxy.io/docs/envoy/v1.18.2/api-v2/api/v2/core/grpc_service.proto#envoy-api-msg-core-grpcservice) and
+[v3](https://www.envoyproxy.io/docs/envoy/v1.18.2/api-v3/config/metrics/v3/metrics_service.proto). SkyWalking (8.3.0+) supports both of them.
+
+## Configure Envoy to send metrics to SkyWalking without Istio
+
+Envoy can be used with/without Istio. This section explains how you can configure the standalone Envoy to send metrics to SkyWalking.
+
+To let Envoy send metrics to SkyWalking, we need to feed Envoy with a configuration that contains `stats_sinks`, which in turn includes `envoy.metrics_service`.
+This `envoy.metrics_service` should be configured as a [`config.grpc_service`](https://www.envoyproxy.io/docs/envoy/v1.18.2/api-v2/api/v2/core/grpc_service.proto#envoy-api-msg-core-grpcservice) entry.
+
+The noteworthy parts of the config are shown below:
+
+```yaml
+stats_sinks:
+ - name: envoy.metrics_service
+ config:
+ grpc_service:
+ # Note: we can use google_grpc implementation as well.
+ envoy_grpc:
+ cluster_name: service_skywalking
+
+static_resources:
+ ...
+ clusters:
+ - name: service_skywalking
+ connect_timeout: 5s
+ type: LOGICAL_DNS
+ http2_protocol_options: {}
+ dns_lookup_family: V4_ONLY
+ lb_policy: ROUND_ROBIN
+ load_assignment:
+ cluster_name: service_skywalking
+ endpoints:
+ - lb_endpoints:
+ - endpoint:
+ address:
+ socket_address:
+ address: skywalking
+ # This is the port where SkyWalking serving the Envoy Metrics Service gRPC stream.
+ port_value: 11800
+```
+
+The comprehensive static configuration can be found [here](config.yaml).
+
+Note that Envoy can also be configured dynamically through [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
+
+As mentioned above, SkyWalking also builds the topology of services from the metrics since Envoy also carries service metadata along with the metrics. To feed Envoy such metadata, see the other part of the configuration as follows:
+
+```yaml
+node:
+ # ... other configs
+ metadata:
+ LABELS:
+ app: test-app
+ NAME: service-instance-name
+```
+
+## Configure Envoy to send metrics to SkyWalking with Istio
+
+Typically, Envoy can also be used with Istio. In this case, the configurations are much simpler because Istio composes the configurations for you and sends them to Envoy via [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
+Istio also automatically injects the metadata, such as service name and instance name, into the bootstrap configurations.
+
+Emitting the metrics to SkyWalking is as simple as adding the option `--set meshConfig.defaultConfig.envoyMetricsService.address=` to Istio install command, like this:
+
+```shell
+istioctl install -y \
+ --set profile=demo # replace the profile as per your need \
+ --set meshConfig.defaultConfig.envoyMetricsService.address= \ # replace with your actual SkyWalking OAP address
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[0]=.*'
+```
+
+If you already have Istio installed, you can use the following command to apply the config without re-installing Istio:
+
+```shell
+istioctl manifest install -y \
+ --set profile=demo # replace the profile as per your need \
+ --set meshConfig.defaultConfig.envoyMetricsService.address= \ # replace with your actual SkyWalking OAP address
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[0]=.*'
+```
+
+Note:
+`proxyStatsMatcher` is only supported by `Istio 1.8+`.
+We recommend using `inclusionRegexps` to reserve specific metrics that need to be analyzed to reduce memory usage and avoid CPU overhead.
+For example, OAP uses these metrics:
+
+```shell
+istioctl manifest install -y \
+ --set profile=demo # replace the profile as per your need \
+ --set meshConfig.defaultConfig.envoyMetricsService.address= \ # replace with your actual SkyWalking OAP address
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[0]=.*membership_healthy.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[1]=.*upstream_cx_active.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[2]=.*upstream_cx_total.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[3]=.*upstream_rq_active.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[4]=.*upstream_rq_total.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[5]=.*upstream_rq_pending_active.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[6]=.*lb_healthy_panic.*' \
+ --set 'meshConfig.defaultConfig.proxyStatsMatcher.inclusionRegexps[7]=.*upstream_cx_none_healthy.*'
+```
+
+# Metrics data
+
+Some Envoy statistics are [listed here](https://www.envoyproxy.io/docs/envoy/v1.17.0/configuration/upstream/cluster_manager/cluster_stats#config-cluster-manager-cluster-stats). Sample data that contain identifiers can be found [here](identify.json), while the metrics can be found [here](metrics.json).
+
+# Network Monitoring
+
+SkyWalking supports network monitoring of the data plane in the Service Mesh. [Read this documentation](../backend/backend-k8s-network-monitoring.md) for learn more.
\ No newline at end of file
diff --git a/docs/en/setup/istio/README.md b/docs/en/setup/istio/README.md
new file mode 100644
index 000000000000..a0ffd4b72e0f
--- /dev/null
+++ b/docs/en/setup/istio/README.md
@@ -0,0 +1,63 @@
+# Working with Istio
+
+This document provides instructions on transporting Istio's metrics to the SkyWalking OAP server.
+
+## Prerequisites
+
+Istio should be installed in a Kubernetes cluster. Simply follow the steps in [Getting Started in Istio](https://istio.io/docs/setup/getting-started/).
+
+## Deploy SkyWalking backend
+
+Follow the steps in [deploying backend in Kubernetes](../backend/backend-k8s.md) to install the OAP server in the Kubernetes cluster.
+Refer to [OpenTelemetry receiver](../backend/opentelemetry-receiver.md) to ingest metrics.
+
+
+## Deploy OpenTelemetry Collector
+OpenTelemetry Collector is the location where Istio telemetry sends metrics, which are then processed and shipped to SkyWalking
+backend.
+
+To deploy this collector, follow the steps in [Getting Started in OpenTelemetry Collector](https://opentelemetry.io/docs/collector/getting-started/).
+Several components are available in the collector, and they could be combined for different use cases.
+
+After installing the collector, you may configure it to scrape metrics from Istio and send them to SkyWalking backend.
+
+The job configuration to scrape metrics from Istio and send them to SkyWalking backend is as follows:
+
+```yaml
+receivers:
+ prometheus:
+ config:
+ scrape_configs:
+ - job_name: 'istiod-monitor'
+ kubernetes_sd_configs:
+ - role: endpoints
+ relabel_configs:
+ - source_labels: [ __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name ]
+ action: keep
+ regex: istiod;http-monitoring
+ - action: labelmap
+ regex: __meta_kubernetes_service_label_(.+)
+ - source_labels: [ ]
+ target_label: cluster
+ replacement: your-cluster # replace this with your cluster name
+
+exporters:
+ otlp:
+ endpoint: oap.skywalking:11800 # replace this with the OAP gRPC service address
+ tls:
+ insecure: true
+
+service:
+ pipelines:
+ metrics:
+ receivers: [ prometheus ]
+ exporters: [ otlp,logging ]
+```
+
+## Observing Istio
+
+Open Istio Dashboard in SkyWalking UI by clicking `Dashboard` -> `Istio`. You can then view charts and diagrams
+generated by Istio metrics. You may also view them through `swctl` and set up alarm rules based on them.
+
+
+Note: If you would like to see metrics of Istio managed services, including topology, you may try our [ALS solution](../envoy/als_setting.md).
diff --git a/docs/en/setup/service-agent/agent-compatibility.md b/docs/en/setup/service-agent/agent-compatibility.md
new file mode 100644
index 000000000000..1d0f00b53ebf
--- /dev/null
+++ b/docs/en/setup/service-agent/agent-compatibility.md
@@ -0,0 +1,32 @@
+# Compatibility
+
+SkyWalking 8.0+ uses v3 protocols. Agents don't have to keep the identical versions as the OAP backend.
+
+## SkyWalking Native Agents
+
+| OAP Server Version | Java | Python | NodeJS | LUA | Kong | Browser Agent | Rust | PHP | Go | Rover | Satellite |
+|--------------------|-------------------------|-----------|-----------|-----|------|---------------|------|-----|------------|------------|------------|
+| 8.0.1 - 8.1.0 | 8.0.0 - 8.3.0 | < = 0.6.0 | < = 0.3.0 | All | All | No | All | No | No | No | No |
+| 8.2.0 - 8.3.0 | 8.0.0 - 8.3.0 | < = 0.6.0 | < = 0.3.0 | All | All | All | All | No | No | No | No |
+| 8.4.0 - 8.8.1 | \> = 8.0.0 | All | All | All | All | All | All | All | No | No | No |
+| 8.9.0+ | \> = 8.0.0 | All | All | All | All | All | All | All | No | No | \> = 0.4.0 |
+| 9.0.0 | \> = 8.0.0 | All | All | All | All | All | All | All | No | No | \> = 0.4.0 |
+| 9.1.0+ | \> = 8.0.0 | All | All | All | All | All | All | All | No | \> = 0.1.0 | \> = 1.0.0 |
+| 9.5.0+ | \> = 8.0.0 & \> = 9.0.0 | All | All | All | All | All | All | All | \> = 0.1.0 | \> = 0.5.0 | \> = 1.2.0 |
+
+## Ecosystem Agents
+
+All following agent implementations are a part of the SkyWalking ecosystem. All the source codes and their distributions
+don't belong to the Apache Software Foundation.
+
+| OAP Server Version | DotNet | cpp2sky |
+|--------------------|---------------|-----------|
+| 8.0.1 - 8.3.0 | 1.0.0 - 1.3.0 | < = 0.2.0 |
+| 8.4.0+ | \> = 1.0.0 | All |
+| 9.0.0+ | \> = 1.0.0 | All |
+
+All these projects are maintained by their own communities, and please reach them if you face any compatibility issues.
+
+___
+All above compatibility are only references, and if you face an `unimplemented` error, it means you need to upgrade the
+OAP backend to support newer features in the agents.
diff --git a/docs/en/setup/service-agent/browser-agent.md b/docs/en/setup/service-agent/browser-agent.md
new file mode 100644
index 000000000000..64f86e146c4d
--- /dev/null
+++ b/docs/en/setup/service-agent/browser-agent.md
@@ -0,0 +1,19 @@
+## Browser Monitoring
+[Apache SkyWalking Client JS](https://github.com/apache/skywalking-client-js) is a client-side JavaScript exception and tracing library.
+
+It has these features:
+- Provides metrics and error collection to SkyWalking backend.
+- Lightweight. A simple JavaScript library. No browser plugin is required.
+- Browser serves as a starting point for the entire distributed tracing system.
+
+See Client JS [official doc](https://github.com/apache/skywalking-client-js#quick-start) for more information.
+
+Note: Make sure receiver-browser is enabled. It is **ON** by default since version 8.2.0.
+
+```yaml
+receiver-browser:
+ selector: ${SW_RECEIVER_BROWSER:default} // This means activated.
+ default:
+ # The sample rate precision is 1/10000. 10000 means 100% sample in default.
+ sampleRate: ${SW_RECEIVER_BROWSER_SAMPLE_RATE:10000}
+```
diff --git a/docs/en/setup/service-agent/server-agents.md b/docs/en/setup/service-agent/server-agents.md
new file mode 100644
index 000000000000..ed469faa9d9c
--- /dev/null
+++ b/docs/en/setup/service-agent/server-agents.md
@@ -0,0 +1,31 @@
+# Server Agents
+
+Server agents in various languages provide auto-instrumentation or/and manual-instrumentation(APIs-based) mechanisms to
+integrate with target services. They support collecting traces, logs, metrics, and events using SkyWalking's native
+format and maximize the analysis capabilities of the SkyWalking OAP server.
+
+## Installing language agents in services
+
+- [Java agent](https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/readme/). Learn how to install the Java agent in your service without affecting your code.
+
+- [LUA agent](https://github.com/apache/skywalking-nginx-lua). Learn how to install the Lua agent in Nginx + LUA module or OpenResty.
+
+- [Kong agent](https://github.com/apache/skywalking-kong). Learn how to install the Lua agent in Kong.
+
+- [Python Agent](https://skywalking.apache.org/docs/skywalking-python/next/en/setup/cli/). Learn how to install the Python Agent in a Python service without affecting your code.
+
+- [Node.js agent](https://github.com/apache/skywalking-nodejs). Learn how to install the NodeJS Agent in a NodeJS service.
+
+- [Rust agent](https://github.com/apache/skywalking-rust). Learn how to integrate the Rust agent with a rust service.
+
+- [PHP agent](https://skywalking.apache.org/docs/skywalking-php/next/readme/). Learn how to install the PHP agent in your service without affecting your code.
+
+- [Go agent](https://skywalking.apache.org/docs/skywalking-go/next/readme/). Learn how to integrate the Go agent with a golang service.
+
+The following agents and SDKs are compatible with SkyWalking's data formats and network protocols but are maintained by
+third parties. See their project repositories for guides and releases.
+
+- [SkyAPM .NET Core agent](https://github.com/SkyAPM/SkyAPM-dotnet). See .NET Core agent project documentation for more
+ details.
+
+- [SkyAPM C++ SDK](https://github.com/SkyAPM/cpp2sky). See cpp2sky project documentation for more details.
diff --git a/docs/en/setup/service-agent/virtual-cache.md b/docs/en/setup/service-agent/virtual-cache.md
new file mode 100644
index 000000000000..b159b7ee80fb
--- /dev/null
+++ b/docs/en/setup/service-agent/virtual-cache.md
@@ -0,0 +1,18 @@
+# Virtual Cache
+
+Virtual cache represent the cache nodes detected by [server agents' plugins](server-agents.md). The performance
+metrics of the cache are also from the Cache client-side perspective.
+
+For example, Redis plugins in the Java agent could detect the latency of command
+As a result, SkyWalking would show traffic, latency, success rate, and sampled slow operations(write/read) powered by backend analysis capabilities in this dashboard.
+
+The cache operation span should have
+- It is an **Exit** or **Local** span
+- **Span's layer == CACHE**
+- Tag key = `cache.type`, value = The type of cache system , e.g. redis
+- Tag key = `cache.op`, value = `read` or `write` , indicates the value of tag `cache.cmd` is used for `write` or `read` operation
+- Tag key = `cache.cmd`, value = the cache command , e.g. get,set,del
+- Tag key = `cache.key`, value = the cache key
+- If the cache system is in-memory (e.g. Guava-cache), agents' plugin would create a local span usually, and the span's peer would be null ,otherwise the peer is the network address(IP or domain) of Cache server.
+
+Ref [slow cache doc](../backend/slow-cache-command.md) to know more slow Cache commands settings.
\ No newline at end of file
diff --git a/docs/en/setup/service-agent/virtual-database.md b/docs/en/setup/service-agent/virtual-database.md
new file mode 100644
index 000000000000..88c09577a972
--- /dev/null
+++ b/docs/en/setup/service-agent/virtual-database.md
@@ -0,0 +1,16 @@
+# Virtual Database
+
+Virtual databases represent the database nodes detected by [server agents' plugins](server-agents.md). The performance
+metrics of the databases are also from the Database client-side perspective.
+
+For example, JDBC plugins(MySQL, PostgreSQL, MariaDB, MSSQL) in the Java agent could detect the latency of SQL
+performance and SQL statements. As a result, SkyWalking would show database traffic, latency, success rate, and sampled slow SQLs powered by backend analysis capabilities in this dashboard.
+
+The Database access span should have
+- It is an **Exit** span
+- **Span's layer == DATABASE**
+- Tag key = `db.statement`, value = SQL statement
+- Tag key = `db.type`, value = the type of Database
+- Span's peer is the network address(IP or domain) of Database server.
+
+Ref [slow cache doc](../backend/slow-db-statement.md) to know more slow SQL settings.
diff --git a/docs/en/setup/service-agent/virtual-mq.md b/docs/en/setup/service-agent/virtual-mq.md
new file mode 100644
index 000000000000..15b209b79246
--- /dev/null
+++ b/docs/en/setup/service-agent/virtual-mq.md
@@ -0,0 +1,16 @@
+
+# Virtual Message Queue (MQ)
+
+Virtual MQ represent the MQ nodes detected by [server agents' plugins](server-agents.md). The performance
+metrics of the MQ are also from the MQ client-side perspective.
+
+For example, Kafka plugins in the Java agent could detect the transmission latency of message
+As a result, SkyWalking would show message count, transmission latency, success rate powered by backend analysis capabilities in this dashboard.
+
+The MQ operation span should have
+- It is an **Exit**(at producer side) or **Entry**(at consumer side) span
+- **Span's layer == MQ**
+- Tag key = `mq.queue`, value = MQ queue name
+- Tag key = `mq.topic`, value = MQ queue topic , it's optional as some MQ don't have topic concept.
+- Tag key = `transmission.latency`, value = Transmission latency from consumer to producer
+- Set `peer` at both sides(producer and consumer). And the value of peer should represent the MQ server cluster.
\ No newline at end of file
diff --git a/docs/en/setup/zipkin/tracing.md b/docs/en/setup/zipkin/tracing.md
new file mode 100644
index 000000000000..6ae7fffcf40e
--- /dev/null
+++ b/docs/en/setup/zipkin/tracing.md
@@ -0,0 +1,54 @@
+# Observe Service Mesh through Zipkin traces
+
+Istio has built-in support to generate Zipkin traces from Envoy proxy sidecar,
+and SkyWalking can serve as a Zipkin server to collect and provide query APIs for these traces,
+you can deploy SkyWalking to replace Zipkin server in Istio, and point the Zipkin address to
+SkyWalking. SkyWalking also embeds Zipkin Lens UI as part of SkyWalking UI,
+you can use it to query Zipkin traces.
+
+## Enable Zipkin Traces Receiver
+
+SkyWalking has built-in Zipkin receiver, you can enable it by setting `receiver-zipkin` to `default`
+in `application.yml`, or by setting environment variable `SW_RECEIVER_ZIPKIN=default` before
+starting OAP server:
+
+```yaml
+receiver-zipkin:
+ selector: ${SW_RECEIVER_ZIPKIN:default}
+ default:
+ # Other configurations...
+```
+
+After enabling the Zipkin receiver, SkyWalking listens on port 9411 for Zipkin traces, you can just
+change the Zipkin server address to SkyWalking's address with 9411 as the port.
+
+## Enable Zipkin Traces Query Module
+
+If you want to query Zipkin traces from SkyWalking, you need to enable the Zipkin traces query module
+by setting `query-zipkin` to `default` in `application.yml`, or by setting environment variable
+`SW_QUERY_ZIPKIN=default` before starting OAP server:
+
+```yaml
+query-zipkin:
+ selector: ${SW_QUERY_ZIPKIN:default}
+ default:
+ # Other configurations
+```
+
+After enabling Zipkin query module, SkyWalking listens on port 9412 for Zipkin query APIs, you can
+also query the Zipkin traces from SkyWalking UI, menu `Service Mesh --> Services --> Zipkin Trace`.
+
+## Set Up Zipkin Traces in Istio
+
+When installing Istio, you can enable Zipkin tracing and point it to SkyWalking by setting
+
+```shell
+istioctl install -y --set profile=demo \
+ --set meshConfig.defaultConfig.tracing.sampling=100 \
+ --set meshConfig.defaultConfig.tracing.zipkin.address=oap.istio-system.svc.cluster.local:9411 \
+ --set meshConfig.enableTracing=true
+```
+
+so that Istio proxy (Envoy) can generate traces and sent them to SkyWalking.
+
+For more details about Zipkin on Istio, refer to [the Istio doc](https://istio.io/latest/docs/tasks/observability/distributed-tracing/zipkin/).
diff --git a/docs/en/status/query_alarm_runtime_status.md b/docs/en/status/query_alarm_runtime_status.md
new file mode 100644
index 000000000000..e3678e0df2d7
--- /dev/null
+++ b/docs/en/status/query_alarm_runtime_status.md
@@ -0,0 +1,161 @@
+# Get Alarm Runtime Status
+
+OAP calculates the alarm conditions in the memory based on the alarm rules and the metrics data.
+The following APIs are exposed to make the alerting running kernel visible.
+
+## Get Alarm Running Rules
+
+Return the list of alarm running rules.
+
+- URL, `http://{core restHost}:{core restPort}/status/alarm/rules`
+- HTTP GET method.
+
+```json
+{
+ "ruleNames": [
+ "service_percentile_rule",
+ "service_resp_time_rule"
+ ]
+}
+```
+
+## Get Alarm Running Rule Info
+
+Return the detailed information of the alarm running rule.
+
+- URL, `http://{core restHost}:{core restPort}/status/alarm/rules/{ruleName}`
+- HTTP GET method.
+
+```json
+{
+ "ruleName": "service_resp_time_rule",
+ "expression": "sum(service_resp_time > baseline(service_resp_time,upper)) >= 1",
+ "period": 10,
+ "silentPeriod": 10,
+ "additonalPeriod": 0,
+ "includeNames": [
+ "mock_a_service",
+ "mock_b_service",
+ "mock_c_service"
+ ],
+ "excludeNames": [],
+ "includeNamesRegex": "",
+ "excludeNamesRegex": "",
+ "affectedEntities": [
+ {
+ "scope": "SERVICE",
+ "name": "mock_b_service"
+ },
+ {
+ "scope": "SERVICE",
+ "name": "mock_a_service"
+ },
+ {
+ "scope": "SERVICE",
+ "name": "mock_c_service"
+ }
+ ],
+ "tags": [
+ {
+ "key": "level",
+ "value": "WARNING"
+ }
+ ],
+ "hooks": [
+ "webhook.default",
+ "wechat.default"
+ ],
+ "includeMetrics": [
+ "service_resp_time"
+ ],
+ "formattedMessages": [
+ {
+ "mock_b_service": "Response time of service mock_b_service is more than upper baseline in 1 minutes of last 10 minutes."
+ },
+ {
+ "mock_a_service": "Response time of service mock_a_service is more than upper baseline in 1 minutes of last 10 minutes."
+ },
+ {
+ "mock_c_service": "Response time of service mock_c_service is more than upper baseline in 1 minutes of last 10 minutes."
+ }
+ ]
+}
+```
+
+- `additonalPeriod` is the additional period if the expression includes the [increase/rate function](../api/metrics-query-expression.md#trend-operation).
+This additional period is used to enlarge window size for calculating the trend value.
+- `affectedEntities` is the entities that have metrics data and being calculated by the alarm rule.
+- `formattedMessages` is the result message according to the message template and the affected entities.
+
+## Get Alarm Running Context
+
+Return the running context of the alarm rule.
+
+- URL, `http://{core restHost}:{core restPort}/status/alarm/{ruleName}/{entityName}`
+- HTTP GET method.
+
+```json
+{
+ "expression": "sum(service_resp_time > baseline(service_resp_time,upper)) >= 1",
+ "endTime": "2025-02-12T13:39:00.000",
+ "additionalPeriod": 0,
+ "size": 10,
+ "silenceCountdown": 10,
+ "windowValues": [
+ {
+ "index": 0,
+ "metrics": []
+ },
+ {
+ "index": 1,
+ "metrics": []
+ },
+ {
+ "index": 2,
+ "metrics": []
+ },
+ {
+ "index": 3,
+ "metrics": []
+ },
+ {
+ "index": 4,
+ "metrics": []
+ },
+ {
+ "index": 5,
+ "metrics": []
+ },
+ {
+ "index": 6,
+ "metrics": []
+ },
+ {
+ "index": 7,
+ "metrics": [
+ {
+ "timeBucket": 202502121437,
+ "name": "service_resp_time",
+ "value": "6000"
+ }
+ ]
+ },
+ {
+ "index": 8,
+ "metrics": []
+ },
+ {
+ "index": 9,
+ "metrics": []
+ }
+ ],
+ "mqeMetricsSnapshot": {
+ "service_resp_time": "[{\"metric\":{\"labels\":[]},\"values\":[{\"id\":\"202502121430\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121431\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121432\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121433\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121434\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121435\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121436\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121437\",\"doubleValue\":6000.0,\"isEmptyValue\":false},{\"id\":\"202502121438\",\"doubleValue\":0.0,\"isEmptyValue\":true},{\"id\":\"202502121439\",\"doubleValue\":0.0,\"isEmptyValue\":true}]}]",
+ "baseline(service_resp_time,upper)": "[{\"metric\":{\"labels\":[]},\"values\":[{\"id\":\"202502121430\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121431\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121432\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121433\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121434\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121435\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121436\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121437\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121438\",\"doubleValue\":10.0,\"isEmptyValue\":false},{\"id\":\"202502121439\",\"doubleValue\":10.0,\"isEmptyValue\":false}]}]"
+ }
+}
+```
+`size` is the window size. Equal to the `period + additionalPeriod`.
+`silenceCountdown` is the countdown of the silence period. -1 means silence countdown is not running.
+`windowValues` is the original metrics data. The `index` is the index of the window, starting from 0.
+`mqeMetricsSnapshot` is the metrics data in the MQE format. When checking conditions, these data will be calculated according to the expression.
diff --git a/docs/en/status/query_cluster_nodes.md b/docs/en/status/query_cluster_nodes.md
new file mode 100644
index 000000000000..4e700f6e0db8
--- /dev/null
+++ b/docs/en/status/query_cluster_nodes.md
@@ -0,0 +1,39 @@
+# Get Node List in the Cluster
+
+The OAP cluster is a set of OAP servers that work together to provide a scalable and reliable service. The OAP cluster
+supports [various cluster coordinator](../setup/backend/backend-cluster.md) to manage the cluster membership and the
+communication.
+This API provides capability to query the node list in the cluster from every OAP node perspective. If the cluster
+coordinator doesn't work properly, the node list may be incomplete or incorrect. So, we recommend you to check the
+node list when set up a cluster.
+
+This API is used to get the unified and effective TTL configurations.
+
+- URL, `http://{core restHost}:{core restPort}/status/cluster/nodes`
+- HTTP GET method.
+
+```json
+{
+ "nodes": [
+ {
+ "host": "10.0.12.23",
+ "port": 11800,
+ "self": true
+ },
+ {
+ "host": "10.0.12.25",
+ "port": 11800,
+ "self": false
+ },
+ {
+ "host": "10.0.12.37",
+ "port": 11800,
+ "self": false
+ }
+ ]
+}
+```
+
+The `nodes` list all the nodes in the cluster. The size of the list should be exactly same as your cluster setup.
+The `host` and `port` are the address of the OAP node, which are used for OAP nodes communicating with each other. The
+`self` is a flag to indicate whether the node is the current node, others are remote nodes.
diff --git a/docs/en/status/query_ttl_setup.md b/docs/en/status/query_ttl_setup.md
new file mode 100644
index 000000000000..f5fadd700229
--- /dev/null
+++ b/docs/en/status/query_ttl_setup.md
@@ -0,0 +1,79 @@
+# Get Effective TTL Configurations
+
+Time To Live (TTL) mechanism has different behaviors according to different storage implementations. By default, the
+core module provides two TTL configurations: [`recordDataTTL` and `metricsDataTTL`](../setup/backend/ttl.md).
+But some storage implementations could override these settings and provide its own TTL configurations, for example,
+BanyanDB provides its native TTL mechanism to support [progressive TTL](../banyandb/ttl.md) feature and [Data Lifecycle Stages(Hot/Warm/Cold)](../banyandb/stages.md) feature.
+
+
+This API is used to get the unified and effective TTL configurations.
+- URL, `http://{core restHost}:{core restPort}/status/config/ttl`
+- HTTP GET method.
+
+```shell
+> curl -X GET "http://127.0.0.1:12800/status/config/ttl"
+# Metrics TTL includes the definition of the TTL of the metrics-ish data in the storage,
+# Metrics TTL includes the definition of the TTL of the metrics-ish data in the storage,
+# e.g.
+# 1. The metadata of the service, instance, endpoint, topology map, etc.
+# 2. Generated metrics data from OAL and MAL engines.
+# 3. Banyandb storage provides Data Lifecycle Stages(Hot/Warm/Cold).
+#
+# TTLs for each granularity metrics are listed separately.
+#
+# Cover hot and warm data for BanyanDB.
+metrics.minute=7
+metrics.hour=15
+metrics.day=15
+# Cold data, '-1' represents no cold stage data.
+metrics.minute.cold=-1
+metrics.hour.cold=-1
+metrics.day.cold=-1
+
+# Records TTL includes the definition of the TTL of the records data in the storage,
+# Records include traces, logs, sampled slow SQL statements, HTTP requests(by Rover), alarms, etc.
+# Super dataset of records are traces and logs, which volume should be much larger.
+#
+# Cover hot and warm data for BanyanDB.
+records.normal=3
+records.trace=10
+records.zipkinTrace=3
+records.log=3
+records.browserErrorLog=3
+# Cold data, '-1' represents no cold stage data.
+records.normal.cold=-1
+records.trace.cold=30
+records.zipkinTrace.cold=-1
+records.log.cold=-1
+records.browserErrorLog.cold=-1
+```
+
+This API also provides the response in JSON format, which is more friendly for programmatic usage.
+
+```shell
+> curl -X GET "http://127.0.0.1:12800/status/config/ttl" \
+ -H "Accept: application/json"
+
+{
+ "metrics": {
+ "minute": 7,
+ "hour": 15,
+ "day": 15,
+ "coldMinute": -1,
+ "coldHour": -1,
+ "coldDay": -1
+ },
+ "records": {
+ "normal": 3,
+ "trace": 10,
+ "zipkinTrace": 3,
+ "log": 3,
+ "browserErrorLog": 3,
+ "coldNormal": -1,
+ "coldTrace": 30,
+ "coldZipkinTrace": -1,
+ "coldLog": -1,
+ "coldBrowserErrorLog": -1
+ }
+}
+```
diff --git a/docs/en/status/status_apis.md b/docs/en/status/status_apis.md
new file mode 100644
index 000000000000..67e144fae091
--- /dev/null
+++ b/docs/en/status/status_apis.md
@@ -0,0 +1,34 @@
+# Status APIs
+
+Status APIs are a set of APIs that allow you to get the status of the OAP status and measurements of queries.
+They are useful for monitoring the health of the OAP server and to diagnose and troubleshoot issues caused by
+configurations and performance bottlenecks.
+
+Since v10, we begin to add status APIs to help users to understand the status of the OAP server, besides looking the raw
+logs and self-observability solutions.
+
+- [Dump Effective Initial Configurations API](../debugging/config_dump.md)
+- [Tracing Query Execution APIs](../debugging/query-tracing.md)
+- [Get Effective TTL Configurations API](query_ttl_setup.md)
+- [Query Cluster Nodes API](query_cluster_nodes.md)
+- [Get Alarm Runtime Status API](query_alarm_runtime_status.md)
+
+If you have a proposal about new status API, please don't hesitate
+to [create a discussion](https://github.com/apache/skywalking/discussions/new?category=ideas).
+The basic principles for a status API are
+
+1. It should be useful for users to understand the status of the OAP server or the reason of the performance behavior,
+ rather than a function feature.
+2. It should be on-demand and not impact the performance of the OAP server too much, especially in the production
+ environment.
+3. HTTP APIs are preferred unless there is a special reason to use other.
+
+## Disable Status APIs
+
+By default, this service is open for helping users to debug and diagnose. If you want to disable it, you need to disable
+the whole `status-query` module through setting `selector=-`.
+
+```yaml
+status-query:
+ selector: ${SW_STATUS_QUERY:default}
+```
diff --git a/docs/en/swip/SWIP-1.md b/docs/en/swip/SWIP-1.md
new file mode 100644
index 000000000000..568375f34ca5
--- /dev/null
+++ b/docs/en/swip/SWIP-1.md
@@ -0,0 +1,216 @@
+# Create and detect Service Hierarchy Relationship
+
+## Motivation
+
+Service relationship is one of the most important parts of collaborating data in the APM. Service Map is supported for
+years from tracing to trace analysis. But still due to the means of the probs, a service could be detected from multiple
+methods, which is the same service in multiple
+layers. [v9 proposal](https://github.com/apache/skywalking/discussions/8241) mentioned the concept of the layer.
+Through this proposal, we plan to establish a kernel-level concept to connect services detected in different layers.
+
+## Architecture Graph
+
+There is no significant architecture-level change.
+
+## Propose Changes
+
+The data sources of SkyWalking APM have covered traditional agent installed service, VMs, cloud infra, k8s, etc.
+
+For example, a Java service is built in a docker image and is going to be deployed in a k8s cluster, with a sidecar
+injected due to service mesh managed. The following services would be able to detect cross-layers
+
+1. Java service, detected as Java agent installed.
+2. A pod of k8s service is detected, due to k8s layer monitoring.
+3. Side car perspective service is detected.
+4. VM Linux monitoring for a general process, as the container of Java service is deployed on this specific k8s node.
+5. Virtual databases, caches, and queues conjectured by agents, and also monitored through k8s monitoring, even traffic
+ monitored by service mesh.
+
+All these services have logic connections or are identical from a physical perspective, but currently, they may be just
+similar on name(s), no further metadata connection.
+
+By those, we have a chance to move one step ahead to connect the dots of the whole infrastructure. This means, for the
+first time, we are going to establish the connections among services detected from various layers.
+
+**In the v10, I am proposing a new concept `Service Hierarchy`.** Service Hierarchy defines the relationships of
+existing services in various layers. With more kinds of agent tech involved(such as eBPF) and deployment tools(such as
+operator and agent injector), we could inject relative service/instance metadata and try to build the connections,
+including,
+
+- Agent injector injects the pod ID into the system env, then Java agent could report the relationship through system
+ properties.
+- Rover(eBPF agent) reveals its next iteration forward k8s monitoring rather than profiling. And add the capabilities to
+ establish connections among k8s pods and service mesh srv.
+
+Meanwhile, as usual with the new major version change, I would expect UI side changes as well. UI should have flexible
+capabilities to show hierarchy services from the service view and topology view. Also, we could consider a deeper view
+of the instance part as well.
+
+## Imported Dependencies libs and their licenses.
+
+No new library is planned to be added to the codebase.
+
+## Compatibility
+
+About the **protocol**, there should be no breaking changes, but enhancements only. New query protocols(
+service-hierarchy and instance-hierarchy) are considered to be added, some new fields should be added on things like
+topology query and instance dependencies to list relative services/instances from other layers directly rather than an
+extra query.
+
+About the data structure, due to the new data concept is going to be created, service hierarchy relative data models are
+going to be added. If the user is using Elasticsearch and BanyanDB, this should be compatible, they just need to
+re-run `init-mode` OAP to extend the existing models. But for SQL database users(MySQL, PostgreSQL), this could require
+new tables.
+
+### GraphQL query protocol
+New query protocol `hierarchy.graphqls` is going to be added.
+```graphql
+type HierarchyRelatedService {
+ # The related service ID.
+ id: ID!
+ # The literal name of the #id.
+ name: String!
+ # The related service's Layer name.
+ layer: String!
+ normal: Boolean!
+}
+
+type HierarchyRelatedInstance {
+ # The related instance ID.
+ id: ID!
+ # The literal name of the #id. Instance Name.
+ name: String!
+ # Service id
+ serviceId: ID!
+ # The literal name of the #serviceId.
+ serviceName: String!
+ # The service's Layer name.
+ # Service could have multiple layers, this is the layer of the service that the instance belongs to.
+ layer: String!
+ normal: Boolean!
+}
+
+type HierarchyServiceRelation {
+ upperService: HierarchyRelatedService!
+ lowerService: HierarchyRelatedService!
+}
+
+type HierarchyInstanceRelation {
+ upperInstance: HierarchyRelatedInstance!
+ lowerInstance: HierarchyRelatedInstance!
+}
+
+type ServiceHierarchy {
+ relations: [HierarchyServiceRelation!]!
+}
+
+type InstanceHierarchy {
+ relations: [HierarchyInstanceRelation!]!
+}
+
+type LayerLevel {
+ # The layer name.
+ layer: String!
+ # The layer level.
+ # The level of the upper service should greater than the level of the lower service.
+ level: Int!
+}
+
+extend type Query {
+ # Query the service hierarchy, based on the given service. Will recursively return all related layers services in the hierarchy.
+ getServiceHierarchy(serviceId: ID!, layer: String!): ServiceHierarchy!
+ # Query the instance hierarchy, based on the given instance. Will return all direct related layers instances in the hierarchy, no recursive.
+ getInstanceHierarchy(instanceId: ID!, layer: String!): InstanceHierarchy!
+ # List layer hierarchy levels. The layer levels are defined in the `hierarchy-definition.yml`.
+ listLayerLevels: [LayerLevel!]!
+}
+```
+
+## New data models
+- service_hierarchy_relation
+
+ | Column name | Data type | Description |
+ |-----------------------|-----------|-------------------------------------------------------------|
+ | id | String | serviceId.servicelayer-relatedServiceId.relatedServiceLayer |
+ | service_id | String | upper service id |
+ | service_layer | int | upper service layer value |
+ | related_service_id | String | lower service id |
+ | related_service_layer | int | lower service layer value |
+ | time_bucket | long | |
+
+- instance_hierarchy_relation
+
+ | Column name | Data type | Description |
+ |-----------------------|-----------|--------------------------------------------------------------|
+ | id | String | instanceId.servicelayer-relateInstanceId.relatedServiceLayer |
+ | instance_id | String | upper instance id |
+ | service_layer | int | upper service layer value |
+ | related_instance_id | String | lower instance id |
+ | related_service_layer | int | lower service layer value |
+ | time_bucket | long | |
+
+## Internal APIs
+Internal APIs should be exposed in the Core module to support building the hierarchy relationship.
+```java
+public void toServiceHierarchyRelation(String upperServiceName, Layer upperServiceLayer, String lowerServiceName, Layer lowerServiceLayer);
+public void toInstanceHierarchyRelation(String upperInstanceName, String upperServiceName, Layer upperServiceLayer, String lowerInstanceName, String lowerServiceName, Layer lowerServiceLayer);
+```
+
+## Hierarchy Definition
+All layers hierarchy relations are defined in the `hierarchy-definition.yml` file.
+OAP will check the hierarchy relations before building and use the matching rules to auto match the relations. Here is an example:
+
+```yaml
+# Define the hierarchy of service layers, the layers under the specific layer are related lower of the layer.
+# The relation could have a matching rule for auto matching, which are defined in the `auto-matching-rules` section.
+# All the layers are defined in the file `org.apache.skywalking.oap.server.core.analysis.Layers.java`.
+
+hierarchy:
+ MESH:
+ MESH_DP: name
+ K8S_SERVICE: short-name
+
+ MESH_DP:
+ K8S_SERVICE: short-name
+
+ GENERAL:
+ K8S_SERVICE: lower-short-name-remove-ns
+
+ MYSQL:
+ K8S_SERVICE: ~
+
+ VIRTUAL_DATABASE:
+ MYSQL: ~
+
+# Use Groovy script to define the matching rules, the input parameters are the upper service(u) and the lower service(l) and the return value is a boolean.
+# which are used to match the relation between the upper service(u) and the lower service(l) on the different layers.
+auto-matching-rules:
+ # the name of the upper service is equal to the name of the lower service
+ name: "{ (u, l) -> u.name == l.name }"
+ # the short name of the upper service is equal to the short name of the lower service
+ short-name: "{ (u, l) -> u.shortName == l.shortName }"
+ # remove the namespace from the lower service short name
+ lower-short-name-remove-ns: "{ (u, l) -> u.shortName == l.shortName.substring(0, l.shortName.lastIndexOf('.')) }"
+
+# The hierarchy level of the service layer, the level is used to define the order of the service layer for UI presentation,
+# The level of the upper service should greater than the level of the lower service in `hierarchy` section.
+layer-levels:
+ MESH: 3
+ GENERAL: 3
+ VIRTUAL_DATABASE: 3
+ MYSQL: 2
+ MESH_DP: 1
+ K8S_SERVICE: 0
+```
+
+## General usage docs
+
+This proposal doesn't impact the end user in any way of using SkyWalking. The remarkable change will be in the UI. On
+the service dashboard and topology map, the user should be able to see the hierarchy relationship, which means other
+services in other layers are logically the same as the current one. UI would provide the link to jump to the relative
+service's dashboard.
+
+## No Goal
+
+This proposal doesn't cover all the logic about how to detect the service hierarchy structure. All those should be in a
+separate SWIP.
diff --git a/docs/en/swip/SWIP-2.md b/docs/en/swip/SWIP-2.md
new file mode 100644
index 000000000000..e993c7666a54
--- /dev/null
+++ b/docs/en/swip/SWIP-2.md
@@ -0,0 +1,123 @@
+# Collecting and Gathering Kubernetes Monitoring Data
+
+## Motivation
+SkyWalking has provided an access log collector based on the Agent layer and Service Mesh layer,
+and can generate corresponding topology maps and metrics based on the data. However, the Kubernetes Layer still lacks
+corresponding access log collector and analysis work.
+
+This proposal is dedicated to collecting and analyzing network access logs in Kubernetes.
+
+## Architecture Graph
+There is no significant architecture-level change. Still using the Rover project to collect data and report it to
+SkyWalking OAP using the gRPC protocol.
+
+## Propose Changes
+
+Based on the content in Motivation, if we want to ignore the application types(different program languages) and
+only monitor network logs, using eBPF is a good choice. It mainly reflects in the following aspects:
+
+1. Non-intrusive: When monitoring network access logs with eBPF, the application do not need to make any changes to be monitored.
+2. Language-unrestricted: Regardless of which programming language is used in the application, network data will ultimately be accessed through [Linux Syscalls](https://linasm.sourceforge.net/docs/syscalls/network.php). Therefore, we can monitor network data by attaching eBPF to the syscalls layer, thus ignoring programming languages.
+3. Kernel interception: Since eBPF can attach to the kernel methods, it can obtain the execution status of each packet at L2-L4 layers and generate more detailed metrics.
+
+Based on these reasons and collected data, they can be implemented in SkyWalking Rover and collected and monitored based on the following steps:
+
+1. Monitor the network execution status of all processes in Kubernetes when the Rover system starts.
+2. Periodically report data content via [gRPC protocol](https://github.com/apache/skywalking-data-collect-protocol/blob/master/ebpf/accesslog.proto) to SkyWalking OAP.
+3. SkyWalking OAP parses network access logs and generates corresponding network topology, metrics, etc.
+
+### Limitation
+
+For content that uses TLS for data transmission, Rover will detect whether the current language uses libraries
+such as [OpenSSL](https://www.openssl.org/). If it is used, it will asynchronously intercept relevant OpenSSL methods
+when the process starts to perceive the original data content.
+
+However, this approach is not feasible for Java because Java does not use the OpenSSL library but performs encryption/decryption
+through Java code. Currently, eBPF cannot intercept Java method calls. Therefore, it results in an inability to perceive
+the TLS data protocol in Java.
+
+#### Service with Istio sidecar scenario
+
+If the Service is deployed in Istio sidecar, it will still monitor each process.
+If the Service is a Java service and uses TLS, it can analyze the relevant traffic generated in the sidecar (envoy).
+
+## Imported Dependencies libs and their licenses.
+
+No new library is planned to be added to the codebase.
+
+## Compatibility
+
+About the **protocol**, there should be no breaking changes, but enhancements only:
+
+1. `Rover`: adding a new gRPC data collection protocol for reporting the [access logs](https://github.com/apache/skywalking-data-collect-protocol/blob/master/ebpf/accesslog.proto).
+2. `OAP`: It should have no protocol updates. The existing query protocols are already sufficient for querying Kubernetes topology and metric data.
+
+### Data Generation
+
+#### Entity
+
+* service_traffic
+
+| column | data type | value description |
+|------------|-----------|-------------------------|
+| name | string | kubernetes service name |
+| short_name | string | same with name |
+| service_id | string | base64(name).1 |
+| group | string | empty string |
+| layer | string | KUBERNETES |
+
+* instance_traffic
+
+| column | data type | value description |
+|------------|-----------|------------------------------------------------|
+| service_id | string | base64(service_name).1 |
+| name | string | pod name |
+| last_ping | long | last access log message timestamp(millisecond) |
+| properties | json | empty string |
+
+* endpoint_traffic
+
+| column | data type | value description |
+|------------|-----------|---------------------------------------------|
+| service_id | string | base64(service_name).1 |
+| name | string | access log endpoint name(for HTTP1, is URI) |
+
+#### Entity Relation
+
+All entity information is built on connections. If the target address is remote, the name will be resolved in the following order:
+
+1. If it is a pod IP, it will be resolved as pod information.
+2. If it is a service IP, it will be resolved as service information.
+3. If neither exists, only pod information will be displayed.
+
+Different entities have different displays for remote addresses. Please refer to the following table.
+
+| table name | remote info(display by following order) |
+|-------------------|-----------------------------------------|
+| service_relation | service name, remote IP address |
+| instance_relation | pod name, remote IP address |
+
+**NOTICE**: If it is the internal data interaction within the pod, such as exchanging data between services and sidecar (envoy),
+no corresponding traffic will be generated. We only generate and interact with external pods.
+
+##### Limitation
+
+If the service IP is used to send requests to the upstream, we will use eBPF to perceive the real target PodIP by
+perceiving relevant [conntrack records](https://en.wikipedia.org/wiki/Netfilter#Connection_tracking).
+
+However, if conntrack technology is not used, it is difficult to perceive the real target IP address.
+In this case, instance relation data of this kind will be **dropped,** but we will mark all discarded relationship
+generation counts through a metric for better understanding of the situation.
+
+#### Metrics
+
+Integrate the data into the OAL system and generate corresponding metrics through predefined data combined with OAL statements.
+
+## General usage docs
+
+This proposal will only add a module to Rover that explains the configuration of access logs, and changes in the Kubernetes module on the UI.
+
+In the Kubernetes UI, users can see the following additions:
+1. Topology: A topology diagram showing the calling relationships between services, instances, and processes.
+2. Entity Metrics: Metric data for services, instances, and processes.
+3. Call Relationship Metrics: Metrics for call relationships between different entities.
diff --git a/docs/en/swip/SWIP-3.md b/docs/en/swip/SWIP-3.md
new file mode 100644
index 000000000000..b5d302989041
--- /dev/null
+++ b/docs/en/swip/SWIP-3.md
@@ -0,0 +1,65 @@
+# Support RocketMQ Monitoring
+## Motivation
+RocketMQ is a cloud native messaging and streaming platform, making it simple to build event-driven applications. Now that Skywalking can monitor OpenTelemetry metrics, I want to add RocketMQ monitoring via the OpenTelemetry Collector, which fetches metrics from the RocketMQ Exporter
+
+## Architecture Graph
+There is no significant architecture-level change.
+
+## Proposed Changes
+```rocketmq-exporter``` collects metrics from RocketMQ and transport the data to OpenTelemetry collector, using SkyWalking openTelemetry receiver to receive these metrics。
+Provide cluster, broker, and topic dimensions monitoring.
+
+### RocketMQ Cluster Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------|------------|-------------------------------------------------------------|---------------------------------------------------------------------------|------------------|
+| Messages Produced Today | Count | meter_rocketmq_cluster_messages_produced_today | The number of cluster messages produced today. | RocketMQ Exporter |
+| Messages Consumed Today | Count | meter_rocketmq_cluster_messages_consumed_today | The number of cluster messages consumed today. | RocketMQ Exporter |
+| Total Producer Tps | Msg/sec | meter_rocketmq_cluster_total_producer_tps | The number of messages produced per second. | RocketMQ Exporter |
+| Total Consume Tps | Msg/sec | meter_rocketmq_cluster_total_consumer_tps | The number of messages consumed per second. | RocketMQ Exporter |
+| Producer Message Size | Bytes/sec | meter_rocketmq_cluster_producer_message_size | The max size of a message produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Bytes/sec | meter_rocketmq_cluster_consumer_message_size | The max size of the consumed message per second. | RocketMQ Exporter |
+| Messages Produced Until Yesterday | Count | meter_rocketmq_cluster_messages_produced_until_yesterday | The total number of messages put until 12 o'clock last night. | RocketMQ Exporter |
+| Messages Consumed Until Yesterday | Count | meter_rocketmq_cluster_messages_consumed_until_yesterday | The total number of messages read until 12 o'clock last night. | RocketMQ Exporter |
+| Max Consumer Latency | ms | meter_rocketmq_cluster_max_consumer_latency | The max number of consumer latency. | RocketMQ Exporter |
+| Max CommitLog Disk Ratio | % | meter_rocketmq_cluster_max_commitLog_disk_ratio | The max utilization ratio of the commit log disk. | RocketMQ Exporter |
+| CommitLog Disk Ratio | % | meter_rocketmq_cluster_commitLog_disk_ratio | The utilization ratio of the commit log disk per broker IP. | RocketMQ Exporter |
+| Pull ThreadPool Queue Head Wait Time | ms | meter_rocketmq_cluster_pull_threadPool_queue_head_wait_time | The wait time in milliseconds for pulling threadPool queue per broker IP. | RocketMQ Exporter |
+| Send ThreadPool Queue Head Wait Time | ms | meter_rocketmq_cluster_send_threadPool_queue_head_wait_time | The wait time in milliseconds for sending threadPool queue per broker IP. | RocketMQ Exporter |
+| Topic Count | Count | meter_rocketmq_cluster_topic_count | The number of topics that received messages from the producer. | RocketMQ Exporter |
+| Broker Count | Count | meter_rocketmq_cluster_broker_count | The number of brokers that received messages from the producer. | RocketMQ Exporter |
+
+### RocketMQ Broker Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|----------------------------------------------------|-------------------|
+| Produce TPS | Msg/sec | meter_rocketmq_broker_produce_tps | The number of broker produces messages per second. | RocketMQ Exporter |
+| Consume QPS | Msg/sec | meter_rocketmq_broker_consume_qps | The number of broker consumes messages per second. | RocketMQ Exporter |
+| Producer Message Size | Bytes/sec | meter_rocketmq_broker_producer_message_size | The max size of the messages produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Bytes/sec | meter_rocketmq_broker_consumer_message_size | The max size of the messages consumed per second. | RocketMQ Exporter |
+
+### RocketMQ Topic Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|---------------------------|-----------|------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------|
+| Max Producer Message Size | Byte | meter_rocketmq_topic_max_producer_message_size | The maximum number of messages produced. | RocketMQ Exporter |
+| Max Consumer Message Size | Byte | meter_rocketmq_topic_max_consumer_message_size | The maximum number of messages consumed. | RocketMQ Exporter |
+| Consumer Latency | ms | meter_rocketmq_topic_consumer_latency | Consumption delay time of a consumer group. | RocketMQ Exporter |
+| Producer Tps | Msg/sec | meter_rocketmq_topic_producer_tps | The number of messages produced per second. | RocketMQ Exporter |
+| Consumer Group Tps | Msg/sec | meter_rocketmq_topic_consumer_group_tps | The number of messages consumed per second per consumer group. | RocketMQ Exporter |
+| Producer Offset | Count | meter_rocketmq_topic_producer_offset | The max progress of a topic's production message. | RocketMQ Exporter |
+| Consumer Group Offset | Count | meter_rocketmq_topic_consumer_group_offset | The max progress of a topic's consumption message per consumer group. | RocketMQ Exporter |
+| Producer Message Size | Byte/sec | meter_rocketmq_topic_producer_message_size | The max size of messages produced per second. | RocketMQ Exporter |
+| Consumer Message Size | Byte/sec | meter_rocketmq_topic_consumer_message_size | The max size of messages consumed per second. | RocketMQ Exporter |
+| Consumer Group_Count | Count | meter_rocketmq_topic_consumer_group_count | The number of consumer groups. | RocketMQ Exporter |
+| Broker Count | Count | meter_rocketmq_topic_broker_count | The number of topics that received messages from the producer. | RocketMQ Exporter |
+
+## Imported Dependencies libs and their licenses.
+No new dependency.
+
+## Compatibility
+no breaking changes.
+
+## General usage docs
+
+This feature is out of the box.
diff --git a/docs/en/swip/SWIP-4.md b/docs/en/swip/SWIP-4.md
new file mode 100644
index 000000000000..6db61f616057
--- /dev/null
+++ b/docs/en/swip/SWIP-4.md
@@ -0,0 +1,57 @@
+# Support available layers of service in the topology.
+
+## Motivation
+
+UI could jump to the service dashboard and query service hierarchy from the topology node.
+For now topology node includes name and ID but without layer, as the service could have multiple layers,
+the limitation is that it is only works on the current layer which the topology represents:
+1. UI could not jump into another layer's dashboard of the service.
+2. UI could not query the service hierarchy from the topology node if the node is not in current layer.
+
+Here are typical use cases:
+should have a chance to jump into another layer's dashboard of the service:
+1. In the mesh topology, mesh(layer MESH) and mesh-dp(layer MESH_DP) share a similar topology, one node will have two layers.
+2. In the mesh topology, agent(layer GENERAL) + virtual database(layer VIRTUAL_DATABASE), the node is in different layers.
+
+Both of these two cases have hybrid layer topology. If we could support that, we could have a better x-layer interaction.
+
+## Architecture Graph
+
+There is no significant architecture-level change.
+
+## Propose Changes
+
+Add the layers info into topology node:
+1. When building the topology node fetch the layers info from the service according to the service id.
+2. Return `layers` info in the `Node` when query the topology.
+
+## Imported Dependencies libs and their licenses.
+
+No new library is planned to be added to the codebase.
+
+## Compatibility
+
+About the **protocol**, there should be no breaking changes, but enhancements only. New field `layers` is going to be added to the
+`Node` in the query protocol `topology.graphqls`.
+
+```graphql
+type Node {
+ # The service ID of the node.
+ id: ID!
+ # The literal name of the #id.
+ name: String!
+ # The type name may be
+ # 1. The service provider/middleware tech, such as: Tomcat, SpringMVC
+ # 2. Conjectural Service, e.g. MySQL, Redis, Kafka
+ type: String
+ # It is a conjecture node or real node, to represent a service or endpoint.
+ isReal: Boolean!
+ # The layers of the service.
+ layers: [String!]!
+}
+```
+
+## General usage docs
+
+This proposal doesn't impact the end user in any way of using SkyWalking. The remarkable change will be in the UI topology map,
+users could jump into the proper layer's service dashboard and query the service hierarchy from the topology node.
diff --git a/docs/en/swip/SWIP-5.md b/docs/en/swip/SWIP-5.md
new file mode 100644
index 000000000000..8943908e822f
--- /dev/null
+++ b/docs/en/swip/SWIP-5.md
@@ -0,0 +1,134 @@
+# Support ClickHouse Monitoring
+
+## Motivation
+
+ClickHouse is a high-performance, column-oriented SQL database management system (DBMS) for online analytical processing (OLAP). It is available as both an [open-source software](https://github.com/ClickHouse/ClickHouse) and a [cloud offering](https://clickhouse.com/cloud).
+
+Now I want to add ClickHouse monitoring via the OpenTelemetry Collector which fetches metrics from it's own HTTP endpoint to expose metrics data for [Prometheus](https://prometheus.io/) (since ClickHouse v20.1.2.4). Clickhouse Exporter used only for old ClickHouse versions, modern versions have embedded prometheus endpoint.
+
+## Architecture Graph
+
+There is no significant architecture-level change.
+
+## Proposed Changes
+
+`ClickHouse` expose own metrics via HTTP endpoint to opentelemetry collector, using skyWalking openTelemetry receiver to fetch these metrics.
+
+The exposed metrics are from the [system.metrics](https://clickhouse.com/docs/en/operations/system-tables/metrics#system_tables-metrics) table / the [system.events](https://clickhouse.com/docs/en/operations/system-tables/events#system_tables-events) table / the [system.asynchronous_metrics](https://clickhouse.com/docs/en/operations/system-tables/asynchronous_metrics#system_tables-asynchronous_metrics) table.
+
+### ClickHouse Instance Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | ---------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | ----------- |
+| CpuUsage | count | meter_clickhouse_instance_cpu_usage | CPU time spent seen by OS per second(according to ClickHouse.system.dashboard.CPU Usage (cores)). | ClickHouse |
+| MemoryUsage | percentage | meter_clickhouse_instance_memory_usage | Total amount of memory (bytes) allocated by the server/ total amount of OS memory. | ClickHouse |
+| MemoryAvailable | percentage | meter_clickhouse_instance_memory_available | Total amount of memory (bytes) available for program / total amount of OS memory. | ClickHouse |
+| Uptime | sec | meter_clickhouse_instance_uptime | The server uptime in seconds. It includes the time spent for server initialization before accepting connections. | ClickHouse |
+| Version | string | meter_clickhouse_instance_version | Version of the server in a single integer number in base-1000. | ClickHouse |
+| FileOpen | count | meter_clickhouse_instance_file_open | Number of files opened. | ClickHouse |
+
+### ClickHouse Network Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------------- | ----- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- | ----------- |
+| TcpConnections | count | meter_clickhouse_instance_tcp_connections
meter_clickhouse_tcp_connections | Number of connections to TCP server. | ClickHouse |
+| MysqlConnections | count | meter_clickhouse_instance_mysql_connections
meter_clickhouse_mysql_connections | Number of client connections using MySQL protocol. | ClickHouse |
+| HttpConnections | count | meter_clickhouse_instance_http_connections
meter_clickhouse_mysql_connections | Number of connections to HTTP server. | ClickHouse |
+| InterserverConnections | count | meter_clickhouse_instance_interserver_connections
meter_clickhouse_interserver_connections | Number of connections from other replicas to fetch parts. | ClickHouse |
+| PostgresqlConnections | count | meter_clickhouse_instance_postgresql_connections
meter_clickhouse_postgresql_connections | Number of client connections using PostgreSQL protocol. | ClickHouse |
+| ReceiveBytes | bytes | meter_clickhouse_instance_network_receive_bytes
meter_clickhouse_network_receive_bytes | Total number of bytes received from network. | ClickHouse |
+| SendBytes | bytes | meter_clickhouse_instance_network_send_bytes
meter_clickhouse_network_send_bytes | Total number of bytes send to network. | ClickHouse |
+
+### ClickHouse Query Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | --------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------- |
+| QueryCount | count | meter_clickhouse_instance_query
meter_clickhouse_query | Number of executing queries. | ClickHouse |
+| SelectQueryCount | count | meter_clickhouse_instance_query_select
meter_clickhouse_query_select | Number of executing queries, but only for SELECT queries. | ClickHouse |
+| InsertQueryCount | count | meter_clickhouse_instance_query_insert
meter_clickhouse_query_insert | Number of executing queries, but only for INSERT queries. | ClickHouse |
+| SelectQueryRate | count/sec | meter_clickhouse_instance_query_select_rate
meter_clickhouse_query_select_rate | Number of SELECT queries per second. | ClickHouse |
+| InsertQueryRate | count/sec | meter_clickhouse_instance_query_insert_rate
meter_clickhouse_query_insert_rate | Number of INSERT queries per second. | ClickHouse |
+| Querytime | microsec | meter_clickhouse_instance_querytime_microseconds
meter_clickhouse_querytime_microseconds | Total time of all queries. | ClickHouse |
+| SelectQuerytime | microsec | meter_clickhouse_instance_querytime_select_microseconds
meter_clickhouse_querytime_select_microseconds | Total time of SELECT queries. | ClickHouse |
+| InsertQuerytime | microsec | meter_clickhouse_instance_querytime_insert_microseconds
meter_clickhouse_querytime_insert_microseconds | Total time of INSERT queries. | ClickHouse |
+| OtherQuerytime | microsec | meter_clickhouse_instance_querytime_other_microseconds
meter_clickhouse_querytime_other_microseconds | Total time of queries that are not SELECT or INSERT. | ClickHouse |
+| QuerySlowCount | count | meter_clickhouse_instance_query_slow
meter_clickhouse_query_slow | Number of reads from a file that were slow. | ClickHouse |
+
+### ClickHouse Insertion Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ------------------ | ----- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| InsertQueryCount | count | meter_clickhouse_instance_query_insert
meter_clickhouse_query_insert | Number of executing queries, but only for INSERT queries. | ClickHouse |
+| InsertedRowCount | count | meter_clickhouse_instance_inserted_rows
meter_clickhouse_inserted_rows | Number of rows INSERTed to all tables. | ClickHouse |
+| InsertedBytes | bytes | meter_clickhouse_instance_inserted_bytes
meter_clickhouse_inserted_bytes | Number of bytes INSERTed to all tables. | ClickHouse |
+| DelayedInsertCount | count | meter_clickhouse_instance_delayed_insert
meter_clickhouse_delayed_insert | Number of times the INSERT of a block to a MergeTree table was throttled due to high number of active data parts for partition. | ClickHouse |
+
+### ClickHouse Replicas Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------- | ----- | ------------------------------------------------------------ | ------------------------------------------------ | ----------- |
+| ReplicatedChecks | count | meter_clickhouse_instance_replicated_checks
meter_clickhouse_replicated_checks | Number of data parts checking for consistency. | ClickHouse |
+| ReplicatedFetch | count | meter_clickhouse_instance_replicated_fetch
meter_clickhouse_replicated_fetch | Number of data parts being fetched from replica. | ClickHouse |
+| ReplicatedSend | count | meter_clickhouse_instance_replicated_send
meter_clickhouse_replicated_send | Number of data parts being sent to replicas. | ClickHouse |
+
+### ClickHouse MergeTree Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ---------------------- | ----- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | ----------- |
+| BackgroundMergeCount | count | meter_clickhouse_instance_background_merge
meter_clickhouse_background_merge | Number of executing background merges. | ClickHouse |
+| MergeRows | count | meter_clickhouse_instance_merge_rows
meter_clickhouse_merge_rows | Rows read for background merges. This is the number of rows before merge. | ClickHouse |
+| MergeUncompressedBytes | bytes | meter_clickhouse_instance_merge_uncompressed_bytes
meter_clickhouse_merge_uncompressed_bytes | Uncompressed bytes (for columns as they stored in memory) that was read for background merges. This is the number before merge. | ClickHouse |
+| MoveCount | count | meter_clickhouse_instance_move
meter_clickhouse_move | Number of currently executing moves. | ClickHouse |
+| PartsActive | Count | meter_clickhouse_instance_parts_active
meter_clickhouse_parts_active | Active data part, used by current and upcoming SELECTs. | ClickHouse |
+| MutationsCount | count | meter_clickhouse_instance_mutations
meter_clickhouse_mutations | Number of mutations (ALTER DELETE/UPDATE). | ClickHouse |
+
+### ClickHouse Kafka Table Engine Supported Metrics
+
+When [table engine](https://clickhouse.com/docs/en/engines/table-engines/integrations/kafka) works
+with [Apache Kafka](http://kafka.apache.org/).
+
+Kafka lets you:
+
+- Publish or subscribe to data flows.
+- Organize fault-tolerant storage.
+- Process streams as they become available.
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ----------------- | ----- | -------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------- |
+| KafkaMessagesRead | count | meter_clickhouse_instance_kafka_messages_read
meter_clickhouse_kafka_messages_read | Number of Kafka messages already processed by ClickHouse. | ClickHouse |
+| KafkaWrites | count | meter_clickhouse_instance_kafka_writes
meter_clickhouse_kafka_writes | Number of writes (inserts) to Kafka tables. | ClickHouse |
+| KafkaConsumers | count | meter_clickhouse_instance_kafka_consumers
meter_clickhouse_kafka_consumers | Number of active Kafka consumers. | ClickHouse |
+| KafkaProducers | count | meter_clickhouse_instance_kafka_producers
meter_clickhouse_kafka_producers | Number of active Kafka producer created. | ClickHouse |
+
+### ClickHouse ZooKeeper Supported Metrics
+
+ClickHouse uses ZooKeeper for storing metadata of replicas when using replicated tables. If replicated tables are not
+used, this section of parameters can be omitted.
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| --------------------- | ----- | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ----------- |
+| ZookeeperSession | count | meter_clickhouse_instance_zookeeper_session
meter_clickhouse_zookeeper_session | Number of sessions (connections) to ZooKeeper. | ClickHouse |
+| ZookeeperWatch | count | meter_clickhouse_instance_zookeeper_watch
meter_clickhouse_zookeeper_watch | Number of watches (event subscriptions) in ZooKeeper. | ClickHouse |
+| ZookeeperBytesSent | bytes | meter_clickhouse_instance_zookeeper_bytes_sent
meter_clickhouse_zookeeper_bytes_sent | Number of bytes send over network while communicating with ZooKeeper. | ClickHouse |
+| ZookeeperBytesReceive | bytes | meter_clickhouse_instance_zookeeper_bytes_received
meter_clickhouse_zookeeper_bytes_received | Number of bytes send over network while communicating with ZooKeeper. | ClickHouse |
+
+### ClickHouse Keeper Supported Metrics
+
+[ClickHouse Keeper](https://clickhouse.com/docs/en/guides/sre/keeper/clickhouse-keeper) provides the coordination system for data replication and distributed DDL queries execution. ClickHouse Keeper is compatible with ZooKeeper.
+
+ClickHouse Keeper can work in embedded mode or standalone cluster mode, the metrics below are for embedded mode.
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+| ------------------------ | ----- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ----------- |
+| KeeperAliveConnections | count | meter_clickhouse_instance_keeper_connections_alive
meter_clickhouse_keeper_connections_alive | Number of alive connections for embedded ClickHouse Keeper. | ClickHouse |
+| KeeperOutstandingRequets | count | meter_clickhouse_instance_keeper_outstanding_requests
meter_clickhouse_keeper_outstanding_requests| Number of outstanding requests for embedded ClickHouse Keeper. | ClickHouse |
+
+## Imported Dependencies libs and their licenses.
+
+No new dependency.
+
+## Compatibility
+
+no breaking changes.
+
+## General usage docs
diff --git a/docs/en/swip/SWIP-6.md b/docs/en/swip/SWIP-6.md
new file mode 100644
index 000000000000..27d7cfd1469f
--- /dev/null
+++ b/docs/en/swip/SWIP-6.md
@@ -0,0 +1,100 @@
+# Support ActiveMQ classic Monitoring
+
+## Motivation
+
+[Apache ActiveMQ Classic](https://activemq.apache.org/components/classic/) is a popular and powerful open source messaging and Integration Patterns server. It supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features.
+
+Now I want to add ActiveMQ Classic monitoring via the [OpenTelemetry Collector](https://opentelemetry.io/docs) which fetches metrics from [jmx prometheus exporter](https://github.com/prometheus/jmx_exporter) run as a Java Agent.
+
+## Architecture Graph
+
+There is no significant architecture-level change.
+
+## Proposed Changes
+
+`Apache ActiveMQ Classic` has extensive support for JMX to allow you to monitor and control the behavior of the broker via the JMX MBeans.
+
+[Jmx prometheus exporter](https://github.com/prometheus/jmx_exporter) collects metrics data from ActiveMQ classic, this exporter is intended to be run as a Java Agent, exposing a HTTP server and serving metrics of the local JVM.
+
+Using openTelemetry receiver to fetch these metrics to SkyWalking OAP server.
+
+### ActiveMQ Cluster Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------|
+| System Load Average | Count | meter_activemq_cluster_system_load_average | The average system load, range:[0, 10000]. | JMX Prometheus Exporter |
+| Thread Count | Count | meter_activemq_cluster_thread_count | Threads currently used by the JVM. | JMX Prometheus Exporter |
+| Init Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_init | The initial amount of heap memory available. | JMX Prometheus Exporter |
+| Committed Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_committed | The memory is guaranteed to be available for the JVM to use. | JMX Prometheus Exporter |
+| Used Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_used | The amount of JVM heap memory currently in use. | JMX Prometheus Exporter |
+| Max Heap Memory Usage | Bytes | meter_activemq_cluster_heap_memory_usage_max | The maximum possible size of the heap memory. | JMX Prometheus Exporter |
+| GC G1 Old Collection Count | Count | meter_activemq_cluster_gc_g1_old_collection_count | The gc count of G1 Old Generation(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Young Collection Count | Count | meter_activemq_cluster_gc_g1_young_collection_count | The gc count of G1 Young Generation(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Old Collection Time | ms | meter_activemq_cluster_gc_g1_old_collection_time | The gc time spent in G1 Old Generation in milliseconds(JDK[9,17]). | JMX Prometheus Exporter |
+| GC G1 Young Collection Time | ms | meter_activemq_cluster_gc_g1_young_collection_time | The gc time spent in G1 Young Generation in milliseconds(JDK[9,17]). | JMX Prometheus Exporter |
+| GC Parallel Old Collection Count | Count | meter_activemq_cluster_gc_parallel_old_collection_count | The gc count of Parallel Old Generation(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Young Collection Count | Count | meter_activemq_cluster_gc_parallel_young_collection_count | The gc count of Parallel Young Generation(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Old Collection Time | ms | meter_activemq_cluster_gc_parallel_old_collection_time | The gc time spent in Parallel Old Generation in milliseconds(JDK[6,8]). | JMX Prometheus Exporter |
+| GC Parallel Young Collection Time | ms | meter_activemq_cluster_gc_parallel_young_collection_time | The gc time spent in Parallel Young Generation in milliseconds(JDK[6,8]). | JMX Prometheus Exporter |
+| Enqueue Rate | Count/s | meter_activemq_cluster_enqueue_rate | Number of messages that have been sent to the cluster per second(JDK[6,8]). | JMX Prometheus Exporter |
+| Dequeue Rate | Count/s | meter_activemq_cluster_dequeue_rate | Number of messages that have been acknowledged or discarded on the cluster per second.| JMX Prometheus Exporter |
+| Dispatch Rate | Count/s | meter_activemq_cluster_dispatch_rate | Number of messages that has been delivered to consumers per second. | JMX Prometheus Exporter |
+| Expired Rate | Count/s | meter_activemq_cluster_expired_rate | Number of messages that have been expired per second. | JMX Prometheus Exporter |
+| Average Enqueue Time | ms | meter_activemq_cluster_average_enqueue_time | The average time a message was held on this cluster. | JMX Prometheus Exporter |
+| Max Enqueue Time | ms | meter_activemq_cluster_max_enqueue_time | The max time a message was held on this cluster. | JMX Prometheus Exporter |
+
+### ActiveMQ Broker Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|-----------|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------- |-------------------------|
+| Uptime | sec | meter_activemq_broker_uptime | Uptime of the broker in day. | JMX Prometheus Exporter |
+| State | | meter_activemq_broker_state | If slave broker 1 else 0. | JMX Prometheus Exporter |
+| Current Connections | Count | meter_activemq_broker_current_connections | The number of clients connected to the broker currently. | JMX Prometheus Exporter |
+| Current Producer Count | Count | meter_activemq_broker_current_producer_count | The number of producers currently attached to the broker. | JMX Prometheus Exporter |
+| Current Consumer Count | Count | meter_activemq_broker_current_consumer_count | The number of consumers consuming messages from the broker. | JMX Prometheus Exporter |
+| Producer Count | Count | meter_activemq_broker_producer_count | Number of message producers active on destinations. | JMX Prometheus Exporter |
+| Consumer Count | Count | meter_activemq_broker_consumer_count | Number of message consumers subscribed to destinations. | JMX Prometheus Exporter |
+| Enqueue Count | Count | meter_activemq_broker_enqueue_count | The total number of messages sent to the broker. | JMX Prometheus Exporter |
+| Dequeue Count | Count | meter_activemq_broker_dequeue_count | The total number of messages the broker has delivered to consumers. | JMX Prometheus Exporter |
+| Enqueue Rate | Count/sec | meter_activemq_broker_enqueue_rate | The total number of messages sent to the broker per second. | JMX Prometheus Exporter |
+| Dequeue Rate | Count/sec | meter_activemq_broker_dequeue_rate | The total number of messages the broker has delivered to consumers per second. | JMX Prometheus Exporter |
+| Memory Percent Usage | % | meter_activemq_broker_memory_percent_usage | Percentage of configured memory used by the broker. | JMX Prometheus Exporter |
+| Memory Usage | Bytes | meter_activemq_broker_memory_percent_usage | Memory used by undelivered messages in bytes. | JMX Prometheus Exporter |
+| Memory Limit | Bytes | meter_activemq_broker_memory_limit | Memory limited used for holding undelivered messages before paging to temporary storage. | JMX Prometheus Exporter |
+| Store Percent Usage | % | meter_activemq_broker_store_percent_usage | Percentage of available disk space used for persistent message storage. | JMX Prometheus Exporter |
+| Store Limit | Bytes | meter_activemq_broker_store_limit | Disk limited used for persistent messages before producers are blocked. | JMX Prometheus Exporter |
+| Temp Percent Usage | Bytes | meter_activemq_broker_temp_percent_usage | Percentage of available disk space used for non-persistent message storage. | JMX Prometheus Exporter |
+| Temp Limit | Bytes | meter_activemq_broker_temp_limit | Disk limited used for non-persistent messages and temporary data before producers are blocked. | JMX Prometheus Exporter |
+| Average Message Size | Bytes | meter_activemq_broker_average_message_size | Average message size on this broker. | JMX Prometheus Exporter |
+| Max Message Size | Bytes | meter_activemq_broker_max_message_size | Max message size on this broker. | JMX Prometheus Exporter |
+| Queue Size | Count | meter_activemq_broker_queue_size | Number of messages on this broker that have been dispatched but not acknowledged. | JMX Prometheus Exporter |
+
+### ActiveMQ Destination Supported Metrics
+
+| Monitoring Panel |Unit | Metric Name | Description | Data Source |
+|--------------------------------------------|------------|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------------------|
+| Producer Count | Count | meter_activemq_destination_producer_count | Number of producers attached to this destination. | JMX Prometheus Exporter |
+| Consumer Count | Count | meter_activemq_destination_consumer_count | Number of consumers subscribed to this destination. | JMX Prometheus Exporter |
+| Topic Consumer Count | Count | meter_activemq_destination_topic_consumer_count | Number of consumers subscribed to the topics. | JMX Prometheus Exporter |
+| Queue Size | Count | meter_activemq_destination_queue_size | The number of messages that have not been acknowledged by a consumer. | JMX Prometheus Exporter |
+| Memory Usage | Bytes | meter_activemq_destination_memory_usage | Memory used by undelivered messages in bytes. | JMX Prometheus Exporter |
+| Memory Percent Usage | % | meter_activemq_destination_memory_percent_usage | Percentage of configured memory used by the destination. | JMX Prometheus Exporter |
+| Enqueue Count | Count | meter_activemq_destination_enqueue_count | The number of messages sent to the destination. | JMX Prometheus Exporter |
+| Dequeue Count | Count | meter_activemq_destination_dequeue_count | The number of messages the destination has delivered to consumers. | JMX Prometheus Exporter |
+| Average Enqueue Time | ms | meter_activemq_destination_average_enqueue_time | The average time a message was held on this destination. | JMX Prometheus Exporter |
+| Max Enqueue Time | ms | meter_activemq_destination_max_enqueue_time | The max time a message was held on this destination. | JMX Prometheus Exporter |
+| Dispatch Count | Count | meter_activemq_destination_dispatch_count | Number of messages that has been delivered to consumers. | JMX Prometheus Exporter |
+| Expired Count | Count | meter_activemq_destination_expired_count | Number of messages that have been expired. | JMX Prometheus Exporter |
+| Inflight Count | Count | meter_activemq_destination_inflight_count | Number of messages that have been dispatched to but not acknowledged by consumers. | JMX Prometheus Exporter |
+| Average Message Size | Bytes | meter_activemq_destination_average_message_size | Average message size on this destination. | JMX Prometheus Exporter |
+| Max Message Size | Bytes | meter_activemq_destination_max_message_size | Max message size on this destination. | JMX Prometheus Exporter |
+
+## Imported Dependencies libs and their licenses.
+
+No new dependency.
+
+## Compatibility
+
+no breaking changes.
+
+## General usage docs
diff --git a/docs/en/swip/SWIP-8.md b/docs/en/swip/SWIP-8.md
new file mode 100644
index 000000000000..2973e451e936
--- /dev/null
+++ b/docs/en/swip/SWIP-8.md
@@ -0,0 +1,61 @@
+# Support Kong Monitoring
+
+## Motivation
+
+[**Kong**](https://github.com/Kong/kong) or **Kong API Gateway** is a cloud-native, platform-agnostic, scalable API Gateway
+distinguished for its high performance and extensibility via plugins. Now I want to add Kong monitoring via the OpenTelemetry Collector,
+which fetches metrics from it's own HTTP endpoint to expose metrics data for [Prometheus](https://prometheus.io/).
+
+## Architecture Graph
+
+There is no significant architecture-level change.
+
+## Proposed Changes
+
+1. Kong expose its own [metrics](https://docs.konghq.com/hub/kong-inc/prometheus/) via HTTP endpoint to opentelemetry collector, OpenTelemetry Collector fetches metrics from it and pushes metrics to SkyWalking OTEL Receiver via OpenTelemetry exporter.
+2. The SkyWalking OAP Server parses the expression with MAL to filter/calculate/aggregate and store the results.
+3. These metrics can be displayed via the SkyWalking UI, and the metrics can be customized for display on the UI dashboard.
+
+### Kong Request Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------|
+| Bandwidth | bytes | meter_kong_service_http_bandwidth
meter_kong_instance_http_bandwidth
meter_kong_endpoint_http_bandwidth | Total bandwidth (ingress/egress) throughput | Kong |
+| HTTP Status | count | meter_kong_service_http_status
meter_kong_instance_http_status
meter_kong_endpoint_http_status | HTTP status codes per consumer/service/route in Kong | Kong |
+| HTTP Request | count | meter_kong_service_http_requests
meter_kong_instance_http_requests | Total number of requests | Kong |
+
+### Kong Database Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|-------------------------------------------------------------------------------------|-------------------------------------------|-------------|
+| DB | count | meter_kong_service_datastore_reachable
meter_kong_instance_datastore_reachable | Datastore reachable from Kong | Kong |
+| DB | bytes | meter_kong_instance_shared_dict_bytes | Allocated slabs in bytes in a shared_dict | Kong |
+| DB | bytes | meter_kong_instance_shared_dict_total_bytes | Total capacity in bytes of a shared_dict | Kong |
+| DB | bytes | meter_kong_instance_memory_workers_lua_vms_bytes | Allocated bytes in worker Lua VM | Kong |
+
+### Kong Latencies Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------|
+| Latency | ms | meter_kong_service_kong_latency
meter_kong_instance_kong_latency
meter_kong_endpoint_kong_latency | Latency added by Kong and enabled plugins for each service/route in Kong | Kong |
+| Latency | ms | meter_kong_service_request_latency
meter_kong_instance_request_latency
meter_kong_endpoint_request_latency | Total latency incurred during requests for each service/route in Kong | Kong |
+| Latency | ms | meter_kong_service_upstream_latency
meter_kong_instance_upstream_latency
meter_kong_endpoint_upstream_latency | Latency added by upstream response for each service/route in Kong | Kong |
+
+
+### Kong Nginx Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|------------------|-------|---------------------------------------------------------------------------------------------|---------------------------------------|-------------|
+| Nginx | count | meter_kong_service_nginx_metric_errors_total | Number of nginx-lua-prometheus errors | Kong |
+| Nginx | count | meter_kong_service_nginx_connections_total
meter_kong_instance_nginx_connections_total | Number of connections by subsystem | Kong |
+| Nginx | count | meter_kong_service_nginx_timers
meter_kong_instance_nginx_timers | Number of Nginx timers | Kong |
+
+## Imported Dependencies libs and their licenses.
+
+No new dependency.
+
+## Compatibility
+
+no breaking changes.
+
+## General usage docs
diff --git a/docs/en/swip/SWIP-9.md b/docs/en/swip/SWIP-9.md
new file mode 100644
index 000000000000..cf1719805ac4
--- /dev/null
+++ b/docs/en/swip/SWIP-9.md
@@ -0,0 +1,94 @@
+# Support Flink Monitoring
+## Motivation
+Apache Flink is a framework and distributed processing engine for stateful computations over unbounded and bounded data streams. Now that Skywalking can monitor OpenTelemetry metrics, I want to add Flink monitoring via the OpenTelemetry Collector, which fetches metrics from its own Http Endpoint
+to expose metrics data for Prometheus.
+
+## Architecture Graph
+There is no significant architecture-level change.
+
+## Proposed Changes
+Flink expose its metrics via HTTP endpoint to OpenTelemetry collector, using SkyWalking openTelemetry receiver to receive these metrics。
+Provide cluster, instance, and endpoint dimensions monitoring.
+
+### Flink Cluster Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-------------------------------|-------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------|
+| Running Jobs | Count | meter_flink_jobManager_running_job_number | The number of running jobs. | Flink JobManager |
+| TaskManagers | Count | meter_flink_jobManager_taskManagers_registered_number | The number of taskManagers. | Flink JobManager |
+| JVM CPU Load | % | meter_flink_jobManager_jvm_cpu_load | The number of the jobManager JVM CPU load. | Flink JobManager |
+| JVM thread count | Count | meter_flink_jobManager_jvm_thread_count | The total number of the jobManager JVM live threads. | Flink JobManager |
+| JVM Memory Heap Used | MB | meter_flink_jobManager_jvm_memory_heap_used | The amount of the jobManager JVM memory heap used. | Flink JobManager |
+| JVM Memory NonHeap Used | MB | meter_flink_jobManager_jvm_memory_NonHeap_used | The amount of the jobManager JVM nonHeap memory used. | Flink JobManager |
+| Task Managers Slots Total | Count | meter_flink_jobManager_taskManagers_slots_total | The number of total slots. | Flink JobManager |
+| Task Managers Slots Available | Count | meter_flink_jobManager_taskManagers_slots_available | The number of available slots. | Flink JobManager |
+| JVM CPU Time | ms | meter_flink_jobManager_jvm_cpu_time | The jobManager CPU time used by the JVM increase per minute. | Flink JobManager |
+| JVM Memory Heap Available | MB | meter_flink_jobManager_jvm_memory_heap_available | The amount of the jobManager available JVM memory Heap. | Flink JobManager |
+| JVM Memory NoHeap Available | MB | meter_flink_jobManager_jvm_memory_nonHeap_available | The amount of the jobManager available JVM memory noHeap. | Flink JobManager |
+| JVM Memory Metaspace Used | MB | meter_flink_jobManager_jvm_memory_metaspace_used | The amount of the jobManager Used JVM metaspace memory. | Flink JobManager |
+| JVM Metaspace Available | MB | meter_flink_jobManager_jvm_memory_metaspace_available | The amount of the jobManager available JVM Metaspace Memory. | Flink JobManager |
+| JVM G1 Young Generation Count | Count | meter_flink_jobManager_jvm_g1_young_generation_count | The incremental number of the jobManager JVM G1 young generation count per minute. | Flink JobManager |
+| JVM G1 Old Generation Count | Count | meter_flink_jobManager_jvm_g1_old_generation_count | The incremental number of the jobManager JVM G1 old generation count per minute. | Flink JobManager |
+| JVM G1 Young Generation Time | Count | meter_flink_jobManager_jvm_g1_young_generation_time | The incremental time of the jobManager JVM G1 young generation per minute. | Flink JobManager |
+| JVM G1 Old Generation Time | ms | meter_flink_jobManager_jvm_g1_old_generation_time | The incremental time of JVM G1 old generation increase per minute. | Flink JobManager |
+| JVM G1 Old Generation Count | Count | meter_flink_jobManager_jvm_all_garbageCollector_count | The incremental number of the jobManager JVM all garbageCollector count per minute. | Flink JobManager |
+| JVM All GarbageCollector Time | ms | meter_flink_jobManager_jvm_all_garbageCollector_time | The incremental time spent performing garbage collection for the given (or all) collector for the jobManager per minute. | Flink JobManager |
+
+
+### Flink taskManager Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|----------------------------------|---------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| JVM CPU Load | % | meter_flink_taskManager_jvm_cpu_load | The number of the JVM CPU load. | Flink TaskManager |
+| JVM Thread Count | Count | meter_flink_taskManager_jvm_thread_count | The total number of JVM live threads. | Flink TaskManager |
+| JVM Memory Heap Used | MB | meter_flink_taskManager_jvm_memory_heap_used | The amount of JVM memory heap used. | Flink TaskManager |
+| JVM Memory NonHeap Used | MB | meter_flink_taskManager_jvm_memory_nonHeap_used | The amount of JVM nonHeap memory used. | Flink TaskManager |
+| JVM CPU Time | ms | meter_flink_taskManager_jvm_cpu_time | The CPU time used by the JVM increase per minute. | Flink TaskManager |
+| JVM Memory Heap Available | MB | meter_flink_taskManager_jvm_memory_heap_available | The amount of available JVM memory Heap. | Flink TaskManager |
+| JVM Memory NonHeap Available | MB | meter_flink_taskManager_jvm_memory_nonHeap_available | The amount of available JVM memory nonHeap. | Flink TaskManager |
+| JVM Memory Metaspace Used | MB | meter_flink_taskManager_jvm_memory_metaspace_used | The amount of Used JVM metaspace memory. | Flink TaskManager |
+| JVM Metaspace Available | MB | meter_flink_taskManager_jvm_memory_metaspace_available | The amount of Available JVM Metaspace Memory. | Flink TaskManager |
+| NumRecordsIn | Count | meter_flink_taskManager_numRecordsIn | The incremental number of records this task has received per minute. | Flink TaskManager |
+| NumRecordsOut | Count | meter_flink_taskManager_numRecordsOut | The incremental number of records this task has emitted per minute. | Flink TaskManager |
+| NumBytesInPerSecond | Bytes/s | meter_flink_taskManager_numBytesInPerSecond | The number of bytes received per second. | Flink TaskManager |
+| NumBytesOutPerSecond | Bytes/s | meter_flink_taskManager_numBytesOutPerSecond | The number of bytes this task emits per second. | Flink TaskManager |
+| Netty UsedMemory | MB | meter_flink_taskManager_netty_usedMemory | The amount of used netty memory. | Flink TaskManager |
+| Netty AvailableMemory | MB | meter_flink_taskManager_netty_availableMemory | The amount of available netty memory. | Flink TaskManager |
+| IsBackPressured | Count | meter_flink_taskManager_isBackPressured | Whether the task is back-pressured. | Flink TaskManager |
+| InPoolUsage | % | meter_flink_taskManager_inPoolUsage | An estimate of the input buffers usage. (ignores LocalInputChannels). | Flink TaskManager |
+| OutPoolUsage | % | meter_flink_taskManager_outPoolUsage | An estimate of the output buffers usage. The pool usage can be > 100% if overdraft buffers are being used. | Flink TaskManager |
+| SoftBackPressuredTimeMsPerSecond | ms | meter_flink_taskManager_softBackPressuredTimeMsPerSecond | The time this task is softly back pressured per second.Softly back pressured task will be still responsive and capable of for example triggering unaligned checkpoints. | Flink TaskManager |
+| HardBackPressuredTimeMsPerSecond | ms | meter_flink_taskManager_hardBackPressuredTimeMsPerSecond | The time this task is back pressured in a hard way per second.During hard back pressured task is completely blocked and unresponsive preventing for example unaligned checkpoints from triggering. | Flink TaskManager |
+| IdleTimeMsPerSecond | ms | meter_flink_taskManager_idleTimeMsPerSecond | The time this task is idle (has no data to process) per second. Idle time excludes back pressured time, so if the task is back pressured it is not idle. | Flink TaskManager |
+| BusyTimeMsPerSecond | ms | meter_flink_taskManager_busyTimeMsPerSecond | The time this task is busy (neither idle nor back pressured) per second. Can be NaN, if the value could not be calculated. | Flink TaskManager |
+
+
+### Flink Job Supported Metrics
+
+| Monitoring Panel | Unit | Metric Name | Description | Data Source |
+|-------------------------|---------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| Job RunningTime | min | meter_flink_job_runningTime | The job running time. | Flink JobManager |
+| Job Restart Number | Count | meter_flink_job_restart_number | The number of job restart. | Flink JobManager |
+| Job RestartingTime | min | meter_flink_job_restartingTime | The job restarting Time. | Flink JobManager |
+| Job CancellingTime | min | meter_flink_job_cancellingTime | The job cancelling time. | Flink JobManager |
+| Checkpoints Total | Count | meter_flink_job_checkpoints_total | The total number of checkpoints. | Flink JobManager |
+| Checkpoints Failed | Count | meter_flink_job_checkpoints_failed | The number of failed checkpoints. | Flink JobManager |
+| Checkpoints Completed | Count | meter_flink_job_checkpoints_completed | The number of completed checkpoints. | Flink JobManager |
+| Checkpoints InProgress | Count | meter_flink_job_checkpoints_inProgress | The number of inProgress checkpoints. | Flink JobManager |
+| CurrentEmitEventTimeLag | ms | meter_flink_job_currentEmitEventTimeLag | The latency between a data record's event time and its emission time from the source. | Flink TaskManager |
+| NumRecordsIn | Count | meter_flink_job_numRecordsIn | The total number of records this operator/task has received. | Flink TaskManager |
+| NumRecordsOut | Count | meter_flink_job_numRecordsOut | The total number of records this operator/task has emitted. | Flink TaskManager |
+| NumBytesInPerSecond | Bytes/s | meter_flink_job_numBytesInPerSecond | The number of bytes this task received per second. | Flink TaskManager |
+| NumBytesOutPerSecond | Bytes/s | meter_flink_job_numBytesOutPerSecond | The number of bytes this task emits per second. | Flink TaskManager |
+| LastCheckpointSize | Bytes | meter_flink_job_lastCheckpointSize | The checkPointed size of the last checkpoint (in bytes), this metric could be different from lastCheckpointFullSize if incremental checkpoint or changelog is enabled. | Flink JobManager |
+| LastCheckpointDuration | ms | meter_flink_job_lastCheckpointDuration | The time it took to complete the last checkpoint. | Flink JobManager |
+
+## Imported Dependencies libs and their licenses.
+No new dependency.
+
+## Compatibility
+no breaking changes.
+
+## General usage docs
+
+This feature is out of the box.
diff --git a/docs/en/swip/readme.md b/docs/en/swip/readme.md
new file mode 100644
index 000000000000..0cf9f8cc43da
--- /dev/null
+++ b/docs/en/swip/readme.md
@@ -0,0 +1,82 @@
+# SWIP - SkyWalking Improvement Proposal
+
+SWIP - SkyWalking Improvement Proposal, is an official document to propose a new feature and/or feature improvement,
+which
+are relative to end users and developers.
+
+SkyWalking has been very stable since v9.x. We are getting over the rapid changing stage. The core concepts, protocols for
+reporting telemetry and query, 3rd party integration, and the streaming process kernel are very stable. From now(2024) on,
+SkyWalking community would focus more on improvement and controllable improvement. All major changes should be evaluated
+more seriously, and try as good as possible to avoid incompatible breaking changes.
+
+## What is considered a major change?
+
+The catalogs of a major change are listed as follows
+
+- New Feature. A feature doesn't exist for the latest version.
+- Any change of the network Interfaces, especially
+ for [Query Protocol](https://github.com/apache/skywalking-query-protocol),
+ [Data Collect Protocols](https://github.com/apache/skywalking-data-collect-protocol),
+ Dynamic Configuration APIs, Exporting APIs, AI pipeline APIs.
+- Any change of storage structure.
+
+**Q: Is Agent side feature or change considered a SWIP?**
+
+A: Right now, SWIP targets OAP and UI side changes. All agent side changes are pending on the reviews from the
+committers of those agents.
+
+## SWIP Template
+
+The purpose of this template should not be considered a hard requirement. The major purpose of SWIP is helping the PMC
+and community member to understand the proposal better.
+
+```markdown
+# Title: SWIP-1234 xxxx
+
+## Motivation
+The description of new feature or improvement.
+
+## Architecture Graph
+Describe the relationship between your new proposal part and existing components.
+
+## Proposed Changes
+State your proposal in detail.
+
+## Imported Dependencies libs and their licenses.
+
+## Compatibility
+Whether breaking configuration, storage structure, or protocols.
+
+## General usage docs
+This doesn't have to be a final version, but helps the reviewers to understand how to use this new feature.
+```
+
+## SWIP Process
+
+Here is the process for starting a SWIP.
+
+1. Start a SWIP discussion at [GitHub Discussion Page](https://github.com/apache/skywalking/discussions/categories/swip)
+ with title `[DISCUSS] xxxx`.
+2. Fill in the sections as described above in `SWIP Template`.
+3. At least one SkyWalking committer commented on the discussion to show interest in adopting it.
+4. This committer could update this page to grant a **SWIP ID**, and update the title to `[SWIP-ID NO.] [DISCUSS] xxxx`.
+5. All further discussion could happen on the discussion page.
+6. Once the consensus is made by enough committer supporters, and/or through a mail list vote, this SWIP should be
+ added [here](./) as `SWIP-ID NO.md` and listed in the below as `Known SWIPs`.
+
+All accepted and proposed SWIPs can be found in [here](https://github.com/apache/skywalking/discussions/categories/swip).
+
+## Known SWIPs
+
+Next SWIP Number: 10
+
+### Accepted SWIPs
+
+- [SWIP-9 Support Flink Monitoring](SWIP-9.md)
+- [SWIP-8 Support Kong Monitoring](SWIP-8.md)
+- [SWIP-6 Support ActiveMQ Monitoring](SWIP-6.md)
+- [SWIP-5 Support ClickHouse Monitoring](SWIP-5.md)
+- [SWIP-4 Support available layers of service in the topology](SWIP-4.md)
+- [SWIP-3 Support RocketMQ Monitoring](SWIP-3.md)
+- [SWIP-2 Collecting and Gathering Kubernetes Monitoring Data](SWIP-2.md)
+- [SWIP-1 Create and detect Service Hierarchy Relationship](SWIP-1.md)
diff --git a/docs/en/ui/README.md b/docs/en/ui/README.md
new file mode 100644
index 000000000000..c7ece22940e7
--- /dev/null
+++ b/docs/en/ui/README.md
@@ -0,0 +1,118 @@
+# Introduction to UI
+
+The SkyWalking official UI provides the default and powerful visualization capabilities for SkyWalking to observe full-stack applications.
+
+
+
+The left side menu lists all available supported stacks with default dashboards.
+
+Follow the `Official Dashboards` menu to explore all default dashboards on their ways to monitor different tech stacks.
+
+## Sidebar Menu and Marketplace
+
+All available feature menu items are only listed in the marketplace(since 9.6.0). They are only visible on the Sidebar Menu when there are relative services
+being observed by various supported observation agents, such as installed language agents, service mesh platform, OTEL integration.
+
+The menu items defined in `ui-initialized-templates/menu.yaml` are the universal marketplace for all default-supported integration.
+The menu definition supports one and two levels items. The leaf menu item should have the `layer` for navigation.
+
+```yaml
+menus:
+ - name: GeneralService
+ icon: general_service
+ menus:
+ - name: Services
+ layer: GENERAL
+ - name: VisualDatabase
+ layer: VIRTUAL_DATABASE
+ - name: VisualCache
+ layer: VIRTUAL_CACHE
+ - name: VisualMQ
+ layer: VIRTUAL_MQ
+ ....
+- name: SelfObservability
+ icon: self_observability
+ menus:
+ - name: SkyWalkingServer
+ layer: SO11Y_OAP
+ - name: Satellite
+ layer: SO11Y_SATELLITE
+```
+
+
+The menu items would automatically pop up on the left after short period of time that at least one service was observed.
+For more details, please refer to the "uiMenuRefreshInterval" configuration item in the [backend settings](../setup/backend/configuration-vocabulary.md)
+
+## Custom Dashboard
+
+Besides official dashboards, **Dashboards** provide customization capabilities to end-users to add new tabs/pages/widgets, and
+flexibility to re-config the dashboard on your own preference.
+
+The dashboard has two key attributes, **Layer** and **Entity Type**. Learn these two concepts first before you begin any
+customization. Also, trace, metrics, and log analysis are relative to OAL, MAL, and LAL engines in the SkyWalking kernel. It would help if you
+learned them first, too.
+
+Service and All entity type dashboard could be set as root(`set this to root`), which means this dashboard would be used
+as the entrance of its Layer. If you have multiple root dashboards, UI will choose one randomly (We don't recommend doing
+so).
+
+**Notice, dashboard editable is disabled on release; set system env(**SW_ENABLE_UPDATE_UI_TEMPLATE=true**) to activate
+them.** Before you save the edited dashboard, it is just stored in memory. Closing a tab would **LOSE** the change permanently.
+
+A new dashboard should be added through `New Dashboard` in the `Dashboards` menu.
+Meanwhile, there are two ways to edit an existing dashboard.
+1. `Dashboard List` in the `Dashboard` menu provides edit/delete/set-as-root features to manage existing dashboards.
+2. In every dashboard page, click the right top `V` toggle, and turn to `E`(representing **Edit**) mode.
+
+## Widget
+
+A dashboard consists of various widget. In the `Edit` mode, widgets could be added/moved/removed/edit according to the Layer.(Every widget declares its suitable layer.)
+
+The widget provides the ability to visualize the metrics, generated through [OAL](../concepts-and-designs/mal.md), [MAL](../concepts-and-designs/mal.md), or [LAL](../concepts-and-designs/lal.md) scripts.
+
+
+
+### Metric Query Expression
+Metric Query Expression provides the ability to query metrics from the backend.
+The query expression could be a simple metric name, or a complex expression with multiple functions.
+Read [Metrics Query Expression(MQE) Syntax doc](../api/metrics-query-expression.md) to learn more about the syntax.
+
+### Graph styles
+
+Setup font size, unit, value mappings etc. to provide better visualization.
+
+### Widget options
+
+
+
+Define the following properties of the widget:
+1. **Name**: The name of the widget, which used to [associate with other widget](#association-options) in the dashboard.
+2. **Title**: The title name of the widget.
+3. **Tooltip Content**: Additional explanation of the widget.
+
+### Association Options
+
+
+
+Widget provides the ability to associate with other widgets to show axis pointer with tips for the same time point, in order to help users to understand
+the connectivity among metrics.
+
+### Widget Static Link
+On the right top of every widget on the dashboard, there is a `Generate Link` option, which could generate a static
+link to represent this widget.
+By using this link, users could share this widget, or integrate it into any 3rd party iFrame to build a
+network operations center(NOC) dashboard on the wall easily.
+About this link, there are several customizable options
+1. `Lock Query Duration`. Set the query duration manually. It is OFF by default.
+2. `Auto Fresh` option is ON with 6s query period and last 30 mins time range. Query period and range are customizable.
+
+## Settings
+
+Settings provide language, server time zone, and auto-fresh options. These settings are stored in the browser's local storage. Unless you clear them manually, those will not change.
+
+## FAQ
+
+### Login and Authentication
+
+SkyWalking doesn't provide login and authentication as usual for years. If you need, a lot of Gateway solutions have
+provides well-established solutions, such as the Nginx ecosystem.
diff --git a/docs/menu.yml b/docs/menu.yml
new file mode 100644
index 000000000000..79e32693040a
--- /dev/null
+++ b/docs/menu.yml
@@ -0,0 +1,492 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+
+catalog:
+ - name: "Welcome"
+ path: "/readme"
+ - name: "Concepts and Designs"
+ catalog:
+ - name: "Overview and Core concepts"
+ path: "/en/concepts-and-designs/overview"
+ - name: "Project Goals"
+ path: "/en/concepts-and-designs/project-goals"
+ - name: "Agents"
+ catalog:
+ - name: "Introduction"
+ path: "/en/concepts-and-designs/probe-introduction"
+ - name: "Service Auto Instrument Agent"
+ path: "/en/concepts-and-designs/service-agent"
+ - name: "Manual Instrument SDK"
+ path: "/en/concepts-and-designs/manual-sdk"
+ - name: "Service Hierarchy"
+ path: "/en/concepts-and-designs/service-hierarchy"
+ - name: "Setup"
+ catalog:
+ - name: "Quick Start"
+ catalog:
+ - name: "Introduction"
+ path: "/en/setup/backend/backend-setup"
+ - name: "Run with Docker"
+ path: "/en/setup/backend/backend-docker"
+ - name: "Run with Kubernetes"
+ path: "/en/setup/backend/backend-k8s"
+ - name: "Find out-of-box Features in Marketplace"
+ path: "/en/setup/backend/marketplace"
+ - name: "Marketplace"
+ catalog:
+ - name: "General Service"
+ catalog:
+ - name: "Server Agents"
+ path: "/en/setup/service-agent/server-agents"
+ - name: "Compatibility"
+ path: "/en/setup/service-agent/agent-compatibility"
+ - name: "Virtual Database"
+ path: "/en/setup/service-agent/virtual-database"
+ - name: "Virtual Cache"
+ path: "/en/setup/service-agent/virtual-cache"
+ - name: "Virtual MQ"
+ path: "/en/setup/service-agent/virtual-mq"
+ - name: "Service Mesh"
+ catalog:
+ - name: "Observe Service Mesh through Access Log Service (ALS)"
+ path: "/en/setup/envoy/als_setting"
+ - name: "Observe Service Mesh through Zipkin traces"
+ path: "/en/setup/zipkin/tracing"
+ - name: "Observe Control Plane (Istio)"
+ path: "/en/setup/istio/readme"
+ - name: "Observe Data Plane (Envoy)"
+ path: "/en/setup/envoy/metrics_service_setting"
+ - name: "Profile Pod's Network"
+ path: "/en/setup/backend/backend-k8s-network-monitoring"
+ - name: "Kubernetes"
+ catalog:
+ - name: "Observe Kubernetes"
+ path: "/en/setup/backend/backend-k8s-monitoring"
+ - name: "kube-state-metrics + cAdvisor"
+ path: "/en/setup/backend/backend-k8s-monitoring-metrics-cadvisor"
+ - name: "Rover"
+ path: "/en/setup/backend/backend-k8s-monitoring-rover"
+ - name: "Profile Pod's Network"
+ path: "/en/setup/backend/backend-k8s-network-monitoring"
+ - name: "Cilium"
+ path: "/en/setup/backend/backend-k8s-monitoring-cilium"
+ - name: "Infrastructure Monitoring"
+ catalog:
+ - name: "Linux Monitoring"
+ path: "/en/setup/backend/backend-vm-monitoring"
+ - name: "Windows Monitoring"
+ path: "/en/setup/backend/backend-win-monitoring"
+ - name: "AWS Cloud Monitoring"
+ catalog:
+ - name: "EKS Monitoring"
+ path: "/en/setup/backend/backend-aws-eks-monitoring"
+ - name: "S3 Monitoring"
+ path: "/en/setup/backend/backend-aws-s3-monitoring"
+ - name: "AWS DynamoDB"
+ path: "/en/setup/backend/backend-aws-dynamodb-monitoring"
+ - name: "AWS API Gateway"
+ path: "/en/setup/backend/backend-aws-api-gateway-monitoring"
+ - name: "Browser Monitoring"
+ path: "/en/setup/service-agent/browser-agent"
+ - name: "Gateway Monitoring"
+ catalog:
+ - name: "Nginx Monitoring"
+ path: "/en/setup/backend/backend-nginx-monitoring"
+ - name: "APISIX Monitoring"
+ path: "/en/setup/backend/backend-apisix-monitoring"
+ - name: "AWS API Gateway"
+ path: "/en/setup/backend/backend-aws-api-gateway-monitoring"
+ - name: "Kong Monitoring"
+ path: "/en/setup/backend/backend-kong-monitoring"
+ - name: "Database Monitoring"
+ catalog:
+ - name: "MySQL/MariaDB Server"
+ path: "/en/setup/backend/backend-mysql-monitoring"
+ - name: "PostgreSQL Server"
+ path: "/en/setup/backend/backend-postgresql-monitoring"
+ - name: "AWS DynamoDB"
+ path: "/en/setup/backend/backend-aws-dynamodb-monitoring"
+ - name: "Redis"
+ path: "/en/setup/backend/backend-redis-monitoring"
+ - name: "Elasticsearch"
+ path: "/en/setup/backend/backend-elasticsearch-monitoring"
+ - name: "MongoDB"
+ path: "/en/setup/backend/backend-mongodb-monitoring"
+ - name: "BookKeeper"
+ path: "/en/setup/backend/backend-bookkeeper-monitoring"
+ - name: "ClickHouse"
+ path: "/en/setup/backend/backend-clickhouse-monitoring"
+ - name: "MQ Monitoring"
+ catalog:
+ - name: "RabbitMQ"
+ path: "/en/setup/backend/backend-rabbitmq-monitoring"
+ - name: "Kafka"
+ path: "/en/setup/backend/backend-kafka-monitoring"
+ - name: "Pulsar"
+ path: "/en/setup/backend/backend-pulsar-monitoring"
+ - name: "RocketMQ"
+ path: "/en/setup/backend/backend-rocketmq-monitoring"
+ - name: "ActiveMQ"
+ path: "/en/setup/backend/backend-activemq-monitoring"
+ - name: "Data Processing Engine"
+ catalog:
+ - name: "Flink"
+ path: "/en/setup/backend/backend-flink-monitoring"
+ - name: "Self Observability"
+ catalog:
+ - name: "OAP self telemetry"
+ path: "/en/setup/backend/dashboards-so11y"
+ - name: "Satellite self telemetry"
+ path: "/en/setup/backend/dashboards-so11y-satellite"
+ - name: "SkyWalking Java Agent self telemetry"
+ path: "/en/setup/backend/dashboards-so11y-java-agent"
+ - name: "SkyWalking Go Agent self telemetry"
+ path: "/en/setup/backend/dashboards-so11y-go-agent"
+ - name: "Configuration Vocabulary"
+ path: "/en/setup/backend/configuration-vocabulary"
+ - name: "Advanced Setup"
+ catalog:
+ - name: "Service Grouping"
+ path: "/en/setup/backend/service-auto-grouping"
+ - name: "Overriding Settings"
+ path: "/en/setup/backend/backend-setting-override"
+ - name: "IP And Port Setting"
+ path: "/en/setup/backend/backend-ip-port"
+ - name: "Backend Init Mode Startup"
+ path: "/en/setup/backend/backend-init-mode"
+ - name: "Cluster Management"
+ path: "/en/setup/backend/backend-cluster"
+ - name: "Choose Storage"
+ catalog:
+ - name: "Introduction"
+ path: "/en/setup/backend/backend-storage"
+ - name: "BanyanDB"
+ path: "/en/setup/backend/storages/banyandb"
+ - name: "MySQL"
+ path: "/en/setup/backend/storages/mysql"
+ - name: "PostgreSQL"
+ path: "/en/setup/backend/storages/postgresql"
+ - name: "Elasticsearch & OpenSearch"
+ path: "/en/setup/backend/storages/elasticsearch"
+ - name: "Setup External Communication Channels"
+ path: "/en/setup/backend/backend-expose"
+ - name: "Kafka Fetcher"
+ path: "/en/setup/backend/kafka-fetcher"
+ - name: "Advanced Deployment Options"
+ path: "/en/setup/backend/advanced-deployment"
+ - name: "Data Lifecycle. Time To Live (TTL)"
+ path: "/en/setup/backend/ttl"
+ - name: "Group Parameterized Endpoints"
+ path: "/en/setup/backend/endpoint-grouping-rules"
+ - name: "Dynamical Logging"
+ path: "/en/setup/backend/dynamical-logging"
+ - name: "Security(SSL/TLS/mTLS)"
+ path: "/en/setup/backend/grpc-security"
+ - name: "Setup Load Balancer"
+ path: "/en/setup/backend/backend-load-balancer"
+ - name: "OAP Self Observability Telemetry"
+ path: "/en/setup/backend/backend-telemetry"
+ - name: "OAP Health Check"
+ path: "/en/setup/backend/backend-health-check"
+ - name: "Circuit Breaking"
+ path: "/en/setup/backend/circuit-breaking"
+ - name: "BanyanDB Exclusive Setup"
+ catalog:
+ - name: "Progressive TTL"
+ path: "/en/banyandb/ttl"
+ - name: "Data Lifecycle Stages(Hot/Warm/Cold)"
+ path: "/en/banyandb/stages"
+ - name: "Tracing"
+ catalog:
+ - name: "Trace Sampling"
+ path: "/en/setup/backend/trace-sampling"
+ - name: "Detect Slow Database Statement"
+ path: "/en/setup/backend/slow-db-statement"
+ - name: "Detect Slow Cache Command"
+ path: "/en/setup/backend/slow-cache-command"
+ - name: "Message Queue Performance"
+ path: "/en/setup/backend/mq"
+ - name: "Uninstrumented Gateways"
+ path: "/en/setup/backend/uninstrumented-gateways"
+ - name: "Zipkin Trace"
+ path: "/en/setup/backend/zipkin-trace"
+ - name: "OpenTelemetry Trace"
+ path: "/en/setup/backend/otlp-trace"
+ - name: "Metrics"
+ catalog:
+ - name: "OAL Scripts"
+ path: "/en/guides/backend-oal-scripts"
+ - name: "OpenTelemetry Metrics"
+ path: "/en/setup/backend/opentelemetry-receiver"
+ - name: "AWS CloudWatch Metrics"
+ path: "/en/setup/backend/aws-firehose-receiver"
+ - name: "Zabbix Metrics"
+ path: "/en/setup/backend/backend-zabbix"
+ - name: "Meter Analysis"
+ path: "/en/setup/backend/backend-meter"
+ - name: "Telegraf Metrics"
+ path: "/en/setup/backend/telegraf-receiver"
+ - name: "Apdex Threshold"
+ path: "/en/setup/backend/apdex-threshold"
+ - name: "Spring MicroMeter Observations Analysis"
+ path: "/en/setup/backend/micrometer-observations"
+ - name: "Alerting"
+ path: "/en/setup/backend/backend-alarm"
+ - name: "Logging"
+ catalog:
+ - name: "Persistent Logging"
+ catalog:
+ - name: "Native Logging from Files"
+ path: "/en/setup/backend/filelog-native"
+ - name: "Native Logging from Agents"
+ path: "/en/setup/backend/log-agent-native"
+ - name: "OpenTelemetry Logging"
+ path: "/en/setup/backend/log-otlp"
+ - name: "Log Analysis"
+ path: "/en/setup/backend/log-analyzer"
+ - name: "On Demand Pod Logs"
+ path: "/en/setup/backend/on-demand-pod-log"
+ - name: "Profiling"
+ catalog:
+ - name: "Tracing Profiling"
+ path: "/en/setup/backend/backend-trace-profiling"
+ - name: "eBPF Profiling"
+ path: "/en/setup/backend/backend-ebpf-profiling"
+ - name: "Continuous Profiling"
+ path: "/en/setup/backend/backend-continuous-profiling"
+ - name: "Java App Profiling"
+ path: "/en/setup/backend/backend-java-app-profiling"
+ - name: "Event"
+ path: "/en/concepts-and-designs/event/"
+ - name: "Extension"
+ catalog:
+ - name: "Exporter"
+ path: "/en/setup/backend/exporter"
+ - name: "Dynamic Configuration"
+ path: "/en/setup/backend/dynamic-config"
+ - name: "AI Pipeline"
+ catalog:
+ - name: "Introduction"
+ path: "/en/setup/ai-pipeline/introduction"
+ - name: "HTTP Restful URI recognition"
+ path: "/en/setup/ai-pipeline/http-restful-uri-pattern"
+ - name: "Metrics Baseline Calculation and Alerting"
+ path: "/en/setup/ai-pipeline/metrics-baseline-integration"
+ - name: "UI Setup"
+ catalog:
+ - name: "Native UI"
+ catalog:
+ - name: "Setup"
+ path: "/en/setup/backend/ui-setup"
+ - name: "Customization"
+ path: "/en/ui/readme"
+ - name: "Grafana UI"
+ path: "/en/setup/backend/ui-grafana"
+ - name: "CLI Setup"
+ path: "https://github.com/apache/skywalking-cli"
+ - name: "Mock Data Generator Setup"
+ path: "/en/setup/backend/backend-data-generator"
+ - name: "APIs"
+ catalog:
+ - name: "Telemetry APIs/Protocols"
+ catalog:
+ - name: "Tracing"
+ catalog:
+ - name: "Spans APIs"
+ path: "/en/api/trace-data-protocol-v3"
+ - name: "Tracing Context Propagation"
+ path: "/en/api/x-process-propagation-headers-v3"
+ - name: "Tracing Correlation Correlation"
+ path: "/en/api/x-process-correlation-headers-v1"
+ - name: "Metrics APIs"
+ catalog:
+ - name: "Meter APIs"
+ path: "/en/api/meter"
+ - name: "Browser Performance APIs"
+ path: "/en/api/browser-protocol"
+ - name: "JVM Metrics APIs"
+ path: "/en/api/jvm-protocol"
+ - name: "Logging"
+ path: "/en/api/log-data-protocol"
+ - name: "Service Instance Properties APIs"
+ path: "/en/api/instance-properties"
+ - name: "Event"
+ path: "/en/api/event"
+ - name: "Profiling"
+ path: "/en/api/profiling-protocol"
+ - name: "Query APIs"
+ catalog:
+ - name: "GraphQL APIs"
+ catalog:
+ - name: "GraphQL APIs"
+ path: "/en/api/query-protocol"
+ - name: "MQE Syntax"
+ path: "/en/api/metrics-query-expression"
+ - name: "Deprecated APIs"
+ path: "/en/api/query-protocol-deprecated"
+ - name: "PromQL APIs"
+ path: "/en/api/promql-service"
+ - name: "LogQL APIs"
+ path: "/en/api/logql-service"
+ - name: "Health Check API"
+ path: "/en/api/health-check"
+ - name: "Status APIs"
+ catalog:
+ - name: "Introduction"
+ path: "/en/status/status_apis"
+ - name: "Dump Effective Initial Configurations"
+ path: "/en/debugging/config_dump"
+ - name: "Tracing Query Execution"
+ path: "/en/debugging/query-tracing"
+ - name: "Get Effective TTL Configurations"
+ path: "/en/status/query_ttl_setup"
+ - name: "Get Node List in the Cluster"
+ path: "/en/status/query_cluster_nodes"
+ - name: "Get Alarm Runtime Status"
+ path: "/en/status/query_alarm_runtime_status"
+ - name: "Customization"
+ catalog:
+ - name: "Overview"
+ path: "/en/concepts-and-designs/backend-overview"
+ - name: "Analysis Traces and Mesh Traffic"
+ path: "/en/concepts-and-designs/oal"
+ - name: "Analysis Metrics and Meters"
+ path: "/en/concepts-and-designs/mal"
+ - name: "Analysis Logs"
+ path: "/en/concepts-and-designs/lal"
+ - name: "Profiling"
+ path: "/en/concepts-and-designs/profiling"
+ - name : "Service Hierarchy Configuration"
+ path: "/en/concepts-and-designs/service-hierarchy-configuration"
+ - name: "Metrics Attributes"
+ path: "/en/concepts-and-designs/metrics-additional-attributes"
+ - name: "Security Notice"
+ path: "/en/security/readme"
+ - name: "Academy"
+ catalog:
+ - name: "Scaling SkyWalking server automatically in kubernetes"
+ path: "/en/academy/scaling-with-apache-skywalking"
+ - name: "STAM Paper, Streaming Topology Analysis Method"
+ path: "/en/papers/stam"
+ - name: "SDK Profiling to Fix the Blind Spot"
+ path: "/en/concepts-and-designs/sdk-profiling"
+ - name: "eBPF CPU Profiling to pinpoint Service Mesh Critical Performance Impact"
+ path: "/en/concepts-and-designs/ebpf-cpu-profiling"
+ - name: "Diagnose Service Mesh Network Performance with eBPF"
+ path: "/en/academy/diagnose-service-mesh-network-performance-with-ebpf"
+ - name: "FAQs"
+ path: "/en/faq/readme"
+ - name: "Contributing Guides"
+ catalog:
+ - name: "Contact the community"
+ path: "/en/guides/community"
+ - name: "Become A Committer"
+ path: "/en/guides/asf/committer"
+ - name: "Release Guide"
+ path: "/en/guides/how-to-release/"
+ - name: "Compiling Guide"
+ path: "/en/guides/how-to-build"
+ - name: "Contribute"
+ catalog:
+ - name: "Integration Tests"
+ path: "/en/guides/it-guide"
+ - name: "Benchmark Tests"
+ path: "/en/guides/benchmark"
+ - name: "End to End Tests"
+ path: "/en/guides/e2e"
+ - name: "Project Extensions"
+ catalog:
+ - name: "Component Library Settings"
+ path: "/en/guides/component-library-settings"
+ - name: "Extend An OAL Source"
+ path: "/en/guides/source-extension"
+ - name: "Dependencies"
+ catalog:
+ - name: "Project Dependencies Check"
+ path: "/en/guides/dependencies"
+ - name: "Zipkin dependency"
+ path: "/en/guides/how-to-bump-up-zipkin"
+ - name: "I18n"
+ path: "/en/guides/i18n"
+ - name: "SWIP"
+ path: "/en/swip/readme"
+ - name: "Changelog"
+ catalog:
+ - name: "Current Version"
+ path: "/en/changes/changes"
+ - name: "10.x Releases"
+ catalog:
+ - name: "10.2.0"
+ path: "/en/changes/changes-10.2.0"
+ - name: "10.1.0"
+ path: "/en/changes/changes-10.1.0"
+ - name: "10.0.1"
+ path: "/en/changes/changes-10.0.1"
+ - name: "10.0.0"
+ path: "/en/changes/changes-10.0.0"
+ - name: "9.x Releases"
+ catalog:
+ - name: "9.7.0"
+ path: "/en/changes/changes-9.7.0"
+ - name: "9.6.0"
+ path: "/en/changes/changes-9.6.0"
+ - name: "9.5.0"
+ path: "/en/changes/changes-9.5.0"
+ - name: "9.4.0"
+ path: "/en/changes/changes-9.4.0"
+ - name: "9.3.0"
+ path: "/en/changes/changes-9.3.0"
+ - name: "9.2.0"
+ path: "/en/changes/changes-9.2.0"
+ - name: "9.1.0"
+ path: "/en/changes/changes-9.1.0"
+ - name: "9.0.0"
+ path: "/en/changes/changes-9.0.0"
+ - name: "Archived Releases"
+ catalog:
+ - name: "8.9.1"
+ path: "/en/changes/changes-8.9.1"
+ - name: "8.9.0"
+ path: "/en/changes/changes-8.9.0"
+ - name: "8.8.1"
+ path: "/en/changes/changes-8.8.1"
+ - name: "8.8.0"
+ path: "/en/changes/changes-8.8.0"
+ - name: "8.7.0"
+ path: "/en/changes/changes-8.7.0"
+ - name: "8.6.0"
+ path: "/en/changes/changes-8.6.0"
+ - name: "8.5.0"
+ path: "/en/changes/changes-8.5.0"
+ - name: "8.4.0"
+ path: "/en/changes/changes-8.4.0"
+ - name: "8.3.0"
+ path: "/en/changes/changes-8.3.0"
+ - name: "8.2.0"
+ path: "/en/changes/changes-8.2.0"
+ - name: "8.1.0"
+ path: "/en/changes/changes-8.1.0"
+ - name: "8.0.1"
+ path: "/en/changes/changes-8.0.1"
+ - name: "8.0.0"
+ path: "/en/changes/changes-8.0.0"
+ - name: "7.0.0"
+ path: "/en/changes/changes-7.0.0"
+ - name: "6.x"
+ path: "/en/changes/changes-6.x"
+ - name: "5.x"
+ path: "/en/changes/changes-5.x"
diff --git a/lombok.config b/lombok.config
new file mode 100644
index 000000000000..7d97bd9aa922
--- /dev/null
+++ b/lombok.config
@@ -0,0 +1,18 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+lombok.addLombokGeneratedAnnotation = true
diff --git a/mvnw b/mvnw
new file mode 100755
index 000000000000..5643201c7d82
--- /dev/null
+++ b/mvnw
@@ -0,0 +1,316 @@
+#!/bin/sh
+# ----------------------------------------------------------------------------
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+# ----------------------------------------------------------------------------
+
+# ----------------------------------------------------------------------------
+# Maven Start Up Batch script
+#
+# Required ENV vars:
+# ------------------
+# JAVA_HOME - location of a JDK home dir
+#
+# Optional ENV vars
+# -----------------
+# M2_HOME - location of maven2's installed home dir
+# MAVEN_OPTS - parameters passed to the Java VM when running Maven
+# e.g. to debug Maven itself, use
+# set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
+# MAVEN_SKIP_RC - flag to disable loading of mavenrc files
+# ----------------------------------------------------------------------------
+
+if [ -z "$MAVEN_SKIP_RC" ] ; then
+
+ if [ -f /usr/local/etc/mavenrc ] ; then
+ . /usr/local/etc/mavenrc
+ fi
+
+ if [ -f /etc/mavenrc ] ; then
+ . /etc/mavenrc
+ fi
+
+ if [ -f "$HOME/.mavenrc" ] ; then
+ . "$HOME/.mavenrc"
+ fi
+
+fi
+
+# OS specific support. $var _must_ be set to either true or false.
+cygwin=false;
+darwin=false;
+mingw=false
+case "`uname`" in
+ CYGWIN*) cygwin=true ;;
+ MINGW*) mingw=true;;
+ Darwin*) darwin=true
+ # Use /usr/libexec/java_home if available, otherwise fall back to /Library/Java/Home
+ # See https://developer.apple.com/library/mac/qa/qa1170/_index.html
+ if [ -z "$JAVA_HOME" ]; then
+ if [ -x "/usr/libexec/java_home" ]; then
+ export JAVA_HOME="`/usr/libexec/java_home`"
+ else
+ export JAVA_HOME="/Library/Java/Home"
+ fi
+ fi
+ ;;
+esac
+
+if [ -z "$JAVA_HOME" ] ; then
+ if [ -r /etc/gentoo-release ] ; then
+ JAVA_HOME=`java-config --jre-home`
+ fi
+fi
+
+if [ -z "$M2_HOME" ] ; then
+ ## resolve links - $0 may be a link to maven's home
+ PRG="$0"
+
+ # need this for relative symlinks
+ while [ -h "$PRG" ] ; do
+ ls=`ls -ld "$PRG"`
+ link=`expr "$ls" : '.*-> \(.*\)$'`
+ if expr "$link" : '/.*' > /dev/null; then
+ PRG="$link"
+ else
+ PRG="`dirname "$PRG"`/$link"
+ fi
+ done
+
+ saveddir=`pwd`
+
+ M2_HOME=`dirname "$PRG"`/..
+
+ # make it fully qualified
+ M2_HOME=`cd "$M2_HOME" && pwd`
+
+ cd "$saveddir"
+ # echo Using m2 at $M2_HOME
+fi
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$M2_HOME" ] &&
+ M2_HOME=`cygpath --unix "$M2_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+ [ -n "$CLASSPATH" ] &&
+ CLASSPATH=`cygpath --path --unix "$CLASSPATH"`
+fi
+
+# For Mingw, ensure paths are in UNIX format before anything is touched
+if $mingw ; then
+ [ -n "$M2_HOME" ] &&
+ M2_HOME="`(cd "$M2_HOME"; pwd)`"
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME="`(cd "$JAVA_HOME"; pwd)`"
+fi
+
+if [ -z "$JAVA_HOME" ]; then
+ javaExecutable="`which javac`"
+ if [ -n "$javaExecutable" ] && ! [ "`expr \"$javaExecutable\" : '\([^ ]*\)'`" = "no" ]; then
+ # readlink(1) is not available as standard on Solaris 10.
+ readLink=`which readlink`
+ if [ ! `expr "$readLink" : '\([^ ]*\)'` = "no" ]; then
+ if $darwin ; then
+ javaHome="`dirname \"$javaExecutable\"`"
+ javaExecutable="`cd \"$javaHome\" && pwd -P`/javac"
+ else
+ javaExecutable="`readlink -f \"$javaExecutable\"`"
+ fi
+ javaHome="`dirname \"$javaExecutable\"`"
+ javaHome=`expr "$javaHome" : '\(.*\)/bin'`
+ JAVA_HOME="$javaHome"
+ export JAVA_HOME
+ fi
+ fi
+fi
+
+if [ -z "$JAVACMD" ] ; then
+ if [ -n "$JAVA_HOME" ] ; then
+ if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
+ # IBM's JDK on AIX uses strange locations for the executables
+ JAVACMD="$JAVA_HOME/jre/sh/java"
+ else
+ JAVACMD="$JAVA_HOME/bin/java"
+ fi
+ else
+ JAVACMD="`\\unset -f command; \\command -v java`"
+ fi
+fi
+
+if [ ! -x "$JAVACMD" ] ; then
+ echo "Error: JAVA_HOME is not defined correctly." >&2
+ echo " We cannot execute $JAVACMD" >&2
+ exit 1
+fi
+
+if [ -z "$JAVA_HOME" ] ; then
+ echo "Warning: JAVA_HOME environment variable is not set."
+fi
+
+CLASSWORLDS_LAUNCHER=org.codehaus.plexus.classworlds.launcher.Launcher
+
+# traverses directory structure from process work directory to filesystem root
+# first directory with .mvn subdirectory is considered project base directory
+find_maven_basedir() {
+
+ if [ -z "$1" ]
+ then
+ echo "Path not specified to find_maven_basedir"
+ return 1
+ fi
+
+ basedir="$1"
+ wdir="$1"
+ while [ "$wdir" != '/' ] ; do
+ if [ -d "$wdir"/.mvn ] ; then
+ basedir=$wdir
+ break
+ fi
+ # workaround for JBEAP-8937 (on Solaris 10/Sparc)
+ if [ -d "${wdir}" ]; then
+ wdir=`cd "$wdir/.."; pwd`
+ fi
+ # end of workaround
+ done
+ echo "${basedir}"
+}
+
+# concatenates all lines of a file
+concat_lines() {
+ if [ -f "$1" ]; then
+ echo "$(tr -s '\n' ' ' < "$1")"
+ fi
+}
+
+BASE_DIR=`find_maven_basedir "$(pwd)"`
+if [ -z "$BASE_DIR" ]; then
+ exit 1;
+fi
+
+##########################################################################################
+# Extension to allow automatically downloading the maven-wrapper.jar from Maven-central
+# This allows using the maven wrapper in projects that prohibit checking in binary data.
+##########################################################################################
+if [ -r "$BASE_DIR/.mvn/wrapper/maven-wrapper.jar" ]; then
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Found .mvn/wrapper/maven-wrapper.jar"
+ fi
+else
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Couldn't find .mvn/wrapper/maven-wrapper.jar, downloading it ..."
+ fi
+ if [ -n "$MVNW_REPOURL" ]; then
+ jarUrl="$MVNW_REPOURL/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar"
+ else
+ jarUrl="https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar"
+ fi
+ while IFS="=" read key value; do
+ case "$key" in (wrapperUrl) jarUrl="$value"; break ;;
+ esac
+ done < "$BASE_DIR/.mvn/wrapper/maven-wrapper.properties"
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Downloading from: $jarUrl"
+ fi
+ wrapperJarPath="$BASE_DIR/.mvn/wrapper/maven-wrapper.jar"
+ if $cygwin; then
+ wrapperJarPath=`cygpath --path --windows "$wrapperJarPath"`
+ fi
+
+ if command -v wget > /dev/null; then
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Found wget ... using wget"
+ fi
+ if [ -z "$MVNW_USERNAME" ] || [ -z "$MVNW_PASSWORD" ]; then
+ wget "$jarUrl" -O "$wrapperJarPath" || rm -f "$wrapperJarPath"
+ else
+ wget --http-user=$MVNW_USERNAME --http-password=$MVNW_PASSWORD "$jarUrl" -O "$wrapperJarPath" || rm -f "$wrapperJarPath"
+ fi
+ elif command -v curl > /dev/null; then
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Found curl ... using curl"
+ fi
+ if [ -z "$MVNW_USERNAME" ] || [ -z "$MVNW_PASSWORD" ]; then
+ curl -o "$wrapperJarPath" "$jarUrl" -f
+ else
+ curl --user $MVNW_USERNAME:$MVNW_PASSWORD -o "$wrapperJarPath" "$jarUrl" -f
+ fi
+
+ else
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo "Falling back to using Java to download"
+ fi
+ javaClass="$BASE_DIR/.mvn/wrapper/MavenWrapperDownloader.java"
+ # For Cygwin, switch paths to Windows format before running javac
+ if $cygwin; then
+ javaClass=`cygpath --path --windows "$javaClass"`
+ fi
+ if [ -e "$javaClass" ]; then
+ if [ ! -e "$BASE_DIR/.mvn/wrapper/MavenWrapperDownloader.class" ]; then
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo " - Compiling MavenWrapperDownloader.java ..."
+ fi
+ # Compiling the Java class
+ ("$JAVA_HOME/bin/javac" "$javaClass")
+ fi
+ if [ -e "$BASE_DIR/.mvn/wrapper/MavenWrapperDownloader.class" ]; then
+ # Running the downloader
+ if [ "$MVNW_VERBOSE" = true ]; then
+ echo " - Running MavenWrapperDownloader.java ..."
+ fi
+ ("$JAVA_HOME/bin/java" -cp .mvn/wrapper MavenWrapperDownloader "$MAVEN_PROJECTBASEDIR")
+ fi
+ fi
+ fi
+fi
+##########################################################################################
+# End of extension
+##########################################################################################
+
+export MAVEN_PROJECTBASEDIR=${MAVEN_BASEDIR:-"$BASE_DIR"}
+if [ "$MVNW_VERBOSE" = true ]; then
+ echo $MAVEN_PROJECTBASEDIR
+fi
+MAVEN_OPTS="$(concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config") $MAVEN_OPTS"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ [ -n "$M2_HOME" ] &&
+ M2_HOME=`cygpath --path --windows "$M2_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ [ -n "$CLASSPATH" ] &&
+ CLASSPATH=`cygpath --path --windows "$CLASSPATH"`
+ [ -n "$MAVEN_PROJECTBASEDIR" ] &&
+ MAVEN_PROJECTBASEDIR=`cygpath --path --windows "$MAVEN_PROJECTBASEDIR"`
+fi
+
+# Provide a "standardized" way to retrieve the CLI args that will
+# work with both Windows and non-Windows executions.
+MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $@"
+export MAVEN_CMD_LINE_ARGS
+
+WRAPPER_LAUNCHER=org.apache.maven.wrapper.MavenWrapperMain
+
+exec "$JAVACMD" \
+ $MAVEN_OPTS \
+ $MAVEN_DEBUG_OPTS \
+ -classpath "$MAVEN_PROJECTBASEDIR/.mvn/wrapper/maven-wrapper.jar" \
+ "-Dmaven.home=${M2_HOME}" \
+ "-Dmaven.multiModuleProjectDirectory=${MAVEN_PROJECTBASEDIR}" \
+ ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
diff --git a/mvnw.cmd b/mvnw.cmd
new file mode 100644
index 000000000000..23b7079a3d4c
--- /dev/null
+++ b/mvnw.cmd
@@ -0,0 +1,188 @@
+@REM ----------------------------------------------------------------------------
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+@REM
+@REM http://www.apache.org/licenses/LICENSE-2.0
+@REM
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+@REM ----------------------------------------------------------------------------
+
+@REM ----------------------------------------------------------------------------
+@REM Maven Start Up Batch script
+@REM
+@REM Required ENV vars:
+@REM JAVA_HOME - location of a JDK home dir
+@REM
+@REM Optional ENV vars
+@REM M2_HOME - location of maven2's installed home dir
+@REM MAVEN_BATCH_ECHO - set to 'on' to enable the echoing of the batch commands
+@REM MAVEN_BATCH_PAUSE - set to 'on' to wait for a keystroke before ending
+@REM MAVEN_OPTS - parameters passed to the Java VM when running Maven
+@REM e.g. to debug Maven itself, use
+@REM set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
+@REM MAVEN_SKIP_RC - flag to disable loading of mavenrc files
+@REM ----------------------------------------------------------------------------
+
+@REM Begin all REM lines with '@' in case MAVEN_BATCH_ECHO is 'on'
+@echo off
+@REM set title of command window
+title %0
+@REM enable echoing by setting MAVEN_BATCH_ECHO to 'on'
+@if "%MAVEN_BATCH_ECHO%" == "on" echo %MAVEN_BATCH_ECHO%
+
+@REM set %HOME% to equivalent of $HOME
+if "%HOME%" == "" (set "HOME=%HOMEDRIVE%%HOMEPATH%")
+
+@REM Execute a user defined script before this one
+if not "%MAVEN_SKIP_RC%" == "" goto skipRcPre
+@REM check for pre script, once with legacy .bat ending and once with .cmd ending
+if exist "%USERPROFILE%\mavenrc_pre.bat" call "%USERPROFILE%\mavenrc_pre.bat" %*
+if exist "%USERPROFILE%\mavenrc_pre.cmd" call "%USERPROFILE%\mavenrc_pre.cmd" %*
+:skipRcPre
+
+@setlocal
+
+set ERROR_CODE=0
+
+@REM To isolate internal variables from possible post scripts, we use another setlocal
+@setlocal
+
+@REM ==== START VALIDATION ====
+if not "%JAVA_HOME%" == "" goto OkJHome
+
+echo.
+echo Error: JAVA_HOME not found in your environment. >&2
+echo Please set the JAVA_HOME variable in your environment to match the >&2
+echo location of your Java installation. >&2
+echo.
+goto error
+
+:OkJHome
+if exist "%JAVA_HOME%\bin\java.exe" goto init
+
+echo.
+echo Error: JAVA_HOME is set to an invalid directory. >&2
+echo JAVA_HOME = "%JAVA_HOME%" >&2
+echo Please set the JAVA_HOME variable in your environment to match the >&2
+echo location of your Java installation. >&2
+echo.
+goto error
+
+@REM ==== END VALIDATION ====
+
+:init
+
+@REM Find the project base dir, i.e. the directory that contains the folder ".mvn".
+@REM Fallback to current working directory if not found.
+
+set MAVEN_PROJECTBASEDIR=%MAVEN_BASEDIR%
+IF NOT "%MAVEN_PROJECTBASEDIR%"=="" goto endDetectBaseDir
+
+set EXEC_DIR=%CD%
+set WDIR=%EXEC_DIR%
+:findBaseDir
+IF EXIST "%WDIR%"\.mvn goto baseDirFound
+cd ..
+IF "%WDIR%"=="%CD%" goto baseDirNotFound
+set WDIR=%CD%
+goto findBaseDir
+
+:baseDirFound
+set MAVEN_PROJECTBASEDIR=%WDIR%
+cd "%EXEC_DIR%"
+goto endDetectBaseDir
+
+:baseDirNotFound
+set MAVEN_PROJECTBASEDIR=%EXEC_DIR%
+cd "%EXEC_DIR%"
+
+:endDetectBaseDir
+
+IF NOT EXIST "%MAVEN_PROJECTBASEDIR%\.mvn\jvm.config" goto endReadAdditionalConfig
+
+@setlocal EnableExtensions EnableDelayedExpansion
+for /F "usebackq delims=" %%a in ("%MAVEN_PROJECTBASEDIR%\.mvn\jvm.config") do set JVM_CONFIG_MAVEN_PROPS=!JVM_CONFIG_MAVEN_PROPS! %%a
+@endlocal & set JVM_CONFIG_MAVEN_PROPS=%JVM_CONFIG_MAVEN_PROPS%
+
+:endReadAdditionalConfig
+
+SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
+set WRAPPER_JAR="%MAVEN_PROJECTBASEDIR%\.mvn\wrapper\maven-wrapper.jar"
+set WRAPPER_LAUNCHER=org.apache.maven.wrapper.MavenWrapperMain
+
+set DOWNLOAD_URL="https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar"
+
+FOR /F "usebackq tokens=1,2 delims==" %%A IN ("%MAVEN_PROJECTBASEDIR%\.mvn\wrapper\maven-wrapper.properties") DO (
+ IF "%%A"=="wrapperUrl" SET DOWNLOAD_URL=%%B
+)
+
+@REM Extension to allow automatically downloading the maven-wrapper.jar from Maven-central
+@REM This allows using the maven wrapper in projects that prohibit checking in binary data.
+if exist %WRAPPER_JAR% (
+ if "%MVNW_VERBOSE%" == "true" (
+ echo Found %WRAPPER_JAR%
+ )
+) else (
+ if not "%MVNW_REPOURL%" == "" (
+ SET DOWNLOAD_URL="%MVNW_REPOURL%/org/apache/maven/wrapper/maven-wrapper/3.1.0/maven-wrapper-3.1.0.jar"
+ )
+ if "%MVNW_VERBOSE%" == "true" (
+ echo Couldn't find %WRAPPER_JAR%, downloading it ...
+ echo Downloading from: %DOWNLOAD_URL%
+ )
+
+ powershell -Command "&{"^
+ "$webclient = new-object System.Net.WebClient;"^
+ "if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and [string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
+ "$webclient.Credentials = new-object System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
+ "}"^
+ "[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%', '%WRAPPER_JAR%')"^
+ "}"
+ if "%MVNW_VERBOSE%" == "true" (
+ echo Finished downloading %WRAPPER_JAR%
+ )
+)
+@REM End of extension
+
+@REM Provide a "standardized" way to retrieve the CLI args that will
+@REM work with both Windows and non-Windows executions.
+set MAVEN_CMD_LINE_ARGS=%*
+
+%MAVEN_JAVA_EXE% ^
+ %JVM_CONFIG_MAVEN_PROPS% ^
+ %MAVEN_OPTS% ^
+ %MAVEN_DEBUG_OPTS% ^
+ -classpath %WRAPPER_JAR% ^
+ "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" ^
+ %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %*
+if ERRORLEVEL 1 goto error
+goto end
+
+:error
+set ERROR_CODE=1
+
+:end
+@endlocal & set ERROR_CODE=%ERROR_CODE%
+
+if not "%MAVEN_SKIP_RC%"=="" goto skipRcPost
+@REM check for post script, once with legacy .bat ending and once with .cmd ending
+if exist "%USERPROFILE%\mavenrc_post.bat" call "%USERPROFILE%\mavenrc_post.bat"
+if exist "%USERPROFILE%\mavenrc_post.cmd" call "%USERPROFILE%\mavenrc_post.cmd"
+:skipRcPost
+
+@REM pause the script if MAVEN_BATCH_PAUSE is set to 'on'
+if "%MAVEN_BATCH_PAUSE%"=="on" pause
+
+if "%MAVEN_TERMINATE_CMD%"=="on" exit %ERROR_CODE%
+
+cmd /C exit /B %ERROR_CODE%
diff --git a/oap-server-bom/pom.xml b/oap-server-bom/pom.xml
new file mode 100644
index 000000000000..5ab55640bd4c
--- /dev/null
+++ b/oap-server-bom/pom.xml
@@ -0,0 +1,685 @@
+
+
+
+
+
+ apm
+ org.apache.skywalking
+ ${revision}
+
+ pom
+ 4.0.0
+ oap-server-bom
+
+
+ 1.7.30
+ 2.17.1
+ 2.11.0
+ 13.0.1
+ 21.5
+ 18.1
+ 3.14.9
+ 4.5.13
+ 2.10.5
+ 3.5.7
+ 32.0.1-jre
+ 2.0
+ 3.25.5
+ 3.25.5
+ 1.11
+ 3.12.0
+ 2.17.0
+ 1.4
+ 6.7.1
+ 3.1.0
+ 2.24.1
+ 2.16.0
+ 2.16.0
+ 0.6.0
+ 1.8.0
+ 2.3.2
+ 4.3.0
+ 2.12.0
+ 2.18.0
+ 2.3.31
+ 3.25.0-GA
+ 0.10.3
+ 4.0.15
+ 2.4.8.Final
+ 1.11.0
+ 1.12.0
+ 42.4.4
+ 0.6.1
+ 1.17.6
+ 1.32.0
+ 3.0.0
+ 4.4.16
+ 4.1.5
+ 1.21
+ 0.9.0-rc2
+ 3.4.0
+ 2.4.6.RELEASE
+ 1.5.3
+ 3.9.0
+ 3.9.0
+ 3.0
+ 1.14.4
+
+
+
+
+
+ io.netty
+ netty-bom
+ ${netty.version}
+ import
+ pom
+
+
+ com.linecorp.armeria
+ armeria-bom
+ ${armeria.version}
+ import
+ pom
+
+
+ org.slf4j
+ slf4j-api
+ ${slf4j.version}
+
+
+ org.slf4j
+ jcl-over-slf4j
+ ${slf4j.version}
+
+
+ org.slf4j
+ log4j-over-slf4j
+ ${slf4j.version}
+
+
+ org.apache.logging.log4j
+ log4j-core
+ ${log4j.version}
+
+
+ org.apache.logging.log4j
+ log4j-api
+ ${log4j.version}
+
+
+ com.google.errorprone
+ error_prone_annotations
+ ${google.error_prone_annotations}
+
+
+ com.graphql-java-kickstart
+ graphql-java-tools
+ ${graphql-java-tools.version}
+
+
+ com.graphql-java
+ graphql-java
+ ${graphql-java.version}
+
+
+ com.graphql-java
+ graphql-java-extended-scalars
+ ${graphql-java-extended-scalars.version}
+
+
+ com.google.code.gson
+ gson
+ ${gson.version}
+
+
+ com.squareup.okhttp3
+ okhttp
+ ${okhttp.version}
+
+
+ joda-time
+ joda-time
+ ${joda-time.version}
+
+
+ org.apache.zookeeper
+ zookeeper
+ ${zookeeper.version}
+
+
+ slf4j-api
+ org.slf4j
+
+
+ slf4j-log4j12
+ org.slf4j
+
+
+
+
+ com.google.guava
+ guava
+ ${guava.version}
+
+
+ com.google.j2objc
+ j2objc-annotations
+
+
+
+
+ org.yaml
+ snakeyaml
+ ${snakeyaml.version}
+
+
+ org.apache.logging.log4j
+ log4j-slf4j-impl
+ ${log4j.version}
+
+
+ org.apache.logging.log4j
+ log4j-core
+
+
+
+
+ io.grpc
+ grpc-core
+ ${grpc.version}
+
+
+ com.google.android
+ annotations
+
+
+
+
+ io.grpc
+ grpc-api
+ ${grpc.version}
+
+
+ io.grpc
+ grpc-netty
+ ${grpc.version}
+
+
+ io.netty
+ netty-codec-http2
+
+
+ io.netty
+ netty-handler-proxy
+
+
+
+
+ io.grpc
+ grpc-protobuf
+ ${grpc.version}
+
+
+
+ com.google.protobuf
+ protobuf-java
+ ${protobuf-java.version}
+
+
+ com.google.protobuf
+ protobuf-java-util
+ ${protobuf-java-util.version}
+
+
+
+ io.grpc
+ grpc-stub
+ ${grpc.version}
+
+
+ io.netty
+ netty-tcnative-boringssl-static
+ ${netty-tcnative-boringssl-static.version}
+
+
+ io.grpc
+ grpc-testing
+ ${grpc.version}
+ test
+
+
+ org.mockito
+ mockito-core
+
+
+ junit
+ junit
+
+
+ io.grpc
+ grpc-core
+
+
+ io.grpc
+ grpc-stub
+
+
+
+
+ io.grpc
+ grpc-grpclb
+ ${grpc.version}
+
+
+ commons-io
+ commons-io
+ ${commons-io.version}
+
+
+
+ io.fabric8
+ kubernetes-client-bom
+ ${kubernetes.version}
+ import
+ pom
+
+
+ io.fabric8
+ kubernetes-client
+ ${kubernetes.version}
+
+
+ io.fabric8
+ kubernetes-httpclient-okhttp
+
+
+
+
+
+ com.zaxxer
+ HikariCP
+ ${hikaricp.version}
+
+
+
+ io.zipkin.zipkin2
+ zipkin
+ ${zipkin.version}
+
+
+
+ io.zipkin
+ zipkin-lens
+ ${zipkin.version}
+
+
+
+ com.fasterxml.jackson.core
+ jackson-core
+ ${jackson.version}
+
+
+ com.fasterxml.jackson.core
+ jackson-annotations
+ ${jackson.version}
+
+
+ com.fasterxml.jackson.core
+ jackson-databind
+ ${jackson-databind.version}
+
+
+ commons-codec
+ commons-codec
+ ${commons-codec.version}
+
+
+ org.apache.commons
+ commons-lang3
+ ${commons-lang3.version}
+
+
+ commons-net
+ commons-net
+ ${commons-net.version}
+
+
+
+ io.prometheus
+ simpleclient
+ ${simpleclient.version}
+
+
+ com.ctrip.framework.apollo
+ apollo-client
+ ${apollo.version}
+
+
+ com.alibaba.nacos
+ nacos-client
+ ${nacos.version}
+
+
+
+ io.etcd
+ jetcd-core
+ ${jetcd.version}
+
+
+ io.grpc
+ grpc-core
+
+
+ io.grpc
+ grpc-netty
+
+
+ io.grpc
+ grpc-protobuf
+
+
+ io.grpc
+ grpc-stub
+
+
+ io.grpc
+ grpc-grpclb
+
+
+ org.slf4j
+ slf4j-api
+
+
+ com.github.spotbugs
+ spotbugs-annotations
+
+
+
+
+
+ org.apache.skywalking
+ banyandb-java-client
+ ${banyandb-java-client.version}
+
+
+ io.grpc
+ grpc-netty
+
+
+ io.grpc
+ grpc-protobuf
+
+
+ io.grpc
+ grpc-stub
+
+
+ io.netty
+ netty-tcnative-boringssl-static
+
+
+
+
+
+ org.apache.curator
+ curator-x-discovery
+ ${curator.version}
+
+
+ com.google.guava
+ guava
+
+
+ org.slf4j
+ slf4j-api
+
+
+ log4j
+ log4j
+
+
+
+
+ org.apache.curator
+ curator-test
+ ${curator-test.version}
+
+
+ com.google.guava
+ guava
+
+
+ log4j
+ log4j
+
+
+ test
+
+
+
+ org.freemarker
+ freemarker
+ ${freemarker.version}
+
+
+ org.javassist
+ javassist
+ ${javaassist.version}
+
+
+ org.apache.commons
+ commons-text
+ ${commons-text.version}
+
+
+ io.vavr
+ vavr
+ ${vavr.version}
+
+
+ org.apache.groovy
+ groovy
+ ${groovy.version}
+
+
+ commons-beanutils
+ commons-beanutils
+ ${commons-beanutils.version}
+
+
+ commons-collections
+ commons-collections
+
+
+ commons-logging
+ commons-logging
+
+
+
+
+
+ org.apache.httpcomponents
+ httpclient
+ ${httpclient.version}
+
+
+
+ org.apache.httpcomponents
+ httpasyncclient
+ ${httpasyncclient.version}
+
+
+
+ com.google.flatbuffers
+ flatbuffers-java
+ ${flatbuffers-java.version}
+
+
+
+ org.postgresql
+ postgresql
+ ${postgresql.version}
+
+
+
+ com.linecorp.armeria
+ armeria
+ ${armeria.version}
+
+
+ com.aayushatharva.brotli4j
+ native-linux-x86_64
+
+
+ com.aayushatharva.brotli4j
+ native-linux-x86_64
+
+
+ com.aayushatharva.brotli4j
+ native-osx-aarch64
+
+
+
+
+ com.linecorp.armeria
+ armeria-grpc
+ ${armeria.version}
+
+
+ org.apache.httpcomponents
+ httpcore
+ ${httpcore.version}
+
+
+ org.apache.httpcomponents
+ httpcore-nio
+ ${httpcore.version}
+
+
+
+ org.testcontainers
+ testcontainers
+ ${testcontainers.version}
+ test
+
+
+ junit
+ junit
+
+
+
+
+ org.testcontainers
+ elasticsearch
+ ${testcontainers.version}
+ test
+
+
+ org.testcontainers
+ kafka
+ ${testcontainers.version}
+ test
+
+
+ org.testcontainers
+ postgresql
+ ${testcontainers.version}
+ test
+
+
+ org.testcontainers
+ junit-jupiter
+ ${testcontainers.version}
+ test
+
+
+ org.awaitility
+ awaitility
+ ${awaitility.version}
+ test
+
+
+ org.apache.commons
+ commons-compress
+ ${commons-compress.version}
+
+
+
+ org.apache.kafka
+ kafka-clients
+ ${kafka-clients.version}
+
+
+ org.springframework.kafka
+ spring-kafka-test
+ ${spring-kafka-test.version}
+ test
+
+
+
+ com.orbitz.consul
+ consul-client
+ ${consul.client.version}
+
+
+ com.google.guava
+ guava
+
+
+ org.slf4j
+ slf4j-api
+
+
+
+
+
+ org.apache.maven
+ maven-plugin-api
+ ${maven-core.version}
+
+
+
+ org.apache.maven
+ maven-core
+ ${maven-core.version}
+ provided
+
+
+
+ org.apache.maven.plugin-tools
+ maven-plugin-annotations
+ ${maven-core.version}
+ provided
+
+
+
+ tools.profiler
+ async-profiler-converter
+ ${async-profiler-converter.version}
+
+
+
+ io.micrometer
+ micrometer-core
+ ${micrometer.version}
+
+
+
+
diff --git a/oap-server/ai-pipeline/pom.xml b/oap-server/ai-pipeline/pom.xml
new file mode 100644
index 000000000000..ddcf480d7caf
--- /dev/null
+++ b/oap-server/ai-pipeline/pom.xml
@@ -0,0 +1,113 @@
+
+
+
+
+ 4.0.0
+
+
+ org.apache.skywalking
+ oap-server
+ ${revision}
+
+
+ org.apache.skywalking
+ ai-pipeline
+
+
+ AI pipeline module include pipelines connecting the OAP kernel and any 3rd party AI and/or algorithm
+ server. The kernel would call the pipeline in the specific context/scenario with well formatted telemetry data,
+ and expect the remote to respond with the result of the AI/algorithm as quick as possible, but in async way in
+ case of large size of data or lower performance behavior of the remote.
+
+
+
+
+ io.grpc
+ grpc-netty
+ ${grpc.version}
+
+
+ io.grpc
+ grpc-protobuf
+ ${grpc.version}
+
+
+ io.grpc
+ grpc-stub
+ ${grpc.version}
+
+
+ org.apache.skywalking
+ library-module
+ ${project.version}
+
+
+ org.apache.skywalking
+ library-client
+ ${project.version}
+
+
+ org.apache.skywalking
+ server-core
+ ${project.version}
+
+
+ io.grpc
+ grpc-testing
+ test
+
+
+ org.powermock
+ powermock-reflect
+ test
+
+
+
+
+
+
+ org.xolstice.maven.plugins
+ protobuf-maven-plugin
+ ${protobuf-maven-plugin.version}
+
+
+
+ com.google.protobuf:protoc:${com.google.protobuf.protoc.version}:exe:${os.detected.classifier}
+
+ grpc-java
+
+ io.grpc:protoc-gen-grpc-java:${protoc-gen-grpc-java.plugin.version}:exe:${os.detected.classifier}
+
+
+
+
+
+ compile
+ compile-custom
+
+
+
+
+
+
+
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineConfig.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineConfig.java
new file mode 100644
index 000000000000..3cd005dc2994
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineConfig.java
@@ -0,0 +1,32 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline;
+
+import lombok.Getter;
+import lombok.Setter;
+import org.apache.skywalking.oap.server.library.module.ModuleConfig;
+
+@Getter
+@Setter
+public class AIPipelineConfig extends ModuleConfig {
+ private String uriRecognitionServerAddr;
+ private int uriRecognitionServerPort = 17128;
+ private String baselineServerAddr;
+ private int baselineServerPort = 18080;
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineModule.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineModule.java
new file mode 100644
index 000000000000..d325447d3d93
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineModule.java
@@ -0,0 +1,35 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline;
+
+import org.apache.skywalking.oap.server.ai.pipeline.services.BaselineQueryService;
+import org.apache.skywalking.oap.server.library.module.ModuleDefine;
+
+public class AIPipelineModule extends ModuleDefine {
+ public static final String NAME = "ai-pipeline";
+
+ public AIPipelineModule() {
+ super(NAME);
+ }
+
+ @Override
+ public Class[] services() {
+ return new Class[]{BaselineQueryService.class};
+ }
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineProvider.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineProvider.java
new file mode 100644
index 000000000000..70dfffdce9eb
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/AIPipelineProvider.java
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline;
+
+import org.apache.skywalking.oap.server.ai.pipeline.services.BaselineQueryService;
+import org.apache.skywalking.oap.server.ai.pipeline.services.BaselineQueryServiceImpl;
+import org.apache.skywalking.oap.server.ai.pipeline.services.HttpUriRecognitionService;
+import org.apache.skywalking.oap.server.core.CoreModule;
+import org.apache.skywalking.oap.server.core.config.group.EndpointNameGroupService;
+import org.apache.skywalking.oap.server.library.module.ModuleConfig;
+import org.apache.skywalking.oap.server.library.module.ModuleDefine;
+import org.apache.skywalking.oap.server.library.module.ModuleProvider;
+import org.apache.skywalking.oap.server.library.module.ModuleStartException;
+import org.apache.skywalking.oap.server.library.module.ServiceNotProvidedException;
+
+public class AIPipelineProvider extends ModuleProvider {
+ private AIPipelineConfig aiPipelineConfig;
+
+ @Override
+ public String name() {
+ return "default";
+ }
+
+ @Override
+ public Class module() {
+ return AIPipelineModule.class;
+ }
+
+ @Override
+ public ConfigCreator newConfigCreator() {
+ return new ConfigCreator() {
+ @Override
+ public Class type() {
+ return AIPipelineConfig.class;
+ }
+
+ @Override
+ public void onInitialized(final AIPipelineConfig initialized) {
+ aiPipelineConfig = initialized;
+ }
+ };
+ }
+
+ @Override
+ public void prepare() throws ServiceNotProvidedException, ModuleStartException {
+ this.registerServiceImplementation(BaselineQueryService.class, new BaselineQueryServiceImpl(
+ aiPipelineConfig.getBaselineServerAddr(),
+ aiPipelineConfig.getBaselineServerPort()
+ ));
+ }
+
+ @Override
+ public void start() throws ServiceNotProvidedException, ModuleStartException {
+ final HttpUriRecognitionService httpUriRecognitionService = new HttpUriRecognitionService(
+ aiPipelineConfig.getUriRecognitionServerAddr(),
+ aiPipelineConfig.getUriRecognitionServerPort()
+ );
+ getManager().find(CoreModule.NAME).provider()
+ .getService(EndpointNameGroupService.class)
+ .startHttpUriRecognitionSvr(httpUriRecognitionService);
+ }
+
+ @Override
+ public void notifyAfterCompleted() throws ServiceNotProvidedException, ModuleStartException {
+ }
+
+ @Override
+ public String[] requiredModules() {
+ return new String[] {
+ CoreModule.NAME
+ };
+ }
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryService.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryService.java
new file mode 100644
index 000000000000..1b97aff777cb
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryService.java
@@ -0,0 +1,45 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline.services;
+
+import java.util.Map;
+import org.apache.skywalking.oap.server.library.module.Service;
+
+import java.util.List;
+
+public interface BaselineQueryService extends Service {
+ /**
+ * query supported query baseline metrics names
+ *
+ * @return
+ */
+ List querySupportedMetrics();
+
+ /**
+ * query predicted metrics
+ */
+ List queryPredictMetrics(List serviceMetrics,
+ long startTimeBucket,
+ long endTimeBucket);
+
+ /**
+ * query predicted metrics from cache, return all predicted metrics for the given service name and time bucket hour
+ */
+ Map queryPredictMetricsFromCache(String serviceName, String timeBucketHour);
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryServiceImpl.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryServiceImpl.java
new file mode 100644
index 000000000000..5f686b071ef9
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/BaselineQueryServiceImpl.java
@@ -0,0 +1,199 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline.services;
+
+import com.google.common.cache.Cache;
+import com.google.common.cache.CacheBuilder;
+import com.google.protobuf.Empty;
+import io.grpc.ManagedChannel;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.concurrent.TimeUnit;
+import lombok.extern.slf4j.Slf4j;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineMetricPrediction;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineMetricsNames;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineRequest;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineResponse;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceGrpc;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceMetricName;
+import org.apache.skywalking.apm.baseline.v3.KeyStringValuePair;
+import org.apache.skywalking.apm.baseline.v3.TimeBucketStep;
+import org.apache.skywalking.oap.server.core.Const;
+import org.apache.skywalking.oap.server.core.analysis.DownSampling;
+import org.apache.skywalking.oap.server.core.analysis.TimeBucket;
+import org.apache.skywalking.oap.server.library.client.grpc.GRPCClient;
+import org.apache.skywalking.oap.server.library.util.CollectionUtils;
+import org.apache.skywalking.oap.server.library.util.StringUtil;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+import java.util.Optional;
+import java.util.stream.Collectors;
+
+@Slf4j
+public class BaselineQueryServiceImpl implements BaselineQueryService {
+ private AlarmBaselineServiceGrpc.AlarmBaselineServiceBlockingStub stub;
+ private final Cache> baselineCache;
+
+ public BaselineQueryServiceImpl(String addr, int port) {
+ this.baselineCache = CacheBuilder.newBuilder()
+ .expireAfterAccess(1, TimeUnit.HOURS)
+ .build();
+ if (StringUtil.isEmpty(addr) || port <= 0) {
+ return;
+ }
+ GRPCClient client = new GRPCClient(addr, port);
+ client.connect();
+ ManagedChannel channel = client.getChannel();
+ stub = AlarmBaselineServiceGrpc.newBlockingStub(channel);
+ }
+
+ @Override
+ public List querySupportedMetrics() {
+ if (stub == null) {
+ log.warn("Baseline service is not set up, return empty list.");
+ return Collections.emptyList();
+ }
+
+ final AlarmBaselineMetricsNames names = stub.querySupportedMetricsNames(Empty.newBuilder().build());
+ return Optional.ofNullable(names)
+ .map(AlarmBaselineMetricsNames::getMetricNamesList)
+ .map(ArrayList::new).orElse(new ArrayList<>(0));
+ }
+
+ public List queryPredictMetrics(List serviceMetrics, long startTimeBucket, long endTimeBucket) {
+ if (stub == null) {
+ log.warn("Baseline service is not set up, return empty baseline values.");
+ return Collections.emptyList();
+ }
+
+ try {
+ return queryPredictMetrics0(serviceMetrics, startTimeBucket, endTimeBucket);
+ } catch (Exception e) {
+ log.warn("Query baseline failure", e);
+ }
+ return Collections.emptyList();
+ }
+
+ public Map queryPredictMetricsFromCache(String serviceName,
+ String timeBucketHour) {
+ if (stub == null) {
+ log.warn("Baseline service is not set up, return empty baseline values.");
+ return Collections.emptyMap();
+ }
+ String key = timeBucketHour + Const.COMMA + serviceName;
+ Map baselineValues = this.baselineCache.asMap().get(key);
+
+ if (CollectionUtils.isNotEmpty(baselineValues)) {
+ return baselineValues;
+ }
+ //reload all metrics and timeBucket baseline values for this service
+ List metrics = querySupportedMetrics();
+ ServiceMetrics serviceMetrics = ServiceMetrics.builder()
+ .serviceName(serviceName)
+ .metricsNames(metrics)
+ .build();
+ //todo: need config?
+ long startTimeBucket = TimeBucket.getTimeBucket(
+ System.currentTimeMillis() - TimeUnit.HOURS.toMillis(24), DownSampling.Hour);
+ long endTimeBucket = TimeBucket.getTimeBucket(
+ System.currentTimeMillis() + TimeUnit.HOURS.toMillis(24), DownSampling.Hour);
+ List predictServiceMetricsList = queryPredictMetrics(
+ Collections.singletonList(serviceMetrics), startTimeBucket, endTimeBucket);
+ if (CollectionUtils.isEmpty(predictServiceMetricsList)) {
+ return Collections.emptyMap();
+ }
+ for (String metricName : metrics) {
+ for (PredictServiceMetrics predictServiceMetrics : predictServiceMetricsList) {
+ List predictMetricsValues = predictServiceMetrics.getMetricsValues()
+ .get(
+ metricName);
+ if (CollectionUtils.isEmpty(predictMetricsValues)) {
+ continue;
+ }
+ for (PredictServiceMetrics.PredictMetricsValue predictMetricsValue : predictMetricsValues) {
+ if (predictMetricsValue == null) {
+ continue;
+ }
+ this.baselineCache.asMap()
+ .computeIfAbsent(
+ predictMetricsValue.getTimeBucket() + Const.COMMA + serviceName,
+ k -> new HashMap<>()
+ )
+ .put(metricName, predictMetricsValue);
+ }
+ }
+ }
+ return this.baselineCache.asMap().getOrDefault(key, Collections.emptyMap());
+ }
+
+ private List queryPredictMetrics0(List serviceMetrics, long startTimeBucket, long endTimeBucket) {
+ // building request
+ final AlarmBaselineRequest.Builder request = AlarmBaselineRequest.newBuilder();
+ serviceMetrics.forEach(s -> {
+ final AlarmBaselineServiceMetricName.Builder serviceMetricsBuilder = AlarmBaselineServiceMetricName.newBuilder();
+ serviceMetricsBuilder.setServiceName(s.getServiceName());
+ serviceMetricsBuilder.addAllMetricNames(s.getMetricsNames());
+ request.addServiceMetricNames(serviceMetricsBuilder);
+ });
+ request.setStartTimeBucket(startTimeBucket);
+ request.setEndTimeBucket(endTimeBucket);
+ // Only support hour level for now
+ request.setStep(TimeBucketStep.HOUR);
+
+ // send request and convert response
+ final AlarmBaselineResponse response = stub.queryPredictedMetrics(request.build());
+ return response.getServiceMetricsList().stream().map(s -> {
+ final PredictServiceMetrics.PredictServiceMetricsBuilder builder = PredictServiceMetrics.builder();
+ builder.serviceName(s.getServiceName());
+ builder.metricsValues(s.getPredictionsList().stream().collect(
+ Collectors.toMap(AlarmBaselineMetricPrediction::getName, p -> p.getValuesList().stream().map(v -> {
+ final PredictServiceMetrics.PredictMetricsValue.PredictMetricsValueBuilder valueBuilder =
+ PredictServiceMetrics.PredictMetricsValue.builder();
+ valueBuilder.timeBucket(v.getTimeBucket());
+ // parsing single value
+ if (v.hasSingleValue()) {
+ valueBuilder.singleValue(PredictServiceMetrics.PredictSingleValue.builder()
+ .value(v.getSingleValue().getValue().getValue())
+ .upperValue(v.getSingleValue().getValue().getUpperValue())
+ .lowerValue(v.getSingleValue().getValue().getLowerValue())
+ .build());
+ }
+ // parsing labeled values
+ if (v.hasLabeledValue()) {
+ valueBuilder.labeledValue(v.getLabeledValue().getValuesList().stream().map(l -> {
+ final PredictServiceMetrics.PredictLabelValue.PredictLabelValueBuilder labelBuilder =
+ PredictServiceMetrics.PredictLabelValue.builder();
+ labelBuilder.labels(l.getLabelsList().stream().collect(
+ Collectors.toMap(KeyStringValuePair::getKey, KeyStringValuePair::getValue)));
+ labelBuilder.value(PredictServiceMetrics.PredictSingleValue.builder()
+ .value(l.getValue().getValue())
+ .upperValue(l.getValue().getUpperValue())
+ .lowerValue(l.getValue().getLowerValue())
+ .build());
+ return labelBuilder.build();
+ }).collect(Collectors.toList()));
+ }
+ return valueBuilder.build();
+ }).collect(Collectors.toList()))));
+ return builder.build();
+ }).collect(Collectors.toList());
+ }
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/HttpUriRecognitionService.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/HttpUriRecognitionService.java
new file mode 100644
index 000000000000..d98b74880532
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/HttpUriRecognitionService.java
@@ -0,0 +1,115 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline.services;
+
+import io.grpc.ManagedChannel;
+import java.util.List;
+import java.util.concurrent.TimeUnit;
+import java.util.stream.Collectors;
+import lombok.extern.slf4j.Slf4j;
+import org.apache.skywalking.oap.server.ai.pipeline.grpc.HttpRawUri;
+import org.apache.skywalking.oap.server.ai.pipeline.grpc.HttpUriRecognitionRequest;
+import org.apache.skywalking.oap.server.ai.pipeline.grpc.HttpUriRecognitionResponse;
+import org.apache.skywalking.oap.server.ai.pipeline.grpc.HttpUriRecognitionServiceGrpc;
+import org.apache.skywalking.oap.server.ai.pipeline.grpc.HttpUriRecognitionSyncRequest;
+import org.apache.skywalking.oap.server.core.config.group.ai.HttpUriPattern;
+import org.apache.skywalking.oap.server.core.config.group.ai.HttpUriRecognition;
+import org.apache.skywalking.oap.server.library.client.grpc.GRPCClient;
+import org.apache.skywalking.oap.server.library.util.StringUtil;
+
+@Slf4j
+public class HttpUriRecognitionService implements HttpUriRecognition {
+ private HttpUriRecognitionServiceGrpc.HttpUriRecognitionServiceBlockingStub stub;
+ private String version = "NULL";
+
+ public HttpUriRecognitionService(String addr, int port) {
+ if (StringUtil.isEmpty(addr) || port <= 0) {
+ return;
+ }
+ GRPCClient client = new GRPCClient(addr, port);
+ client.connect();
+ ManagedChannel channel = client.getChannel();
+ stub = HttpUriRecognitionServiceGrpc.newBlockingStub(channel);
+ }
+
+ @Override
+ public boolean isInitialized() {
+ return stub != null;
+ }
+
+ @Override
+ public List fetchAllPatterns(final String service) {
+ try {
+ if (stub == null) {
+ return null;
+ }
+ final HttpUriRecognitionResponse httpUriRecognitionResponse
+ = stub.withDeadlineAfter(30, TimeUnit.SECONDS)
+ .fetchAllPatterns(
+ HttpUriRecognitionSyncRequest.newBuilder()
+ .setService(service)
+ .setVersion(version)
+ .build()
+ );
+ final String newVersion = httpUriRecognitionResponse.getVersion();
+ if (log.isDebugEnabled()) {
+ log.debug("Remote response version: {}, local version {}", newVersion, version);
+ }
+ if (version.equals(newVersion)) {
+ return null;
+ } else {
+ version = newVersion;
+ }
+
+ return httpUriRecognitionResponse.getPatternsList()
+ .stream()
+ .map(pattern -> new HttpUriPattern(pattern.getPattern()))
+ .collect(Collectors.toList());
+
+ } catch (Exception e) {
+ log.error("fetch all patterns failed from remote server.", e);
+ return null;
+ }
+ }
+
+ @Override
+ public void feedRawData(final String service, final List unrecognizedURIs) {
+ try {
+ if (stub == null) {
+ return;
+ }
+ final HttpUriRecognitionRequest.Builder builder = HttpUriRecognitionRequest.newBuilder();
+ builder.setService(service);
+ if (log.isDebugEnabled()) {
+ log.debug("Feeding to remote, service: {}, uri size: {}", service, unrecognizedURIs.size());
+ }
+ List rawUriList = unrecognizedURIs.stream()
+ .map(httpUri -> HttpRawUri.newBuilder()
+ .setName(httpUri.getName())
+ .build())
+ .collect(Collectors.toList());
+
+ builder.addAllUnrecognizedUris(rawUriList);
+ stub.withDeadlineAfter(30, TimeUnit.SECONDS)
+ .feedRawData(builder.build());
+ } catch (Exception e) {
+ log.error("Failed to feed matched and unmatched URIs to the remote server.", e);
+ }
+ }
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/PredictServiceMetrics.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/PredictServiceMetrics.java
new file mode 100644
index 000000000000..b5c4442bad5b
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/PredictServiceMetrics.java
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline.services;
+
+import lombok.Builder;
+import lombok.Data;
+
+import java.util.List;
+import java.util.Map;
+
+@Data
+@Builder
+public class PredictServiceMetrics {
+ private String serviceName;
+ private Map> metricsValues;
+
+ @Data
+ @Builder
+ public static class PredictMetricsValue {
+ private long timeBucket;
+ private PredictSingleValue singleValue;
+ private List labeledValue;
+ }
+
+ @Data
+ @Builder
+ public static class PredictSingleValue {
+ private long value;
+ private long upperValue;
+ private long lowerValue;
+ }
+
+ @Data
+ @Builder
+ public static class PredictLabelValue {
+ private Map labels;
+ private PredictSingleValue value;
+ }
+}
diff --git a/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/ServiceMetrics.java b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/ServiceMetrics.java
new file mode 100644
index 000000000000..e46c94a70cca
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/java/org/apache/skywalking/oap/server/ai/pipeline/services/ServiceMetrics.java
@@ -0,0 +1,31 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.ai.pipeline.services;
+
+import lombok.Builder;
+import lombok.Data;
+
+import java.util.List;
+
+@Data
+@Builder
+public class ServiceMetrics {
+ private String serviceName;
+ private List metricsNames;
+}
diff --git a/oap-server/ai-pipeline/src/main/proto/ai_http_uri_recognition.proto b/oap-server/ai-pipeline/src/main/proto/ai_http_uri_recognition.proto
new file mode 100644
index 000000000000..b03e7e7323a1
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/proto/ai_http_uri_recognition.proto
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+syntax = "proto3";
+
+import "google/protobuf/empty.proto";
+
+
+option java_multiple_files = true;
+option java_package = "org.apache.skywalking.oap.server.ai.pipeline.grpc";
+
+service HttpUriRecognitionService {
+ // Sync for the pattern recognition dictionary.
+ rpc fetchAllPatterns(HttpUriRecognitionSyncRequest) returns (HttpUriRecognitionResponse) {}
+ // Feed new raw data and matched patterns to the AI-server.
+ rpc feedRawData(HttpUriRecognitionRequest) returns (google.protobuf.Empty) {}
+}
+
+message HttpUriRecognitionSyncRequest {
+ string service = 1;
+ // The version of pattern dictionary at the OAP side.
+ string version = 2;
+}
+
+message HttpUriRecognitionRequest {
+ string service = 1;
+ repeated HttpRawUri unrecognizedUris = 2;
+}
+
+message HttpRawUri {
+ string name = 1;
+}
+
+message HttpUriRecognitionResponse {
+ repeated Pattern patterns = 1;
+ // The version of pattern dictionary at the AI-server side.
+ // If it is as same as HttpUriRecognitionSyncRequest#version,
+ // patterns could be empty as nothing should be updated.
+ string version = 2;
+}
+
+message Pattern {
+ // Quick match URI pattern. {var} represents a variable part in the URI.
+ // /product/{var} is the pattern for /product/1, /product/2
+ // GET:/product/{var}/detail is the pattern for GET:/product/1/detail, GET:/product/2/detail
+ string pattern = 2;
+}
\ No newline at end of file
diff --git a/oap-server/ai-pipeline/src/main/proto/baseline.proto b/oap-server/ai-pipeline/src/main/proto/baseline.proto
new file mode 100644
index 000000000000..41fe11f2162f
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/proto/baseline.proto
@@ -0,0 +1,118 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+syntax = "proto3";
+package skywalking.v3;
+
+import "google/protobuf/empty.proto";
+
+option java_multiple_files = true;
+option java_package = "org.apache.skywalking.apm.baseline.v3";
+
+service AlarmBaselineService {
+ // Query the supported metrics names.
+ rpc querySupportedMetricsNames(google.protobuf.Empty) returns (AlarmBaselineMetricsNames);
+ // Query the predicted metrics of the given service.
+ rpc queryPredictedMetrics(AlarmBaselineRequest) returns (AlarmBaselineResponse);
+}
+
+message AlarmBaselineMetricsNames {
+ repeated string metricNames = 1;
+}
+
+// The request of the predicted metrics query.
+message AlarmBaselineRequest {
+ // The request service metrics names.
+ repeated AlarmBaselineServiceMetricName serviceMetricNames = 1;
+ // The request start TimeBucket.
+ int64 startTimeBucket = 2;
+ // The request end TimeBucket.
+ int64 endTimeBucket = 3;
+ // The step of the TimeBucket.
+ TimeBucketStep step = 4;
+}
+
+enum TimeBucketStep {
+ HOUR = 0;
+}
+
+message AlarmBaselineServiceMetricName {
+ // The service name.
+ string serviceName = 1;
+ // The metrics names.
+ repeated string metricNames = 2;
+}
+
+// The response of the predicted metrics query.
+message AlarmBaselineResponse {
+ repeated AlarmBaselineServiceMetric serviceMetrics = 1;
+}
+
+message AlarmBaselineServiceMetric {
+ // The service name.
+ string serviceName = 1;
+ // The service metrics.
+ repeated AlarmBaselineMetricPrediction predictions = 2;
+}
+
+// The predicted metric.
+message AlarmBaselineMetricPrediction {
+ // The metric name.
+ string name = 1;
+ // The metric predicated values(timeBucket with predicted value).
+ repeated AlarmBaselinePredicatedValue values = 2;
+}
+
+// The predicted metric sample.
+message AlarmBaselinePredicatedValue {
+ int64 timeBucket = 1;
+ oneof value {
+ AlarmBaselineSingleValue singleValue = 2;
+ AlarmBaselineLabeledValue labeledValue = 3;
+ }
+}
+
+// The predicted value. The metric values provided within this baseline are at a minute-level granularity. For example, it includes metrics such as the number of visits per minute.
+message AlarmBaselineValue {
+ // The predicted value.
+ int64 value = 1;
+ // The upper value of the predicted range.
+ int64 upperValue = 2;
+ // The lower value of the predicted range.
+ int64 lowerValue = 3;
+}
+
+// The predicted single value metric.
+message AlarmBaselineSingleValue {
+ AlarmBaselineValue value = 2;
+}
+
+// The predicted labeled value metric.
+message AlarmBaselineLabeledValue {
+ // label pairs with value.
+ message LabelWithValue {
+ repeated KeyStringValuePair labels = 1;
+ AlarmBaselineValue value = 2;
+ }
+ repeated LabelWithValue values = 1;
+}
+
+message KeyStringValuePair {
+ string key = 1;
+ string value = 2;
+}
diff --git a/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleDefine b/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleDefine
new file mode 100644
index 000000000000..fcfbe3cc1ce6
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleDefine
@@ -0,0 +1,19 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+#
+
+org.apache.skywalking.oap.server.ai.pipeline.AIPipelineModule
diff --git a/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleProvider b/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleProvider
new file mode 100644
index 000000000000..84a4ce71d66c
--- /dev/null
+++ b/oap-server/ai-pipeline/src/main/resources/META-INF/services/org.apache.skywalking.oap.server.library.module.ModuleProvider
@@ -0,0 +1,19 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+#
+
+org.apache.skywalking.oap.server.ai.pipeline.AIPipelineProvider
\ No newline at end of file
diff --git a/oap-server/ai-pipeline/src/test/java/BaselineQueryServer.java b/oap-server/ai-pipeline/src/test/java/BaselineQueryServer.java
new file mode 100644
index 000000000000..65f3b72ce6d0
--- /dev/null
+++ b/oap-server/ai-pipeline/src/test/java/BaselineQueryServer.java
@@ -0,0 +1,194 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+import com.google.protobuf.Empty;
+import io.grpc.stub.StreamObserver;
+import lombok.Builder;
+import lombok.Data;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineLabeledValue;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineMetricsNames;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceGrpc;
+import org.apache.skywalking.apm.baseline.v3.AlarmBaselineValue;
+import org.apache.skywalking.apm.baseline.v3.KeyStringValuePair;
+import org.apache.skywalking.oap.server.core.analysis.DownSampling;
+import org.apache.skywalking.oap.server.core.analysis.TimeBucket;
+
+import java.util.ArrayList;
+import java.util.Calendar;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Random;
+import java.util.stream.Collectors;
+
+public class BaselineQueryServer extends AlarmBaselineServiceGrpc.AlarmBaselineServiceImplBase {
+
+ private static final Random RANDOM = new Random(System.currentTimeMillis());
+
+ private static final Map VALUE_GENERATOR = new HashMap<>();
+
+ static {
+ VALUE_GENERATOR.put("service_cpm", MetricConfig.builder()
+ .single(true)
+ .singleValue(MetricsValueConfig.builder().minValue(0).maxValue(1000).build()).build());
+ VALUE_GENERATOR.put("service_sla", MetricConfig.builder()
+ .single(true)
+ .singleValue(MetricsValueConfig.builder().minValue(8000).maxValue(10000).build()).build());
+ VALUE_GENERATOR.put("service_apdex", MetricConfig.builder()
+ .single(true)
+ .singleValue(MetricsValueConfig.builder().minValue(8000).maxValue(10000).build()).build());
+ VALUE_GENERATOR.put("service_resp_time", MetricConfig.builder()
+ .single(true)
+ .singleValue(MetricsValueConfig.builder().minValue(10).maxValue(1000).build()).build());
+ VALUE_GENERATOR.put("service_percentile", MetricConfig.builder()
+ .single(false)
+ .multiValue(new HashMap<>() {
+ {
+ put(KeyStringValuePair.newBuilder().setKey("p").setValue("50").build(),
+ MetricsValueConfig.builder().minValue(0).maxValue(100).build());
+ put(KeyStringValuePair.newBuilder().setKey("p").setValue("75").build(),
+ MetricsValueConfig.builder().minValue(0).maxValue(100).build());
+ put(KeyStringValuePair.newBuilder().setKey("p").setValue("90").build(),
+ MetricsValueConfig.builder().minValue(0).maxValue(100).build());
+ put(KeyStringValuePair.newBuilder().setKey("p").setValue("95").build(),
+ MetricsValueConfig.builder().minValue(0).maxValue(100).build());
+ put(KeyStringValuePair.newBuilder().setKey("p").setValue("99").build(),
+ MetricsValueConfig.builder().minValue(0).maxValue(100).build());
+ }
+ }).build());
+ VALUE_GENERATOR.put("service_status_code", MetricConfig.builder()
+ .single(false)
+ .multiValue(new HashMap<>() {
+ {
+ put(KeyStringValuePair.newBuilder().setKey("status").setValue("200").build(),
+ MetricsValueConfig.builder().minValue(10).maxValue(1000).build());
+ put(KeyStringValuePair.newBuilder().setKey("status").setValue("400").build(),
+ MetricsValueConfig.builder().minValue(10).maxValue(1000).build());
+ put(KeyStringValuePair.newBuilder().setKey("status").setValue("500").build(),
+ MetricsValueConfig.builder().minValue(10).maxValue(1000).build());
+ }
+ })
+ .build());
+ }
+
+ @Override
+ public void querySupportedMetricsNames(Empty request, StreamObserver responseObserver) {
+ responseObserver.onNext(AlarmBaselineMetricsNames.newBuilder()
+ .addAllMetricNames(VALUE_GENERATOR.keySet())
+ .build());
+ responseObserver.onCompleted();
+ }
+
+ @Override
+ public void queryPredictedMetrics(org.apache.skywalking.apm.baseline.v3.AlarmBaselineRequest request, StreamObserver responseObserver) {
+ final List metrics = new ArrayList<>();
+ final List timeBucketRange = generateTimeBucketRange(request);
+
+ for (org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceMetricName serviceMetricName : request.getServiceMetricNamesList()) {
+ final List predictions = new ArrayList<>();
+
+ for (String metricName : serviceMetricName.getMetricNamesList()) {
+ final List values = timeBucketRange.stream()
+ .map(t -> VALUE_GENERATOR.get(metricName).generate(t))
+ .collect(Collectors.toList());
+
+ predictions.add(org.apache.skywalking.apm.baseline.v3.AlarmBaselineMetricPrediction.newBuilder()
+ .setName(metricName)
+ .addAllValues(values)
+ .build());
+ }
+
+ metrics.add(org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceMetric.newBuilder()
+ .setServiceName(serviceMetricName.getServiceName())
+ .addAllPredictions(predictions)
+ .build());
+ }
+
+ responseObserver.onNext(org.apache.skywalking.apm.baseline.v3.AlarmBaselineResponse.newBuilder().addAllServiceMetrics(metrics).build());
+ responseObserver.onCompleted();
+ }
+
+ private List generateTimeBucketRange(org.apache.skywalking.apm.baseline.v3.AlarmBaselineRequest request) {
+ if (request.getStep() != org.apache.skywalking.apm.baseline.v3.TimeBucketStep.HOUR) {
+ return Collections.emptyList();
+ }
+
+ final Calendar start = Calendar.getInstance();
+ start.setTimeInMillis(TimeBucket.getTimestamp(request.getStartTimeBucket(), DownSampling.Hour));
+
+ final Calendar end = Calendar.getInstance();
+ end.setTimeInMillis(TimeBucket.getTimestamp(request.getEndTimeBucket(), DownSampling.Hour));
+
+ final ArrayList result = new ArrayList<>();
+ while (start.getTimeInMillis() <= end.getTimeInMillis()) {
+ result.add(TimeBucket.getTimeBucket(start.getTimeInMillis(), DownSampling.Hour));
+ start.add(Calendar.HOUR, 1);
+ }
+ return result;
+ }
+
+ @Data
+ @Builder
+ private static class MetricConfig {
+ private boolean single;
+ private MetricsValueConfig singleValue;
+ private Map multiValue;
+
+ public org.apache.skywalking.apm.baseline.v3.AlarmBaselinePredicatedValue generate(long timeBucket) {
+ if (single) {
+ return org.apache.skywalking.apm.baseline.v3.AlarmBaselinePredicatedValue.newBuilder()
+ .setTimeBucket(timeBucket)
+ .setSingleValue(org.apache.skywalking.apm.baseline.v3.AlarmBaselineSingleValue.newBuilder().setValue(singleValue.generateValue()))
+ .build();
+ }
+
+ final org.apache.skywalking.apm.baseline.v3.AlarmBaselinePredicatedValue.Builder builder = org.apache.skywalking.apm.baseline.v3.AlarmBaselinePredicatedValue.newBuilder();
+ builder.setTimeBucket(timeBucket);
+ builder.setLabeledValue(AlarmBaselineLabeledValue.newBuilder()
+ .addAllValues(multiValue.entrySet().stream()
+ .map(e -> AlarmBaselineLabeledValue.LabelWithValue.newBuilder()
+ .addLabels(e.getKey())
+ .setValue(e.getValue().generateValue())
+ .build())
+ .collect(Collectors.toList()))
+ .build());
+ return builder.build();
+ }
+ }
+
+ @Data
+ @Builder
+ private static class MetricsValueConfig {
+ private long minValue;
+ private long maxValue;
+
+ public AlarmBaselineValue generateValue() {
+ final AlarmBaselineValue.Builder valueBuilder = AlarmBaselineValue.newBuilder();
+ valueBuilder.setLowerValue(generateRandomValue(minValue, maxValue));
+ valueBuilder.setUpperValue(generateRandomValue(valueBuilder.getLowerValue(), maxValue));
+ valueBuilder.setValue(generateRandomValue(valueBuilder.getLowerValue(), valueBuilder.getUpperValue()));
+ return valueBuilder.build();
+ }
+ }
+
+ private static long generateRandomValue(long minValue, long maxValue) {
+ int range = Math.toIntExact(maxValue - minValue);
+ return minValue + RANDOM.nextInt(range);
+ }
+}
diff --git a/oap-server/ai-pipeline/src/test/java/BaselineServerTest.java b/oap-server/ai-pipeline/src/test/java/BaselineServerTest.java
new file mode 100644
index 000000000000..2685a849af79
--- /dev/null
+++ b/oap-server/ai-pipeline/src/test/java/BaselineServerTest.java
@@ -0,0 +1,105 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+import io.grpc.ManagedChannel;
+import io.grpc.Server;
+import io.grpc.inprocess.InProcessChannelBuilder;
+import io.grpc.inprocess.InProcessServerBuilder;
+import io.grpc.util.MutableHandlerRegistry;
+import lombok.extern.slf4j.Slf4j;
+import org.apache.skywalking.oap.server.ai.pipeline.services.BaselineQueryServiceImpl;
+import org.apache.skywalking.oap.server.ai.pipeline.services.PredictServiceMetrics;
+import org.apache.skywalking.oap.server.ai.pipeline.services.ServiceMetrics;
+import org.apache.skywalking.oap.server.core.analysis.DownSampling;
+import org.apache.skywalking.oap.server.core.analysis.TimeBucket;
+import org.junit.jupiter.api.AfterEach;
+import org.junit.jupiter.api.BeforeEach;
+import org.junit.jupiter.api.Test;
+import org.powermock.reflect.Whitebox;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.List;
+import java.util.UUID;
+import java.util.concurrent.TimeUnit;
+
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+
+@Slf4j
+public class BaselineServerTest {
+ private Server server;
+ private ManagedChannel channel;
+ private MutableHandlerRegistry serviceRegistry;
+ private BaselineQueryServiceImpl queryService;
+
+ @BeforeEach
+ public void before() throws IOException {
+ serviceRegistry = new MutableHandlerRegistry();
+ final String name = UUID.randomUUID().toString();
+ InProcessServerBuilder serverBuilder =
+ InProcessServerBuilder
+ .forName(name)
+ .fallbackHandlerRegistry(serviceRegistry);
+ serverBuilder.addService(new BaselineQueryServer());
+ server = serverBuilder.build();
+ server.start();
+
+ channel = InProcessChannelBuilder.forName(name).build();
+
+ queryService = new BaselineQueryServiceImpl("", 0);
+ org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceGrpc.AlarmBaselineServiceBlockingStub blockingStub = org.apache.skywalking.apm.baseline.v3.AlarmBaselineServiceGrpc.newBlockingStub(channel);
+ Whitebox.setInternalState(queryService, "stub", blockingStub);
+ }
+
+ @AfterEach
+ public void after() {
+ channel.shutdown();
+ server.shutdown();
+
+ try {
+ channel.awaitTermination(1L, TimeUnit.MINUTES);
+ server.awaitTermination(1L, TimeUnit.MINUTES);
+ } catch (InterruptedException e) {
+ Thread.currentThread().interrupt();
+ throw new RuntimeException(e);
+ } finally {
+ channel.shutdownNow();
+ channel = null;
+ server.shutdownNow();
+ server = null;
+ }
+ }
+
+ @Test
+ public void queryServices() throws Exception {
+ final List metrics = queryService.queryPredictMetrics(Arrays.asList(ServiceMetrics.builder()
+ .serviceName("test")
+ .metricsNames(Arrays.asList("service_cpm")).build()),
+ TimeBucket.getTimeBucket(System.currentTimeMillis() - TimeUnit.HOURS.toMillis(4), DownSampling.Hour),
+ TimeBucket.getTimeBucket(System.currentTimeMillis(), DownSampling.Hour)
+ );
+ assertNotNull(metrics);
+ }
+
+ @Test
+ public void queryMetricsNames() {
+ final List metrics = queryService.querySupportedMetrics();
+ assertNotNull(metrics);
+ }
+
+}
diff --git a/oap-server/analyzer/agent-analyzer/pom.xml b/oap-server/analyzer/agent-analyzer/pom.xml
new file mode 100644
index 000000000000..b4b96cd62eb8
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/pom.xml
@@ -0,0 +1,47 @@
+
+
+
+
+
+ analyzer
+ org.apache.skywalking
+ ${revision}
+
+ 4.0.0
+
+ agent-analyzer
+ jar
+
+
+ org.apache.skywalking
+ configuration-api
+ ${project.version}
+
+
+ org.apache.skywalking
+ server-core
+ ${project.version}
+
+
+ org.apache.skywalking
+ meter-analyzer
+ ${project.version}
+
+
+
\ No newline at end of file
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/module/AnalyzerModule.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/module/AnalyzerModule.java
new file mode 100644
index 000000000000..a406b4b2fb21
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/module/AnalyzerModule.java
@@ -0,0 +1,39 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.module;
+
+import org.apache.skywalking.oap.server.analyzer.provider.meter.process.IMeterProcessService;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.ISegmentParserService;
+import org.apache.skywalking.oap.server.library.module.ModuleDefine;
+
+public class AnalyzerModule extends ModuleDefine {
+ public static final String NAME = "agent-analyzer";
+
+ public AnalyzerModule() {
+ super(NAME);
+ }
+
+ @Override
+ public Class[] services() {
+ return new Class[] {
+ ISegmentParserService.class,
+ IMeterProcessService.class
+ };
+ }
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleConfig.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleConfig.java
new file mode 100644
index 000000000000..db6b38b4bd0d
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleConfig.java
@@ -0,0 +1,164 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider;
+
+import com.google.common.base.Splitter;
+import lombok.Getter;
+import lombok.Setter;
+import lombok.extern.slf4j.Slf4j;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.CacheReadLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.CacheWriteLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.DBLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.TraceSamplingPolicyWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.UninstrumentedGatewaysConfig;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.strategy.SegmentStatusStrategy;
+import org.apache.skywalking.oap.server.core.Const;
+import org.apache.skywalking.oap.server.library.module.ModuleConfig;
+
+import java.util.ArrayList;
+import java.util.List;
+
+import static org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.strategy.SegmentStatusStrategy.FROM_SPAN_STATUS;
+
+@Slf4j
+public class AnalyzerModuleConfig extends ModuleConfig {
+ /**
+ * The sample policy setting file
+ */
+ @Setter
+ @Getter
+ private String traceSamplingPolicySettingsFile;
+ /**
+ * Some of the agent can not have the upstream real network address, such as https://github.com/apache/skywalking-nginx-lua.
+ * service instance mapping and service instance client side relation are ignored.
+ *
+ * Read component-libraries.yml for more details.
+ */
+ @Getter
+ private String noUpstreamRealAddressAgents = Const.EMPTY_STRING;
+ /**
+ * The threshold used to check the slow database access. Unit, millisecond.
+ */
+ @Setter
+ @Getter
+ private String slowDBAccessThreshold = "default:200";
+ @Setter
+ @Getter
+ private DBLatencyThresholdsAndWatcher dbLatencyThresholdsAndWatcher;
+
+ @Setter
+ @Getter
+ private String slowCacheWriteThreshold = "default:20,redis:10";
+
+ @Setter
+ @Getter
+ private CacheWriteLatencyThresholdsAndWatcher cacheWriteLatencyThresholdsAndWatcher;
+
+ @Setter
+ @Getter
+ private String slowCacheReadThreshold = "default:20,redis:10";
+
+ @Setter
+ @Getter
+ private CacheReadLatencyThresholdsAndWatcher cacheReadLatencyThresholdsAndWatcher;
+
+ @Setter
+ @Getter
+ private UninstrumentedGatewaysConfig uninstrumentedGatewaysConfig;
+ @Setter
+ @Getter
+ private TraceSamplingPolicyWatcher traceSamplingPolicyWatcher;
+ /**
+ * Analysis trace status.
+ *
+ * 1. Default(YES) means analysis all metrics from trace.
+ *
+ * 2. NO means, only save trace, but metrics come other places, such as service mesh.
+ */
+ @Setter
+ @Getter
+ private boolean traceAnalysis = true;
+ /**
+ * Slow Sql string length can't beyond this limit. This value should be as same as the length annotation at the
+ * {@code org.apache.skywalking.oap.server.core.analysis.manual.database.TopNDatabaseStatement#statement}. And share
+ * the system env name, SW_SLOW_DB_THRESHOLD
+ */
+ @Setter
+ @Getter
+ private int maxSlowSQLLength = 2000;
+
+ @Getter
+ private final String configPath = "meter-analyzer-config";
+
+ /**
+ * Which files could be meter analyzed, files split by ","
+ */
+ @Setter
+ private String meterAnalyzerActiveFiles = Const.EMPTY_STRING;
+
+ /**
+ * Sample the trace segment if the segment has span(s) tagged as error status, and ignore the sampleRate
+ * configuration.
+ */
+ @Setter
+ @Getter
+ private boolean forceSampleErrorSegment = true;
+
+ /**
+ * Determine the final segment status from the status of spans.
+ *
+ * @see SegmentStatusStrategy
+ */
+ @Setter
+ @Getter
+ private String segmentStatusAnalysisStrategy = FROM_SPAN_STATUS.name();
+
+ private List virtualPeers;
+
+ /**
+ * @param componentId of the exit span
+ * @return true, means should not generate the instance relationship for the client-side exit span.
+ */
+ public boolean shouldIgnorePeerIPDue2Virtual(int componentId) {
+ if (virtualPeers == null) {
+ virtualPeers = new ArrayList<>(20);
+ for (final String component : noUpstreamRealAddressAgents.split(",")) {
+ try {
+ virtualPeers.add(Integer.parseInt(component));
+ } catch (NumberFormatException e) {
+ log.warn("noUpstreamRealAddressAgents config {} includes illegal value {}",
+ noUpstreamRealAddressAgents, component
+ );
+ }
+ }
+ }
+ return virtualPeers.contains(componentId);
+ }
+
+ /**
+ * Get all files could be meter analyzed, files split by ","
+ */
+ public List meterAnalyzerActiveFileNames() {
+ if (StringUtils.isEmpty(this.meterAnalyzerActiveFiles)) {
+ return null;
+ }
+ return Splitter.on(",").splitToList(this.meterAnalyzerActiveFiles);
+ }
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleProvider.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleProvider.java
new file mode 100644
index 000000000000..0c19854bb0fd
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/AnalyzerModuleProvider.java
@@ -0,0 +1,167 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider;
+
+import java.util.List;
+import lombok.Getter;
+import org.apache.skywalking.oap.server.analyzer.module.AnalyzerModule;
+import org.apache.skywalking.oap.server.analyzer.provider.meter.config.MeterConfig;
+import org.apache.skywalking.oap.server.analyzer.provider.meter.config.MeterConfigs;
+import org.apache.skywalking.oap.server.analyzer.provider.meter.process.IMeterProcessService;
+import org.apache.skywalking.oap.server.analyzer.provider.meter.process.MeterProcessService;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.CacheReadLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.CacheWriteLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.DBLatencyThresholdsAndWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.TraceSamplingPolicyWatcher;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.UninstrumentedGatewaysConfig;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.ISegmentParserService;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.SegmentParserListenerManager;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.SegmentParserServiceImpl;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.EndpointDepFromCrossThreadAnalysisListener;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.NetworkAddressAliasMappingListener;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.RPCAnalysisListener;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.SegmentAnalysisListener;
+import org.apache.skywalking.oap.server.analyzer.provider.trace.parser.listener.VirtualServiceAnalysisListener;
+import org.apache.skywalking.oap.server.configuration.api.ConfigurationModule;
+import org.apache.skywalking.oap.server.configuration.api.DynamicConfigurationService;
+import org.apache.skywalking.oap.server.core.CoreModule;
+import org.apache.skywalking.oap.server.core.oal.rt.CoreOALDefine;
+import org.apache.skywalking.oap.server.core.oal.rt.OALEngineLoaderService;
+import org.apache.skywalking.oap.server.library.module.ModuleDefine;
+import org.apache.skywalking.oap.server.library.module.ModuleProvider;
+import org.apache.skywalking.oap.server.library.module.ModuleStartException;
+import org.apache.skywalking.oap.server.library.module.ServiceNotProvidedException;
+import org.apache.skywalking.oap.server.telemetry.TelemetryModule;
+
+public class AnalyzerModuleProvider extends ModuleProvider {
+ @Getter
+ private AnalyzerModuleConfig moduleConfig;
+ @Getter
+ private DBLatencyThresholdsAndWatcher dbLatencyThresholdsAndWatcher;
+ private CacheReadLatencyThresholdsAndWatcher cacheReadLatencyThresholdsAndWatcher;
+ private CacheWriteLatencyThresholdsAndWatcher cacheWriteLatencyThresholdsAndWatcher;
+ @Getter
+ private UninstrumentedGatewaysConfig uninstrumentedGatewaysConfig;
+ @Getter
+ private SegmentParserServiceImpl segmentParserService;
+ @Getter
+ private TraceSamplingPolicyWatcher traceSamplingPolicyWatcher;
+
+ private List meterConfigs;
+ @Getter
+ private MeterProcessService processService;
+
+ @Override
+ public String name() {
+ return "default";
+ }
+
+ @Override
+ public Class module() {
+ return AnalyzerModule.class;
+ }
+
+ @Override
+ public ConfigCreator newConfigCreator() {
+ return new ConfigCreator() {
+ @Override
+ public Class type() {
+ return AnalyzerModuleConfig.class;
+ }
+
+ @Override
+ public void onInitialized(final AnalyzerModuleConfig initialized) {
+ moduleConfig = initialized;
+ }
+ };
+ }
+
+ @Override
+ public void prepare() throws ServiceNotProvidedException, ModuleStartException {
+ dbLatencyThresholdsAndWatcher = new DBLatencyThresholdsAndWatcher(moduleConfig.getSlowDBAccessThreshold(), this);
+ uninstrumentedGatewaysConfig = new UninstrumentedGatewaysConfig(this);
+ traceSamplingPolicyWatcher = new TraceSamplingPolicyWatcher(moduleConfig, this);
+ cacheReadLatencyThresholdsAndWatcher = new CacheReadLatencyThresholdsAndWatcher(moduleConfig.getSlowCacheReadThreshold(), this);
+ cacheWriteLatencyThresholdsAndWatcher = new CacheWriteLatencyThresholdsAndWatcher(moduleConfig.getSlowCacheWriteThreshold(), this);
+
+ moduleConfig.setDbLatencyThresholdsAndWatcher(dbLatencyThresholdsAndWatcher);
+ moduleConfig.setUninstrumentedGatewaysConfig(uninstrumentedGatewaysConfig);
+ moduleConfig.setTraceSamplingPolicyWatcher(traceSamplingPolicyWatcher);
+ moduleConfig.setCacheReadLatencyThresholdsAndWatcher(cacheReadLatencyThresholdsAndWatcher);
+ moduleConfig.setCacheWriteLatencyThresholdsAndWatcher(cacheWriteLatencyThresholdsAndWatcher);
+
+ segmentParserService = new SegmentParserServiceImpl(getManager(), moduleConfig);
+ this.registerServiceImplementation(ISegmentParserService.class, segmentParserService);
+
+ meterConfigs = MeterConfigs.loadConfig(
+ moduleConfig.getConfigPath(), moduleConfig.meterAnalyzerActiveFileNames());
+ processService = new MeterProcessService(getManager());
+ this.registerServiceImplementation(IMeterProcessService.class, processService);
+ }
+
+ @Override
+ public void start() throws ModuleStartException {
+ // load official analysis
+ getManager().find(CoreModule.NAME)
+ .provider()
+ .getService(OALEngineLoaderService.class)
+ .load(CoreOALDefine.INSTANCE);
+
+ DynamicConfigurationService dynamicConfigurationService = getManager().find(ConfigurationModule.NAME)
+ .provider()
+ .getService(
+ DynamicConfigurationService.class);
+ dynamicConfigurationService.registerConfigChangeWatcher(dbLatencyThresholdsAndWatcher);
+ dynamicConfigurationService.registerConfigChangeWatcher(uninstrumentedGatewaysConfig);
+ dynamicConfigurationService.registerConfigChangeWatcher(traceSamplingPolicyWatcher);
+ dynamicConfigurationService.registerConfigChangeWatcher(cacheReadLatencyThresholdsAndWatcher);
+ dynamicConfigurationService.registerConfigChangeWatcher(cacheWriteLatencyThresholdsAndWatcher);
+
+ segmentParserService.setListenerManager(listenerManager());
+
+ processService.start(meterConfigs);
+ }
+
+ @Override
+ public void notifyAfterCompleted() {
+
+ }
+
+ @Override
+ public String[] requiredModules() {
+ return new String[] {
+ TelemetryModule.NAME,
+ CoreModule.NAME,
+ ConfigurationModule.NAME
+ };
+ }
+
+ private SegmentParserListenerManager listenerManager() {
+ SegmentParserListenerManager listenerManager = new SegmentParserListenerManager();
+ if (moduleConfig.isTraceAnalysis()) {
+ listenerManager.add(new RPCAnalysisListener.Factory(getManager()));
+ listenerManager.add(new EndpointDepFromCrossThreadAnalysisListener.Factory(getManager()));
+ listenerManager.add(new NetworkAddressAliasMappingListener.Factory(getManager()));
+ }
+ listenerManager.add(new SegmentAnalysisListener.Factory(getManager(), moduleConfig));
+ listenerManager.add(new VirtualServiceAnalysisListener.Factory(getManager()));
+
+ return listenerManager;
+ }
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/jvm/JVMSourceDispatcher.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/jvm/JVMSourceDispatcher.java
new file mode 100644
index 000000000000..bf7139014a04
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/jvm/JVMSourceDispatcher.java
@@ -0,0 +1,242 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider.jvm;
+
+import java.util.List;
+import lombok.extern.slf4j.Slf4j;
+import org.apache.skywalking.apm.network.common.v3.CPU;
+import org.apache.skywalking.apm.network.language.agent.v3.Class;
+import org.apache.skywalking.apm.network.language.agent.v3.GC;
+import org.apache.skywalking.apm.network.language.agent.v3.JVMMetric;
+import org.apache.skywalking.apm.network.language.agent.v3.Memory;
+import org.apache.skywalking.apm.network.language.agent.v3.MemoryPool;
+import org.apache.skywalking.apm.network.language.agent.v3.Thread;
+import org.apache.skywalking.oap.server.core.CoreModule;
+import org.apache.skywalking.oap.server.core.analysis.IDManager;
+import org.apache.skywalking.oap.server.core.analysis.TimeBucket;
+import org.apache.skywalking.oap.server.core.source.GCPhase;
+import org.apache.skywalking.oap.server.core.source.MemoryPoolType;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMCPU;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMClass;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMGC;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMMemory;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMMemoryPool;
+import org.apache.skywalking.oap.server.core.source.ServiceInstanceJVMThread;
+import org.apache.skywalking.oap.server.core.source.SourceReceiver;
+import org.apache.skywalking.oap.server.library.module.ModuleManager;
+
+@Slf4j
+public class JVMSourceDispatcher {
+ private final SourceReceiver sourceReceiver;
+
+ public JVMSourceDispatcher(ModuleManager moduleManager) {
+ this.sourceReceiver = moduleManager.find(CoreModule.NAME).provider().getService(SourceReceiver.class);
+ }
+
+ public void sendMetric(String service, String serviceInstance, JVMMetric metrics) {
+ long minuteTimeBucket = TimeBucket.getMinuteTimeBucket(metrics.getTime());
+
+ final String serviceId = IDManager.ServiceID.buildId(service, true);
+ final String serviceInstanceId = IDManager.ServiceInstanceID.buildId(serviceId, serviceInstance);
+
+ this.sendToCpuMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getCpu());
+ this.sendToMemoryMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getMemoryList());
+ this.sendToMemoryPoolMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getMemoryPoolList());
+ this.sendToGCMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getGcList());
+ this.sendToThreadMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getThread());
+ this.sendToClassMetricProcess(
+ service, serviceId, serviceInstance, serviceInstanceId, minuteTimeBucket, metrics.getClazz());
+ }
+
+ private void sendToCpuMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ CPU cpu) {
+ ServiceInstanceJVMCPU serviceInstanceJVMCPU = new ServiceInstanceJVMCPU();
+ serviceInstanceJVMCPU.setId(serviceInstanceId);
+ serviceInstanceJVMCPU.setName(serviceInstance);
+ serviceInstanceJVMCPU.setServiceId(serviceId);
+ serviceInstanceJVMCPU.setServiceName(service);
+ // If the cpu usage percent is less than 1, will set to 1
+ double adjustedCpuUsagePercent = Math.max(cpu.getUsagePercent(), 1.0);
+ serviceInstanceJVMCPU.setUsePercent(adjustedCpuUsagePercent);
+ serviceInstanceJVMCPU.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMCPU);
+ }
+
+ private void sendToGCMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ List gcs) {
+ gcs.forEach(gc -> {
+ ServiceInstanceJVMGC serviceInstanceJVMGC = new ServiceInstanceJVMGC();
+ serviceInstanceJVMGC.setId(serviceInstanceId);
+ serviceInstanceJVMGC.setName(serviceInstance);
+ serviceInstanceJVMGC.setServiceId(serviceId);
+ serviceInstanceJVMGC.setServiceName(service);
+
+ switch (gc.getPhase()) {
+ case NEW:
+ serviceInstanceJVMGC.setPhase(GCPhase.NEW);
+ break;
+ case OLD:
+ serviceInstanceJVMGC.setPhase(GCPhase.OLD);
+ break;
+ case NORMAL:
+ serviceInstanceJVMGC.setPhase(GCPhase.NORMAL);
+ break;
+ }
+
+ serviceInstanceJVMGC.setTime(gc.getTime());
+ serviceInstanceJVMGC.setCount(gc.getCount());
+ serviceInstanceJVMGC.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMGC);
+ });
+ }
+
+ private void sendToMemoryMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ List memories) {
+ memories.forEach(memory -> {
+ ServiceInstanceJVMMemory serviceInstanceJVMMemory = new ServiceInstanceJVMMemory();
+ serviceInstanceJVMMemory.setId(serviceInstanceId);
+ serviceInstanceJVMMemory.setName(serviceInstance);
+ serviceInstanceJVMMemory.setServiceId(serviceId);
+ serviceInstanceJVMMemory.setServiceName(service);
+ serviceInstanceJVMMemory.setHeapStatus(memory.getIsHeap());
+ serviceInstanceJVMMemory.setInit(memory.getInit());
+ serviceInstanceJVMMemory.setMax(memory.getMax());
+ serviceInstanceJVMMemory.setUsed(memory.getUsed());
+ serviceInstanceJVMMemory.setCommitted(memory.getCommitted());
+ serviceInstanceJVMMemory.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMMemory);
+ });
+ }
+
+ private void sendToMemoryPoolMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ List memoryPools) {
+
+ memoryPools.forEach(memoryPool -> {
+ ServiceInstanceJVMMemoryPool serviceInstanceJVMMemoryPool = new ServiceInstanceJVMMemoryPool();
+ serviceInstanceJVMMemoryPool.setId(serviceInstanceId);
+ serviceInstanceJVMMemoryPool.setName(serviceInstance);
+ serviceInstanceJVMMemoryPool.setServiceId(serviceId);
+ serviceInstanceJVMMemoryPool.setServiceName(service);
+
+ switch (memoryPool.getType()) {
+ case NEWGEN_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.NEWGEN_USAGE);
+ break;
+ case OLDGEN_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.OLDGEN_USAGE);
+ break;
+ case PERMGEN_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.PERMGEN_USAGE);
+ break;
+ case SURVIVOR_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.SURVIVOR_USAGE);
+ break;
+ case METASPACE_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.METASPACE_USAGE);
+ break;
+ case CODE_CACHE_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.CODE_CACHE_USAGE);
+ break;
+ case ZHEAP_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.ZHEAP_USAGE);
+ break;
+ case COMPRESSED_CLASS_SPACE_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.COMPRESSED_CLASS_SPACE_USAGE);
+ break;
+ case CODEHEAP_NON_NMETHODS_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.CODEHEAP_NON_NMETHODS_USAGE);
+ break;
+ case CODEHEAP_PROFILED_NMETHODS_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.CODEHEAP_PROFILED_NMETHODS_USAGE);
+ break;
+ case CODEHEAP_NON_PROFILED_NMETHODS_USAGE:
+ serviceInstanceJVMMemoryPool.setPoolType(MemoryPoolType.CODEHEAP_NON_PROFILED_NMETHODS_USAGE);
+ break;
+ }
+
+ serviceInstanceJVMMemoryPool.setInit(memoryPool.getInit());
+ serviceInstanceJVMMemoryPool.setMax(memoryPool.getMax());
+ serviceInstanceJVMMemoryPool.setUsed(memoryPool.getUsed());
+ serviceInstanceJVMMemoryPool.setCommitted(memoryPool.getCommitted());
+ serviceInstanceJVMMemoryPool.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMMemoryPool);
+ });
+ }
+
+ private void sendToThreadMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ Thread thread) {
+ ServiceInstanceJVMThread serviceInstanceJVMThread = new ServiceInstanceJVMThread();
+ serviceInstanceJVMThread.setId(serviceInstanceId);
+ serviceInstanceJVMThread.setName(serviceInstance);
+ serviceInstanceJVMThread.setServiceId(serviceId);
+ serviceInstanceJVMThread.setServiceName(service);
+ serviceInstanceJVMThread.setLiveCount(thread.getLiveCount());
+ serviceInstanceJVMThread.setDaemonCount(thread.getDaemonCount());
+ serviceInstanceJVMThread.setPeakCount(thread.getPeakCount());
+ serviceInstanceJVMThread.setRunnableStateThreadCount(thread.getRunnableStateThreadCount());
+ serviceInstanceJVMThread.setBlockedStateThreadCount(thread.getBlockedStateThreadCount());
+ serviceInstanceJVMThread.setWaitingStateThreadCount(thread.getWaitingStateThreadCount());
+ serviceInstanceJVMThread.setTimedWaitingStateThreadCount(thread.getTimedWaitingStateThreadCount());
+ serviceInstanceJVMThread.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMThread);
+ }
+
+ private void sendToClassMetricProcess(String service,
+ String serviceId,
+ String serviceInstance,
+ String serviceInstanceId,
+ long timeBucket,
+ Class clazz) {
+ ServiceInstanceJVMClass serviceInstanceJVMClass = new ServiceInstanceJVMClass();
+ serviceInstanceJVMClass.setId(serviceInstanceId);
+ serviceInstanceJVMClass.setName(serviceInstance);
+ serviceInstanceJVMClass.setServiceId(serviceId);
+ serviceInstanceJVMClass.setServiceName(service);
+ serviceInstanceJVMClass.setLoadedClassCount(clazz.getLoadedClassCount());
+ serviceInstanceJVMClass.setTotalUnloadedClassCount(clazz.getTotalUnloadedClassCount());
+ serviceInstanceJVMClass.setTotalLoadedClassCount(clazz.getTotalLoadedClassCount());
+ serviceInstanceJVMClass.setTimeBucket(timeBucket);
+ sourceReceiver.receive(serviceInstanceJVMClass);
+ }
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfig.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfig.java
new file mode 100644
index 000000000000..4bc3bec8c7bb
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfig.java
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider.meter.config;
+
+import lombok.Data;
+import lombok.NoArgsConstructor;
+import org.apache.skywalking.oap.meter.analyzer.MetricRuleConfig;
+
+import java.util.List;
+
+@Data
+@NoArgsConstructor
+public class MeterConfig implements MetricRuleConfig {
+ private String metricPrefix;
+ private String expSuffix;
+ private String expPrefix;
+ private String filter;
+ private List metricsRules;
+ private String initExp;
+
+ @Data
+ @NoArgsConstructor
+ public static class Rule implements RuleConfig {
+ private String name;
+ private String exp;
+ }
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfigs.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfigs.java
new file mode 100644
index 000000000000..b1eff96fbcba
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/config/MeterConfigs.java
@@ -0,0 +1,78 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider.meter.config;
+
+import lombok.extern.slf4j.Slf4j;
+import org.apache.skywalking.oap.server.library.module.ModuleStartException;
+import org.apache.skywalking.oap.server.library.util.CollectionUtils;
+import org.apache.skywalking.oap.server.library.util.ResourceUtils;
+import org.yaml.snakeyaml.Yaml;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.io.FileReader;
+import java.io.IOException;
+import java.io.Reader;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.List;
+import java.util.Objects;
+import java.util.stream.Collectors;
+
+/**
+ * Meter config loader.
+ */
+@Slf4j
+public class MeterConfigs {
+
+ /**
+ * Load all configs from path
+ */
+ public static List loadConfig(String path, List fileNames) throws ModuleStartException {
+ if (CollectionUtils.isEmpty(fileNames)) {
+ return Collections.emptyList();
+ }
+
+ File[] configs;
+ try {
+ configs = ResourceUtils.getPathFiles(path);
+ } catch (FileNotFoundException e) {
+ throw new ModuleStartException("Load meter configs failed", e);
+ }
+
+ return Arrays.stream(configs)
+ .map(f -> {
+ String fileName = f.getName();
+ int dotIndex = fileName.lastIndexOf('.');
+ fileName = (dotIndex == -1) ? fileName : fileName.substring(0, dotIndex);
+ if (!fileNames.contains(fileName)) {
+ return null;
+ }
+ try (Reader r = new FileReader(f)) {
+ return new Yaml().loadAs(r, MeterConfig.class);
+ } catch (IOException e) {
+ log.warn("Reading file {} failed", f, e);
+ }
+ return null;
+ })
+ .filter(Objects::nonNull)
+ .collect(Collectors.toList());
+ }
+
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/IMeterProcessService.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/IMeterProcessService.java
new file mode 100644
index 000000000000..13944d4a5745
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/IMeterProcessService.java
@@ -0,0 +1,27 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider.meter.process;
+
+import org.apache.skywalking.oap.server.library.module.Service;
+
+public interface IMeterProcessService extends Service {
+
+ MeterProcessor createProcessor();
+
+}
diff --git a/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/MeterProcessService.java b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/MeterProcessService.java
new file mode 100644
index 000000000000..e3f30c96804d
--- /dev/null
+++ b/oap-server/analyzer/agent-analyzer/src/main/java/org/apache/skywalking/oap/server/analyzer/provider/meter/process/MeterProcessService.java
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.skywalking.oap.server.analyzer.provider.meter.process;
+
+import org.apache.skywalking.oap.meter.analyzer.MetricConvert;
+import org.apache.skywalking.oap.server.analyzer.provider.meter.config.MeterConfig;
+import org.apache.skywalking.oap.server.core.CoreModule;
+import org.apache.skywalking.oap.server.core.analysis.meter.MeterSystem;
+import org.apache.skywalking.oap.server.library.module.ModuleManager;
+
+import java.util.List;
+import java.util.stream.Collectors;
+
+/**
+ * Management all of the meter builders.
+ */
+public class MeterProcessService implements IMeterProcessService {
+
+ private final ModuleManager manager;
+ private List metricConverts;
+
+ public MeterProcessService(ModuleManager manager) {
+ this.manager = manager;
+ }
+
+ public void start(List
+
+ Thank you for finding the time to report the problem! We really appreciate the community efforts to improve SkyWalking.
+
+ Please make sure what you are reporting is indeed a bug with reproducible steps, if you want to ask questions
+ or share ideas, please [subscribe to our mailing list](mailto:dev-subscribe@skywalking.apache.org) and sent
+ emails to [our mailing list](mailto:dev@skywalking.apache.org), you can also head to our
+ [Discussion](https://github.com/apache/skywalking/discussions) tab.
+
+ - type: checkboxes
+ attributes:
+ label: Search before asking
+ description: >
+ Please make sure to search in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) first to see
+ whether the same issue was reported already.
+ options:
+ - label: >
+ I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar
+ issues.
+ required: true
+
+ - type: dropdown
+ attributes:
+ label: Apache SkyWalking Component
+ description: |
+ What Apache SkyWalking component are you using? Apache SkyWalking has many subprojects, please make sure
+ to choose the component that you found the bug. For non-Apache community projects, please refer to their
+ corresponding repos.
+ multiple: false
+ options:
+ - "OAP server (apache/skywalking)"
+ - "UI (apache/skywalking-booster-ui)"
+ - "Java Agent (apache/skywalking-java)"
+ - "Python Agent (apache/skywalking-python)"
+ - "NodeJS Server Side Agent (apache/skywalking-nodejs)"
+ - "NodeJS Client Side Agent (apache/skywalking-client-js)"
+ - "Nginx Lua Agent (apache/skywalking-nginx-lua)"
+ - "Kong Agent (apache/skywalking-kong)"
+ - "Go Agent (apache/skywalking-go)"
+ - "PHP (apache/skywalking-php)"
+ - "Rust (apache/skywalking-rust)"
+ - "Satellite (apache/skywalking-satellite)"
+ - "CLI (apache/skywalking-cli)"
+ - "Helm Chart (apache/skywalking-helm)"
+ - "SWCK (apache/skywalking-swck)"
+ - "License Tools (apache/skywalking-eyes)"
+ - "Infra E2E (apache/skywalking-infra-e2e)"
+ - "BanyanDB (apache/skywalking-banyandb)"
+ - "Agent Test Tool (apache/skywalking-agent-test-tool)"
+ - "Showcase (apache/skywalking-showcase)"
+ validations:
+ required: true
+
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened
+ validations:
+ required: true
+
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy and paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems. You can include files by dragging and dropping them here.
+
+ **NOTE**: please copy and paste texts instead of taking screenshots of them for easy future search.
+ validations:
+ required: true
+
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/skywalking/discussions) instead.
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your deployment.
+ Remember that non-reproducible issues will be closed! Opening a discussion is recommended as a
+ first step.
+ validations:
+ required: true
+
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? (Once? Every time? Only when certain conditions are met?)
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a collapsable details tag if it's too long:
+ 
+
+**SkyWalking**: an APM (Application Performance Monitoring) system, especially designed for
+microservices, cloud native and container-based architectures.
+
+[](https://github.com/apache/skywalking)
+[](https://x.com/AsfSkyWalking)
+
+
+
+# Abstract
+**SkyWalking** is an open-source APM system that provides monitoring, tracing and diagnosing capabilities for distributed systems in Cloud Native architectures.
+
+
+* Distributed Tracing
+ * End-to-end distributed tracing. Service topology analysis, service-centric observability and APIs dashboards.
+* Agents for your stack
+ * Java, .Net Core, PHP, NodeJS, Golang, LUA, Rust, C++, Client JavaScript and Python agents with active development and maintenance.
+* eBPF early adoption
+ * Rover agent works as a monitor and profiler powered by eBPF to monitor Kubernetes deployments and diagnose CPU and network performance.
+* Scaling
+ * 100+ billion telemetry data could be collected and analyzed from one SkyWalking cluster.
+* Mature Telemetry Ecosystems Supported
+ * Metrics, Traces, and Logs from mature ecosystems are supported, e.g. Zipkin, OpenTelemetry, Prometheus, Zabbix, Fluentd
+* Native APM Database
+ * BanyanDB, an observability database, created in 2022, aims to ingest, analyze and store telemetry/observability data.
+* Consistent Metrics Aggregation
+ * SkyWalking native meter format and widely known metrics format(OpenTelemetry, Telegraf, Zabbix, e.g.) are processed through the same script pipeline.
+* Log Management Pipeline
+ * Support log formatting, extract metrics, various sampling policies through script pipeline in high performance.
+* Alerting and Telemetry Pipelines
+ * Support service-centric, deployment-centric, API-centric alarm rule setting. Support forwarding alarms and all telemetry data to 3rd party.
+* AI Power Enabled
+ * Machine Learning (ML) and Artificial Intelligence (AI) analyze observability data to identify patterns and enhance capabilities, such as recognizing HTTP URI patterns and automatically calculating metric baselines for intelligent alerting, improving anomaly detection.
+
+
+
+# Live Demo
+- Find the [SkyWalking live demo with native UI and Grafana](https://skywalking.apache.org/#demo), and [screenshots](https://skywalking.apache.org/#arch) on our website.
+- Follow the [showcase](https://skywalking.apache.org/docs/skywalking-showcase/next/readme/) to set up a preview deployment quickly.
+
+# Documentation
+- [Official documentation](https://skywalking.apache.org/docs/#SkyWalking)
+
+# Downloads
+Please head to the [releases page](https://skywalking.apache.org/downloads/) to download a release of Apache SkyWalking.
+
+# Compiling project
+Follow this [document](docs/en/guides/How-to-build.md).
+
+# Code of conduct
+This project adheres to the Contributor Covenant [code of conduct](https://www.apache.org/foundation/policies/conduct). By participating, you are expected to uphold this code.
+Please follow the [REPORTING GUIDELINES](https://www.apache.org/foundation/policies/conduct#reporting-guidelines) to report unacceptable behavior.
+
+# Contact Us
+* Mail list: **dev@skywalking.apache.org**. Mail to `dev-subscribe@skywalking.apache.org`, follow the reply to subscribe the mail list.
+* Send `Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
+* For Chinese speaker, send `[CN] Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
+* Twitter, [ASFSkyWalking](https://twitter.com/AsfSkyWalking)
+* [bilibili B站 视频](https://space.bilibili.com/390683219)
+* [掘金](https://juejin.cn/user/13673577331607/posts)
+
+# Our Users
+Hundreds of companies and organizations use SkyWalking for research, production, and commercial purposes.
+Visit our [website](http://skywalking.apache.org/users/) to find the user page.
+
+# License
+[Apache 2.0 License.](LICENSE)
diff --git a/apm-checkstyle/checkStyle.xml b/apm-checkstyle/checkStyle.xml
new file mode 100755
index 000000000000..096680e7b602
--- /dev/null
+++ b/apm-checkstyle/checkStyle.xml
@@ -0,0 +1,118 @@
+
+
+
+
+
+
+Here's what we think.
+
+### Is MQ appropriate for communicating with the OAP backend?
+This question arises when users consider the circumstances where the OAP cluster may not be powerful enough or becomes offline.
+But the following issues must first be addressed:
+1. Why do you think that the OAP is not powerful enough? Were it not powerful, the speed of data analysis wouldn't have caught up with the producers (or agents). Then what is the point of adding new deployment requirements?
+1. Some may argue that the payload is sometimes higher than usual during peak times. But we must consider how much higher the payload really is.
+1. If it is higher by less than 40%, how many resources would you use for the new MQ cluster? How about moving them to new OAP and ES nodes?
+1. Say it is higher by 40% or more, such as by 70% to 200%. Then, it is likely that your MQ would use up more resources than it saves.
+Your MQ would support 2 to 3 times the payload using 10%-20% of the cost during usual times. Furthermore, in this case,
+if the payload/throughput are so high, how long would it take for the OAP cluster to catch up? The challenge here is that well before it catches up, the next peak times would have come.
+
+With the analysis above in mind, why would you still want the traces to be 100%, given the resources they would cost?
+The preferred way to do this would be adding a better dynamic trace sampling mechanism at the backend. When throughput exceeds the threshold, gradually modify the active sampling rate from 100% to 10%, which means you could get the OAP and ES 3 times more powerful than usual, while ignoring the traces at peak times.
+
+### Is MQ transport recommended despite its side effects?
+Even though MQ transport is not recommended from the production perspective, SkyWalking still provides optional plugins named
+`kafka-reporter` and `kafka-fetcher` for this feature since 8.1.0.
+
+### How about MQ metrics data exporter?
+Log and trace exporters are using MQ as transport channel. And metrics exporter uses gRPC, as considering the scale.
diff --git a/docs/en/academy/diagnose-service-mesh-network-performance-with-ebpf.md b/docs/en/academy/diagnose-service-mesh-network-performance-with-ebpf.md
new file mode 100644
index 000000000000..34ef3b1f8b23
--- /dev/null
+++ b/docs/en/academy/diagnose-service-mesh-network-performance-with-ebpf.md
@@ -0,0 +1,256 @@
+# Diagnose Service Mesh Network Performance with eBPF
+
+## Background
+
+This article will show how to use [Apache SkyWalking](https://github.com/apache/skywalking) with [eBPF](https://ebpf.io/what-is-ebpf/) to make network troubleshooting easier in a service mesh environment.
+
+Apache SkyWalking is an application performance monitor tool for distributed systems. It observes metrics, logs, traces, and events in the service mesh environment and uses that data to generate a dependency graph of your pods and services. This dependency graph can provide quick insights into your system, especially when there's an issue.
+
+However, when troubleshooting network issues in SkyWalking's service topology, it is not always easy to pinpoint where the error actually is. There are two reasons for the difficulty:
+
+- **Traffic through the Envoy sidecar is not easy to observe.** Data from Envoy's [Access Log Service (ALS)](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/accesslog/v3/als.proto) shows traffic between services (sidecar-to-sidecar), but not metrics on communication between the Envoy sidecar and the service it proxies. Without that information, it is more difficult to understand the impact of the sidecar.
+- **There is a lack of data from transport layer (OSI Layer 4) communication.** Since services generally use application layer (OSI Layer 7) protocols such as HTTP, observability data is generally restricted to application layer communication. However, the root cause may actually be in the transport layer, which is typically opaque to observability tools.
+
+Access to metrics from Envoy-to-service and transport layer communication can make it easier to diagnose service issues. To this end, SkyWalking needs to collect and analyze transport layer metrics between processes inside Kubernetes pods - a task well suited to eBPF. We investigated using eBPF for this purpose and present our results and
+a demo below.
+
+## Monitoring Kubernetes Networks with eBPF
+
+With its origins as the Extended Berkeley Packet Filter, eBPF is a general purpose mechanism for injecting and running your own code into the Linux kernel and is an excellent tool for monitoring network traffic in Kubernetes Pods. In the next few sections, we\'ll provide an overview of how to use eBPF for network monitoring as background for introducing [Skywalking Rover](https://github.com/apache/skywalking-rover), a metrics collector and profiler powered by eBPF to diagnose CPU and network performance.
+
+### How Applications and the Network Interact
+
+Interactions between the application and the network can generally be
+divided into the following steps from higher to lower levels of
+abstraction:
+
+
+
+1. **User Code:** Application code uses high-level network libraries in the application stack to exchange data across the network, like sending and receiving HTTP requests.
+2. **Network Library:** When the network library receives a network request, it interacts with the language API to send the network data.
+3. **Language API:** Each language provides an API for operating the network, system, etc. When a request is received, it interacts with the system API. In Linux, this API is called syscalls.
+4. **Linux API:** When the Linux kernel receives the request through the API, it communicates with the socket to send the data, which is usually closer to an OSI Layer 4 protocol, such as TCP, UDP, etc.
+5. **Socket Ops:** Sending or receiving the data to/from the NIC.
+
+Our hypothesis is that eBPF can monitor the network. There are two ways
+to implement the interception: **User space (uprobe)** or **Kernel space
+(kprobe)**. The table below summarizes the differences.
+
+| | Pros | Cons |
+| ------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| uprobe | • Get more application-related contexts, such as whether the current request is HTTP or HTTPS.• Requests and responses can be intercepted by a single method | • Data structures can be unstable, so it is more difficult to get the desired data. • Implementation may differ between language/library versions. • Does not work in applications without [symbol tables](https://en.wikipedia.org/wiki/Symbol_table). |
+| kprobe | • Available for all languages. • The data structure and methods are stable and do not require much adaptation. • Easier correlation with underlying data, such as getting the destination address of TCP, OSI Layer 4 protocol metrics, etc. | • A single request and response may be split into multiple probes. • Contextual information is not easy to get for stateful requests. For example header compression in HTTP/2. |
+
+For the general network performance monitor, we chose to use the kprobe (intercept the syscalls) for the following reasons:
+
+1. It's available for applications written in any programming language, and it's stable, so it saves a lot of development/adaptation costs.
+2. It can be correlated with metrics from the system level, which makes it easier to troubleshoot.
+3. As a single request and response are split into multiple probes, we can use technology to correlate them.
+4. For contextual information, It's usually used in OSI Layer 7 protocol network analysis. So, if we just monitor the network performance, then they can be ignored.
+
+### Kprobes and network monitoring
+
+Following the [network syscalls of Linux documentation](http://linasm.sourceforge.net/docs/syscalls/network.php), we can implement network monitoring by intercepting two types of methods: **socket operations** and **send/receive** methods.
+
+#### Socket Operations
+
+When accepting or connecting with another socket, we can get the
+following information:
+
+1. **Connection information**: Includes the remote address from the connection which helps us to understand which pod is connected.
+2. **Connection statics:** Includes basic metrics from sockets, such as round-trip time ([RTT](https://en.wikipedia.org/wiki/Round-trip_delay)), lost packet count in TCP, etc.
+3. **Socket and file descriptor ([FD](https://en.wikipedia.org/wiki/File_descriptor)) mapping:** Includes the relationship between the Linux file descriptor and socket object. It is useful when sending and receiving data through a Linux file descriptor.
+
+#### Send/Receive
+
+The interface related to sending or receiving data is the focus of
+performance analysis. It mainly contains the following parameters:
+
+1. **Socket file descriptor:** The file descriptor of the current operation corresponding to the socket.
+2. **Buffer:** The data sent or received, passed as a byte array.
+
+Based on the above parameters, we can analyze the following data:
+
+1. **Bytes:** The size of the packet in bytes.
+2. **Protocol:** The protocol analysis according to the buffer data, such as HTTP, MySQL, etc.
+3. **Execution Time:** The time it takes to send/receive the data.
+
+At this point (Figure 1) we can analyze the following steps for the
+whole lifecycle of the connection:
+
+1. **Connect/Accept:** When the connection is created.
+2. **Transform:** Sending and receiving data on the connection.
+3. **Close:** When the connection is closed.
+
+
+
+***Figure 1***
+
+### Protocol and TLS
+
+The previous section described how to analyze connections using send or receive buffer data. For example, following the [HTTP/1.1 message specification](https://www.rfc-editor.org/rfc/rfc2068.html#section-4.1) to analyze the connection. However, this does not work for TLS requests/responses.
+
+
+
+***Figure 2***
+
+When TLS is in use, the Linux Kernel transmits data encrypted in user space. In the figure above, The application usually transmits SSL data through a third-party library (such as OpenSSL). For this case, the Linux API can only get the encrypted data, so it cannot recognize any higher layer protocol. To decrypt inside eBPF, we need to follow these steps:
+
+1. **Read unencrypted data through uprobe:** Compatible multiple languages, using uprobe to capture the data that is not encrypted before sending or after receiving. In this way, we can get the original data and associate it with the socket.
+2. **Associate with socket:** We can associate unencrypted data with the socket.
+
+#### OpenSSL Use case
+
+For example, the most common way to send/receive SSL data is to use OpenSSL as a shared library, specifically the [SSL_read](https://www.openssl.org/docs/man1.1.1/man3/SSL_read.html) and [SSL_write](https://www.openssl.org/docs/man1.1.1/man3/SSL_write.html) methods to submit the buffer data with the socket.
+
+Following the [documentation](https://www.openssl.org/docs/man1.1.1/man7/ssl.html), we can intercept these two methods, which are almost identical to the API in Linux. The source code of the SSL structure in OpenSSL shows that the [Socket FD](https://github.com/openssl/openssl/blob/9eae491721209f302a9a475bffd271370e8bcb8f/crypto/bio/bio_local.h#L115-L125) exists in the [BIO object of the SSL structure](https://github.com/openssl/openssl/blob/9eae491721209f302a9a475bffd271370e8bcb8f/ssl/ssl_local.h#L1068-L1083), and we can get it by the offset.
+
+In summary, with knowledge of how OpenSSL works, we can read unencrypted data in an eBPF function.
+
+## Introducing SkyWalking Rover, an eBPF-based Metrics Collector and Profiler
+
+[SkyWalking Rover](https://github.com/apache/skywalking-rover) introduces the eBPF network profiling feature into the SkyWalking ecosystem. It's currently supported in a Kubernetes environment, so must be deployed inside a Kubernetes cluster. Once the deployment is complete, SkyWalking Rover can monitor the network for all processes inside a given Pod. Based on the monitoring data, SkyWalking can generate the topology relationship diagram and metrics between processes.
+
+### Topology Diagram
+
+The topology diagram can help us understand the network access between processes inside the same Pod, and between the process and external environment (other Pod or service). Additionally, it can identify the data direction of traffic based on the line flow direction.
+
+In Figure 3 below, all nodes within the hexagon are the internal process of a Pod, and nodes outside the hexagon are externally associated services or Pods. Nodes are connected by lines, which indicate the direction of requests or responses between nodes (client or server). The protocol is indicated on the line, and it's either HTTP(S), TCP, or TCP(TLS). Also, we can see in this figure that the line between Envoy and Python applications is bidirectional because Envoy intercepts all application traffic.
+
+
+
+***Figure 3***
+
+### Metrics
+
+Once we recognize the network call relationship between processes through the topology, we can select a specific line and view the TCP metrics between the two processes.
+
+The diagram below (Figure 4) shows the metrics of network monitoring between two processes. There are four metrics in each line. Two on the left side are on the client side, and two on the right side are on the server side. If the remote process is not in the same Pod, only one side of the metrics is displayed.
+
+
+
+***Figure 4***
+
+The following two metric types are available:
+
+1. **Counter:** Records the total number of data in a certain period. Each counter contains the following data:
+ a. **Count:** Execution count.
+ b. **Bytes:** Packet size in bytes.
+ c. **Execution time:** Execution duration.
+2. **Histogram:** Records the distribution of data in the buckets.
+
+Based on the above data types, the following metrics are exposed:
+
+| Name | Type | Unit | Description |
+| ---------- | --------------------- | ----------- | ------------------------------------------------------------ |
+| Write | Counter and histogram | Millisecond | The socket write counter. |
+| Read | Counter and histogram | Millisecond | The socket read counter. |
+| Write RTT | Counter and histogram | Microsecond | The socket write round trip time (RTT) counter. |
+| Connect | Counter and histogram | Millisecond | The socket connect/accept with another server/client counter. |
+| Close | Counter and histogram | Millisecond | The socket with other socket counter. |
+| Retransmit | Counter | Millisecond | The socket retransmit package counter. |
+| Drop | Counter | Millisecond | The socket drop package counter. |
+
+## Demo
+
+In this section, we demonstrate how to perform network profiling in the
+service mesh. To follow along, you will need a running Kubernetes
+environment.
+
+**NOTE:** All commands and scripts are available [in this GitHub repository](https://github.com/mrproliu/skywalking-network-profiling-demo).
+
+### Install Istio
+
+Istio is the most widely deployed service mesh, and comes with a complete demo application that we can use for testing. To install Istio and the demo application, follow these steps:
+
+1. Install Istio using the demo configuration profile.
+2. Label the default namespace, so Istio automatically injects Envoy sidecar proxies when we'll deploy the application.
+3. Deploy the bookinfo application to the cluster.
+4. Deploy the traffic generator to generate some traffic to the application.
+
+```bash
+export ISTIO_VERSION=1.13.1
+
+# install istio
+istioctl install -y --set profile=demo
+kubectl label namespace default istio-injection=enabled
+
+# deploy the bookinfo applications
+kubectl apply -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml
+kubectl apply -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/networking/bookinfo-gateway.yaml
+kubectl apply -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/networking/destination-rule-all.yaml
+kubectl apply -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/networking/virtual-service-all-v1.yaml
+
+# generate traffic
+kubectl apply -f https://raw.githubusercontent.com/mrproliu/skywalking-network-profiling-demo/main/resources/traffic-generator.yaml
+```
+
+### Install SkyWalking
+
+The following will install the storage, backend, and UI needed for SkyWalking:
+
+```bash
+git clone https://github.com/apache/skywalking-helm.git
+cd skywalking-helm
+cd chart
+helm dep up skywalking
+helm -n istio-system install skywalking skywalking \
+ --set fullnameOverride=skywalking \
+ --set elasticsearch.minimumMasterNodes=1 \
+ --set elasticsearch.imageTag=7.5.1 \
+ --set oap.replicas=1 \
+ --set ui.image.repository=apache/skywalking-ui \
+ --set ui.image.tag=9.2.0 \
+ --set oap.image.tag=9.2.0 \
+ --set oap.envoy.als.enabled=true \
+ --set oap.image.repository=apache/skywalking-oap-server \
+ --set oap.storageType=elasticsearch \
+ --set oap.env.SW_METER_ANALYZER_ACTIVE_FILES='network-profiling'
+```
+
+### Install SkyWalking Rover
+
+SkyWalking Rover is deployed on every node in Kubernetes, and it automatically detects the services in the Kubernetes cluster. The network profiling feature has been released in the version 0.3.0 of SkyWalking Rover. When a network monitoring task is created, the SkyWalking rover sends the data to the SkyWalking backend.
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/mrproliu/skywalking-network-profiling-demo/main/resources/skywalking-rover.yaml
+```
+
+### Start the Network Profiling Task
+
+Once all deployments are completed, we must create a network profiling task for a specific instance of the service in the SkyWalking UI.
+
+To open SkyWalking UI, run:
+
+```bash
+kubectl port-forward svc/skywalking-ui 8080:80 --namespace
+istio-system
+```
+
+Currently, we can select the specific instances that we wish to monitor by clicking the **Data Plane** item in the Service Mesh panel and the **Service** item in the **Kubernetes** panel.
+
+In the figure below, we have selected an instance with a list of tasks in the network profiling tab. When we click the start button, the SkyWalking Rover starts monitoring this instance's network.
+
+
+
+***Figure 5***
+
+### Done!
+
+After a few seconds, you will see the process topology appear on the right side of the page.
+
+
+
+***Figure 6***
+
+When you click on the line between processes, you can see the TCP metrics between the two processes.
+
+
+
+***Figure 7***
+
+## Conclusion
+
+In this article, we detailed a problem that makes troubleshooting service mesh architectures difficult: lack of context between layers in the network stack. These are the cases when eBPF begins to really help with debugging/productivity when existing service mesh/envoy cannot. Then, we researched how eBPF could be applied to common communication, such as TLS. Finally, we demo the implementation of this process with SkyWalking Rover.
+
+For now, we have completed the performance analysis for OSI layer 4 (mostly TCP). In the future, we will also introduce the analysis for OSI layer 7 protocols like HTTP.
diff --git a/docs/en/academy/scaling-with-apache-skywalking.md b/docs/en/academy/scaling-with-apache-skywalking.md
new file mode 100644
index 000000000000..d9a6952ae779
--- /dev/null
+++ b/docs/en/academy/scaling-with-apache-skywalking.md
@@ -0,0 +1,300 @@
+# Scaling with Apache SkyWalking
+
+## Background
+
+In the Apache SkyWalking ecosystem, the OAP obtains metrics, traces, logs, and event data through SkyWalking Agent, Envoy, or other data sources. Under the gRPC protocol, it transmits data by communicating with a single server node. Only when the connection is broken, the reconnecting policy would be used based on DNS round-robin mode. When new services are added at runtime or the OAP load is kept high due to increased traffic of observed services, the OAP cluster needs to scale out for increased traffic. The load of the new OAP node would be less due to all existing agents having connected to previous nodes. Even without scaling, the load of OAP nodes would be unbalanced, because the agent would keep the connection due to random policy at the booting stage. In these cases, it would become a challenge to keep up the health status of all nodes, and be able to scale out when needed.
+
+In this article, we mainly discuss how to solve this challenge in SkyWalking.
+
+## How to Load Balance
+
+SkyWalking mainly uses the gRPC protocol for data transmission, so this article mainly introduces load balancing in the gRPC protocol.
+
+### Proxy Or Client-side
+
+Based on the [gRPC official Load Balancing blog](https://grpc.io/blog/grpc-load-balancing/), there are two approaches to load balancing:
+
+1. **Client-side**: The client perceives multiple back-end services and uses a load-balancing algorithm to select a back-end service for each RPC.
+2. **Proxy**: The client sends the message to the proxy server, and the proxy server load balances the message to the back-end service.
+
+From the perspective of observability system architecture:
+
+| | Pros | Cons |
+| --- | ---- | ---- |
+|Client-side|
+
+The expression supported by LogQL is composed of the following parts (expression with [✅] is implemented in SkyWalking):
+- [x] `stream selector`：The stream selector determines which log streams to include in a query’s results by labels.
+- [x] `line filter`: The line filter expression does a grep over the logs from the matching log streams.
+- [ ] `label filter`: Label filter expression allows filtering log line using their original and extracted labels.
+- [ ] `parser`: Parser expression can parse and extract labels from the log content. Those extracted labels can then be used by label filter expressions.
+- [ ] `line formate`: The line format expression can rewrite the log line content by using the text/template format.
+- [ ] `labels formate`: The label format expression can rename, modify or add labels.
+- [ ] `drop labels`: The drop expression will drop the given labels in the pipeline.
+
+The stream selector operator supported by LogQL is composed of the following (operator with [✅] is implemented in SkyWalking):
+- [x] `=`: exactly equal
+- [ ] `!=`: not equal
+- [ ] `=~`: regex matches
+- [ ] `!~`: regex does not match
+
+The filter operator supported by LogQL is composed of the following (operator with [✅] is implemented in SkyWalking):
+- [x] `|=`: Log line contains string
+- [x] `!=`: Log line does not contain string
+- [ ] `|~`: Log line contains a match to the regular expression
+- [ ] `!~`: Log line does not contain a match to the regular expression
+
+Here are some typical expressions used in SkyWalking log query:
+```
+# query service instance logs with specified traceId
+{service="$service", service_instance="$service_instance", trace_id="$trace_id"}
+```
+```
+# query service instance logs contains keyword in content
+{service="$service", service_instance="$service_instance"} |= "$keyword_contains"
+```
+```
+# query service instance logs not contains keyword in content
+{service="$service", service_instance="$service_instance"} != "$keyword_not_contains"
+```
+```
+# query service instance logs contains A keyword but not contains B keyword in content
+{service="$service", service_instance="$service_instance"} |= "$keyword_contains" != "$keyword_not_contains"
+```
+
+### [Metric queries](https://grafana.com/docs/loki/latest/logql/metric_queries/)
+Metric queries is used to calculate metrics from logs in Loki.
+In SkyWalking, it is recommended to use LAL([Log Analysis Language](https://skywalking.apache.org/docs/main/next/en/concepts-and-designs/lal/)).
+So metric queries LogQL won't be supported in SkyWalking.
+
+## Details Of Supported Http Query API
+### [List Labels](https://grafana.com/docs/loki/latest/api/#list-labels-within-a-range-of-time)
+Query log tags within a range of time.
+It is different from Loki. In loki, this api query all labels used in stream selector,
+but in SkyWalking, this api only for log tags query. Others metadata (service, service_instance, endpoint) query is provided by [PromQL Service](https://skywalking.apache.org/docs/main/next/en/api/promql-service/).
+
+```text
+GET /loki/api/v1/labels
+```
+
+| Parameter | Definition | Optional |
+|-----------|--------------------------------|----------|
+| start | start timestamp in nanoseconds | no |
+| end | end timestamp in nanoseconds | no |
+
+For example:
+```text
+/loki/api/v1/labels?start=1690947455457000000&end=1690947671936000000
+```
+
+Result:
+```json
+{
+ "status": "success",
+ "data": [
+ "level"
+ ]
+}
+```
+### [List Label values](https://grafana.com/docs/loki/latest/api/#list-label-values-within-a-range-of-time)
+Query log tag values of tag within a range of time.
+
+```text
+GET /loki/api/v1/label/