New message text here

@kapa.ai can you send me the link to edr report parameters documentation

Based on the knowledge sources, here are the links to the

edr report

parameters documentation: Main CLI Commands Documentation: [CLI commands and usage](https://docs.elementary-data.com/oss/cli-commands) - This page covers the basic

edr report

command and links to more detailed options. Detailed CLI Options: [CLI Options](https://docs.elementary-data.com/oss/cli-commands#cli-options) - This page provides a comprehensive list of all available CLI options for

edr report

, including: -

--days-back

- Limit how far back to collect data -

--file-path

- Specify where to save the report -

--executions-limit

- Set the number of invocations shown per test -

--disable-passed-test-metrics

- Improve performance by excluding metrics for passed tests -

--project-dir

- Specify your dbt project directory -

--profiles-dir

- Specify your profiles directory - And many more options Generate Report Guide: [Generate observability report](https://docs.elementary-data.com/oss/guides/generate-report-ui) - This guide covers how to generate the report and includes information about filtering reports by invocation. You can also run

edr report --help

in your terminal to see all available options directly in your command line.

Based on the knowledge sources, the

--executions-limit

parameter controls the number of test invocations shown for each test in the "Test Runs" section of the report. According to the [CLI Options documentation](https://docs.elementary-data.com/oss/cli-commands#cli-options), this parameter allows you to "Set a limit to how far back Elementary should collect dbt and Elementary results while generating alerts/report." ## How It Works - Default value: 720 invocations per test - Purpose: Limits the amount of historical test execution data that gets loaded into memory and displayed in the report - Impact: Reducing this value can significantly improve report generation performance and reduce memory usage ## When to Use It As mentioned in [this support thread](https://slack.com/archives/C02CTC89LAX/p1691169511715969), if you're experiencing timeouts or memory issues, you should try reducing the executions-limit. The support staff suggested: - Start with a low value like

--executions-limit 10

to see if the report generates successfully - Then gradually increase it to find the right balance between performance and historical visibility In [another case](https://slack.com/archives/C02CTC89LAX/p1697714006352379), a user reduced it from the default 720 to 360 to help reduce their report file size. ## Example Usage

bash edr report --executions-limit 100

This is particularly useful when you have a large volume of test results and need to reduce the data being processed to avoid out-of-memory errors or timeouts.