Run overview, run page and compare runs
Run overview
The runs are related to jobs. On the run overview you get a list of runs related to the selected job. You can find the run overviews on two locations in the project. The first location is on the project page in the section Jobs. Here the jobs for that project are listed and via the you can expand a section that will list the runs related to that job.
The second location is on the job page in the section Runs. On both locations you will find a table like the screenshot below.
In this table you see:
| Name | Description |
|---|---|
| SUUID | The first four charactes of the run SUUID. If you put your mouse on the text you can also see the full SUUID and a copy button to copy the full SUUID. |
| Name | If a name was set for the run, we show the name. If no name is set, we show an empty cell. |
| Status | The status of the run |
| Timing | Information when the run started and what the duration was/is (depending on the status) |
| By | The member who triggered the run |
| Input | The number of lines the input payload file has. When the payload is empty, it is reported as 1 line. |
| Metrics | The number of metrics tracked for the run |
When you click on a run, the related run page will open. If you click on any object on the row, the run page will open. But if you specifically click on the input or metrics, we will directly open the tab INPUT or METRICS on the related run page.
On the job page in the section Runs you can also search and filter the run list. On this page, you find a search and filter bar. Searching works on the run SUUID and name. You can also filter the run list on:
- Created by
- Status
- Trigger
When you filter with the above attributes, you can filter with is or is not and select an available value. You can also combine multiple filters and combine filters with search.
Run page
On the run page we list all information related to the run. Here you can find the meta information of the run, the input, results, metrics, artifact, variables, code and logs. An example of the run page:
When you open the run page, you will see:
- Title with name (if set) or SUUID of the run
- Navigation bar with tabs
In the navigation bar you find the next tabs:
| Tab | Description |
|---|---|
| Overview | Meta information of the run |
| Input | The input used for the run |
| Result | The result for the run |
| Metrics | The metrics tracked for the run |
| Artifact | Saved files and directories for the run |
| Code | The code version used on this run |
| Variables | The variables tracked by the run and set in the run environment |
| Log | The log (console output) of the run |
| Menu with additional options for the run |
On the tab OVERVIEW you can find the following meta-information about the run:
| Name | Description |
|---|---|
| Status | Status of the run |
| SUUID | SUUID of the run |
| Job | Name of the job used for this run |
| Start date | Date the run started |
| Duration | Duration of the run |
| Code | Version of the code used for this run |
| By | Member who triggered the run |
| Trigger | How the run was triggered |
| Environment | Environment/image used for the run |
For input we only support the JSON payload (for now). In both the payload and the result we assume that this is a JSON file. In the section you can see the content of the file. Also there is an option to download the file or copy the content of the file.
In the log section you can find the console output of the run environment. By default we load the first 100 lines, and when you have a larger log it will automatically load more lines when you scroll trough the log. Also you can download or copy the content of the log.
Compare runs
The compare runs page is an initial version that helps you to compare runs directly in AskAnna. You can find the compare runs link on the job page in the section Runs. On this page, you find a -button which you can use to open the compare runs page.
On the compare runs page, you see the runs to be compared in the columns. The rows contain the run data and the data is grouped (see table below). Each group can be expanded or collapsed. The groups are similar to the sections you get on the run page. The groups on the compare runs page are:
| Group | Description |
|---|---|
| Overview | Information about the start time, duration, code version, who triggered the run and the environment used |
| Input | Meta information of the input used |
| Result | Meta information about the result |
| Metrics | Metrics can be compared by value. Each row shows the metric that matches based on the metric name and the label names + label values. By default we show the first 25 metrics. You can load more variables via the SHOW MORE METRICS-button. |
| Variables | Variables can be compared by value. Each row shows the variable that matches based on the variable name and the label names + label values. By default we show the first 25 variables. You can load more variables vi the SHOW MORE VARIABLES-button. |
| Artifact | Meta information about the artifact |
: If none of the selected runs has input, result, metrics, variables or artifact, then you will see an informational message like Artifact: these runs don't have an artifact and the option to expand or collapse the section is disabled.
In the initial version, the compare runs page shows the last 15 runs. If you are working on a larger screen, you can get the full-width page by clicking the -button.