robocanic opened a new issue, #1338:
URL: https://github.com/apache/dubbo-admin/issues/1338

   <!-- Please only use this template for submitting feature requests -->
   **What would you like to be added**:
   
   <img width="2548" height="1313" alt="Image" 
src="https://github.com/user-attachments/assets/ac1781d8-a15e-46f7-a7c4-3143ee650d0a";
 />
   The homepage of Dubbo admin is full of different metrics, these metrics are 
statistical analysis attributes of different Resource. We need to defined a 
Counter to count the number of these metrics in cache in case to support the 
homepage data query.
   
   Below are the procedures to implement homepage data query:
   1. Define a unified CounterManager, which is responsible for managing 
different kinds of Counter.
   2. Subscribe the specific  type of Resource Event through [Event 
Bus](https://github.com/apache/dubbo-admin/blob/develop/pkg/core/events/eventbus.go).
   3. Create or update the number of Counter during event processing.
   4. Implement [http 
handler](https://github.com/apache/dubbo-admin/blob/develop/pkg/console/handler/overview.go)
 of the homepage data query
   **Why is this needed**:
   The query of homepage data includes different kinds of resources. In the 
last version of admin, we list all the objects to get the metric like the 
number of application. It's really cumbersome. So we need to improve it. For 
now, using event bus we can easily catch a resource event and calculate the 
metrics. And metrics do not need to be completely precise and it's perfect for 
implmenting Counter in the event process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to