image_1.pngCopyright©2024 Yonyou Group All Rights Reserved.Without the written permission of Yonyou Group, no part of this user manual may be copied, reproduced, translated, or reduced for any purpose. The content of this user manual may change without notice, please stay informed.Please note: The content of this user manual does not represent a commitment made by Yonyou Network.Product IntroductionProduct ArchitectureThe new generation YonBIP Monitoring Center, referred to as YMC, is characterized by real-time monitoring and rapid diagnosis and problem location. It provides diversified monitoring and problem diagnosis analysis services for YonBIP, ranging from public cloud to dedicated cloud, through multi-level resource monitoring of host-microservices-instances-middleware, full-link monitoring of microservices, real-time thread monitoring and analysis, BPR business recording diagnosis, and cloud remote monitoring capabilities.The YMC module mainly includes YMC-Link (Central Console), YMC (Portal), YMC-Proxy (Client Proxy), thread monitoring, BPR performance reports, alarm center, log center, monitoring metrics, link analysis, performance tools, operation and maintenance tools, user insights, user management, customer project management, and other module capabilities.image_2.pngAdopting a cloud-edge architecture design to achieve remote real-time monitoring of customer project site systems, facilitating the discovery and analysis of on-site project issues.image_3.pngSystem Description1) YMC Portal Entry https://ymc.{environment configuration domain}2) YMC Link Console Entrance https://ymclink.yonyoucloud.com3) Requirements for Accessing YMC:The microservice uses the second-party package version 8.2.100-RELEASE.Execute the pipeline to activate the introduction of the two-party package, which will automatically connect to the YMC system.License DescriptionStarting from version R6, YMC distinguishes between basic features and advanced features.The basic version of YMC can be used after purchasing the [Cloud Resource Management Platform].The advanced features of YMC require a separate purchase of the [YMC Monitoring Center] to be used.The feature division between the Standard Edition and the Premium Edition is as follows:Basic Version Features| 1. Alarm Center: a. Current Alarms b. Alarm Query c. Policy Management d. Notification Management e. Channel Management f. Basic Information 2. Log Center: a. Cluster Event Query b. Cluster Event Analysis c. Access Log Analysis d. Nginx Log Analysis e. Business Log Analysis 3. Metric Monitoring: a. Microservice Monitoring (Basic Version Homepage Entry) b. Instance Monitoring c. Cluster Monitoring d. Host Monitoring e. Middleware Monitoring f. Microservice Overview 4. Link Analysis: Link Tracing (Hubble Diagnostic Report, Hubble Recording) |Advanced Features| 1. Home Thread Overview (Advanced Version Home Entry) 2. Real-time Thread Monitoring 3. BPR (BPR Diagnostic Report, BPR Recording) 4. Snapshot (Thread Snapshot) 5. Log Center -> Warning Log Analysis 6. Metric Monitoring -> Process Monitoring 7. Performance Tools: a. Flame Graph b. Historical Analysis Report c. JVM Performance Diagnosis d. JVM Monitoring Panel e. Microservices Performance Analysis f. SQL Force Kill 8. Operation and Maintenance Tools: a. Remote Host Management b. Remote Task Management 9. Container and Host Console (Supports Arthas Functionality) 10. User Insights (UBA): a. Active Reports (Tenant Activity, Active Queries) b. Dashboard Overview (YonBIP Monitoring Dashboard) c. Analysis Queries (Overview Statistics, Session Analysis, Error Analysis, Event Queries) |Usage InstructionsRegister the Youhutong account deployed in the environment (if you have an account, you can skip this step).Access the YMC portal page and log in to Youhutong: https://ymc.{environment domain}Production environment domain: yonyoucloud.comResearch and Development Network Environment Domain Name: yyuap.comPrivate cloud environment address: https://{Technical Platform Environment Domain}/ymcNotify the YMC system administrator to authorize a regular user role for themselves using the administrator role account and grant the necessary environment permissions.After authorization, log out and log in again to use YMC normally.image_4.pngHome PageSystem OverviewReal-time display of the current YonBIP project and environment's operational information, active user count, task count, QPS, and alarms.The overall usage of numbers, as well as CPU, memory, and network.image_5.pngDescription:30-Minute Active Users: The system will count the number of active users within 30 minutes. Clicking will allow you to view the ranking of specific users based on the number of requests made within that 30-minute period.Real-time task count: Click to display the current number of system tasks, which reflects the current status of active threads.QPS: Statistics of the number of requests per second at the Ingress entry, providing feedback on the request volume at the entry;QPM: The amount of tasks the system handles per minute, reflecting the current minute-level throughput of the system.Environment selection: You can switch between different environments for use.Link TopologyReal-time display of the call chain from Ingress to microservices and then to middleware.image_6.pngimage_7.pngDescription:Display the current environment's Ingress Controller QPS and the upstream and downstream bandwidth.Display the current number of microservice execution tasks by domain, distinguishing the number of tasks and whether there are any anomalies by color. Additionally, allow users to click through to the microservice thread-level monitoring page.Show the relationship between microservices and middleware, and it can also display the relationship from middleware to microservices (to be completed).Microservices and ExamplesDisplay all microservices and instances currently connected to YMC. The microservices should show the domain, total resources, instance configuration, number of instances, number of abnormal instances, QPM, current task count, and number of active users, with the ability to view thread information and historical data under each microservice. The instance display should include host IP, instance IP, status, QPM, requests (number of requests), bgTasks (number of background tasks), CPU, memory, JVM information, and the ability to view thread information and historical requests within the instance, as well as direct access to the instance console. All fields should support sorting operations.image_8.pngimage_9.pngMicroservices and Instance Executable Operations on a Single Microservice or Instance:Microservice executable threads, microservice monitoring operations;Instance executable threads, console, recent requests, metrics monitoring operations.Middleware, Hosts, Host GroupsThis section displays the monitoring information for middleware, hosts, and host groups. The host groups not only include the monitoring of the previous resource pools but also the monitoring of custom host groups.image_10.pngimage_11.pngimage_12.pngDescription:Middleware and resource pools can view status as well as CPU and memory information;The host can view CPU, memory, disk, and network information;The total number of instances for the host refers to the number of instances excluding business instances. Hovering the mouse over it can display specific instance information.The number of business instances of the host refers to the instances connected to the YMC system. Clicking will directly take you to the thread information page of the instance.image_13.pngThread MonitoringProduct DesignThread monitoring is a very core function of YMC. The system collects real-time running information of the current threads in microservices, supports refreshing collection, generating snapshots, snapshot lists, recent requests, and allows direct access to the instance console.Instance ListReal-time collection of all instance running information in the current system.image_14.pngDescription:Display all executing tasks' threads in the current system, including the throughput per minute (QPM), corresponding average response time (avg), number of active requests (requests), number of active background tasks (bgTasks), instance CPU load, instance memory, and JVM memory.Thread ListReal-time collection of detailed performance data for requests occurring in the selected instance.image_15.pngimage_16.pngThread list display, TraceID, business operation, total time consumed, computation time consumed, SQL time consumed and count, result set reading time and count, RPC time and count, Cache time and count, DB connection time and count, thread name, calling method, SQL count, result reading time, result set, network uplink and downlink traffic, number of unclosed connections, total number of connections, client IP address, tenant ID, username, current service, upstream service;TraceID, marked with [*RPC], indicates that the traceID is not equal to the spanID. Conversely, if the traceID equals the spanID, it indicates an entry request, which is a non-RPC request.Clicking on each record in the thread list will display the SQL stack, execution time, number of response rows, start execution time, data source, connId, and thread stack information below.Click on TraceID or double-click on each row in the thread list to pull out the thread detail page on the right drawer.Calculation of time consumed = Total time consumed - SQL time consumed - Result set reading time - RPC time consumed - Cache time consumed;image_17.pngRPC Stack Informationimage_18.pngReal-time association of front-end business operation names;image_19.pngThread DetailsThread Details PageYou can refresh the current thread, generate a thread snapshot, and display specific business operations, thread information, SQL information, calling methods, thread stack, SQL stack, RPC stack, current services, upstream services, the most time-consuming SQL, the most time-consuming RPC, and other information on the page.Most Time-Consuming SQL, Most Time-Consuming RPCimage_20.pngUpstream Service Informationimage_21.pngThe business operation name will be passed downstream like a TraceId, so that the downstream can know which page button triggered this call.image_22.pngThread AnalysisThis feature is suitable for analyzing requests that have been running for a long time without ending, accessible in the thread details.image_23.pngAfter starting the thread profiling, performance data for the request will be requested every 2 seconds and displayed in a tree structure.image_24.pngThread information. Includes instance name, thread name, trace ID, total time consumed, business operation name, thread status, current event, performance statistics data, remote call method name, client address, operating user ID, tenant ID;Real-time refresh switch. Enabled by default. When turned on, it samples threads at 2-second intervals until the task stops or the refresh switch is manually turned off;Thread real-time data trend chart. Displays the number of SQL queries, result set size, number of RPC calls, as well as SQL execution time, result set reading time, RPC time, and total time (merged into a single area chart).Thread profiling. Display the thread sampling stack content. Multiple calls will generate multiple thread stacks.CPU: Represents the number of times the method for CPU usage has been collected;Max: Represents the maximum number of times the CPU usage is collected for a single method;Find the stack information that identifies the maximum number of CPU usage through the text marked in red.Thread SnapshotTypes of SnapshotsSnapshots are divided into three types:Single-threaded snapshot (current page...
