Activities
Updated:2024-09-29 MAIA
MAIA enables the monitoring of client-side activities in real-time through activity pipelines.
- Individual activities can be chained into pipelines.
- An activity is defined by the kind of task running in it.
- The activity status is indicated with colors.
- Each individual activity:
- is also a link to detailed information in a separate show page.
- indicates ongoing activity progress with striped progress bars.
- displays execution time.
An activity can be created with monitoring properties that allows for improved user control, for example, heartbeat intervals and maximum time to live.
How to create activities in WebApp, read more about MAIA Agent commands and workflows.
Activities index page
Updated:2024-09-29 MAIA
Is a listing of all past and present activities sorted with newest on top.
The activities table displays all activities the current team has permission to see. If the user performs a search (filter), the table displays the results from the search.
Table description
| Heading | Description |
|---|---|
| Start Time | When the activity pipeline started. |
| Owner | The origin of the activity. The owner can be a component, a track or a team. |
| Activity Pipeline | A chain of activities with Kind, Status, Time, etc. Each activity contains a link to more detailed information |
| Comment | Additional info on the pipeline. |
| Tags | The tags related to the activities. |
Filter
| Filter by | Description |
|---|---|
| Search | Search the Name of an artifact. |
| state | Filter on activity pipeline state, Successful, Failed, Active, etc. |
| tags | Filter on tags to narrow the search. |
| start date | Select a start date to narrow the search. |
| end date | Select a end date to narrow the search. |
Activities show page
Updated:2024-09-29 MAIA
This page can be opened by clicking on an activity in the Activity pipeline column on the Activities index page .
The main area displays the log output from the activity.
Top box
| Box | Description |
|---|---|
| Status box | Displays the status of the activity. |
Right hand info box
| Attribute | Description |
|---|---|
| "Activity" | Built artifact/Test execution with reference link. |
| Start time | The time the activity started. |
| Duration | The duration of the activity. |
| Progress | The progress of the activity, in percent. |
| State | The status of the activity. |
| Kind | The kind of activity. The kind can be Build, BuildCheck, BuildClean, Checkout, Deploy, Exec, Fetch, Scan or Test. |
| Comment | The comment written when the activity was started. |
| Environment | The name of the environment that the activity runs on. An environment can have tags selected by the user, these tags are not related to the name of the environment. |
| Tags | Tags related to the activity. |
| Heartbeat interval | The time between heartbeats on the activity. The heartbeat is used by MAIA Software to ensure that the activity is still running. |
| Uuid | The universal unique identifier of the activity. |
| Owner | The owner that tracks the activity on their dashboard. The owner can be a component, a track or a team. If an activity has no owner the activity is not tracked on a dashboard. |
| Parent activity | The link to the parent activity. If an activity is part of a pipeline, the previous activity is the parent. |
| Child activities | The link to the child activity. If an activity is part of a pipeline, the next activity is the child. |
Kind of Activity
| Kind | Description |
|---|---|
| Checkout | Checks out code from a specific commit for each related repository. The default is a check out from the last commit in each repository, but can be set to an older revision. |
| BuildCheck | Checks if there are previously produced artifacts that can be fetched for the same source code and environment. BuildCheck is used to avoid the need to rebuild |
| BuildClean | Prepares the Fetch and Build phases by removing old outputs. |
| Fetch | Loads a built artifact from an external storage, if existing. Fetch is used to avoid the need to rebuild. |
| Build | Produces artifacts from source code or other fetched artifacts. Build may include fetching external dependencies and license information. |
| Deploy | Moves created artifacts to an external storage. |
| Exec | Runs a shell command. |
| Scan | Retrieves commits from one or more repositories. |
| Test | Test execution posting data to MAIA in real-time. |
State
| State | Description | Pipeline color |
|---|---|---|
| Success | The activity is completed without errors. | Light blue |
| Active | The activity is ongoing. | Light blue |
| Failed | The activity is completed with errors. | Red |
| Failing | The activity is active but errors are reported | Red |
| Created | The activity is registered but not started. | |
| Cancelled | The activity is cancelled. | |
| Interrupted | The activity is interrupted, and terminated before completion. The interruption can be caused manually or from an external source (a program). | Grey |
| Timed out | The activity is not completed within a set time span. | Red |
Files
The Files tab contains a list of log files produced during the activity. Each file name includes a link to open the file.
