[Dataset quality] Tracking kibana:plugin_render_time metric in dataset quality

[yngrdyn]

I modified the current dashboard in staging and now the metrics of Dataset quality are being reported.

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[gbamparop]

Is PerformanceContextProvider needed in both here and application.tsx?

[yngrdyn]

yup, this is what I'm figuring out with Kate.
Dataset quality plugin is not aware that a provider have been placed outside its context

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 719b82a
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-186627-719b82a531b4
• Observability Deployment

Failed CI Steps

• Jest Integration Tests #4

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
dataQuality	73	146	+73
datasetQuality	198	271	+73
total			+146

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
dataQuality	25.3KB	111.4KB	+86.1KB
datasetQuality	188.7KB	274.5KB	+85.8KB
total			+171.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
dataQuality	7.2KB	7.2KB	+1.0B
datasetQuality	39.4KB	40.3KB	+829.0B
total			+830.0B

Unknown metric groups

async chunk count

id	before	after	diff
dataQuality	1	2	+1
datasetQuality	11	12	+1
total			+2

History

• 💛 Build #217604 was flaky e01876a
• 💛 Build #217180 was flaky 65cf508

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @yngrdyn