initial commit for storage dashboard in ES integration

[jsvd]

No description provided.

[elasticmachine]

💚 Build Succeeded

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-12-14T15:24:02.177+0000

• Duration: 36 min 10 sec

Test stats 🧪

Test	Results
Failed	0
Passed	62
Skipped	0
Total	62

🤖 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% (5/5)	💚
Files	100.0% (9/9)	💚
Classes	100.0% (9/9)	💚
Methods	87.5% (98/112)	❕
Lines	91.993% (563/612)	❕
Conditionals	100.0% (0/0)	💚

[miltonhultgren]

I've tested the dashboards and they work. My only feedback would be to consider aligning the naming of the dashboards with those added for Ingest Pipeline monitoring.

[jsvd]

Done: ba40c10
@miltonhultgren thanks for the feedback

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[jsvd]

@jsoriano taking up your offer to look at this PR, I set you up as a reviewer. thanks!

[jsoriano]

Nice. Consider adding screenshots of the dashboards. They can be added to the img directory and referenced in the manifest.

[mrodm]

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

[jsvd]

@mrodm rebase done!
@jsoriano neat! I'll work on getting some screenshots when I'm back from PTO next year.

[jsvd]

@jsoriano screenshots added, looking for final LGTM. thanks!

[jsoriano]

@jsoriano screenshots added, looking for final LGTM. thanks!

Nice, thanks!

[elasticmachine]

Package elasticsearch - 1.12.0 containing this change is available at https://epr.elastic.co/search?package=elasticsearch

[IanLee1521]

@jsvd / whomever - I've been using these dashboards recently and am having some issues with them in our environment, what's the best way to provide feedback? Open a new issue?

[jsvd]

Hi @IanLee1521 yes a new issue on this repo would be the right approach! /cc @flexitrev