Update mongodb dashboard JSON

[ghost]

Issue: ZENKO-5003

The scalgrafanalib integration will be done in ZENKO-5010

updated Jul 21 11pm

[bert-e]

Hello williamlardier,

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]

Conflict

There is a conflict between your branch feature/ZENKO-5003-mongodb-dashboard and the
destination branch development/2.12.

Please resolve the conflict on the feature branch (feature/ZENKO-5003-mongodb-dashboard).

git fetch && \
git checkout origin/feature/ZENKO-5003-mongodb-dashboard && \
git merge origin/development/2.12

Resolve merge conflicts and commit

git push origin HEAD:feature/ZENKO-5003-mongodb-dashboard

[francoisferrand]

same

[ghost]

Must keep pod here, as this is not a mongodb exported metric... I will define and use POD_PATTERN in several places, for these metrics. I think it is valuable to keep these panels in this dashboard, even if not directly exported by mongodb, because it gives the big picture that we are often missing in current dashboards... But please challenge if you disagree.

[francoisferrand]

should not be a POD_PATTERN (hardcoded in the dashboard code), but rely on inputs specified by ZKOP.

(or create a -hidden- template parameter which extracts the values of pod label from the up{job=...} query, to get this list)

[ghost]

@francoisferrand : The PR mesage was updated with the new dashboard image. I checked one by one and I resolved all comments, plus some related. Just one thing, I changed (removed) the Jobs class to just use it as an input from the dashboard:

Please tell me if you had something else in mind.

[francoisferrand]

does not seem solved?
did you create a cleanup ticket for later?

[francoisferrand]

/after_pull_request 2240

[ghost]

/approve

[bert-e]

Incorrect fix version

The Fix Version/s in issue ZENKO-5003 contains:

• 2.12.4

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 2.12.5

Please check the Fix Version/s of ZENKO-5003, or the target
branch of this pull request.

The following options are set: approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/2.12

The following branches will NOT be impacted:

• development/2.10
• development/2.11
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

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

• ✔️ development/2.12

The following branches have NOT changed:

• development/2.10
• development/2.11
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

Please check the status of the associated issue ZENKO-5003.

Goodbye williamlardier.