You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/07/10 14:47:02 UTC
[GitHub] [skywalking] wu-sheng opened a new issue #7280: [SkyWalking 10] Service Architecture-Layer Concept
wu-sheng opened a new issue #7280:
URL: https://github.com/apache/skywalking/issues/7280
Hi @apache/skywalking-committers
I am writing this issue and created 10.0.0 milestone to track for long-term ideas. We are going to maintain and enhance SkyWalking 8.x and reserve 9.x for possible breaking upgrades. So, SkyWalking 10 would be the next core-level features and architecture-related version.
The first idea in mine and @Fine0830 's mind is a new and powerful UI, with all existing monitoring targets that would work together. Currently, we have in-process agents, mesh-controlled services/pods, k8s nodes, VM(OS) nodes. In real architecture, they are in different layers physically.
1. Language agents monitoring services are in-process level, which is the code and method level monitoring. They are on the top of VM(OS) or in a pod managed by k8s, even service mesh
2. Mesh-controlled services are in k8s pod or VM.
3. K8s nodes are on VM(OS) nodes.
Also, we could have higher lever layer, such as
1. `Versioned service` to group service instances based on CD and version control system
2. `Cluster` to group services based on physical deployment.
Each instance could have layer concepts, including `on top of` and `contains` 2 types.
1. `on top of` could represent a service instance that is running on a VM node.
2. `contains` could represent a k8s node containing several images.
For filling this relationship, each level's agents should enhance the capabilities to build this kind of link.
Service should aggregate instances' layers(2 directions) together, and automatically splits into different logic service group to represent different groups of instances which have same layer information.
To @Fine0830, UI should have a totally different layout, the first level should be dynamic layers, then each layer should provide supported observability data, such as whether
1. Traces/logs are available
2. Events detected
3. Metrics dashboards
All these things are dynamic in the runtime. Alarms should be another one on the top level, but be able to link to a specific service/instance in a specific layer.
Also, we should have a layer map, from top to bottom, such as this(only a demo)
But also, should accept those layers could have more than one of this scenograph.
___
All above changes are compatible at the protocol level, as layers could be assigned at the backend or using new fields.
If anyone has anything want to discuss, welcome to comment here or set up a video meeting with me.
--
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-unsubscribe@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [skywalking] wu-sheng closed issue #7280: [SkyWalking 10] Service Architecture-Layer Concept
Posted by GitBox <gi...@apache.org>.
wu-sheng closed issue #7280:
URL: https://github.com/apache/skywalking/issues/7280
--
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-unsubscribe@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [skywalking] wu-sheng commented on issue #7280: [SkyWalking 10] Service Architecture-Layer Concept
Posted by GitBox <gi...@apache.org>.
wu-sheng commented on issue #7280:
URL: https://github.com/apache/skywalking/issues/7280#issuecomment-891876845
This is still open to discussion, just close as this is long-term. All committers are welcome to share ideas.
--
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-unsubscribe@skywalking.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org