CLDSRV-717: Unification prometheus monitoring cluster mode

[BourgoisMickael]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 88.46154% with 3 lines in your changes missing coverage. Please review.

Project coverage is 83.10%. Comparing base (514a8ac) to head (73488a3).
Report is 6 commits behind head on development/9.0.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
lib/server.js	88.88%	2 Missing ⚠️
lib/utilities/monitoringHandler.js	80.00%	1 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
lib/Config.js	79.29% <100.00%> (+0.07%)	⬆️
lib/utilities/monitoringHandler.js	90.81% <80.00%> (-0.68%)	⬇️
lib/server.js	77.01% <88.88%> (-1.76%)	⬇️

@@                 Coverage Diff                 @@
##           development/9.0    #5881      +/-   ##
===================================================
- Coverage            83.13%   83.10%   -0.03%     
===================================================
  Files                  188      188              
  Lines                12046    12048       +2     
===================================================
- Hits                 10014    10013       -1     
- Misses                2032     2035       +3     

Flag	Coverage Δ
ceph-backend-test	65.62% <73.07%> (+0.01%)	⬆️
file-ft-tests	66.01% <76.92%> (+0.02%)	⬆️
kmip-ft-tests	26.92% <69.23%> (+0.02%)	⬆️
mongo-v0-ft-tests	67.86% <80.76%> (+0.02%)	⬆️
mongo-v1-ft-tests	67.86% <80.76%> (-0.01%)	⬇️
multiple-backend	35.43% <73.07%> (+0.01%)	⬆️
quota-tests	32.17% <73.07%> (+0.01%)	⬆️
quota-tests-inflights	34.14% <73.07%> (+0.01%)	⬆️
unit	67.09% <65.38%> (-0.01%)	⬇️
utapi-v2-tests	33.27% <73.07%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[anurag4DSB]

Are there any tests for this?

[BourgoisMickael]

Are there any tests for this?

Unit tests here: https://github.com/scality/cloudserver/blob/development/9.0/tests/unit/utils/monitoring.js

They don't test based on config though so it only use the non cluster mode

[bert-e]

Hello bourgoismickael,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[BourgoisMickael]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge improvement/CLDSRV-717-prom-cluster into
  development/9.0
• w/9.1/improvement/CLDSRV-717-prom-cluster will be merged into development/9.1

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.8

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/9.0

• ✔️ development/9.1

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.8

Please check the status of the associated issue CLDSRV-717.

Goodbye bourgoismickael.

The following options are set: approve