After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).
Pinpoint is an APM (Application Performance Management) tool for large-scale distributed systems written in Java. Inspired by Dapper, Pinpoint provides a solution to help analyze the overall structure of the system and how components within them are interconnected by tracing transactions across distributed applications.
You should definitely check Pinpoint out If you want to
understand your application topology at a glance monitor your application in Real-Time gain code-level visibility to every transaction install APM Agents without changing a single line of code have minimal impact on the performance (approximately 3% increase in resource usage)
Understand the topology of any distributed systems by visualizing how their components are interconnected. Clicking on a node reveals details about the component, such as its current status, and transaction count.
Monitor active threads inside applications in real-time.
Visualize request count and response patterns over time to identify potential problems. Transactions can be selected for additional detail by dragging over the chart.
Gain code-level visibility to every transaction in a distributed environment, identifying bottlenecks and points of failure in a single view.
View additional details on the application such as CPU usage, Memory/Garbage Collection, TPS, and JVM arguments.
Quick start(No neet to start TestApp)
pom.xml
Create API interface:
pom.xml
HelloService
interface:application.properties
:pom.xml
@Reference
injection HelloService
application.properties
:Dubbo provider
and Dubbo consumer
http://localhost:8080/sayHello?name=ABC
The user request here is double the number of requests for DubboProvider, because the favicon.ico icon request is recorded.
The example simply simulates the provision and call of Dubbo, and does not carry out the application of other middleware such as database. For detailed use, please refer to the Pinpoint document.