 Hello everyone, I'm pleasure to be here to have the opportunity to sharing and the series smash conference Europe. This topic I'm sharing today is use skywalking satellite to process tracing login and the metrics insert smash. Let me introduce myself first. My name is Ming Wen. I'm the co-founder of API 7.ai, which is an open source software startup company in China. And I'm also the PMC chair of Apache API 6. API 6 is the Apache software foundation's top level project and API 6 is a dynamic real time high performance API gateway. API 6 provides traffic management features such as load balancing, dynamic breaking upstream, other observability and more features. You can use Apache API 6 to handle traditional North source traffic, as well as the east to west traffic between the services. It can also be used as Kubernetes ingress controller. I'm also the committer of Apache skywalking. You can reach me through the following Twitter, email and the GitHub channels. First, let's take a look at the summer problems faced by the series smash. The surface mesh is absolutely a good solution. But at the same time, the surface mesh will also bring some problems. We may have hundreds or thousands of services. And there is a set current to the each service. The calling relationship between services is more complicated. So do you know how your services call each other? And how can we see each service have problems with calls? This is the first question. And the second problem is that we hope to analyze and process this kind of observability data in the series smash. In the traditional solution, we need to send the metrics data to primary shoes and send the tracing data to ZIPK or Apache skywalking. And then we send the logging data to electric search. There will have lots of differences in our system. In terms of observability, we need to relay on and the list three open source governments. Primary shoes, skywalking and ERK. This is more difficult for a system to maintain so many open source projects. For the enterprise, the cost will be higher. So is there any way we can make it easy to maintain and reduce our use costs? Before this introduction, let's take a look at what Apache skywalking is. Apache skywalking is an APM tools for distributed systems. APM means application performance monitor. Skywalking is special designed for the microservices, cloud native and the container based architectures. The 8.4 version of skywalking supports three types of data including logging, metrics and tracing. So we can process the data uniformly through Apache skywalking. Let's look at another question. How can we better collect the data on the service side? Then we need to introduce a sub-project of skywalking, the skywalking satellite. Skywalking satellite is a highway to collector. It's also a sidecar that could be deployed close to the target system to collect metrics, tracing and logging. And it also provides more features such as the local cache, format, transform, shaping. The following is a texture of satellite. We can see that we can collect the log data through satellite. The log data may come from the APP's log or you may have Enable Envoys, ARS, Plugin or Engix log. Yes, it can be all kinds of logs. About tracing, skywalking has a lot of agents such as Golan agent, Lula agent or the Java agent. This agent can also send the data to a satellite. The third part is Plumiceus data. We know that Plumiceus data is provided by polling, which is a request to you to expose a port to the outside, which is not safe. We can limit the polling behavior to the local machine through the satellite. And then satellite pushes Plumiceus data to the remote skywalking instead of polling. Now, satellite can use the Kafka protocol to send data to Kafka. And then we like skywalking act as a consumer to process the data sent from the satellite. Then let's take a look at why we need this project, why we need the skywalking satellite. Forms above are captured. We can see that we only use one component of the APP side, satellite. Satellite is a one stop APM data collector. It's covering the tracing, logging and metrics. As we mentioned earlier, it can cover the Plumiceus fetch model to a safer push model. Because it is local, so we can do more data filter and cache before we send the data to the skywalking. Another advantage of satellite is that when the service restart or the service crash, we will not lose data because all of the data has been saved in the satellite. Then let's take a look at another example of use satellite with Apache API 6. The previous architecture is more suitable for the deploy the service and the skywalking in the same VPC because you send all of the data to Kafka. But how to send the data from hybrid cloud architecture? You may use both satellite and Apache API 6. API 6 is an infrastructure part of the processing critical traffic in grass. And API 6 has the skywalking plugin. So it can replace Kafka to receive such as observability data. In other words, API 6 and skywalking are deployment in the public cloud while the service may be on-premise. So while sending your data, you cannot use the Kafka protocol but use the GIPC and MTRS. In this way, you can send the satellite data to Apache API 6 on the public cloud and then the API 6 send it to the skywalking, so the skywalking plugin of API 6 for processing. The satellite is a very young open source project, so it still has a lot of tutu features. For example, we want to support demon site so that we can save more resources. Especially for the deployment model of the service mesh, saving resources is also a critical factor. Also, we will support more protocols such as open telemetry, Envoy ARS, ARS means the accept log service and Apache API 6 ARS. Because the satellite is a project deployed on the edge side, so we can do more works on the edge. For example, we can pre-process the data and we can compromise the data. In this way, when we send data to the back-end skywalking service, our data has been filtered. So that will make it easy and process and stop. This is just a brief introduction above. If you want to know more about the skywalking, skywalking satellite and the Apache API 6 project, you can learn more from the GitHub. Thank you.