[GitHub] liyongfa0311 opened a new issue #2208: The UI cannot be accessed when a collector hangs
liyongfa0311 opened a new issue #2208: The UI cannot be accessed when a collector hangs URL: https://github.com/apache/incubator-skywalking/issues/2208 Please answer these questions before submitting your issue. - Why do you submit this issue? - [x] Question or discussion - [ ] Bug - [ ] Requirement - [ ] Feature or performance improvement ___ ### Question - What do you want to know? I have deployed the cluster, I found that after a collector is hanged, the UI is inaccessible.Does deploying cluster mode also require all nodes to survive? When I configure the listOfServers option of the webapp.yml file to be a partial node，"com.netflix.zuul.exception.ZuulException: Forwarding error" error occurs in the webapp.log file,Also, the agent's collector.backend_service parameter configures all nodes. ,Will the data be lost when some nodes are hanged ? ___ ### Bug - Which version of SkyWalking, OS and JRE? skywalking 6..0.0-GA OS :centos 7.3 JRE:1.8 - Which company or project? - What happen? If possible, provide a way for reproducing the error. e.g. demo application, component version. How to configure can guarantee that my program is still normal when a node hangs, including page access ___ ### Requirement or improvement - Please describe about your requirements or improvement suggestions. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng commented on issue #2206: Loss of metadata causes the server to fail to start properly
wu-sheng commented on issue #2206: Loss of metadata causes the server to fail to start properly URL: https://github.com/apache/incubator-skywalking/issues/2206#issuecomment-457520494 Auto reset from UI command is in this milestone, let's see whether it will deliver in time. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng closed issue #2208: The UI cannot be accessed when a collector hangs
wu-sheng closed issue #2208: The UI cannot be accessed when a collector hangs URL: https://github.com/apache/incubator-skywalking/issues/2208 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch master updated: Sync UI (#2205)
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/incubator-skywalking.git The following commit(s) were added to refs/heads/master by this push: new b5b6900 Sync UI (#2205) b5b6900 is described below commit b5b69000cae0615e96f1fe355b5e0f0196b68ba2 Author: jason1016 AuthorDate: Fri Jan 25 18:04:36 2019 +0800 Sync UI (#2205) --- skywalking-ui | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skywalking-ui b/skywalking-ui index 6c00408..e88bc6f 16 --- a/skywalking-ui +++ b/skywalking-ui @@ -1 +1 @@ -Subproject commit 6c00408995a56171f0ee799c69b363bf17f8186a +Subproject commit e88bc6f1bbbe0963756c29a7159f2378bcac13ee
[GitHub] wu-sheng merged pull request #2205: Sync UI
wu-sheng merged pull request #2205: Sync UI URL: https://github.com/apache/incubator-skywalking/pull/2205 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng commented on issue #2204: what is the search rule of EndpointName in trace page?
wu-sheng commented on issue #2204: what is the search rule of EndpointName in trace page? URL: https://github.com/apache/incubator-skywalking/issues/2204#issuecomment-457521797 Endpoint is from entry span, which means the entry of your segment. Other spans would be used in query condition. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng closed issue #2204: what is the search rule of EndpointName in trace page?
wu-sheng closed issue #2204: what is the search rule of EndpointName in trace page? URL: https://github.com/apache/incubator-skywalking/issues/2204 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] liyongfa0311 commented on issue #2208: The UI cannot be accessed when a collector hangs
liyongfa0311 commented on issue #2208: The UI cannot be accessed when a collector hangs URL: https://github.com/apache/incubator-skywalking/issues/2208#issuecomment-457534485 I know UI would work.But collector break down, it will have 500 errors.I want to know how to configure to avoid this problem. And will the data uploaded by the agent be lost when the cluster is normal and some collector break down？ This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] coveralls commented on issue #2207: Increase the ability of the agent to manually trigger registration
coveralls commented on issue #2207: Increase the ability of the agent to manually trigger registration URL: https://github.com/apache/incubator-skywalking/pull/2207#issuecomment-457536847 [](https://coveralls.io/builds/21272494) Coverage decreased (-0.01%) to 14.309% when pulling **af1ebf75cf37f083c0328d3e4dafde8df7e41109 on Liu-XinYuan:master-register** into **b5b69000cae0615e96f1fe355b5e0f0196b68ba2 on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] hanahmily commented on a change in pull request #30: Mesh performance test blog
hanahmily commented on a change in pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30#discussion_r250970889 ## File path: docs/blog/2019-01-25-mesh-loadtest.md ## @@ -0,0 +1,82 @@ +# Performance Testing of Service Mesh Receiver + +- Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC +- [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) + +Jan. 25th, 2019 + +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, etc. What’s the service mesh? According to Istio’s explain: + +The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. + +As a PMC of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. + +## Different between trace and service mesh + +Following chart presents a typical trace map: + + + +You could find a variety of elements in it just like web service, local method, database, cache, MQ and so on. But service mesh only collect service network telemetry data that contains the entrance and exit data of a service. A smaller quantity of data is sent to the service mesh receiver than the trace. + +But using sidecar is a little different. + + + +The client requesting “A” that will send a segment to service mesh receiver from “A”’s sidecar. If “A” depends on “B”, another segment will be sent from “A”’s sidecar. But for a trace system, only one segment is received by the collector. The sidecar model splits one segment into small segments, that will increase service mesh receiver network overhead. Review comment: > In trace mode, still you will receive segment from both sides. Clien't segment includes the exit span, and Server's segment includes the entry span. Trace scenario always includes more span than mesh. So you need to change this description In this section, I focus on the TCP package. For a single instance, mesh style will send double packages than the trace. More TCP package will affect network traffic(overhead) that means if the amount of 1MB mesh data would be more than 1 MB trace data. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] hanahmily commented on a change in pull request #30: Mesh performance test blog
hanahmily commented on a change in pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30#discussion_r250971581 ## File path: docs/blog/README.md ## @@ -3,6 +3,11 @@ layout: LayoutBlog blog: +- title: Performance Testing of Service Mesh Receiver Review comment: Make sense This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] hanahmily commented on a change in pull request #30: Mesh performance test blog
hanahmily commented on a change in pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30#discussion_r250971721 ## File path: docs/blog/2019-01-25-mesh-loadtest.md ## @@ -0,0 +1,82 @@ +# Performance Testing of Service Mesh Receiver + +- Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC +- [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) + +Jan. 25th, 2019 + +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, etc. What’s the service mesh? According to Istio’s explain: Review comment: Added it. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] hanahmily commented on a change in pull request #30: Mesh performance test blog
hanahmily commented on a change in pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30#discussion_r250971854 ## File path: docs/blog/2019-01-25-mesh-loadtest.md ## @@ -0,0 +1,82 @@ +# Performance Testing of Service Mesh Receiver + +- Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC +- [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) + +Jan. 25th, 2019 + +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, etc. What’s the service mesh? According to Istio’s explain: + +The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. + +As a PMC of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. + +## Different between trace and service mesh + +Following chart presents a typical trace map: + + Review comment: Fixed this. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] hanahmily commented on a change in pull request #30: Mesh performance test blog
hanahmily commented on a change in pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30#discussion_r250971791 ## File path: docs/blog/2019-01-25-mesh-loadtest.md ## @@ -0,0 +1,82 @@ +# Performance Testing of Service Mesh Receiver + +- Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC +- [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) + +Jan. 25th, 2019 + +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, etc. What’s the service mesh? According to Istio’s explain: + +The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. + +As a PMC of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. Review comment: Fixed this. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking-website] branch mesh-loadtest updated: fix some issues
This is an automated email from the ASF dual-hosted git repository. hanahmily pushed a commit to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git The following commit(s) were added to refs/heads/mesh-loadtest by this push: new 4963969 fix some issues 4963969 is described below commit 4963969fd105c35a3d49975cea99e12a4b65f999 Author: gaohongtao AuthorDate: Fri Jan 25 20:44:14 2019 +0800 fix some issues --- docs/blog/2019-01-25-mesh-loadtest.md | 18 +- docs/blog/README.md | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/blog/2019-01-25-mesh-loadtest.md b/docs/blog/2019-01-25-mesh-loadtest.md index 261224d..82bb6cc 100644 --- a/docs/blog/2019-01-25-mesh-loadtest.md +++ b/docs/blog/2019-01-25-mesh-loadtest.md @@ -1,27 +1,27 @@ -# Performance Testing of Service Mesh Receiver +# SkyWalking performance in Service Mesh scenario - Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC - [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) Jan. 25th, 2019 -Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, etc. What’s the service mesh? According to Istio’s explain: +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, Envoy etc. What’s the service mesh? According to Istio’s explain: The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. -As a PMC of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. +As a PMC member of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. ## Different between trace and service mesh Following chart presents a typical trace map: - + You could find a variety of elements in it just like web service, local method, database, cache, MQ and so on. But service mesh only collect service network telemetry data that contains the entrance and exit data of a service. A smaller quantity of data is sent to the service mesh receiver than the trace. But using sidecar is a little different. - + The client requesting “A” that will send a segment to service mesh receiver from “A”’s sidecar. If “A” depends on “B”, another segment will be sent from “A”’s sidecar. But for a trace system, only one segment is received by the collector. The sidecar model splits one segment into small segments, that will increase service mesh receiver network overhead. @@ -45,7 +45,7 @@ Receiving mesh fragments per second(MPS) depends on the following variables. In this test, I use Bookinfo app as a demo cluster. - + So every request will touch max 4 nodes. Plus picking the sidecar mode(every request will send two telemetry data), the MPS will be QPS * 4 *2. @@ -58,17 +58,17 @@ There are also some important metrics that should be explained ### Mini Unit - + You could find collector can process up to **25k** data per second. The CPU usage is about 4 cores. Most of the query latency is less than 50ms. After login the VM on which collector instance running, I know that system load is reaching the limit(max is 8). - + According to the previous formula, a single collector instance could process **3k** QPS of Bookinfo traffic. ### Standard Cluster - + Compare to the mini-unit, cluster’s throughput increases linearly. Three instances provide total 80k per second processing power. Query latency increases slightly, but it’s also very small(less than 500ms). I also checked every collector instance system load that all reached
[incubator-skywalking-website] branch mesh-loadtest updated (4963969 -> 3def3ff)
This is an automated email from the ASF dual-hosted git repository. hanahmily pushed a change to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git. discard 4963969 fix some issues new 3def3ff fix some issues This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4963969) \ N -- N -- N refs/heads/mesh-loadtest (3def3ff) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 110 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: docs/blog/2019-01-25-mesh-loadtest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[incubator-skywalking-website] branch asf-site updated (61707e8 -> 4ef77de)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard 61707e8 Update asf-site
new 4ef77de Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (61707e8)
\
N -- N -- N refs/heads/asf-site (4ef77de)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html| 6 +++---
.../image1.png => assets/img/image1.6aa5501b.png| Bin
.../image3.png => assets/img/image3.d21be62b.png| Bin
.../image4.png => assets/img/image4.6772bca0.png| Bin
.../image5.png => assets/img/image5.e2954636.png| Bin
.../image6.png => assets/img/image6.fa5e2945.png| Bin
assets/js/10.cfe0c5a7.js| 1 +
assets/js/{10.695b6db0.js => 11.39e31df9.js}| 2 +-
assets/js/{11.4bb1ec73.js => 12.e313e146.js}| 2 +-
assets/js/13.9e4388dc.js| 1 -
assets/js/{12.893cc1d2.js => 13.becafcf4.js}| 2 +-
assets/js/{14.5851bce8.js => 14.ff1dd683.js}| 2 +-
assets/js/{15.7384e8dd.js => 15.d45331fe.js}| 2 +-
assets/js/{16.9c900212.js => 16.cd06eef3.js}| 2 +-
assets/js/{17.2d2c54e2.js => 17.da1a8d91.js}| 2 +-
assets/js/{18.d7cc.js => 18.599b28b1.js}| 2 +-
assets/js/{19.f5301a86.js => 19.e5b08a92.js}| 2 +-
assets/js/{2.19c67ce7.js => 2.e0180d36.js} | 2 +-
assets/js/{20.df3a470c.js => 20.72899d7d.js}| 2 +-
assets/js/{21.2f7155e2.js => 21.4e755b4d.js}| 2 +-
assets/js/{22.2638db75.js => 22.7127ebc8.js}| 2 +-
assets/js/{23.d3a8a4af.js => 23.9607b3fa.js}| 2 +-
assets/js/{24.e3e8ae60.js => 24.233ee907.js}| 2 +-
assets/js/{25.78156d93.js => 25.6eaacfbc.js}| 2 +-
assets/js/{26.71aeefaf.js => 26.ba41e955.js}| 2 +-
assets/js/27.7945c32b.js| 1 +
assets/js/27.bb515b6f.js| 1 -
assets/js/{3.915cd6f4.js => 3.4c16a9ad.js} | 2 +-
assets/js/{4.ac49de80.js => 4.3fd9864f.js} | 2 +-
assets/js/{5.c3739bf7.js => 5.88d1c0bb.js} | 2 +-
assets/js/{6.520efd8f.js => 6.c89ccd19.js} | 2 +-
assets/js/7.3074d918.js | 1 +
assets/js/{7.615a83a1.js => 8.146cc705.js} | 2 +-
assets/js/{8.ea7f7f0d.js => 9.0d9f78fe.js} | 2 +-
assets/js/9.29c39bc9.js | 1 -
assets/js/{app.e17c7794.js => app.0449b5fa.js} | 4 ++--
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html | 4 ++--
blog/2019-01-25-mesh-loadtest.html | 8
blog/index.html | 6 +++---
downloads/index.html| 4 ++--
events/index.html | 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html| 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html | 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html| 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html | 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html
[incubator-skywalking-website] branch mesh-loadtest updated (3def3ff -> 8baae32)
This is an automated email from the ASF dual-hosted git repository. hanahmily pushed a change to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git. discard 3def3ff fix some issues new 8baae32 fix some issues This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (3def3ff) \ N -- N -- N refs/heads/mesh-loadtest (8baae32) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 110 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes:
[incubator-skywalking-website] branch asf-site updated (4ef77de -> a1bf38b)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard 4ef77de Update asf-site
new a1bf38b Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4ef77de)
\
N -- N -- N refs/heads/asf-site (a1bf38b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html | 6 +++---
assets/js/{app.0449b5fa.js => app.962a8734.js} | 2 +-
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html| 4 ++--
blog/2019-01-25-mesh-loadtest.html | 4 ++--
blog/index.html | 4 ++--
downloads/index.html | 4 ++--
events/index.html| 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html| 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html | 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html| 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html | 4 ++--
zh/blog/index.html | 4 ++--
zh/doc/index.html| 4 ++--
zh/downloads/index.html | 4 ++--
zh/events/index.html | 4 ++--
zh/index.html| 4 ++--
zh/team/index.html | 4 ++--
26 files changed, 52 insertions(+), 52 deletions(-)
rename assets/js/{app.0449b5fa.js => app.962a8734.js} (84%)
[incubator-skywalking-website] branch mesh-loadtest updated (8baae32 -> 480f634)
This is an automated email from the ASF dual-hosted git repository. hanahmily pushed a change to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git. discard 8baae32 fix some issues new 480f634 fix some issues This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (8baae32) \ N -- N -- N refs/heads/mesh-loadtest (480f634) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 110 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes:
[incubator-skywalking-website] branch asf-site updated (a1bf38b -> 275dcae)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard a1bf38b Update asf-site
new 275dcae Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a1bf38b)
\
N -- N -- N refs/heads/asf-site (275dcae)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html | 4 ++--
assets/js/{app.962a8734.js => app.900c0a98.js} | 2 +-
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html| 4 ++--
blog/2019-01-25-mesh-loadtest.html | 4 ++--
blog/index.html | 4 ++--
downloads/index.html | 4 ++--
events/index.html| 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html| 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html | 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html| 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html | 4 ++--
zh/blog/index.html | 4 ++--
zh/doc/index.html| 4 ++--
zh/downloads/index.html | 4 ++--
zh/events/index.html | 4 ++--
zh/index.html| 4 ++--
zh/team/index.html | 4 ++--
26 files changed, 51 insertions(+), 51 deletions(-)
rename assets/js/{app.962a8734.js => app.900c0a98.js} (83%)
[incubator-skywalking-website] branch mesh-loadtest updated (480f634 -> 293a47a)
This is an automated email from the ASF dual-hosted git repository. hanahmily pushed a change to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git. discard 480f634 fix some issues new 293a47a fix some issues This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (480f634) \ N -- N -- N refs/heads/mesh-loadtest (293a47a) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 110 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: docs/blog/2019-01-25-mesh-loadtest.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
[incubator-skywalking-website] branch asf-site updated (275dcae -> 64c2749)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard 275dcae Update asf-site
new 64c2749 Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (275dcae)
\
N -- N -- N refs/heads/asf-site (64c2749)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html | 6 +++---
assets/js/{7.3074d918.js => 7.79f6c3db.js} | 2 +-
assets/js/{app.900c0a98.js => app.c88dafc4.js} | 4 ++--
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html| 4 ++--
blog/2019-01-25-mesh-loadtest.html | 6 +++---
blog/index.html | 4 ++--
downloads/index.html | 4 ++--
events/index.html| 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html| 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html | 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html| 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html | 4 ++--
zh/blog/index.html | 4 ++--
zh/doc/index.html| 4 ++--
zh/downloads/index.html | 4 ++--
zh/events/index.html | 4 ++--
zh/index.html| 4 ++--
zh/team/index.html | 4 ++--
27 files changed, 55 insertions(+), 55 deletions(-)
rename assets/js/{7.3074d918.js => 7.79f6c3db.js} (79%)
rename assets/js/{app.900c0a98.js => app.c88dafc4.js} (96%)
[GitHub] coveralls edited a comment on issue #2152: Support lettuce plugin
coveralls edited a comment on issue #2152: Support lettuce plugin URL: https://github.com/apache/incubator-skywalking/pull/2152#issuecomment-453734639 [](https://coveralls.io/builds/21275561) Coverage increased (+0.01%) to 14.333% when pulling **a492f804ce69cd2ac075cf466bb0a6aeb7a29192 on zhaoyuguang:local_plugin_lettuce** into **b5b69000cae0615e96f1fe355b5e0f0196b68ba2 on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] JaredTan95 opened a new pull request #2209: add thread-name.
JaredTan95 opened a new pull request #2209: add thread-name. URL: https://github.com/apache/incubator-skywalking/pull/2209 Please answer these questions before submitting pull request - Why submit this pull request? - [ ] Bug fix - [ ] New feature provided - [ ] Improve performance - Related issues ___ ### Bug fix - Bug description. - How to fix? ___ ### New feature or improvement - Describe the details and related test reports. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng opened a new pull request #2210: Fix a broken link
wu-sheng opened a new pull request #2210: Fix a broken link URL: https://github.com/apache/incubator-skywalking/pull/2210 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch wu-sheng-patch-1 deleted (was c24ed1d)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch wu-sheng-patch-1 in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git. was c24ed1d Update backend-cluster.md This change permanently discards the following revisions: discard c24ed1d Update backend-cluster.md
[GitHub] wu-sheng merged pull request #30: Mesh performance test blog
wu-sheng merged pull request #30: Mesh performance test blog URL: https://github.com/apache/incubator-skywalking-website/pull/30 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking-website] branch mesh-loadtest deleted (was 293a47a)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch mesh-loadtest in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git. was 293a47a fix some issues The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
[GitHub] coveralls commented on issue #2209: add thread-name.
coveralls commented on issue #2209: add thread-name. URL: https://github.com/apache/incubator-skywalking/pull/2209#issuecomment-457603230 [](https://coveralls.io/builds/21276396) Coverage increased (+0.002%) to 14.325% when pulling **b6cafcb34aff1dc46197b9d44cd6afb2ebf4689e on JaredTan95:thread_name** into **b5b69000cae0615e96f1fe355b5e0f0196b68ba2 on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking-website] branch master updated: Mesh performance test blog (#30)
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/incubator-skywalking-website.git The following commit(s) were added to refs/heads/master by this push: new 96d7dee Mesh performance test blog (#30) 96d7dee is described below commit 96d7dee1cdb19d0bae5fb1319f415a9e50b057d7 Author: Gao Hongtao AuthorDate: Fri Jan 25 23:10:18 2019 +0800 Mesh performance test blog (#30) * add mesh performance test blog * fix some issues --- .../blog/2019-01-25-mesh-loadtest/image1.png | Bin 0 -> 39044 bytes .../blog/2019-01-25-mesh-loadtest/image2.png | Bin 0 -> 6095 bytes .../blog/2019-01-25-mesh-loadtest/image3.png | Bin 0 -> 317634 bytes .../blog/2019-01-25-mesh-loadtest/image4.png | Bin 0 -> 308347 bytes .../blog/2019-01-25-mesh-loadtest/image5.png | Bin 0 -> 248460 bytes .../blog/2019-01-25-mesh-loadtest/image6.png | Bin 0 -> 51443 bytes docs/blog/2019-01-25-mesh-loadtest.md | 80 + docs/blog/README.md| 5 ++ 8 files changed, 85 insertions(+) diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image1.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image1.png new file mode 100755 index 000..2b11cd4 Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image1.png differ diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image2.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image2.png new file mode 100755 index 000..f666067 Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image2.png differ diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image3.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image3.png new file mode 100755 index 000..dcdde59 Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image3.png differ diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image4.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image4.png new file mode 100755 index 000..721bc6e Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image4.png differ diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image5.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image5.png new file mode 100755 index 000..99d0786 Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image5.png differ diff --git a/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image6.png b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image6.png new file mode 100755 index 000..24a3ea2 Binary files /dev/null and b/docs/.vuepress/public/static/blog/2019-01-25-mesh-loadtest/image6.png differ diff --git a/docs/blog/2019-01-25-mesh-loadtest.md b/docs/blog/2019-01-25-mesh-loadtest.md new file mode 100644 index 000..cb840b2 --- /dev/null +++ b/docs/blog/2019-01-25-mesh-loadtest.md @@ -0,0 +1,80 @@ +# SkyWalking performance in Service Mesh scenario + +- Auther: Hongtao Gao, Apache SkyWalking & ShardingShpere PMC +- [GitHub](https://github.com/hanahmily), [Twitter](https://twitter.com/hanahmily), [Linkedin](https://www.linkedin.com/in/gao-hongtao-47b835168/) + +Jan. 25th, 2019 + +Service mesh receiver was first introduced in Apache SkyWalking 6.0.0-beta. It is designed to provide a common entrance for receiving telemetry data from service mesh framework, for instance, Istio, Linkerd, Envoy etc. What’s the service mesh? According to Istio’s explain: + +The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. + +As a PMC member of Apache SkyWalking, I tested trace receiver and well understood the performance of collectors in trace scenario. I also would like to figure out the performance of service mesh receiver. + +## Different between trace and service mesh + +Following chart presents a typical trace map: + + + +You could find a variety of elements in it just like web service, local method, database, cache, MQ and so on. But service mesh only collect service network telemetry data that contains the entrance and exit data of a service for now(more elements will be imported soon, just like Database). A smaller quantity of data is sent to the service mesh receiver than the trace. + + + +But using sidecar is a little different.The client requesting “A” that will send a segment to service mesh receiver from “A”’s sidecar. If “A” depends on “B”, another segment will be sent from “
[incubator-skywalking-website] branch asf-site updated (64c2749 -> 9eb5479)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard 64c2749 Update asf-site
new 9eb5479 Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (64c2749)
\
N -- N -- N refs/heads/asf-site (9eb5479)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html | 6 +++---
assets/js/{app.c88dafc4.js => app.0e408921.js} | 2 +-
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html| 4 ++--
blog/2019-01-25-mesh-loadtest.html | 4 ++--
blog/index.html | 4 ++--
downloads/index.html | 4 ++--
events/index.html| 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html| 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html | 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html| 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html | 4 ++--
zh/blog/index.html | 4 ++--
zh/doc/index.html| 4 ++--
zh/downloads/index.html | 4 ++--
zh/events/index.html | 4 ++--
zh/index.html| 4 ++--
zh/team/index.html | 4 ++--
26 files changed, 52 insertions(+), 52 deletions(-)
rename assets/js/{app.c88dafc4.js => app.0e408921.js} (83%)
[GitHub] wu-sheng commented on issue #2199: httpClient-4.x-plugin throw MalformedURLException
wu-sheng commented on issue #2199: httpClient-4.x-plugin throw MalformedURLException URL: https://github.com/apache/incubator-skywalking/issues/2199#issuecomment-457604469 Could you help about why you could request a service without `http://xxx:123`? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng closed issue #2172: class[class com.alibaba.dubbo.monitor.support.MonitorFilter] after method[invoke] intercept failure java.lang.NullPointerException
wu-sheng closed issue #2172: class[class com.alibaba.dubbo.monitor.support.MonitorFilter] after method[invoke] intercept failure java.lang.NullPointerException URL: https://github.com/apache/incubator-skywalking/issues/2172 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng commented on issue #2172: class[class com.alibaba.dubbo.monitor.support.MonitorFilter] after method[invoke] intercept failure java.lang.NullPointerException
wu-sheng commented on issue #2172: class[class com.alibaba.dubbo.monitor.support.MonitorFilter] after method[invoke] intercept failure java.lang.NullPointerException URL: https://github.com/apache/incubator-skywalking/issues/2172#issuecomment-457605643 If you are using ElasticSearch 2.x, then this is not a bug. You could submit another issue to request supporting for ElasticSearch 2.x. But I don't know whether someone wants to take that, I could only tag that one as `help wanted`. So, I am closing this issue. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking-website] branch master updated: Update .travis.yml
This is an automated email from the ASF dual-hosted git repository. tanjian pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git The following commit(s) were added to refs/heads/master by this push: new 58b47c7 Update .travis.yml 58b47c7 is described below commit 58b47c74eecfb6f768415a13b5dde24fd91c9a69 Author: Jared Tan AuthorDate: Fri Jan 25 23:18:40 2019 +0800 Update .travis.yml --- .travis.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 6a6b2b7..07f962a 100644 --- a/.travis.yml +++ b/.travis.yml @@ -30,7 +30,8 @@ after_script: branches: only: -- master + - master + env: global: - GH_REF: github.com/apache/incubator-skywalking-website.git
[GitHub] wu-sheng commented on issue #2208: The UI cannot be accessed when a collector hangs
wu-sheng commented on issue #2208: The UI cannot be accessed when a collector hangs URL: https://github.com/apache/incubator-skywalking/issues/2208#issuecomment-457606299 If the data is in the process, definitely they are lost. The easy way, put a load balance between agent and backend cluster could help. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng merged pull request #2209: add thread-name.
wu-sheng merged pull request #2209: add thread-name. URL: https://github.com/apache/incubator-skywalking/pull/2209 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch master updated: add thread-name. (#2209)
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/incubator-skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 5914a2b add thread-name. (#2209)
5914a2b is described below
commit 5914a2b582236581c4073830eaa434475fcbe004
Author: Jared Tan
AuthorDate: Fri Jan 25 23:21:47 2019 +0800
add thread-name. (#2209)
---
.../org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java| 1 +
1 file changed, 1 insertion(+)
diff --git
a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
index 4a21173..7d25099 100644
---
a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
+++
b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
@@ -67,6 +67,7 @@ public class EasyLogger implements ILog {
String format(LogLevel level, String message, Throwable t) {
return StringUtil.join(' ', level.name(),
new SimpleDateFormat("-MM-dd HH:mm:ss:SSS").format(new Date()),
+Thread.currentThread().getName(),
targetClass.getSimpleName(),
": ",
message,
[incubator-skywalking-website] branch asf-site updated (9eb5479 -> c4b2970)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a change to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-skywalking-website.git.
discard 9eb5479 Update asf-site
new c4b2970 Update asf-site
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9eb5479)
\
N -- N -- N refs/heads/asf-site (c4b2970)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
404.html | 6 +++---
assets/js/{app.0e408921.js => app.1092991c.js} | 2 +-
blog/2018-05-24-skywalking-net.html | 4 ++--
blog/2018-12-12-skywalking-service-mesh-ready.html | 4 ++--
blog/2019-01-01-Understand-Trace.html| 4 ++--
blog/2019-01-25-mesh-loadtest.html | 4 ++--
blog/index.html | 4 ++--
downloads/index.html | 4 ++--
events/index.html| 4 ++--
index.html | 4 ++--
team/index.html | 4 ++--
zh/blog/2018-05-24-skywalking-net.html | 4 ++--
zh/blog/2018-12-18-Apache-SkyWalking-5-0-UserGuide.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-apm-sniffer-beginning.html | 4 ++--
zh/blog/2018-12-21-SkyWalking-source-code-read.html | 4 ++--
zh/blog/2019-01-02-Understand-trace-trans2cn.html| 4 ++--
zh/blog/2019-01-02-skywalking-elasticsearch-basic.html | 4 ++--
zh/blog/2019-01-03-monitor-microservice.html | 4 ++--
zh/blog/2019-01-21-agent-plugin-practice.html| 4 ++--
zh/blog/2019-01-24-skywalking-remote-debug.html | 4 ++--
zh/blog/index.html | 4 ++--
zh/doc/index.html| 4 ++--
zh/downloads/index.html | 4 ++--
zh/events/index.html | 4 ++--
zh/index.html| 4 ++--
zh/team/index.html | 4 ++--
26 files changed, 52 insertions(+), 52 deletions(-)
rename assets/js/{app.0e408921.js => app.1092991c.js} (84%)
[incubator-skywalking] branch wu-sheng-patch-2 updated: add thread-name. (#2209)
This is an automated email from the ASF dual-hosted git repository.
tanjian pushed a commit to branch wu-sheng-patch-2
in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git
The following commit(s) were added to refs/heads/wu-sheng-patch-2 by this push:
new 5914a2b add thread-name. (#2209)
new 344e632 Merge branch 'master' into wu-sheng-patch-2
5914a2b is described below
commit 5914a2b582236581c4073830eaa434475fcbe004
Author: Jared Tan
AuthorDate: Fri Jan 25 23:21:47 2019 +0800
add thread-name. (#2209)
---
.../org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java| 1 +
1 file changed, 1 insertion(+)
diff --git
a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
index 4a21173..7d25099 100644
---
a/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
+++
b/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/logging/core/EasyLogger.java
@@ -67,6 +67,7 @@ public class EasyLogger implements ILog {
String format(LogLevel level, String message, Throwable t) {
return StringUtil.join(' ', level.name(),
new SimpleDateFormat("-MM-dd HH:mm:ss:SSS").format(new Date()),
+Thread.currentThread().getName(),
targetClass.getSimpleName(),
": ",
message,
[GitHub] JaredTan95 opened a new pull request #31: [NO OPS！！！]test-braches
JaredTan95 opened a new pull request #31: [NO OPS！！！]test-braches URL: https://github.com/apache/incubator-skywalking-website/pull/31 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] coveralls commented on issue #2210: Fix a broken link
coveralls commented on issue #2210: Fix a broken link URL: https://github.com/apache/incubator-skywalking/pull/2210#issuecomment-457613789 [](https://coveralls.io/builds/21276931) Coverage decreased (-0.002%) to 14.321% when pulling **54c614b16911e76942f0d703598fb9e1a802bcda on wu-sheng-patch-2** into **b5b69000cae0615e96f1fe355b5e0f0196b68ba2 on master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] JaredTan95 closed pull request #31: [NO OPS！！！]test-braches
JaredTan95 closed pull request #31: [NO OPS！！！]test-braches URL: https://github.com/apache/incubator-skywalking-website/pull/31 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] coveralls edited a comment on issue #2152: Support lettuce plugin
coveralls edited a comment on issue #2152: Support lettuce plugin URL: https://github.com/apache/incubator-skywalking/pull/2152#issuecomment-453734639 [](https://coveralls.io/builds/21277333) Coverage increased (+0.008%) to 14.335% when pulling **d649c6c6d1234a964a91575acd3b591a4c33ba41 on zhaoyuguang:local_plugin_lettuce** into **5914a2b582236581c4073830eaa434475fcbe004 on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] coveralls edited a comment on issue #2210: Fix a broken link
coveralls edited a comment on issue #2210: Fix a broken link URL: https://github.com/apache/incubator-skywalking/pull/2210#issuecomment-457613789 [](https://coveralls.io/builds/21277401) Coverage decreased (-0.004%) to 14.323% when pulling **344e632816a7e5641c848cc47cc38f97ee1f5436 on wu-sheng-patch-2** into **5914a2b582236581c4073830eaa434475fcbe004 on master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch master updated: Update How-to-release.md (#2210)
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/incubator-skywalking.git The following commit(s) were added to refs/heads/master by this push: new 3b0a1d3 Update How-to-release.md (#2210) 3b0a1d3 is described below commit 3b0a1d3132ed5518f7729a3a349dccb99f0d9267 Author: 吴晟 Wu Sheng AuthorDate: Sat Jan 26 10:10:25 2019 +0800 Update How-to-release.md (#2210) --- docs/en/guides/How-to-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/guides/How-to-release.md b/docs/en/guides/How-to-release.md index edbc388..c81efc5 100644 --- a/docs/en/guides/How-to-release.md +++ b/docs/en/guides/How-to-release.md @@ -216,7 +216,7 @@ All PPMC members and committers should check these before vote +1. are in `https://dist.apache.org/repos/dist/dev/incubator/skywalking/x.y.z` with .asc, .sha512 1. `LICENSE` and `NOTICE` are in Source code and distribution package. 1. Check `shasum -c apache-skywalking-apm-incubating-x.y.z-src.tgz.sha512` -1. Build distribution from source code package (apache-skywalking-incubating-x.y.z-src.tar.gz) by following this [doc](https://github.com/apache/incubator-skywalking/blob/master/docs/en/How-to-build.md#build-from-apache-source-codes). +1. Build distribution from source code package (apache-skywalking-incubating-x.y.z-src.tar.gz) by following this [doc](https://github.com/apache/incubator-skywalking/blob/master/docs/en/guides/How-to-build.md#build-from-apache-source-code-release). 1. Apache RAT check. Run `./mvnw apache-rat:check`. (No binary in source codes) 1. DISCLAIMER exists
[GitHub] wu-sheng merged pull request #2210: Fix a broken link
wu-sheng merged pull request #2210: Fix a broken link URL: https://github.com/apache/incubator-skywalking/pull/2210 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch wu-sheng-patch-2 deleted (was 344e632)
This is an automated email from the ASF dual-hosted git repository. wusheng pushed a change to branch wu-sheng-patch-2 in repository https://gitbox.apache.org/repos/asf/incubator-skywalking.git. was 344e632 Merge branch 'master' into wu-sheng-patch-2 The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
[GitHub] coveralls edited a comment on issue #2152: Support lettuce plugin
coveralls edited a comment on issue #2152: Support lettuce plugin URL: https://github.com/apache/incubator-skywalking/pull/2152#issuecomment-453734639 [](https://coveralls.io/builds/21286688) Coverage increased (+0.01%) to 14.335% when pulling **5da716b11e53c112c0f9fbc2fd23252b80713a2a on zhaoyuguang:local_plugin_lettuce** into **3b0a1d3132ed5518f7729a3a349dccb99f0d9267 on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wu-sheng merged pull request #2152: Support lettuce plugin
wu-sheng merged pull request #2152: Support lettuce plugin URL: https://github.com/apache/incubator-skywalking/pull/2152 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[incubator-skywalking] branch master updated: Support lettuce plugin (#2152)
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/incubator-skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new a36394d Support lettuce plugin (#2152)
a36394d is described below
commit a36394d9bc2d66de37a50a01ea7fb0edecd5db3e
Author: 于玉桔 <769213...@qq.com>
AuthorDate: Sat Jan 26 13:09:03 2019 +0800
Support lettuce plugin (#2152)
* Support lettuce plugin
* lettuce plugin bugfix
* lettuce plugin fix license issue
* lettuce plugin fix cluster and config issue
* plugin lettuce compatible with low 5.0.x version
* lettuce plugin support version accurately describes on Supported-list.md
* plugin lettuce compatible with low 5.0.2 version
* lettuce plugin fix wrong batch method intercept point
* move lettuce to optional plugins
* fix ci issue
* fix ci issue
* Modify the description file
* Pom code optimization
* Optimization operation name
* Optimization operation name2
---
.../network/trace/component/ComponentsDefine.java | 5 +-
.../optional-plugins/lettuce-5.x-plugin/pom.xml| 46 +
.../lettuce/v5/AsyncCommandMethodInterceptor.java | 60 +++
.../v5/ClientOptionsConstructorInterceptor.java| 37 +++
.../lettuce/v5/RedisChannelWriterInterceptor.java | 89
.../v5/RedisClientConstructorInterceptor.java | 39 +++
.../RedisClusterClientConstructorInterceptor.java | 44
.../apm/plugin/lettuce/v5/SWConsumer.java | 56 +++
.../v5/define/AsyncCommandInstrumentation.java | 72 +
.../v5/define/ClientOptionsInstrumentation.java| 67
.../define/RedisChannelWriterInstrumentation.java | 87
.../v5/define/RedisClientInstrumentation.java | 67
.../define/RedisClusterClientInstrumentation.java | 67
.../src/main/resources/skywalking-plugin.def | 21
.../v5/RedisChannelWriterInterceptorTest.java | 112 +
apm-sniffer/optional-plugins/pom.xml | 1 +
docker/config/component-libraries.yml | 4 +
docs/en/guides/Component-library-settings.md | 1 +
docs/en/setup/service-agent/java-agent/README.md | 1 +
.../service-agent/java-agent/Supported-list.md | 1 +
.../others/cn/guides/Component-library-settings.md | 2 +
.../cn/guides/Java-Plugin-Development-Guide.md | 2 +-
.../src/test/resources/component-libraries.yml | 4 +
.../src/main/resources/component-libraries.yml | 4 +
24 files changed, 887 insertions(+), 2 deletions(-)
diff --git
a/apm-protocol/apm-network/src/main/java/org/apache/skywalking/apm/network/trace/component/ComponentsDefine.java
b/apm-protocol/apm-network/src/main/java/org/apache/skywalking/apm/network/trace/component/ComponentsDefine.java
index 2c0c566..c0784d1 100644
---
a/apm-protocol/apm-network/src/main/java/org/apache/skywalking/apm/network/trace/component/ComponentsDefine.java
+++
b/apm-protocol/apm-network/src/main/java/org/apache/skywalking/apm/network/trace/component/ComponentsDefine.java
@@ -110,6 +110,8 @@ public class ComponentsDefine {
public static final OfficialComponent REDISSON = new
OfficialComponent(56, "Redisson");
+public static final OfficialComponent LETTUCE = new OfficialComponent(57,
"Lettuce");
+
private static ComponentsDefine INSTANCE = new ComponentsDefine();
private String[] components;
@@ -119,7 +121,7 @@ public class ComponentsDefine {
}
public ComponentsDefine() {
-components = new String[57];
+components = new String[58];
addComponent(TOMCAT);
addComponent(HTTPCLIENT);
addComponent(DUBBO);
@@ -161,6 +163,7 @@ public class ComponentsDefine {
addComponent(CANAL);
addComponent(GSON);
addComponent(REDISSON);
+addComponent(LETTUCE);
}
private void addComponent(OfficialComponent component) {
diff --git a/apm-sniffer/optional-plugins/lettuce-5.x-plugin/pom.xml
b/apm-sniffer/optional-plugins/lettuce-5.x-plugin/pom.xml
new file mode 100644
index 000..1ad9451
--- /dev/null
+++ b/apm-sniffer/optional-plugins/lettuce-5.x-plugin/pom.xml
@@ -0,0 +1,46 @@
+
+
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+4.0.0
+
+org.apache.skywalking
+optional-plugins
+6.1.0-SNAPSHOT
+
+
+apm-lettuce-5.x-plugin
+jar
+
+lettuce-5.x-plugin
+http://maven.apache.org
+
+5.1.3.RELEASE
+1.8
+
+
+
+
+io.lettuce
+lettuce-core
+${lettuce-core.
[GitHub] zhaoyuguang opened a new pull request #2211: Support Zookeeper plugin
zhaoyuguang opened a new pull request #2211: Support Zookeeper plugin URL: https://github.com/apache/incubator-skywalking/pull/2211 Please answer these questions before submitting pull request - Why submit this pull request? - [ ] Bug fix - [ ] New feature provided - [x] Improve performance ___ ### New feature or improvement - Describe the details and related test reports. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
