You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For tracking remote store nightly runs, we need the changes to be done in opensearch-build repo to enable collection of node-stats/segments stats. The below is the change summarised - --telemetry="node-stats" --telemetry-params='{"node-stats-include-indices":"true"}' in OSB run command.
Also, we are seeing discrepancy in the Remote Store nightly runs where the throughput is showing almost 1/3rd of the expected throughput. Link
Please help to get the above 2 points addressed (introduction of remote store metrics and fixing the remote store dashboard) as we need to track the performance characteristics and couple of remote store specific stats at the earliest to avoid any unintentional regression (by catching it from the nightly remote store dashboards).
The text was updated successfully, but these errors were encountered:
For tracking remote store nightly runs, we need the changes to be done in opensearch-build repo to enable collection of node-stats/segments stats. The below is the change summarised -
--telemetry="node-stats" --telemetry-params='{"node-stats-include-indices":"true"}'
in OSB run command.{"node-stats-include-indices":"true","node-stats-include-indices-metrics":"segments"} - parameters required.
Also, we are seeing discrepancy in the Remote Store nightly runs where the throughput is showing almost 1/3rd of the expected throughput. Link
Please help to get the above 2 points addressed (introduction of remote store metrics and fixing the remote store dashboard) as we need to track the performance characteristics and couple of remote store specific stats at the earliest to avoid any unintentional regression (by catching it from the nightly remote store dashboards).
The text was updated successfully, but these errors were encountered: