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
Copy file name to clipboardExpand all lines: docs/dashboard-overviews.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,39 @@
1
-
# Reporters
1
+
# Overviews
2
2
3
-
Reporters are scripts that analyze the historical data collected by the modules. While the modules are responsible for _gathering_ data, reporters are responsible for _interpreting_ it.
3
+
Overviews are scripts that analyze the historical data collected by the modules. While the modules are responsible for _gathering_ data, overviews are responsible for _interpreting_ it.
4
4
5
-
## How to Run a Reporter
5
+
## How to Run an Overview
6
6
7
-
You can run any reporter using the `-r` flag on the main `dashboard.sh` script:
7
+
You can run any overview using the `-o` flag on the main `dashboard.sh` script:
For example, to run the `top-stars`reporter, you would use:
13
+
For example, to run the `top-stars`overview, you would use:
14
14
15
15
```bash
16
-
./dashboard.sh -r top-stars
16
+
./dashboard.sh -o top-stars
17
17
```
18
18
19
-
Some reporters accept their own arguments, which you can pass after the reporter's name:
19
+
Some overviews accept their own arguments, which you can pass after the overview's name:
20
20
21
21
```bash
22
-
./dashboard.sh -r top-stars 5
22
+
./dashboard.sh -o top-stars 5
23
23
```
24
24
25
-
## Available Reporters
25
+
## Available Overviews
26
26
27
-
Here is a list of the currently available reporters.
27
+
Here is a list of the currently available overviews.
28
28
29
29
### `trending`
30
30
31
-
The `trending`reporter shows the change in each metric over a period of time, but it only includes metrics that have actually changed. It reads all the `.tsv` report files from the `reports/` directory and calculates the difference between the first and last recorded values for each metric, filtering out any that have a change of zero.
31
+
The `trending`overview shows the change in each metric over a period of time, but it only includes metrics that have actually changed. It reads all the `.tsv` report files from the `reports/` directory and calculates the difference between the first and last recorded values for each metric, filtering out any that have a change of zero.
32
32
33
33
**Usage:**
34
34
35
35
```bash
36
-
./dashboard.sh -r trending [days]
36
+
./dashboard.sh -o trending [days]
37
37
```
38
38
39
39
-**`[days]`** (optional): The number of days of history to analyze.
@@ -57,12 +57,12 @@ Change Last Value First Value Metrics
57
57
58
58
### `top-stars`
59
59
60
-
The `top-stars`reporter finds the most recent report file and lists the top repositories by their star count.
60
+
The `top-stars`overview finds the most recent report file and lists the top repositories by their star count.
61
61
62
62
**Usage:**
63
63
64
64
```bash
65
-
./dashboard.sh -r top-stars [count]
65
+
./dashboard.sh -o top-stars [count]
66
66
```
67
67
68
68
-**`[count]`** (optional): The number of top repositories to display. Defaults to 10.
@@ -76,14 +76,14 @@ Rank Stars Repository
76
76
1 1 attogram/dashboard
77
77
```
78
78
79
-
## Creating Your Own Reporter
79
+
## Creating Your Own Overview
80
80
81
-
You can easily create your own reporter by adding a new executable shell script to the `reporters/` directory.
81
+
You can easily create your own overview by adding a new executable shell script to the `overviews/` directory.
82
82
83
-
A reporter script should:
83
+
An overview script should:
84
84
85
-
1. Be placed in the `reporters/` directory.
86
-
2. Be executable (`chmod +x reporters/my_reporter.sh`).
85
+
1. Be placed in the `overviews/` directory.
86
+
2. Be executable (`chmod +x overviews/my_overview.sh`).
87
87
3. Read data from the `.tsv` files in the `reports/` directory. The path to the reports directory can be found relative to the script's own location: `REPORTS_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/../reports"`.
Copy file name to clipboardExpand all lines: docs/dashboard-script.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# The Main Script (`dashboard.sh`)
2
2
3
-
The `dashboard.sh` script is the main entry point for the application. It serves as an orchestrator, responsible for parsing arguments, loading configuration, and running modules for data collection, or running reporters for data analysis.
3
+
The `dashboard.sh` script is the main entry point for the application. It serves as an orchestrator, responsible for parsing arguments, loading configuration, and running modules for data collection, or running overviews for data analysis.
-`-f, --format <format>`: (For module runs only) Specify the output format. See [Output Formats](./dashboard-output-formats.md) for a full list of supported formats. If not provided, the default is `tsv`.
22
-
-`-r, --reporter <name>`: Run a specific reporter from the `reporters/` directory. Any subsequent arguments will be passed to the reporter script.
22
+
-`-o, --overview <name>`: Run a specific overview from the `overviews/` directory. Any subsequent arguments will be passed to the overview script.
23
+
-`-v, --verbose`: Enable verbose (debug) mode, which prints detailed messages about the script's execution to standard error.
23
24
-`-h, --help`: Display a help message with usage information and exit.
24
25
25
26
### Arguments
@@ -32,7 +33,7 @@ The script has two main modes of operation: data collection and reporting.
32
33
33
34
### Data Collection Mode
34
35
35
-
This is the default mode when the `-r` flag is not used.
36
+
This is the default mode when the `-o` flag is not used.
36
37
37
38
1.**Argument Parsing**: It parses command-line options (`-f`, `-h`) and an optional module name.
38
39
@@ -46,10 +47,10 @@ This is the default mode when the `-r` flag is not used.
46
47
47
48
5.**Report Generation**: The script collects the output from each executed module. For structured formats like `json`, `xml`, and `html`, it wraps the collected outputs with the appropriate root elements. For simpler formats like `plain` or `csv`, it concatenates the outputs. The final report is printed to standard output, which can be redirected to a file.
48
49
49
-
### Reporter Mode
50
+
### Overview Mode
50
51
51
-
This mode is triggered by the `-r` flag.
52
+
This mode is triggered by the `-o` flag.
52
53
53
-
1.**Argument Parsing**: The script looks for the `-r` flag. When found, it takes the next argument as the reporter's name. All following arguments are passed directly to the reporter.
54
+
1.**Argument Parsing**: The script looks for the `-o` flag. When found, it takes the next argument as the overview's name. All following arguments are passed directly to the overview.
54
55
55
-
2.**Reporter Execution**: The script looks for an executable file with the given name in the `reporters/` directory and runs it, passing along any reporter-specific arguments. The output of the reporter is printed to standard output.
56
+
2.**Overview Execution**: The script looks for an executable file with the given name in the `overviews/` directory and runs it, passing along any overview-specific arguments. The output of the overview is printed to standard output.
This directory contains scripts that analyze the historical data collected by the modules.
4
+
5
+
## Available Overviews
6
+
7
+
Here is a list of the currently available overviews:
8
+
9
+
-**`trending`**: Shows the change in each metric over a period of time.
10
+
-**`top-stars`**: Lists the top repositories by their star count from the most recent report.
11
+
12
+
## Creating Your Own Overview
13
+
14
+
You can easily create your own overview by adding a new executable shell script to this directory. An overview script should be executable and placed in this directory.
15
+
16
+
For more detailed documentation, please see the main project documentation in the `docs/` directory.
0 commit comments