Conversation
…tanceProperties as a new source. 3. Remove Month as downsamping and query step.
|
The codes level key changes are
|
…just the receiver, starting with trace analysis.
|
@kezhenxu94 @ascrutae @arugal @heyanlong @ElderJames New protocol |
|
@apache/skywalking-committers , I just made the project package passed. Now we could move on the core tests.
|
|
Mark it as "Ready for review" as the test cases should be fixed now, and move to next step if anyone will review the code |
| exitSpan = parentSpan; | ||
| } else { | ||
| final int parentSpanId = parentSpan == null ? -1 : parentSpan.getSpanId(); | ||
| if (StringUtil.isEmpty(remotePeer)) { |
There was a problem hiding this comment.
This deletion actually is not related to this PR. The lazy peer initialization is another feature :) @kezhenxu94
SummaryThis pull request is open for 10 days, and I worked on this 2 weeks ago. Thanks everyone to help making this PR and tests work now. Here are the list of changes we made in this pull request. Top 3 are the principle changes, others are following these principles.
FYI @apache/skywalking-committers |
mrproliu
left a comment
There was a problem hiding this comment.
I have a test with the profile and alarm module, it works well. And test Nginx agent on the local environment, it works well too.
dmsolr
left a comment
There was a problem hiding this comment.
I have tested java agent and agent plugin. It looks good to me.
|
@kezhenxu94 Are you going to do code level review? |
I can do another round of review recently, but that’s not a blocker to merge this, it looks good to me generally, just merge it if necessary |
|
@kezhenxu94 I am adjusting some documentations, after that, I will merge this. |
This would be a huge pull request, relating to protocol, agent and backend. 8.x would be an new core without back forward compatibility.
After the experiences of removing endpoint_inventory, I found out this
strategy is successful.
Especially, we totally get rid of register, so I want to do more.
SkyWalking 8.0.0
First, it is already unexpected for me, we have to move to 8.0.0 so
quickly, but after the discussion with @hanahmily , and thinking about this for several days, I think
we have to.
The key chances are following
register protocols are totally going to be removed.
Instance name are generated by the agent itself, but the extra information,
such as IP, hostname, language, should report to backend separately.
the time bucket as we need accurate service name in the given duration
such as language, hostname.
service instance name, endpoint name and network address. This could ease
the agent logic, but also, requires changes in all language agent and
plugin test tool,
string.
compatibility test(doesn't support anymore).
The benefits we will get are
users. (We received a lot of issue reports about this)
one. (Users don't feel comfortable about upgrade)
In my mind, I think this totally break upgrade is super meaningful and will
be good change. Even we break many things, they are easy to follow.
@mrproliu I think by following this, we need
to change the collaboration header to
sw8:) As no 7.1.0 release willhappen.
Link to mail list, https://lists.apache.org/thread.html/rda36fa8d191fc5750fc793993c69e14a917138bf97f9c2a461b72811%40%3Cdev.skywalking.apache.org%3E