Why can't the open source dubbo monitoring solution be sent to the production environment?
---------------
The principle of monitoring is:
1 Service consumers and providers accumulate the number of calls and call time in memory, and send statistical data to the monitoring center every minute.
2 After the monitoring center collects the data, save the statistical data to the local, and draw the chart
3 The monitoring center provides query capabilities
Reasons for not choosing to go online:
1 Through the simple monitoring center, you can only see the TPS of the service and the response information, and the serialization of the call chain cannot be achieved. The function is too weak.
Website maintainers are most concerned with monitoring user experience, focusing on access statistics of app interfaces, rather than simple service-oriented statistics
2 The simple registration center can only be a single machine, and cannot do multiple machines, because multiple opportunities make it inconvenient to view monitoring data, and a single machine is prone to hot spots, resulting in system instability.
3 Single-machine deployment, when there are many applications based on dubbo, the throughput capacity of the "monitorService" provided by the simple registry may be problematic.
Although the collect method provided by monitorService only puts the request into the queue, in the case of a sudden increase in requests, the monitorService may have problems processing statistical data
4 monitorService will save a lot of data locally without providing cleanup