Integrate IO Usage Tracker to the Resource Usage Collector Service and Emit IO Usage Stats

[ajaymovva]

Description

Integrate IO Based Usage Tracker and Stats for the Resource Usage Collector Service

• This change is to track IO Usage Stats and emit these stats as part of resource_usage_stats.
• Created AverageIoUsageTracker which uses IO stats from the fsService and evaluate the IO Usage Consumption.
• Currently we are emitting only IO UsagePercent as part of io_usage_stats and eventually we will add more parameters.

NodeStats Output on Linux

resource_usage_stats: {
    Edk086LhT_mu47MpzHgc4g: {
        timestamp: 1709545252312,
        cpu_utilization_percent: "0.0",
        memory_utilization_percent: "1.0",
        io_usage_stats: {
            max_io_utilization_percent: "99.6"
        }
    }
}

NodeStats Output on Mac

resource_usage_stats: {
    qi1V9avrSwC_OyRtA2khbA: {
        timestamp: 1709544705354,
        cpu_utilization_percent: "0.1",
        memory_utilization_percent: "35.5"
    }
}

Related Issues

• Parent PR where we are exposing other resource_usage_stats - Add resource usage trackers and resource usage collector service #9890
• [RFC] Admission Controller framework for OpenSearch #8910
• [META] Admission Controller Framework #9504

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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

[github-actions]

Compatibility status:

Checks if related components are compatible with change 55db771

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/sql.git]

[github-actions]

❌ Gradle check result for 4b4f782: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 8dcf40e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 842d3d4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 27b60be: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for b5fa081: SUCCESS

[github-actions]

❌ Gradle check result for 14ca3ca: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for a39baba: SUCCESS

[Bukhtawar]

LGTM minor comments

[github-actions]

❌ Gradle check result for 4b4dd48: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 55db771: SUCCESS

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-11880-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 63f20fe5e4a2bba269db619c5ad0ce6df95c82ba
# Push it to GitHub
git push --set-upstream origin backport/backport-11880-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-11880-to-2.x.