『Skywalking』. Net core fast access distributed link tracking platform

---

Pay attention to me and don't get lost in learning back-end architecture
If it helps you , welcome Point a praise To encourage
If you need it next time , Sure Collection get up , Avoid missing next time

---

Share good news
『ScheduleMaster』 Get started quickly with a highly available open source distributed task scheduling platform

---

After reading this article, you can gain

• .NET Core Access Skywalking
• understand Skywalking The overall architecture design
• understand Skywalking What about the technical indicators of
• All pits during production deployment are skipped

One 、 summary

1 Concept ——SkyWalking What is it? ？

Application performance monitor tool for distributed systems, especially designed for microservices, cloud native and container-based (Kubernetes) architectures.

Application performance monitoring tools for distributed systems , Dedicated to micro Services 、 Cloud native architecture and container based （Docker、K8s、Mesos） Architecture and Design .
Provide distributed tracking 、 Service grid telemetry analysis 、 Measurement aggregation and visualization integration solution .

2 Core functions

• Multiple monitoring means . You can use language probes and service mesh Getting monitoring is data
• Multiple language auto probes . Include Java,.NET Core and Node.JS
• Lightweight and efficient . No big data platform , And a lot of server resources
• modularization .UI、 Storage 、 There are various mechanisms for cluster management
• Support alarm
• Excellent visualization solution

3 System architecture

Consider making the description simpler , We give up Metric Index correlation , And focus on Tracing Link related functions .

• Upper part Agent ： Responsible for... From the application , Collect link information , Send to SkyWalking OAP The server . At present, we support SkyWalking、Zikpin、Jaeger And so on Tracing Data and information . And what we're using now is ,SkyWalking Agent collect SkyWalking Tracing data , Pass it to the server .
• Lower part SkyWalking OAP ： Responsible for receiving Agent Sent Tracing Data and information , And then analyze it (Analysis Core) , To external storage ( Storage ), Finally, provide the query ( Query ) function .
• Right section Storage：Tracing data storage . At present, we support ES、MySQL、Sharding Sphere、TiDB、H2 Multiple memories . And what we're using now is ES , The main consideration is SkyWalking The development team's own production environment uses ES Mainly .
• Left part SkyWalking UI ： Responsible for providing the console , Look at the links and so on .

Two 、 Tool installation

• Skywalking Download installation reference for ： Click here to jump

3、 ... and 、.NET Project access

1. NuGet Package reference

• It needs to pass in every service NuGet quote SkyAPM.Agent.AspNetCore , If it is .net core3.1 You need to choose 1.3.0 edition
  

2. Add configuration file skyapm.json

{
    
  "SkyWalking": {
    
    "ServiceName": "demo-application",
    "Namespace": "",
    "HeaderVersions": [
      "sw8"  //6.x The following version is sw6
    ],
    "Sampling": {
    
      "SamplePer3Secs": -1,
      "Percentage": -1.0
    },
    "Logging": {
    
      "Level": "Information", // Fill in the blanks 
      "FilePath": "logs\\skyapm-{Date}.log"// Fill in the blanks 
    },
    "Transport": {
    
      "Interval": 3000,
      "ProtocolVersion": "v8", //6.x The following version is v6
      "QueueSize": 30000,
      "BatchSize": 3000,
      "gRPC": {
    
        "Servers": "localhost:11800", //ip:port
        "Timeout": 10000,
        "ConnectTimeout": 10000,
        "ReportTimeout": 600000
      }
    }
  }
}

• Be careful ：

1. gRPC Of Servers You need to specify the SkyWalking The server address of , The default port is 11800
2. v8 Refers to the version number , The new version is v8

3. Configure environment variables

• Directly change the startup file

 "ASPNETCORE_HOSTINGSTARTUPASSEMBLIES": "SkyAPM.Agent.AspNetCore"

• Or at startup Program.cs->Main() Set the environment variable at the beginning of the method

Environment.SetEnvironmentVariable("ASPNETCORE_HOSTINGSTARTUPASSEMBLIES", "SkyAPM.Agent.AspNetCore");

4. skyapm.json File output

• take skyapm.json File properties ” Copy to output directory “ It is amended as follows ” If newer, copy ”

Four 、 Operation monitoring

• Now you can use , open skywalking Address , See the effect
• here , We can see .NET Core The service of the application is demo-application

1 General service ——General-Service

General service (General-Service)： Represents a series or set of workloads that provide the same behavior for requests . In the use of Agent or SDK When , You can define the name of the service .

2 Main monitoring indicators

• Click on demo-application This service name , You can see the 【 Overall monitoring information 】

• ApdexScore ： Performance index ,Apdex(Application Performance Index) It is an international standard ,Apdex It is the quantitative value of users' satisfaction with application performance . It provides a unified way to measure and report user experience , Take the end-user experience and application performance as a complete indicator for unified measurement , The highest is 1 The lowest is 0;

• ResponseTime： response time , That is, within the selected time , Average response time for all requests served (ms);

• ServiceLoad-Throughput: Service load - throughput , That is, within the selected time , The number of requests that the service responds to per minute (cpm)

• SuccessRate: Company -（SLA）service level agreement, Service level agreement ,SW Specifically refers to the percentage of successful requests that are responded to every minute .

• Slow Endpoint in Current Service : Current service slow Endpoint , The service indicator dashboard will list the endpoints with the largest response time of the current service Top10, If the response time of an endpoint is too high , We need to pay more attention to its indicators （ Click to copy the endpoint name ）.

• Endpoint Load in Current Service : Current service load （ throughput ） High endpoint , From this, we can infer the load between instances . If the throughput of an instance is found to be low , You need to query instance indicators （ For example, query whether the instance has occurred GC, Or CPU Utilization is too high ）

3 Service instance ——Service Instance

• Service instance (Service Instance)： Each of the above set of workloads is called an instance . It's like Kubernetes Medium pods equally , An instance of an operating system is not necessarily a service . But when you're using Agent When , A service instance is actually a real process on the operating system
• Click on [Instance] tab , You can find the service 【 The instance list 】

4 Endpoint ——Endpoint

• Endpoint (Endpoint) ： For the request path received by a specific service , Such as HTTP Of URI Path and gRPC The class name of the service + Method signature . here , We can see .Net Core An endpoint of the application , by API Interface /demo/echo

• Click on [Endpoint] tab , You can view the 【 Endpoint list 】

5 Topology ——Topology

• Click on [Topology] tab , You can view the 【 Topology 】
  

6 link ——Trace

• Click on [Trace] tab , You can view the 【 link 】.

7 journal ——Log

• Click on [Log] tab , You can view the 【 journal 】.

5、 ... and 、 Production environment deployment

If the start-up of the third point is adopted Program.cs->Main() Set the environment variable at the beginning of the method
Then the following operations can be omitted

---

1. Linux Deploy

• Command line startup mode , increase systemd environment variable , The grammar is

Environment=ASPNETCORE_HOSTINGSTARTUPASSEMBLIES=SkyAPM.Agent.AspNetCore

2. Windows IIS Mode deployment

The project is compiled and published to IIS,SkyWalking It doesn't work , We need to be in IIS Set the environment variable in , There are two ways to set environment variables

1. Method 1 ： There will be web.config, We need to be in web.config Add environment variables to
   

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\MI.Web.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout">
                <environmentVariables>
                    <environmentVariable name="ASPNETCORE_HOSTINGSTARTUPASSEMBLIES" value="SkyAPM.Agent.AspNetCore" />
                    <environmentVariable name="SKYWALKING__SERVICENAME" value="xx.Service" />
                </environmentVariables>
            </aspNetCore>
    </system.webServer>
  </location>
</configuration>

2. Method 2 ： adopt IIS To configure

• Select the corresponding item , Click configuration editor