Similar to #38, we would like to gather Monitoring metrics during load test runs. This would show things like the Elasticsearch search queue and rejected searches. It would also show Kibana memory and response times.
In the current local load test job we build the current Kibana and get the most recently promoted Elasticsearch build.
To gather monitoring we would need to also get the most recent metricbeat build, configure it, and start it.
Then it should be a relatively simple job of configuring that metricbeat to send Elasticsearch and Kibana monitoring data to kibana-stats.elastic.dev.
APM data too...(separate issue)
/cc @dmlemeshko @marius-dr
Similar to #38, we would like to gather Monitoring metrics during load test runs. This would show things like the Elasticsearch search queue and rejected searches. It would also show Kibana memory and response times.
In the current local load test job we build the current Kibana and get the most recently promoted Elasticsearch build.
To gather monitoring we would need to also get the most recent metricbeat build, configure it, and start it.
Then it should be a relatively simple job of configuring that metricbeat to send Elasticsearch and Kibana monitoring data to kibana-stats.elastic.dev.
APM data too...(separate issue)
/cc @dmlemeshko @marius-dr