Re: [I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
wu-sheng closed issue #12043: [Feature] PHP extension supports link tracking sampling rate configuration URL: https://github.com/apache/skywalking/issues/12043 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
elricli commented on issue #12043: URL: https://github.com/apache/skywalking/issues/12043#issuecomment-2008614717 Ok, I created a discussion. #12044 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
wu-sheng commented on issue #12043: URL: https://github.com/apache/skywalking/issues/12043#issuecomment-2008589096 SkyWalking issue track is only for on-going things. Feature request is only hosting on the discussion panel to wait for someone picks up. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
elricli commented on issue #12043: URL: https://github.com/apache/skywalking/issues/12043#issuecomment-2008588343 > Are you going to do this? I can try -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
wu-sheng commented on issue #12043: URL: https://github.com/apache/skywalking/issues/12043#issuecomment-2008587462 Are you going to do this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] [Feature] PHP extension supports link tracking sampling rate configuration [skywalking]
elricli opened a new issue, #12043: URL: https://github.com/apache/skywalking/issues/12043 ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Like: - `skywalking.sample_n_per_3_secs` in the [SkyAPM/SkyAPM-php-sdk v4](https://github.com/SkyAPM/SkyAPM-php-sdk/blob/205bfc1c1d15c1fe1f45821a0948562df7bbdec2/skywalking.c#L75) - `agent.sampler` in the [skywalking-go](https://github.com/apache/skywalking-go/blob/642606007162e9b6f5c6827e4903994f6364d8fe/tools/go-agent/config/agent.default.yaml#L26) ### Use case Added a php.ini configuration: `skywalking_agent.sampler` (Sampling rate of tracing data, which is a floating-point value that must be between 0 and 1.) ### Related issues _No response_ ### Are you willing to submit a pull request to implement this on your own? - [X] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(skywalking) branch quick-start-windows-doc deleted (was 8641a66490)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch quick-start-windows-doc in repository https://gitbox.apache.org/repos/asf/skywalking.git was 8641a66490 Merge branch 'master' into quick-start-windows-doc The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
(skywalking) branch 9.6.0 deleted (was c24a0c5a4d)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch 9.6.0 in repository https://gitbox.apache.org/repos/asf/skywalking.git was c24a0c5a4d [maven-release-plugin] prepare for next development iteration This change permanently discards the following revisions: discard c24a0c5a4d [maven-release-plugin] prepare for next development iteration
Re: [PR] Add support trace ignore [skywalking-go]
mrproliu commented on code in PR #177:
URL: https://github.com/apache/skywalking-go/pull/177#discussion_r1531417175
##
tools/go-agent/config/agent.default.yaml:
##
@@ -30,8 +30,11 @@ agent:
correlation:
max_key_count: ${SW_AGENT_CORRELATION_MAX_KEY_COUNT:3}
max_value_size: ${SW_AGENT_CORRELATION_MAX_VALUE_SIZE:128}
- # If the operation name of the first span is included in this set, this
segment should be ignored.(multiple split by ",")
+ # If the operation name of the first span is included in this set, this
segment should be ignored.(multiple split by ",").
ignore_suffix:
${SW_AGENT_IGNORE_SUFFIX:.jpg,.jpeg,.js,.css,.png,.bmp,.gif,.ico,.mp3,.mp4,.html,.svg}
+ # If the operation name of the first span is matching, this segment should
be ignored.(multiple split by ",").
+ # Matching rules follow Ant Path match style, like /path/*, /path/**,
/path/?.
Review Comment:
Please add more comments about when the user should use `*`, `**`, or `?`.
##
plugins/core/tracer_ignore.go:
##
@@ -0,0 +1,144 @@
+// Licensed to 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. Apache Software Foundation (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 core
+
+import (
+ "strings"
+)
+
+const (
+ PERIOD = "."
+ COLON = ":"
+)
+
+func tracerIgnore(operationName string, ignoreSuffixList []string, ignorePath
[]string) bool {
+ return ignoreSuffix(operationName, ignoreSuffixList) ||
traceIgnorePath(operationName, ignorePath)
+}
+
+func ignoreSuffix(operationName string, ignoreSuffix []string) bool {
+ suffixIdx := strings.LastIndex(operationName, PERIOD)
+ if suffixIdx == -1 {
+ return false
+ }
+ for _, suffix := range ignoreSuffix {
+ if suffix == operationName[suffixIdx:] {
+ return true
+ }
+ }
+ return false
+}
+
+func traceIgnorePath(operationName string, ignorePath []string) bool {
+ op := strings.Index(operationName, COLON)
Review Comment:
Why need to check the operation name must-have :, if the operation is
generated by another RPC framework(not HTTP), then this configuration will be
broken.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] Add support trace ignore [skywalking-go]
wu-sheng commented on code in PR #177: URL: https://github.com/apache/skywalking-go/pull/177#discussion_r1531403406 ## docs/en/agent/tracing-metrics-logging.md: ## @@ -22,10 +22,11 @@ If you wish to disable a particular plugin to prevent enhancements related to th The basic configuration is as follows: -| Name| Environment Key| Default Value | Description | -|-||--|--| -| agent.sampler | SW_AGENT_SAMPLER | 1 | Sampling rate of tracing data, which is a floating-point value that must be between 0 and 1. | -| agent.ignore_suffix | SW_AGENT_IGNORE_SUFFIX | .jpg,.jpeg,.js,.css,.png,.bmp,.gif,.ico,.mp3,.mp4,.html,.svg | If the operation name of the first span is included in this set, this segment should be ignored.(multiple split by ","). | +| Name| Environment Key| Default Value | Description | +|-||--|--| +| agent.sampler | SW_AGENT_SAMPLER | 1 | Sampling rate of tracing data, which is a floating-point value that must be between 0 and 1. | +| agent.ignore_suffix | SW_AGENT_IGNORE_SUFFIX | .jpg,.jpeg,.js,.css,.png,.bmp,.gif,.ico,.mp3,.mp4,.html,.svg | If the operation name of the first span is included in this set, this segment should be ignored.(multiple split by ","). | +| agent.trace_ignore_path | SW_AGENT_TRACE_IGNORE_PATH | | If the operation name of the first span is matching, this segment should be ignored.(multiple split by ","). | Review Comment: If the entry span(first span) of the segment is `GET:/ABC`, in theory, when I set `agent.ignore_suffix=GET:/ABC`, what will happen? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add support trace ignore [skywalking-go]
wu-sheng commented on PR #177: URL: https://github.com/apache/skywalking-go/pull/177#issuecomment-2008474913 > matching rules follow Ant Path match style, like /path/*, /path/**, /path/?. Is this a question or something? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Add support trace ignore [skywalking-go]
CodePrometheus opened a new pull request, #177: URL: https://github.com/apache/skywalking-go/pull/177 ### Summary If the operation name of the first span is matching, this segment should be ignored.(multiple split by ","), matching rules follow Ant Path match style, like /path/*, /path/**, /path/?. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(skywalking) branch master updated: Fix SkyWalking Rover dead link in documentation (#12042)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/skywalking.git The following commit(s) were added to refs/heads/master by this push: new 16757403a3 Fix SkyWalking Rover dead link in documentation (#12042) 16757403a3 is described below commit 16757403a3bac8c867767293d7764a4900f07c23 Author: mrproliu <741550...@qq.com> AuthorDate: Wed Mar 20 00:31:05 2024 + Fix SkyWalking Rover dead link in documentation (#12042) --- docs/en/setup/backend/backend-k8s-monitoring-rover.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/setup/backend/backend-k8s-monitoring-rover.md b/docs/en/setup/backend/backend-k8s-monitoring-rover.md index ee0936f062..d409cd7241 100644 --- a/docs/en/setup/backend/backend-k8s-monitoring-rover.md +++ b/docs/en/setup/backend/backend-k8s-monitoring-rover.md @@ -7,7 +7,7 @@ SkyWalking uses the SkyWalking Rover system to collect access logs from Kubernet 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/examples/deploy/kubernetes/readme/) and enable [access log service](https://skywalking.apache.org/docs/skywalking-rover/next/en/setup/configuration/accesslog/). +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:
Re: [PR] Fix SkyWalking Rover dead link in documentation [skywalking]
wu-sheng merged PR #12042: URL: https://github.com/apache/skywalking/pull/12042 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Fix SkyWalking Rover dead link in documentation [skywalking]
mrproliu opened a new pull request, #12042: URL: https://github.com/apache/skywalking/pull/12042 - [ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #. - [ ] Update the [`CHANGES` log](https://github.com/apache/skywalking/blob/master/docs/en/changes/changes.md). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add windows powershell quick start guide [skywalking]
wu-sheng commented on PR #12028: URL: https://github.com/apache/skywalking/pull/12028#issuecomment-2008390558 Yes, we changed them as 0.6 release is a new one. We will fix the links. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(skywalking) branch master updated: Add windows powershell quick start guide (#12028)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/skywalking.git The following commit(s) were added to refs/heads/master by this push: new 065a321dcf Add windows powershell quick start guide (#12028) 065a321dcf is described below commit 065a321dcff344ad19fef21330b5349cece6d522 Author: Superskyyy AuthorDate: Tue Mar 19 20:19:51 2024 -0400 Add windows powershell quick start guide (#12028) --- docs/en/setup/backend/backend-docker.md | 28 ++-- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/docs/en/setup/backend/backend-docker.md b/docs/en/setup/backend/backend-docker.md index b0dc88c925..1bfc2a4e35 100644 --- a/docs/en/setup/backend/backend-docker.md +++ b/docs/en/setup/backend/backend-docker.md @@ -1,34 +1,42 @@ # How to use the Docker images -## Start the storage, OAP and UI with docker-compose +## Start the storage, OAP and Booster UI with docker-compose -As a quick start, you can use our one-line script to start ElasticSearch or -BanyanDB as the storage, OAP server and UI, please make sure you have installed -Docker. +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. +**Linux, macOS, Windows (WSL)** ```shell bash <(curl -sSL https://skywalking.apache.org/quickstart-docker.sh) ``` -You will be prompted to choose the storage type, and then the script will start -the backend cluster with the selected storage. +**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 `H2` storage ```shell -docker run --name oap --restart always -d apache/skywalking-oap-server:9.0.0 +docker run --name oap --restart always -d apache/skywalking-oap-server:9.7.0 +``` + +## Start a `standalone` container with BanyanDB as storage, whose address is `banyandb:17912` + +```shell +docker run --name oap --restart always -d -e SW_STORAGE=banyandb -e SW_STORAGE_BANYANDB_TARGETS=banyandb:17912 apache/skywalking-oap-server:9.7.0 ``` -## Start a `standalone` container with ElasticSearch 7 as storage whose address is `elasticsearch:9200` +## Start a `standalone` container with ElasticSearch 7 as storage, whose address is `elasticsearch:9200` ```shell -docker run --name oap --restart always -d -e SW_STORAGE=elasticsearch -e SW_STORAGE_ES_CLUSTER_NODES=elasticsearch:9200 apache/skywalking-oap-server:9.0.0 +docker run --name oap --restart always -d -e SW_STORAGE=elasticsearch -e SW_STORAGE_ES_CLUSTER_NODES=elasticsearch:9200 apache/skywalking-oap-server:9.7.0 ``` # Configuration
Re: [PR] Add windows powershell quick start guide [skywalking]
wu-sheng merged PR #12028: URL: https://github.com/apache/skywalking/pull/12028 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Add windows powershell quick start guide [skywalking]
Superskyyy commented on PR #12028: URL: https://github.com/apache/skywalking/pull/12028#issuecomment-2008345612 Rover doc is having dead links -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(skywalking) branch quick-start-windows-doc updated (a8e3033ba2 -> 8641a66490)
This is an automated email from the ASF dual-hosted git repository.
yihaochen pushed a change to branch quick-start-windows-doc
in repository https://gitbox.apache.org/repos/asf/skywalking.git
from a8e3033ba2 Replace PS command
add 121e8d29f0 Bump up changed-files GHA (#12032)
add 935ab0b17d Display the port services listen to from OAP and UI (#12030)
add 3f4126a28a Refactor data-generator to support generating metrics
(#12031)
add f4836327a6 Remove redanduent source in mock mode (#12033)
add b6d8d3a174 Fix `AvgHistogramPercentileFunction` legacy name. (#12039)
add 8641a66490 Merge branch 'master' into quick-start-windows-doc
No new revisions were added by this update.
Summary of changes:
.github/workflows/skywalking.yaml | 8 +-
apm-webapp/src/main/assembly/log4j2.xml| 10 ++
.../oap/server/webapp/ApplicationStartUp.java | 9 +
dist-material/bin/oapService.sh| 2 +-
dist-material/bin/startup.sh | 4 +-
dist-material/bin/webappService.sh | 2 +-
dist-material/log4j2.xml | 10 ++
docs/en/changes/changes.md | 3 +
docs/en/setup/backend/segment-template.json| 183 +
.../avg/AvgHistogramPercentileFunction.java| 2 +-
.../oap/server/library/server/grpc/GRPCServer.java | 5 +-
.../apache/skywalking/generator/BoolGenerator.java | 6 +-
.../skywalking/generator/FixedStringGenerator.java | 6 +-
.../org/apache/skywalking/generator/Generator.java | 4 +-
.../apache/skywalking/generator/IntGenerator.java | 6 +-
.../apache/skywalking/generator/ListGenerator.java | 6 +-
.../skywalking/generator/SequenceGenerator.java| 6 +-
.../skywalking/generator/StringGenerator.java | 15 +-
.../apache/skywalking/generator/UUIDGenerator.java | 6 +-
.../skywalking/restapi/LogGeneratorHandler.java| 2 +-
.../org/apache/skywalking/restapi/LogRequest.java | 54 +++---
.../skywalking/restapi/SegmentGenerator.java | 144
.../restapi/SegmentGeneratorHandler.java | 37 +++--
.../apache/skywalking/restapi/SegmentRequest.java | 87 ++
.../apache/skywalking/restapi/SpanGenerator.java | 79 +
.../apache/skywalking/restapi/TagGenerator.java| 10 +-
.../src/main/resources/application.yml | 105 ++--
.../skywalking/generator/IntGeneratorTest.java | 2 +-
.../generator/SequenceGeneratorTest.java | 4 +-
.../SegmentGeneratorTest.java} | 34 ++--
.../src/test/resources/segment.tpl.json| 122 ++
31 files changed, 656 insertions(+), 317 deletions(-)
create mode 100644
oap-server/server-tools/data-generator/src/main/java/org/apache/skywalking/restapi/SegmentGenerator.java
copy
oap-server/server-tools/data-generator/src/test/java/org/apache/skywalking/{generator/IntGeneratorTest.java
=> restapi/SegmentGeneratorTest.java} (51%)
create mode 100644
oap-server/server-tools/data-generator/src/test/resources/segment.tpl.json
(skywalking) branch quick-start-windows-doc updated (a382dfa2a5 -> a8e3033ba2)
This is an automated email from the ASF dual-hosted git repository. yihaochen pushed a change to branch quick-start-windows-doc in repository https://gitbox.apache.org/repos/asf/skywalking.git from a382dfa2a5 Add hyperlink add a8e3033ba2 Replace PS command No new revisions were added by this update. Summary of changes: docs/en/setup/backend/backend-docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
(skywalking-website) branch asf-site updated: deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/skywalking-website.git The following commit(s) were added to refs/heads/asf-site by this push: new 42f9f1696e7 deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a 42f9f1696e7 is described below commit 42f9f1696e758aacb65bf39ce515f5fd7c812146 Author: wu-sheng AuthorDate: Tue Mar 19 14:38:32 2024 + deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a --- contributors/index.html| 2 +- .../en/concepts-and-designs/overview/index.html| 36 +++-- .../en/guides/compile/how-to-compile/index.html| 36 +++-- .../guides/contribution/how-to-release/index.html | 40 +++--- .../contribution/how-to-write-module/index.html| 36 +++-- .../next/en/guides/readme/index.html | 36 +++-- .../next/en/setup/configuration/common/index.html | 36 +++-- .../configuration/override-settings/index.html | 36 +++-- .../en/setup/configuration/profiling/index.html| 36 +++-- .../configuration/service-discovery/index.html | 36 +++-- .../next/en/setup/configuration/traffic/index.html | 36 +++-- .../setup/deployment/kubernetes/readme/index.html | 36 +++-- .../next/en/setup/overview/index.html | 86 +++--- docs/skywalking-rover/next/menu.yml| 6 +- docs/skywalking-rover/next/readme/index.html | 36 +++-- index.json | 2 +- searchindex.json | 2 +- 17 files changed, 141 insertions(+), 393 deletions(-) diff --git a/contributors/index.html b/contributors/index.html index 7c3e70cdbd8..edb6bc115ce 100644 --- a/contributors/index.html +++ b/contributors/index.html @@ -18542,7 +18542,7 @@ -4 +5 2 diff --git a/docs/skywalking-rover/next/en/concepts-and-designs/overview/index.html b/docs/skywalking-rover/next/en/concepts-and-designs/overview/index.html index 1cfd96a299c..c48aff3b7d6 100644 --- a/docs/skywalking-rover/next/en/concepts-and-designs/overview/index.html +++ b/docs/skywalking-rover/next/en/concepts-and-designs/overview/index.html @@ -356,6 +356,14 @@ Why use SkyWalking Rover? On the Kubernetes platform, we could collect a lot of + + +Deploy on Kubernetes + + + + + @@ -399,32 +407,6 @@ Why use SkyWalking Rover? On the Kubernetes platform, we could collect a lot of - - - - - - - - - - - -Deployment - - - - - - - - -Deploy on K8s - - - - - @@ -534,7 +516,7 @@ Why use SkyWalking Rover? On the Kubernetes platform, we could collect a lot of })() - Commit Id: ee34f43 + Commit Id: dabe462 diff --git a/docs/skywalking-rover/next/en/guides/compile/how-to-compile/index.html b/docs/skywalking-rover/next/en/guides/compile/how-to-compile/index.html index 4bbcc15614f..6bf9ec9242e 100644 --- a/docs/skywalking-rover/next/en/guides/compile/how-to-compile/index.html +++ b/docs/skywalking-rover/next/en/guides/compile/how-to-compile/index.html @@ -359,6 +359,14 @@ Command git clone https://github.com/apache/skywalking-rover cd skywalking-rover + + +Deploy on Kubernetes + + + + + @@ -402,32 +410,6 @@ Command git clone https://github.com/apache/skywalking-rover cd skywalking-rover - - - - - - - - - - - -Deployment - - - - - - - - -Deploy on K8s - - - - - @@ -537,7 +519,7 @@ Command git clone https://github.com/apache/skywalking-rover cd skywalking-rover })() - Commit Id: ee34f43 + Commit Id: dabe462 diff --git a/docs/skywalking-rover/next/en/guides/contribution/how-to-release/index.html b/docs/skywalking-rover/next/en/guides/contribution/how-to-release/index.html index a386c7e2a16..a6eb52c92c1 100644 --- a/docs/skywalking-rover/next/en/guides/contribution/how-to-release/index.html +++ b/docs/skywalking-rover/next/en/guides/contribution/how-to-release/index.html @@ -353,6 +353,14 @@ Prerequisites Close(if finished, or move to next milestone otherwise) all issue + + +Deploy on Kubernetes + + + + + @@ -396,32 +404,6 @@ Prerequisites Close(if finished, or move to next milestone otherwise) all issue - - - - - - - -
Re: [PR] Polish docs [skywalking-rover]
mrproliu merged PR #121: URL: https://github.com/apache/skywalking-rover/pull/121 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Polish docs [skywalking-rover]
wu-sheng opened a new pull request, #121: URL: https://github.com/apache/skywalking-rover/pull/121 I polished some words in the docs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix release script path [skywalking-rover]
wu-sheng merged PR #120: URL: https://github.com/apache/skywalking-rover/pull/120 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Fix release script path [skywalking-rover]
mrproliu opened a new pull request, #120: URL: https://github.com/apache/skywalking-rover/pull/120 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Adjust documentation [skywalking-rover]
wu-sheng merged PR #119: URL: https://github.com/apache/skywalking-rover/pull/119 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Doc] Update Rover 0.6 doc [skywalking]
wu-sheng closed issue #11988: [Doc] Update Rover 0.6 doc URL: https://github.com/apache/skywalking/issues/11988 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Adjust documentation [skywalking-rover]
mrproliu commented on code in PR #119: URL: https://github.com/apache/skywalking-rover/pull/119#discussion_r1530211616 ## docs/menu.yml: ## @@ -23,34 +23,24 @@ catalog: catalog: - name: Overview and Core Concepts path: /en/concepts-and-designs/overview -- name: Design - catalog: -- name: Module Design - path: /en/concepts-and-designs/module_design -- name: Project Structure - path: /en/concepts-and-designs/project_structue - name: Setup catalog: - name: Overview path: /en/setup/overview - name: Configuration catalog: -- name: Logger Module - path: /en/setup/configuration/logger -- name: Core Module - path: /en/setup/configuration/core -- name: Process Discovery Module - path: /en/setup/configuration/process-discovery -- name: Profiling Module +- name: Common + path: /en/setup/configuration/common +- name: Service Discovery + path: /en/setup/configuration/service-discovery +- name: Traffic + path: /en/setup/configuration/traffic +- name: Profiling path: /en/setup/configuration/profiling -- name: Access Log Module - path: /en/setup/configuration/accesslog - name: Examples catalog: -- name: Deploy - catalog: -- name: Deploy on Kubernetes - path: /en/setup/examples/deploy/kubernetes/readme +- name: Deploy on K8s + path: /en/setup/examples/deploy/kubernetes/readme Review Comment: Updated, please help to re-check -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(skywalking-website) branch asf-site updated: deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d20f7a166c1 deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a
d20f7a166c1 is described below
commit d20f7a166c1a2173ed4add778d484bf5f7464082
Author: wu-sheng
AuthorDate: Tue Mar 19 10:05:15 2024 +
deploy: 1f1136138fc85506d9d9aefb3d38ce0108facd1a
---
contributors/index.html | 2 +-
index.json | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/contributors/index.html b/contributors/index.html
index 63c9b28d297..a30aeb525cd 100644
--- a/contributors/index.html
+++ b/contributors/index.html
@@ -655,7 +655,7 @@
-17
+18
8
diff --git a/index.json b/index.json
index b7369c57d32..1bd16347ad0 100644
--- a/index.json
+++ b/index.json
@@ -1 +1 @@
-[{"body":"SkyWalking Client JS 0.11.0 is released. Go to downloads page to
find release tars.\n Fixed the bug that navigator.sendBeacon sent json to
backend report \u0026ldquo;No suitable request converter found for a
@RequestObject List\u0026rdquo;. Fix reading property from null. Pin selenium
version and update license CI. Bump dependencies. Update README.
","excerpt":"SkyWalking Client JS 0.11.0 is released. Go to downloads page to
find release tars.\n Fixed the bug …","ref":"/events [...]
\ No newline at end of file
+[{"body":"SkyWalking Client JS 0.11.0 is released. Go to downloads page to
find release tars.\n Fixed the bug that navigator.sendBeacon sent json to
backend report \u0026ldquo;No suitable request converter found for a
@RequestObject List\u0026rdquo;. Fix reading property from null. Pin selenium
version and update license CI. Bump dependencies. Update README.
","excerpt":"SkyWalking Client JS 0.11.0 is released. Go to downloads page to
find release tars.\n Fixed the bug …","ref":"/events [...]
\ No newline at end of file
Re: [PR] Adjust documentation [skywalking-rover]
wu-sheng commented on code in PR #119: URL: https://github.com/apache/skywalking-rover/pull/119#discussion_r1529975115 ## docs/en/setup/overview.md: ## @@ -33,24 +33,17 @@ You can quickly build your Rover according to the following examples: 1. [Deploy on Kubernetes](examples/deploy/kubernetes/readme.md) -### Use Cases - -1. [Profiling a Golang/C/C++/Rust service on Linux](examples/cases/profiling-process/readme.md) -1. [Detect Process by Agent Sensor](examples/cases/agent-sensor/readme.md) -1. [Detect Process in Kubernetes Environemnt](examples/cases/kubernetes-process/readme.md) - ## Configuration The core concept behind this setting file is, that SkyWalking Rover is based on pure modularization design. The end-user can switch or assemble the collector features to their requirements. So, in rover_configs.yaml, there contains these parts. -1. [Logger Module](./configuration/logger.md). -2. [Core Module](./configuration/core.md). -3. [Process Discovery Module](configuration/process-discovery.md). -4. [Profiling Module](./configuration/profiling.md). -5. [Access Log Module](./configuration/accesslog.md). +1. [Common](./configuration/common.md). +2. [Service Discovery](configuration/service-discovery.md). +3. [Traffic](./configuration/traffic.md). +4. [Profiling](./configuration/profiling.md). -Also, You could using [Overriding Setting](./configuration/override-settings.md) feature to setup the configuration. +Also, You could use [Overriding Setting](./configuration/override-settings.md) feature to setup the configuration. Review Comment: ```suggestion Also, You could use [Overriding Setting](./configuration/override-settings.md) feature to adjust the configurations. ``` ## docs/menu.yml: ## @@ -23,34 +23,24 @@ catalog: catalog: - name: Overview and Core Concepts path: /en/concepts-and-designs/overview -- name: Design - catalog: -- name: Module Design - path: /en/concepts-and-designs/module_design -- name: Project Structure - path: /en/concepts-and-designs/project_structue - name: Setup catalog: - name: Overview path: /en/setup/overview - name: Configuration catalog: -- name: Logger Module - path: /en/setup/configuration/logger -- name: Core Module - path: /en/setup/configuration/core -- name: Process Discovery Module - path: /en/setup/configuration/process-discovery -- name: Profiling Module +- name: Common + path: /en/setup/configuration/common +- name: Service Discovery + path: /en/setup/configuration/service-discovery +- name: Traffic + path: /en/setup/configuration/traffic +- name: Profiling path: /en/setup/configuration/profiling -- name: Access Log Module - path: /en/setup/configuration/accesslog - name: Examples catalog: -- name: Deploy - catalog: -- name: Deploy on Kubernetes - path: /en/setup/examples/deploy/kubernetes/readme +- name: Deploy on K8s + path: /en/setup/examples/deploy/kubernetes/readme Review Comment: You could set it as Deployment directly to replace the whole examples menu, there is no other examples, and this is the official deployment I think, rather han an example. Please remove the examples folder too. ## docs/en/setup/configuration/traffic.md: ## @@ -1,6 +1,6 @@ -# Access Log Module +# Traffic -The access log module is used to collecting the network access logs from the [Kerbernetes Module](process_discovery/kubernetes.md), +The traffic is used to collecting the network access logs from the [Service Discovery](service-discovery.md), Review Comment: ```suggestion The traffic is used to collecting the network access logs from services through the [Service Discovery](service-discovery.md), ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Adjust documentation [skywalking-rover]
mrproliu opened a new pull request, #119: URL: https://github.com/apache/skywalking-rover/pull/119 Fix https://github.com/apache/skywalking/issues/11988 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Bug] SkyWalking Operator helm does not yet include the CRD for BanyanDB. [skywalking]
wu-sheng commented on issue #12040: URL: https://github.com/apache/skywalking/issues/12040#issuecomment-2006072909 This is addressed helm needs a new release and align with swck latest updates, e.g. CRD. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
mrproliu commented on code in PR #693: URL: https://github.com/apache/skywalking-website/pull/693#discussion_r1529820736 ## content/blog/2023-03-18-monitor-kubernetes-network-by-ebpf/kubernetes-service-list.md: ## @@ -0,0 +1,199 @@ +--- +title: "Monitoring Kubernetes network traffic by using eBPF" +date: 2024-03-18 +author: Han Liu +description: This article demonstrates how SkyWalking uses eBPF technology to monitor network traffic on Kubernetes. +--- + +## Background + + +[Apache SkyWalking](https://skywalking.apache.org/) is an open-source Application Performance Management system that helps users gather logs, traces, metrics, and events from various platforms and display them on the UI. +With version 9.7.0, SkyWalking can collect access logs from probes in multiple languages and from Kubernetes, generating corresponding topologies, links, and other data. However, it could not initially collect and map access logs from applications in Kubernetes environments. This article explores how the 10.0.0 version of Apache SkyWalking employs eBPF technology to collect and store application access logs, addressing this limitation. + +## Why eBPF? + +To monitor the network traffic in Kubernetes, the following features support be support: + +1. **Cross Language**: Applications deployed in Kubernetes may be written in any programming language, making support for diverse languages important. +2. **Non-Intrusiveness**: It's imperative to monitor network traffic without making any modifications to the applications, as direct intervention with applications in Kubernetes is not feasible. +3. **Kernel Metrics Monitoring**: Often, diagnosing network issues by analyzing traffic performance at the user-space level is insufficient. A deeper analysis incorporating kernel-space network traffic metrics is frequently necessary. +4. **Support for Various Network Protocols**: Applications may communicate using different transport protocols, necessitating support for a range of protocols. + +Given these requirements, eBPF emerges as a capable solution. In the next section, we will delve into detailed explanations of how Apache SkyWalking Rover resolves these aspects. + +## Kernel Monitoring and Protocol Analysis + +In previous articles, we've discussed how to monitor network traffic from programs written in various languages. +This technique remains essential for network traffic monitoring, allowing for the collection of traffic data without language limitations. +However, due to the unique aspects of our monitoring trigger mechanism and the specific features of kernel monitoring, these two areas warrant separate explanations. + +### Kernel Monitoring + +Kernel monitoring allows users to gain insights into network traffic performance based on the execution at the kernel level, +specifically from Layer 2 (Data Link) to Layer 4 (Transport) of the OSI model. + +Network monitoring at the kernel layer is deference from the syscall (user-space) layer in terms of the metrics and identifiers used. +While the syscalls layer can utilize file descriptors to correlate various operations, kernel layer network operations primarily use packets as unique identifiers. +This discrepancy necessitates a mapping relationship that SkyWalking Rover can use to bind these two layers together for comprehensive monitoring. + +Let's dive into the details of how data is monitored in both sending and receiving modes. + + Sending traffic + +When sending data, tracking the status and timing of each packet is crucial for understanding the state of each transmission. +Within the kernel, operations progress from Layer 4 (L4) down to Layer 2 (L2), maintaining the same thread ID as during the syscalls layer, which simplifies data correlation. + +SkyWalking Rover monitors several key kernel functions to observe packet transmission dynamics, listed from L4 to L2: + +1. **kprobe/tcp_sendmsg**: Captures the time when a packet enters the L4 protocol stack for sending and the time it finishes processing. + This function is essential for tracking the initial handling of packets at the transport layer. +2. **kprobe/tcp_transmit_skb**: Records the total number of packet transmissions and the size of each packet sent. + This function helps identify how many times a packet or a batch of packets is attempted to be sent, which is critical for understanding network throughput and congestion. +3. **tracepoint/tcp/tcp_retransmit_skb**: Notes whether packet retransmission occurs, providing insights into network reliability and connection quality. + Retransmissions can significantly impact application performance and user experience. +4. **tracepoint/skb/kfree_skb**: Records packet loss during transmission and logs the reason for such occurrences. + Understanding packet loss is crucial for diagnosing network issues and ensuring data integrity. +5. **kprobe/__ip_queue_xmit**: Records the start and end times of
Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
wu-sheng commented on code in PR #693: URL: https://github.com/apache/skywalking-website/pull/693#discussion_r1529791085 ## content/blog/2023-03-18-monitor-kubernetes-network-by-ebpf/kubernetes-service-list.md: ## @@ -0,0 +1,199 @@ +--- +title: "Monitoring Kubernetes network traffic by using eBPF" +date: 2024-03-18 +author: Han Liu +description: This article demonstrates how SkyWalking uses eBPF technology to monitor network traffic on Kubernetes. +--- + +## Background + + +[Apache SkyWalking](https://skywalking.apache.org/) is an open-source Application Performance Management system that helps users gather logs, traces, metrics, and events from various platforms and display them on the UI. +With version 9.7.0, SkyWalking can collect access logs from probes in multiple languages and from Kubernetes, generating corresponding topologies, links, and other data. However, it could not initially collect and map access logs from applications in Kubernetes environments. This article explores how the 10.0.0 version of Apache SkyWalking employs eBPF technology to collect and store application access logs, addressing this limitation. + +## Why eBPF? + +To monitor the network traffic in Kubernetes, the following features support be support: + +1. **Cross Language**: Applications deployed in Kubernetes may be written in any programming language, making support for diverse languages important. +2. **Non-Intrusiveness**: It's imperative to monitor network traffic without making any modifications to the applications, as direct intervention with applications in Kubernetes is not feasible. +3. **Kernel Metrics Monitoring**: Often, diagnosing network issues by analyzing traffic performance at the user-space level is insufficient. A deeper analysis incorporating kernel-space network traffic metrics is frequently necessary. +4. **Support for Various Network Protocols**: Applications may communicate using different transport protocols, necessitating support for a range of protocols. + +Given these requirements, eBPF emerges as a capable solution. In the next section, we will delve into detailed explanations of how Apache SkyWalking Rover resolves these aspects. + +## Kernel Monitoring and Protocol Analysis + +In previous articles, we've discussed how to monitor network traffic from programs written in various languages. +This technique remains essential for network traffic monitoring, allowing for the collection of traffic data without language limitations. +However, due to the unique aspects of our monitoring trigger mechanism and the specific features of kernel monitoring, these two areas warrant separate explanations. + +### Kernel Monitoring + +Kernel monitoring allows users to gain insights into network traffic performance based on the execution at the kernel level, +specifically from Layer 2 (Data Link) to Layer 4 (Transport) of the OSI model. + +Network monitoring at the kernel layer is deference from the syscall (user-space) layer in terms of the metrics and identifiers used. +While the syscalls layer can utilize file descriptors to correlate various operations, kernel layer network operations primarily use packets as unique identifiers. +This discrepancy necessitates a mapping relationship that SkyWalking Rover can use to bind these two layers together for comprehensive monitoring. + +Let's dive into the details of how data is monitored in both sending and receiving modes. + + Sending traffic + +When sending data, tracking the status and timing of each packet is crucial for understanding the state of each transmission. +Within the kernel, operations progress from Layer 4 (L4) down to Layer 2 (L2), maintaining the same thread ID as during the syscalls layer, which simplifies data correlation. + +SkyWalking Rover monitors several key kernel functions to observe packet transmission dynamics, listed from L4 to L2: + +1. **kprobe/tcp_sendmsg**: Captures the time when a packet enters the L4 protocol stack for sending and the time it finishes processing. + This function is essential for tracking the initial handling of packets at the transport layer. +2. **kprobe/tcp_transmit_skb**: Records the total number of packet transmissions and the size of each packet sent. + This function helps identify how many times a packet or a batch of packets is attempted to be sent, which is critical for understanding network throughput and congestion. +3. **tracepoint/tcp/tcp_retransmit_skb**: Notes whether packet retransmission occurs, providing insights into network reliability and connection quality. + Retransmissions can significantly impact application performance and user experience. +4. **tracepoint/skb/kfree_skb**: Records packet loss during transmission and logs the reason for such occurrences. + Understanding packet loss is crucial for diagnosing network issues and ensuring data integrity. +5. **kprobe/__ip_queue_xmit**: Records the start and end times of
Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
wu-sheng commented on code in PR #693: URL: https://github.com/apache/skywalking-website/pull/693#discussion_r1529790155 ## content/blog/2023-03-18-monitor-kubernetes-network-by-ebpf/kubernetes-service-list.md: ## @@ -0,0 +1,199 @@ +--- +title: "Monitoring Kubernetes network traffic by using eBPF" +date: 2024-03-18 +author: Han Liu +description: This article demonstrates how SkyWalking uses eBPF technology to monitor network traffic on Kubernetes. +--- + +## Background + + +[Apache SkyWalking](https://skywalking.apache.org/) is an open-source Application Performance Management system that helps users gather logs, traces, metrics, and events from various platforms and display them on the UI. +With version 9.7.0, SkyWalking can collect access logs from probes in multiple languages and from Kubernetes, generating corresponding topologies, links, and other data. However, it could not initially collect and map access logs from applications in Kubernetes environments. This article explores how the 10.0.0 version of Apache SkyWalking employs eBPF technology to collect and store application access logs, addressing this limitation. + +## Why eBPF? + +To monitor the network traffic in Kubernetes, the following features support be support: + +1. **Cross Language**: Applications deployed in Kubernetes may be written in any programming language, making support for diverse languages important. +2. **Non-Intrusiveness**: It's imperative to monitor network traffic without making any modifications to the applications, as direct intervention with applications in Kubernetes is not feasible. +3. **Kernel Metrics Monitoring**: Often, diagnosing network issues by analyzing traffic performance at the user-space level is insufficient. A deeper analysis incorporating kernel-space network traffic metrics is frequently necessary. +4. **Support for Various Network Protocols**: Applications may communicate using different transport protocols, necessitating support for a range of protocols. + +Given these requirements, eBPF emerges as a capable solution. In the next section, we will delve into detailed explanations of how Apache SkyWalking Rover resolves these aspects. + +## Kernel Monitoring and Protocol Analysis + +In previous articles, we've discussed how to monitor network traffic from programs written in various languages. +This technique remains essential for network traffic monitoring, allowing for the collection of traffic data without language limitations. +However, due to the unique aspects of our monitoring trigger mechanism and the specific features of kernel monitoring, these two areas warrant separate explanations. + +### Kernel Monitoring + +Kernel monitoring allows users to gain insights into network traffic performance based on the execution at the kernel level, +specifically from Layer 2 (Data Link) to Layer 4 (Transport) of the OSI model. + +Network monitoring at the kernel layer is deference from the syscall (user-space) layer in terms of the metrics and identifiers used. +While the syscalls layer can utilize file descriptors to correlate various operations, kernel layer network operations primarily use packets as unique identifiers. +This discrepancy necessitates a mapping relationship that SkyWalking Rover can use to bind these two layers together for comprehensive monitoring. + +Let's dive into the details of how data is monitored in both sending and receiving modes. + + Sending traffic + +When sending data, tracking the status and timing of each packet is crucial for understanding the state of each transmission. +Within the kernel, operations progress from Layer 4 (L4) down to Layer 2 (L2), maintaining the same thread ID as during the syscalls layer, which simplifies data correlation. + +SkyWalking Rover monitors several key kernel functions to observe packet transmission dynamics, listed from L4 to L2: + +1. **kprobe/tcp_sendmsg**: Captures the time when a packet enters the L4 protocol stack for sending and the time it finishes processing. + This function is essential for tracking the initial handling of packets at the transport layer. +2. **kprobe/tcp_transmit_skb**: Records the total number of packet transmissions and the size of each packet sent. + This function helps identify how many times a packet or a batch of packets is attempted to be sent, which is critical for understanding network throughput and congestion. +3. **tracepoint/tcp/tcp_retransmit_skb**: Notes whether packet retransmission occurs, providing insights into network reliability and connection quality. + Retransmissions can significantly impact application performance and user experience. +4. **tracepoint/skb/kfree_skb**: Records packet loss during transmission and logs the reason for such occurrences. + Understanding packet loss is crucial for diagnosing network issues and ensuring data integrity. +5. **kprobe/__ip_queue_xmit**: Records the start and end times of
Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
mrproliu commented on PR #693: URL: https://github.com/apache/skywalking-website/pull/693#issuecomment-2005865037 > Would you add one for CN version as well? Sure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
mrproliu commented on code in PR #693: URL: https://github.com/apache/skywalking-website/pull/693#discussion_r1529781056 ## content/blog/2023-03-18-monitor-kubernetes-network-by-ebpf/kubernetes-service-list.md: ## @@ -0,0 +1,199 @@ +--- +title: "Monitoring Kubernetes network traffic by using eBPF" +date: 2024-03-18 +author: Han Liu +description: This article demonstrates how SkyWalking uses eBPF technology to monitor network traffic on Kubernetes. +--- + +## Background + + +[Apache SkyWalking](https://skywalking.apache.org/) is an open-source Application Performance Management system that helps users gather logs, traces, metrics, and events from various platforms and display them on the UI. +With version 9.7.0, SkyWalking can collect access logs from probes in multiple languages and from Kubernetes, generating corresponding topologies, links, and other data. However, it could not initially collect and map access logs from applications in Kubernetes environments. This article explores how the 10.0.0 version of Apache SkyWalking employs eBPF technology to collect and store application access logs, addressing this limitation. + +## Why eBPF? + +To monitor the network traffic in Kubernetes, the following features support be support: + +1. **Cross Language**: Applications deployed in Kubernetes may be written in any programming language, making support for diverse languages important. +2. **Non-Intrusiveness**: It's imperative to monitor network traffic without making any modifications to the applications, as direct intervention with applications in Kubernetes is not feasible. +3. **Kernel Metrics Monitoring**: Often, diagnosing network issues by analyzing traffic performance at the user-space level is insufficient. A deeper analysis incorporating kernel-space network traffic metrics is frequently necessary. +4. **Support for Various Network Protocols**: Applications may communicate using different transport protocols, necessitating support for a range of protocols. + +Given these requirements, eBPF emerges as a capable solution. In the next section, we will delve into detailed explanations of how Apache SkyWalking Rover resolves these aspects. + +## Kernel Monitoring and Protocol Analysis + +In previous articles, we've discussed how to monitor network traffic from programs written in various languages. +This technique remains essential for network traffic monitoring, allowing for the collection of traffic data without language limitations. +However, due to the unique aspects of our monitoring trigger mechanism and the specific features of kernel monitoring, these two areas warrant separate explanations. + +### Kernel Monitoring + +Kernel monitoring allows users to gain insights into network traffic performance based on the execution at the kernel level, +specifically from Layer 2 (Data Link) to Layer 4 (Transport) of the OSI model. + +Network monitoring at the kernel layer is deference from the syscall (user-space) layer in terms of the metrics and identifiers used. +While the syscalls layer can utilize file descriptors to correlate various operations, kernel layer network operations primarily use packets as unique identifiers. +This discrepancy necessitates a mapping relationship that SkyWalking Rover can use to bind these two layers together for comprehensive monitoring. + +Let's dive into the details of how data is monitored in both sending and receiving modes. + + Sending traffic + +When sending data, tracking the status and timing of each packet is crucial for understanding the state of each transmission. +Within the kernel, operations progress from Layer 4 (L4) down to Layer 2 (L2), maintaining the same thread ID as during the syscalls layer, which simplifies data correlation. + +SkyWalking Rover monitors several key kernel functions to observe packet transmission dynamics, listed from L4 to L2: + +1. **kprobe/tcp_sendmsg**: Captures the time when a packet enters the L4 protocol stack for sending and the time it finishes processing. + This function is essential for tracking the initial handling of packets at the transport layer. +2. **kprobe/tcp_transmit_skb**: Records the total number of packet transmissions and the size of each packet sent. + This function helps identify how many times a packet or a batch of packets is attempted to be sent, which is critical for understanding network throughput and congestion. +3. **tracepoint/tcp/tcp_retransmit_skb**: Notes whether packet retransmission occurs, providing insights into network reliability and connection quality. + Retransmissions can significantly impact application performance and user experience. +4. **tracepoint/skb/kfree_skb**: Records packet loss during transmission and logs the reason for such occurrences. + Understanding packet loss is crucial for diagnosing network issues and ensuring data integrity. +5. **kprobe/__ip_queue_xmit**: Records the start and end times of
Re: [I] [Bug] SkyWalking Operator helm does not yet include the CRD for BanyanDB. [skywalking]
wu-sheng commented on issue #12040: URL: https://github.com/apache/skywalking/issues/12040#issuecomment-2005842770 We need to check whether this is a SWCK issue or helm repo or banyandb helm repository. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
