[O11y][MongoDB] Add custom number formatting to visualizations

[rajvi-patel-22]

Urgency

• High

Activity Type

• Enhancement

What does this PR do?

Revisit panels and add custom number formatting (2000->2k) to visualizations.
[Reference]

Checklist

• I have added an entry to my package's changelog.yml file.
• I have verified that panels are populated with data.
• I have verified that panels are not distorted after being migrated to the lens.
• I have updated screenshots of the dashboard.
• I have verified that the data counts are matching and panel aggregations are the same as before.

Author's Checklist

• Migrated panels should be removed from visualization folder.
• Migrated visualizations are populating in current Kibana version 8.10.2 itself.

Related issues

• Closes [O11y][MongoDB] Add custom number formatting to visualizations #7116

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-30T13:26:31.682+0000

• Duration: 23 min 24 sec

Test stats 🧪

Test	Results
Failed	4
Passed	20
Skipped	0
Total	24

Test errors

Expand to view the tests failures

system test: collstats – mongodb.collstats

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in documents stored in metrics-mongodb.collstats-ep data stream: [0] found error.message in event: ['top' command failed: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service-mongodb-1:27017, Type: RSGhost, Average RTT: 723023 }, ] }] 

system test: dbstats – mongodb.dbstats

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in documents stored in metrics-mongodb.dbstats-ep data stream: [0] found error.message in event: [could not retrieve database names from Mongo instance: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service-mongodb-1:27017, Type: RSGhost, Average RTT: 548908 }, ] }] 

system test: metrics – mongodb.metrics

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in documents stored in metrics-mongodb.metrics-ep data stream: [0] found error.message in event: [failed to retrieve data from 'serverStatus' command: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service-mongodb-1:27017, Type: RSGhost, Average RTT: 729808 }, ] }] 

system test: status – mongodb.status

Expand to view the error details

 null 

Expand to view the stacktrace

 one or more errors found in documents stored in metrics-mongodb.status-ep data stream: [0] found error.message in event: [failed to retrieve 'serverStatus': server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service-mongodb-1:27017, Type: RSGhost, Average RTT: 564354 }, ] }] 

Steps errors

Expand to view the steps failures

Test integration: mongodb

• Took 7 min 20 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Google Storage Download

• Took 0 min 0 sec . View more details here

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	96.97% (32/33)	❕
Lines	68.217% (88/129)	❕
Conditionals	100.0% (0/0)	💚

[rajvi-patel-22]

/test

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[ali786XI]

/test

[mrodm]

Hi @rajvi-patel-22, please update your branch with the latest contents from main branch. There was an important PR merged updating the CI pipelines. Thanks!

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!