elasticsearch

Tiny supportability nit: today we emit these log messages when adding a write block to an index:

[2022-03-22T19:43:26,897][INFO ][o.e.c.m.MetadataIndexStateService] [node_t1] adding block write to indices [[test-blocks/eLkrYpm_S3WNemfWpXrhPA]]
[2022-03-22T19:43:26,933][INFO ][o.e.c.m.MetadataIndexStateService] [node_t1] completed adding block write to indices [test-blocks]

This is

If you look at the panels below, some are set to 0% while others are 0.000%. The decimal field is set to 3 so I expect all 0 value panels to show as 0.000 %. Could this be done? This is a stat panel with a repeat variable. I've highlighted it in the 2nd image.

The report_info_flyout_content has breached a point where it is more convenient for maintainers of the file to source the user-facing content strings from a separate file.

This issue is to follow the imports added in https://github.com/elastic/kibana/pull/130020/files#diff-83b67268eba04e092077b198cf34a3a7c273878024670feac96ca495fc8d829f to hoist all the user-facing content strings from the e

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}