GaOrtiga opened a new pull request, #13561:
URL: https://github.com/apache/cloudstack/pull/13561

   ### Description
   
   Currently, KVM metric collections are performed for each Management Server 
independently. This process sends command to the Agents, requesting a 
collection of VM metrics. The Agent receives the command, collects the current 
metrics, compares it with the previous collection, and sends the final results 
to the MS that requested the metrics. Finally, the MS saves the data to the DB.
   
   The new metrics are compared to the previous metrics collected, regardless 
of the MS that triggered the process. Thus, the collection interval depends on 
the interval between the Management Servers, and not the interval defined in 
the configuration. This does not affect the authenticity of the data, however, 
it disregards the configured timeout.
   
   To prevent this situation, the source code has been adjusted, guaranteeing 
that the MS only sends metric collection commands to hosts connected to it.
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [X] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [X] Minor
   - [ ] Trivial
   
   ### How Has This Been Tested?
   
   - In an environment with two MSs, I verified that VM metric collection 
occured normally for the VMs on hosts connected to the MS.
   - For the remaining hosts, the collection did not occur.
    


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

Reply via email to