Re: [PR] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
wu-sheng commented on PR #693: URL: https://github.com/apache/skywalking-website/pull/693#issuecomment-2005838175 Would you add one for CN version as well? -- 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]
wu-sheng commented on code in PR #693: URL: https://github.com/apache/skywalking-website/pull/693#discussion_r1529766436 ## 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_r1529765181 ## 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_r1529765034
##
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
Review Comment:
```suggestion
Observe Sending
```
--
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]
wu-sheng commented on code in PR #693:
URL:
https://github.com/apache/skywalking-website/pull/693#discussion_r1529763664
##
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
Review Comment:
```suggestion
Traffic Observation
```
--
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]
wu-sheng commented on code in PR #693:
URL:
https://github.com/apache/skywalking-website/pull/693#discussion_r1529763664
##
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
Review Comment:
```suggestion
Sending Traffic
```
--
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]
wu-sheng commented on code in PR #693:
URL:
https://github.com/apache/skywalking-website/pull/693#discussion_r1529763664
##
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
Review Comment:
```suggestion
Traffic Observation
```
--
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]
netlify[bot] commented on PR #693: URL: https://github.com/apache/skywalking-website/pull/693#issuecomment-2005828287 ### Deploy Preview for *skywalking-website-preview* processing. | Name | Link | |:-:|| | Latest commit | 3d4ab562e97c9dddf385bb0ccc2fa68d241f00df | | Latest deploy log | https://app.netlify.com/sites/skywalking-website-preview/deploys/65f926e386d28600084e9a01 | -- 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] blog: Monitoring kubernetes network traffic by using eBPF [skywalking-website]
mrproliu opened a new pull request, #693: URL: https://github.com/apache/skywalking-website/pull/693 (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
[I] [Bug] SkyWalking Operator helm does not yet include the CRD for BanyanDB. [skywalking]
yswdqz opened a new issue, #12040: URL: https://github.com/apache/skywalking/issues/12040 ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component Helm Chart (apache/skywalking-helm) ### What happened When installing the SWCK operator using Helm, a CRD called 'BanyanDB' is required. However, this CRD is not directly provided in the Helm charts. Currently, it can only be installed by executing make -C operator install from the root path of SWCK. https://github.com/apache/skywalking/assets/74546965/07b58cbf-8079-4aea-8efa-50de6ad3851c;> ### What you expected to happen 'BanyanDB' crd will automaticly install when we install the SWCK operator using Helm. ### How to reproduce Installing the SWCK operator using Helm without running make install in the SWCK root directory. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] 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-website) branch fix-powershell-script deleted (was 7782af21944)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch fix-powershell-script in repository https://gitbox.apache.org/repos/asf/skywalking-website.git was 7782af21944 Fix powershell quick start bug 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-website) branch master updated: Fix powershell quick start bug (#692)
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-website.git
The following commit(s) were added to refs/heads/master by this push:
new 1f1136138fc Fix powershell quick start bug (#692)
1f1136138fc is described below
commit 1f1136138fc85506d9d9aefb3d38ce0108facd1a
Author: Superskyyy
AuthorDate: Tue Mar 19 00:44:45 2024 -0400
Fix powershell quick start bug (#692)
---
content/quickstart-docker.ps1 | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/content/quickstart-docker.ps1 b/content/quickstart-docker.ps1
index 89ad3e1f4db..bcbd5f57110 100644
--- a/content/quickstart-docker.ps1
+++ b/content/quickstart-docker.ps1
@@ -38,14 +38,13 @@ function Show-Usage {
Write-Host " -h/--help About running the quickstart script
without interaction"
Write-Host " -f Run in foreground mode (docker compose
up)"
Write-Host " --storage Set the storage option (elasticsearch or
banyandb)"
-exit
}
# Process command-line arguments
for ($i = 0; $i -lt $args.Length; $i++) {
switch ($args[$i]) {
-"-h" { Show-Usage; exit }
-"--help" { Show-Usage; exit }
+"-h" { Show-Usage; return; }
+"--help" { Show-Usage; return; }
"-f" { $DETACHED = $false; $foregroundOptionProvided = $true; }
"--storage" {
if ($i -lt $args.Length - 1) {
@@ -53,26 +52,22 @@ for ($i = 0; $i -lt $args.Length; $i++) {
$storageOptionProvided = $true
# Validate storage option if provided
if ($storageOptionProvided -and -not ($env:SW_STORAGE -eq
"elasticsearch" -or $env:SW_STORAGE -eq "banyandb")) {
-Write-Host "Invalid storage option: $env:SW_STORAGE. Valid
options are 'elasticsearch' or 'banyandb'."
-exit 1
+throw "Invalid storage option: $env:SW_STORAGE. Valid
options are 'elasticsearch' or 'banyandb'."
}
}
else {
-Write-Host "Error: --storage option requires an argument."
-exit 1
+throw "Error: --storage option requires an argument."
}
}
default {
-Write-Host "Invalid option: $($args[$i]), try -h or --help"
-exit 1
+throw "Invalid option: $($args[$i]), try -h or --help"
}
}
}
if (-not (Get-Command "docker" -ErrorAction SilentlyContinue)) {
-Write-Host "Docker is not found. Please make sure Docker is installed and
the docker command is available in PATH.`n"
-exit 1
+throw "Docker is not found. Please make sure Docker is installed and the
docker command is available in PATH.`n"
}
Write-Host "Docker is installed, continue...`n"
@@ -84,14 +79,17 @@ if (Test-Path -Path $COMPOSE_FILE_PATH) {
if ($reuseFlag -eq 'y' -or $reuseFlag -eq 'Y') {
$DOWNLOAD = $true
}
+} else {
+$DOWNLOAD = $true
}
+
if ($DOWNLOAD) {
Invoke-WebRequest -Uri
"https://github.com/apache/skywalking/raw/master/docker/docker-compose.yml;
-OutFile $COMPOSE_FILE_PATH
-Write-Host "`nDownloaded SkyWalking Docker Compose manifest to the current
directory...`n"
+Write-Host "Downloaded SkyWalking Docker Compose manifest to the current
directory...`n"
}
else {
-Write-Host "`nAttempting to reuse the existing SkyWalking Docker Compose
manifest from the current directory.`n"
+Write-Host "Attempting to reuse the existing SkyWalking Docker Compose
manifest from the current directory.`n"
}
# If SW_STORAGE is not set, prompt the user to select a storage option
@@ -111,8 +109,7 @@ if (-not $storageOptionProvided) {
Write-Host "You have selected: BanyanDB as the storage option.`n"
}
else {
-Write-Host "Invalid choice. Please enter 1 or 2.`n"
-exit 1
+throw "Invalid choice. Please enter 1 or 2.`n"
}
}
@@ -140,8 +137,7 @@ Invoke-Expression $composeCommand
# Check if the command was successful, try catch won't work here
if ($LASTEXITCODE -ne 0) {
-Write-Host "`nFailed to start SkyWalking. Please check the Docker compose
logs for more information.`n"
-exit $LASTEXITCODE
+throw "`nFailed to start SkyWalking. Please check the Docker compose logs
for more information.`n"
}
else {
Write-Host "`nSkyWalking is now running. You can send telemetry data to
localhost:11800 and access the UI at http://localhost:8080.`n;
Re: [PR] Fix powershell quick start bug [skywalking-website]
wu-sheng merged PR #692: URL: https://github.com/apache/skywalking-website/pull/692 -- 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 powershell quick start bug [skywalking-website]
netlify[bot] commented on PR #692: URL: https://github.com/apache/skywalking-website/pull/692#issuecomment-2005749033 ### Deploy Preview for *skywalking-website-preview* processing. | Name | Link | |:-:|| | Latest commit | 7782af219444c8133f6da8bbecc6f9b040416ee1 | | Latest deploy log | https://app.netlify.com/sites/skywalking-website-preview/deploys/65f9172e1f749a00083c2d77 | -- 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 powershell quick start bug [skywalking-website]
Superskyyy opened a new pull request, #692: URL: https://github.com/apache/skywalking-website/pull/692 Fixes: 1. Use throw instead of exit when running scripts from the website. Exit will kill the entire terminal when it's evaluated from the input stream. 2. Download should be by default triggered. -- 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 fix-powershell-script updated: Fix powershell quick start bug
This is an automated email from the ASF dual-hosted git repository.
yihaochen pushed a commit to branch fix-powershell-script
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
The following commit(s) were added to refs/heads/fix-powershell-script by this
push:
new 7782af21944 Fix powershell quick start bug
7782af21944 is described below
commit 7782af219444c8133f6da8bbecc6f9b040416ee1
Author: Superskyyy
AuthorDate: Tue Mar 19 00:37:46 2024 -0400
Fix powershell quick start bug
---
content/quickstart-docker.ps1 | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/content/quickstart-docker.ps1 b/content/quickstart-docker.ps1
index 89ad3e1f4db..bcbd5f57110 100644
--- a/content/quickstart-docker.ps1
+++ b/content/quickstart-docker.ps1
@@ -38,14 +38,13 @@ function Show-Usage {
Write-Host " -h/--help About running the quickstart script
without interaction"
Write-Host " -f Run in foreground mode (docker compose
up)"
Write-Host " --storage Set the storage option (elasticsearch or
banyandb)"
-exit
}
# Process command-line arguments
for ($i = 0; $i -lt $args.Length; $i++) {
switch ($args[$i]) {
-"-h" { Show-Usage; exit }
-"--help" { Show-Usage; exit }
+"-h" { Show-Usage; return; }
+"--help" { Show-Usage; return; }
"-f" { $DETACHED = $false; $foregroundOptionProvided = $true; }
"--storage" {
if ($i -lt $args.Length - 1) {
@@ -53,26 +52,22 @@ for ($i = 0; $i -lt $args.Length; $i++) {
$storageOptionProvided = $true
# Validate storage option if provided
if ($storageOptionProvided -and -not ($env:SW_STORAGE -eq
"elasticsearch" -or $env:SW_STORAGE -eq "banyandb")) {
-Write-Host "Invalid storage option: $env:SW_STORAGE. Valid
options are 'elasticsearch' or 'banyandb'."
-exit 1
+throw "Invalid storage option: $env:SW_STORAGE. Valid
options are 'elasticsearch' or 'banyandb'."
}
}
else {
-Write-Host "Error: --storage option requires an argument."
-exit 1
+throw "Error: --storage option requires an argument."
}
}
default {
-Write-Host "Invalid option: $($args[$i]), try -h or --help"
-exit 1
+throw "Invalid option: $($args[$i]), try -h or --help"
}
}
}
if (-not (Get-Command "docker" -ErrorAction SilentlyContinue)) {
-Write-Host "Docker is not found. Please make sure Docker is installed and
the docker command is available in PATH.`n"
-exit 1
+throw "Docker is not found. Please make sure Docker is installed and the
docker command is available in PATH.`n"
}
Write-Host "Docker is installed, continue...`n"
@@ -84,14 +79,17 @@ if (Test-Path -Path $COMPOSE_FILE_PATH) {
if ($reuseFlag -eq 'y' -or $reuseFlag -eq 'Y') {
$DOWNLOAD = $true
}
+} else {
+$DOWNLOAD = $true
}
+
if ($DOWNLOAD) {
Invoke-WebRequest -Uri
"https://github.com/apache/skywalking/raw/master/docker/docker-compose.yml;
-OutFile $COMPOSE_FILE_PATH
-Write-Host "`nDownloaded SkyWalking Docker Compose manifest to the current
directory...`n"
+Write-Host "Downloaded SkyWalking Docker Compose manifest to the current
directory...`n"
}
else {
-Write-Host "`nAttempting to reuse the existing SkyWalking Docker Compose
manifest from the current directory.`n"
+Write-Host "Attempting to reuse the existing SkyWalking Docker Compose
manifest from the current directory.`n"
}
# If SW_STORAGE is not set, prompt the user to select a storage option
@@ -111,8 +109,7 @@ if (-not $storageOptionProvided) {
Write-Host "You have selected: BanyanDB as the storage option.`n"
}
else {
-Write-Host "Invalid choice. Please enter 1 or 2.`n"
-exit 1
+throw "Invalid choice. Please enter 1 or 2.`n"
}
}
@@ -140,8 +137,7 @@ Invoke-Expression $composeCommand
# Check if the command was successful, try catch won't work here
if ($LASTEXITCODE -ne 0) {
-Write-Host "`nFailed to start SkyWalking. Please check the Docker compose
logs for more information.`n"
-exit $LASTEXITCODE
+throw "`nFailed to start SkyWalking. Please check the Docker compose logs
for more information.`n"
}
else {
Write-Host "`nSkyWalking is now running. You can send telemetry data to
localhost:11800 and access the UI at http://localhost:8080.`n;
(skywalking-website) branch fix-powershell-script created (now ee299565224)
This is an automated email from the ASF dual-hosted git repository. yihaochen pushed a change to branch fix-powershell-script in repository https://gitbox.apache.org/repos/asf/skywalking-website.git at ee299565224 Add quick-start script for Windows (#690) No new revisions were added by this update.
Re: [PR] Add windows powershell quick start guide [skywalking]
Superskyyy commented on PR #12028: URL: https://github.com/apache/skywalking/pull/12028#issuecomment-2005704828 Ok it didn't work, gotta fix on the website side first. -- 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 `AvgHistogramPercentileFunction` legacy name. [skywalking]
wu-sheng merged PR #12039: URL: https://github.com/apache/skywalking/pull/12039 -- 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 `AvgHistogramPercentileFunction` legacy name. (#12039)
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 b6d8d3a174 Fix `AvgHistogramPercentileFunction` legacy name. (#12039) b6d8d3a174 is described below commit b6d8d3a1742154e22cd8c365a57fb068d86caf34 Author: Wan Kai AuthorDate: Tue Mar 19 09:42:14 2024 +0800 Fix `AvgHistogramPercentileFunction` legacy name. (#12039) --- docs/en/changes/changes.md | 1 + .../analysis/meter/function/avg/AvgHistogramPercentileFunction.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/changes/changes.md b/docs/en/changes/changes.md index ca4c1cf743..f45aaf4933 100644 --- a/docs/en/changes/changes.md +++ b/docs/en/changes/changes.md @@ -79,6 +79,7 @@ * Add Golang as a supported language for Kafka. * Support displaying the port services listen to from OAP and UI during server start. * Refactor data-generator to support generating metrics. +* Fix `AvgHistogramPercentileFunction` legacy name. UI diff --git a/oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/meter/function/avg/AvgHistogramPercentileFunction.java b/oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/meter/function/avg/AvgHistogramPercentileFunction.java index f69bc9ced7..0856188507 100644 --- a/oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/meter/function/avg/AvgHistogramPercentileFunction.java +++ b/oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/meter/function/avg/AvgHistogramPercentileFunction.java @@ -81,7 +81,7 @@ public abstract class AvgHistogramPercentileFunction extends Meter implements Ac @Getter @Setter @Column(name = VALUE, dataType = Column.ValueDataType.LABELED_VALUE, storageOnly = true) -@ElasticSearch.Column(legacyName = "name") +@ElasticSearch.Column(legacyName = "value") @BanyanDB.MeasureField private DataTable percentileValues = new DataTable(10); @Getter
[PR] Fix `AvgHistogramPercentileFunction` legacy name. [skywalking]
wankai123 opened a new pull request, #12039: URL: https://github.com/apache/skywalking/pull/12039 - [ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #. - [X] Update the [`CHANGES` log](https://github.com/apache/skywalking/blob/master/docs/en/changes/changes.md). I think the legacy name was and should be `value`. -- 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-python) branch dependabot/pip/django-3.2.25 deleted (was a567419)
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/pip/django-3.2.25 in repository https://gitbox.apache.org/repos/asf/skywalking-python.git was a567419 Bump django from 3.2.8 to 3.2.25 The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
Re: [PR] Bump django from 3.2.8 to 3.2.25 [skywalking-python]
dependabot[bot] commented on PR #334: URL: https://github.com/apache/skywalking-python/pull/334#issuecomment-2005465391 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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] Bump django from 3.2.8 to 3.2.25 [skywalking-python]
wu-sheng closed pull request #334: Bump django from 3.2.8 to 3.2.25 URL: https://github.com/apache/skywalking-python/pull/334 -- 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-python) branch dependabot/pip/django-3.2.25 created (now a567419)
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/pip/django-3.2.25 in repository https://gitbox.apache.org/repos/asf/skywalking-python.git at a567419 Bump django from 3.2.8 to 3.2.25 No new revisions were added by this update.
[PR] Bump django from 3.2.8 to 3.2.25 [skywalking-python]
dependabot[bot] opened a new pull request, #334: URL: https://github.com/apache/skywalking-python/pull/334 Bumps [django](https://github.com/django/django) from 3.2.8 to 3.2.25. Commits https://github.com/django/django/commit/c98eca322af87adf046ab621e7c8a23d340f7afe;>c98eca3 [3.2.x] Bumped version for 3.2.25 release. https://github.com/django/django/commit/072963e4c4d0b3a7a8c5412bc0c7d27d1a9c3521;>072963e [3.2.x] Fixed CVE-2024-27351 -- Prevented potential ReDoS in Truncator.words(). https://github.com/django/django/commit/2ad2676456316eb211104d1f0cfc8dea7a7ca76b;>2ad2676 [3.2.x] Added release date for 3.2.25. https://github.com/django/django/commit/fc41af69a2e49a717ef069a37e1d68b80a6a5d56;>fc41af6 [3.2.x] Fixed https://redirect.github.com/django/django/issues/35172;>#35172 -- Fixed intcomma for string floats. https://github.com/django/django/commit/b9170b4a9e7f0dde5d29ef69354c94efa6d6edfb;>b9170b4 [3.2.x] Added CVE-2024-24680 to security archive. https://github.com/django/django/commit/e5350a931a017fab6aa0026e8f2d6e9ef09e1e1b;>e5350a9 [3.2.x] Post release version bump. https://github.com/django/django/commit/f5c880857e8e01b006c75b9e79a9088cc2c6228f;>f5c8808 [3.2.x] Bumped version for 3.2.24 release. https://github.com/django/django/commit/c1171ffbd570db90ca206c30f8e2b9f691243820;>c1171ff [3.2.x] Fixed CVE-2024-24680 -- Mitigated potential DoS in intcomma template ... https://github.com/django/django/commit/9dc345643e94f3a48d58fe7547fbc88ce8dab6e9;>9dc3456 [3.2.x] Added stub release notes 3.2.24. https://github.com/django/django/commit/90eae45b3818f6c6e74c2fcb972e2a692ade4c1e;>90eae45 [3.2.x] Fixed documented alias of smart_text(). Additional commits viewable in https://github.com/django/django/compare/3.2.8...3.2.25;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/skywalking-python/network/alerts). -- 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] [Bug] skywalking-backend-js :: i use "mongoose": "^8.2.2", got error: Error installing plugin mongodb * /usr/src/app/node_modules/skywalking-backend-js/lib/core/PluginInstaller.js [skywalking]
liuqixing opened a new issue, #12038:
URL: https://github.com/apache/skywalking/issues/12038
### Search before asking
- [X] I had searched in the
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no
similar issues.
### Apache SkyWalking Component
NodeJS Server Side Agent (apache/skywalking-nodejs)
### What happened
i use "mongoose": "^8.2.2", got error, and can not access my mongodb any more
{
message: 'Error installing plugin mongodb *',
level: 'error',
file:
'/usr/src/app/node_modules/skywalking-backend-js/lib/core/PluginInstaller.js'
}
### What you expected to happen
can not access my mongodb any more
### How to reproduce
can not access my mongodb any more
### Anything else
_No response_
### Are you willing to submit a pull request to fix on your own?
- [ ] 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-banyandb) branch part deleted (was e918adf1)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch part in repository https://gitbox.apache.org/repos/asf/skywalking-banyandb.git was e918adf1 Move part deletion to the close phase The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
Re: [PR] Add windows powershell quick start guide [skywalking]
Superskyyy commented on PR #12028: URL: https://github.com/apache/skywalking/pull/12028#issuecomment-2004053426 > The script has been hosted on website. Please verify and continue. Sure, gonna test that after work. -- 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-2003900470 The script has been hosted on website. Please verify and continue. -- 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 windows-quickstart deleted (was 0f49d9dfd6a)
This is an automated email from the ASF dual-hosted git repository. kezhenxu94 pushed a change to branch windows-quickstart in repository https://gitbox.apache.org/repos/asf/skywalking-website.git was 0f49d9dfd6a Avoid overriding existing manifest & remove -d 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-website) branch master updated: Add quick-start script for Windows (#690)
This is an automated email from the ASF dual-hosted git repository.
kezhenxu94 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
The following commit(s) were added to refs/heads/master by this push:
new ee299565224 Add quick-start script for Windows (#690)
ee299565224 is described below
commit ee29956522493f42a19ac04cf5ff7abe90bfa1a3
Author: Superskyyy
AuthorDate: Mon Mar 18 08:30:25 2024 -0400
Add quick-start script for Windows (#690)
---
content/quickstart-docker.ps1 | 154 ++
content/quickstart-docker.sh | 8 ++-
2 files changed, 159 insertions(+), 3 deletions(-)
diff --git a/content/quickstart-docker.ps1 b/content/quickstart-docker.ps1
new file mode 100644
index 000..89ad3e1f4db
--- /dev/null
+++ b/content/quickstart-docker.ps1
@@ -0,0 +1,154 @@
+# 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.
+
+# Default values for SkyWalking versions
+$SW_VERSION = "9.7.0"
+$SW_BANYANDB_VERSION = "0.5.0"
+
+$COMPOSE_FILE_PATH = ".\docker-compose.yml"
+$env:BANYANDB_IMAGE = "apache/skywalking-banyandb:$SW_BANYANDB_VERSION"
+$env:OAP_IMAGE = "apache/skywalking-oap-server:$SW_VERSION"
+$env:UI_IMAGE = "apache/skywalking-ui:$SW_VERSION"
+
+# Unset the SW_STORAGE environment variable at the start of the script
+Remove-Item Env:\SW_STORAGE -ErrorAction Ignore
+
+# Ensuring script stops on error
+$ErrorActionPreference = "Stop"
+
+$storageOptionProvided = $false
+$foregroundOptionProvided = $false
+# Function to display usage information
+function Show-Usage {
+Write-Host "Usage: quickstart-docker.ps1 [-h/--help] [-f] [--storage
]"
+Write-Host "Options:"
+Write-Host " -h/--help About running the quickstart script
without interaction"
+Write-Host " -f Run in foreground mode (docker compose
up)"
+Write-Host " --storage Set the storage option (elasticsearch or
banyandb)"
+exit
+}
+
+# Process command-line arguments
+for ($i = 0; $i -lt $args.Length; $i++) {
+switch ($args[$i]) {
+"-h" { Show-Usage; exit }
+"--help" { Show-Usage; exit }
+"-f" { $DETACHED = $false; $foregroundOptionProvided = $true; }
+"--storage" {
+if ($i -lt $args.Length - 1) {
+$env:SW_STORAGE = $args[++$i]
+$storageOptionProvided = $true
+# Validate storage option if provided
+if ($storageOptionProvided -and -not ($env:SW_STORAGE -eq
"elasticsearch" -or $env:SW_STORAGE -eq "banyandb")) {
+Write-Host "Invalid storage option: $env:SW_STORAGE. Valid
options are 'elasticsearch' or 'banyandb'."
+exit 1
+}
+}
+else {
+Write-Host "Error: --storage option requires an argument."
+exit 1
+}
+}
+default {
+Write-Host "Invalid option: $($args[$i]), try -h or --help"
+exit 1
+}
+}
+}
+
+
+if (-not (Get-Command "docker" -ErrorAction SilentlyContinue)) {
+Write-Host "Docker is not found. Please make sure Docker is installed and
the docker command is available in PATH.`n"
+exit 1
+}
+Write-Host "Docker is installed, continue...`n"
+
+# In place download, prompt user before overriding
+if (Test-Path -Path $COMPOSE_FILE_PATH) {
+Write-Host "A docker-compose.yml already exists in the current
directory.`n"
+$reuseFlag = Read-Host "Would you like to override the existing manifest
(default: False)? [Y/n]: "
+$DOWNLOAD = $false
+if ($reuseFlag -eq 'y' -or $reuseFlag -eq 'Y') {
+$DOWNLOAD = $true
+}
+}
+
+if ($DOWNLOAD) {
+Invoke-WebRequest -Uri
"https://github.com/apache/skywalking/raw/master/docker/docker-compose.yml;
-OutFile $COMPOSE_FILE_PATH
+Write-Host "`nDownloaded SkyWalking Docker Compose manifest to the current
directory...`n"
+}
+else {
+Write-Host "`nAttempting to reuse the existing SkyWalking Docker Compose
manifest from the current directory.`n"
+}
+
+# If SW_STORAGE is not set, prompt the user to select a storage option
+if (-not $storageOptionProvided) {
+Write-Host "Please select a storage option:"
+
Re: [PR] Add quick-start script for Windows [skywalking-website]
kezhenxu94 merged PR #690: URL: https://github.com/apache/skywalking-website/pull/690 -- 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] Bump up Kafka Client [skywalking]
wu-sheng opened a new issue, #12037: URL: https://github.com/apache/skywalking/issues/12037 ### 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 https://github.com/advisories/GHSA-26f8-x7cc-wqpc was annouced as servity 8.8 / 10, and our version(2.8.1) was released Sep 17, 2021. Also, I can see a lot of CVEs reported for this version, https://mvnrepository.com/artifact/org.apache.kafka/kafka-clients/2.8.1 Let's try to bump up the version to the latest if possible. ### Use case _No response_ ### Related issues _No response_ ### Are you willing to submit a pull request to implement this on your own? - [ ] 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
Re: [I] [Feature][BanyanDB] Support for Tags and Fields TTL [skywalking]
wu-sheng commented on issue #11987: URL: https://github.com/apache/skywalking/issues/11987#issuecomment-2003035093 About this, I think we need to update the protocol to support this. The server side can't / shouldn't determine which fields could be removed with time, unless OAP told so. Because in some cases(mostly for streaming), fields and tags are required until TTL reached. -- 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] php agent cant report [skywalking]
wu-sheng commented on issue #12034: URL: https://github.com/apache/skywalking/issues/12034#issuecomment-2003027778 Use the English on GitHub communication, please. Please submit a new one in English. -- 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] php agent cant report [skywalking]
wu-sheng closed issue #12034: [Bug] php agent cant report URL: https://github.com/apache/skywalking/issues/12034 -- 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] [Bug] php agent cant report [skywalking]
pan269 opened a new issue, #12034: URL: https://github.com/apache/skywalking/issues/12034 ### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component PHP (apache/skywalking-php) ### What happened 使用php-fpm时，无法上报，日志里面显示 ERROR shutdown: skywalking_agent::channel: channel send failed err=No such file or directory (os error 2) ### What you expected to happen 我希望使用php-fpm时能正常上报 ### How to reproduce php版本7.4 angent版本0.7.0 直接按照扩展后使用fpm模式运行均可触发 ### Anything else 发生错误的原因是socket_file文件生成以后被删除了 在worker.rs 中去除 这一段 WorkerExitGuard的drop就可以修复这个问题，  不过这样会导致之前的sock文件一直残留在那里，由于我的rust水平太次，只能请求开发组修复这个bug ### Are you willing to submit a pull request to fix 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 data-generator deleted (was 92145108e6)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch data-generator in repository https://gitbox.apache.org/repos/asf/skywalking.git was 92145108e6 Remove redanduent source 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 master updated: Remove redanduent source in mock mode (#12033)
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 f4836327a6 Remove redanduent source in mock mode (#12033)
f4836327a6 is described below
commit f4836327a65efe76cbbc12f013cc9cbc63a82b2c
Author: Gao Hongtao
AuthorDate: Mon Mar 18 14:11:20 2024 +0800
Remove redanduent source in mock mode (#12033)
---
.../java/org/apache/skywalking/restapi/SegmentGeneratorHandler.java | 5 -
1 file changed, 5 deletions(-)
diff --git
a/oap-server/server-tools/data-generator/src/main/java/org/apache/skywalking/restapi/SegmentGeneratorHandler.java
b/oap-server/server-tools/data-generator/src/main/java/org/apache/skywalking/restapi/SegmentGeneratorHandler.java
index 6e7a520dbf..0b018324c3 100644
---
a/oap-server/server-tools/data-generator/src/main/java/org/apache/skywalking/restapi/SegmentGeneratorHandler.java
+++
b/oap-server/server-tools/data-generator/src/main/java/org/apache/skywalking/restapi/SegmentGeneratorHandler.java
@@ -35,8 +35,6 @@ import io.netty.util.concurrent.Future;
import lombok.extern.slf4j.Slf4j;
import org.apache.skywalking.oap.server.analyzer.module.AnalyzerModule;
import
org.apache.skywalking.oap.server.analyzer.provider.trace.parser.ISegmentParserService;
-import org.apache.skywalking.oap.server.core.CoreModule;
-import org.apache.skywalking.oap.server.core.source.SourceReceiver;
import org.apache.skywalking.oap.server.library.module.ModuleManager;
import java.util.List;
@@ -51,13 +49,11 @@ import java.util.stream.IntStream;
@Slf4j
public class SegmentGeneratorHandler {
-private final SourceReceiver sourceReceiver;
private final Map> futures = new ConcurrentHashMap<>();
private final EventLoopGroup eventLoopGroup =
EventLoopGroups.newEventLoopGroup(10);
private final ISegmentParserService segmentParserService;
public SegmentGeneratorHandler(ModuleManager manager) {
-sourceReceiver =
manager.find(CoreModule.NAME).provider().getService(SourceReceiver.class);
segmentParserService =
manager.find(AnalyzerModule.NAME).provider().getService(ISegmentParserService.class);
}
@@ -79,7 +75,6 @@ public class SegmentGeneratorHandler {
final List segments =
request.next(null);
log.debug("Generating segment: {}", (Object) segments);
segments.forEach(s -> {
-sourceReceiver.receive(s.segment);
segmentParserService.send(s.segmentObject);
});
};
Re: [PR] Remove redandunt source [skywalking]
wu-sheng merged PR #12033: URL: https://github.com/apache/skywalking/pull/12033 -- 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
