zuobiao-zhou commented on PR #2718:
URL: https://github.com/apache/hertzbeat/pull/2718#issuecomment-2351558972

   @tomsun28 Hi, the stange problem mentioned here 
https://github.com/apache/hertzbeat/pull/2271#issuecomment-2232155864 has been 
solved. 
   According to the previous code, for jobs with multiple collection metrics, 
the `metrics.setCollectTime` execution time for metrics with a higher priority 
is somewhat delayed. This causes them to be missed during the selection of 
expired metrics in the next cycle, resulting in updates occurring every two 
cycles. so I move `metrics.setCollectTime` in `constructPriorMetrics`.
   
![image](https://github.com/user-attachments/assets/9ddcc3e6-938d-4c30-aa30-c652532e0883)
   
![image](https://github.com/user-attachments/assets/c065b260-63ae-415b-a376-ad7458b0d94a)
   
![image](https://github.com/user-attachments/assets/c1849708-563a-4570-b7ba-79a0a3378c52)
   
![image](https://github.com/user-attachments/assets/183e89e8-905b-4077-acef-d01b5c90a4e2)
   
![image](https://github.com/user-attachments/assets/6ab8d05c-cc7b-4d98-a760-ab1a1bae7987)
   
![image](https://github.com/user-attachments/assets/c1a06a17-3fcc-460f-a037-0737a21c2398)
   Customize collect intervals have been tested and there are no problem.
   


-- 
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