https://ramendr.github.io/ramen/docs/drenv/Recent content in drenv on RamenHugoenhttps://ramendr.github.io/ramen/docs/drenv/metrics/Mon, 01 Jan 0001 00:00:00 +0000https://ramendr.github.io/ramen/docs/drenv/metrics/<!-- SPDX-FileCopyrightText: The RamenDR authors SPDX-License-Identifier: Apache-2.0 --> <h1 id="drenv-metrics">drenv metrics</h1> <p>The <code>drenv stress-test report</code> command automatically collects system metrics from Netdata if it is running. This is important to correlate test failures to system load.</p> <h2 id="installing-netdata">Installing Netdata</h2> <p>macOS:</p> <pre tabindex="0"><code>brew install netdata </code></pre><p>Linux:</p> <pre tabindex="0"><code>curl --fail --silent --show-error --location --output /tmp/netdata-kickstart.sh \ https://get.netdata.cloud/kickstart.sh bash /tmp/netdata-kickstart.sh --no-updates --stable-channel </code></pre><h2 id="configuring-netdata">Configuring netdata</h2> <p>For stress testing, configure Netdata to use minimal resources and store data on disk (persists across restarts, uses less memory).</p>https://ramendr.github.io/ramen/docs/drenv/stress-test/Mon, 01 Jan 0001 00:00:00 +0000https://ramendr.github.io/ramen/docs/drenv/stress-test/<!-- SPDX-FileCopyrightText: The RamenDR authors SPDX-License-Identifier: Apache-2.0 --> <h1 id="drenv-stress-test">drenv stress test</h1> <p>The drenv stress test evaluates <code>drenv start</code> robustness and helps debug failed runs.</p> <h2 id="setup">Setup</h2> <p>Before running stress tests install <em>Netdata</em> on the host to allow correlating test failures with system load. See <a href="https://ramendr.github.io/ramen/docs/drenv/metrics/">metrics</a> for more info.</p> <h2 id="running-stress-test">Running stress test</h2> <p>In this example we run 100 runs starting the regional-dr environment. If a run fails, we delete the clusters and continue. This is useful for understanding what are the most common failures.</p>