Add understanding results page

[Naarcha-AWS]

Add understanding results page to the OpenSearch Benchmark user guide

Addresses part of #5815

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[IanHoang]

yhe -> the

[IanHoang]

the measurable latency and service time of the query

[IanHoang]

Maybe add error rate associated with the ingesting documents and running query operations should be added to both points.

[IanHoang]

the compare results --> the summary report

[IanHoang]

  --show-in-results {available,all-percentiles,all}
                        Define which values are shown in the summary publish (default: available).

Allows users to define which values are shown in the summary report

[IanHoang]

We can also add how this is useful when storing metrics and results in an external metric store

[IanHoang]

interested in the latency or service time for a document to be queried.

[IanHoang]

We should stick with summary report (instead of using command line results)

[IanHoang]

a summary results table

[IanHoang]

on an OpenSearch cluster

[IanHoang]

about how to understand the summary results

[IanHoang]

I think we can also remove "what steps to take before running another test on your cluster" as that's not found here.

[hdhalter]

Thanks, Nate! I reviewed the first half and will do the second half later today. I left a few suggestions for reorganizing some of the info and some wording tweaks.

[hdhalter]

This sounds better as the opening paragraph because the first paragraph doesn't give any context. Can you move it up?

[Naarcha-AWS]

This is specific to the link provided in the paragraph. It only applies as an example and not as the standard for summary reports. In the orginal draft, this section was at the bottom and included a disclaimer similar to the following, "Use the nightly benchmark runs as an example of how to present your benchmark results in OpenSearch Dashboards."

[hdhalter]

Understanding workload test results?

[Naarcha-AWS]

"Understanding benchmark results?" What do you think @IanHoang

[hdhalter]

This should come later in the topic, perhaps to introduce a sample table.

[hdhalter]

Is this necessary?

[hdhalter]

HI Nate, here are a few tweaks to the second half.

[hdhalter]

Suggested change

	When stored in-memory, results can be found in the `/.benchmark/benchmarks/test_executions/<test_execution_id>` directory. Results are named based off of the `test_execution_id` given to the workload test during its last run.
	When stored in-memory, results are found in the `/.benchmark/benchmarks/test_executions/<test_execution_id>` directory. The name of the result is based on the `test_execution_id` given to the workload test during its most recent run.

[hdhalter]

Looks good! Just one comment on a heading. Thanks.

[hdhalter]

Can we define 'runs' here if that is the terminology that we are using for the nightly test? OpenSearch Benchmark runs are the nightly tests that target the OS dev cluster..."

[natebower]

@Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!