In the web console, you can create filters to manage resources. Currently the following resources are supported:
- Container
Filter is dynamic, e.g. new resources matched with the filter will be automatically selected, and decommissioned resources are auto-removed.
The filter syntax is resource specfic. More details can be found at:
- Container (The part of ps filters)
- id (container's id)
- label (
label=<key>orlabel=<key>=<value>)- name (container's name or a substring in the name)
- image (container's image name)
The same filter expression attribute will be treated as a union, different attributes will be as an intersection.
- Login to the web console
- Goto the resource page e.g. container
- Enter the criteria in the filter area
- Click
Save - Enter a new name, or replace an existing filter
- Login to the web console
- Goto the resource page e.g. container
- Click
Filterand select the filter you want to edit - Edit the criteria in the filter area
- Click
Save
Once a filter is created, you can set up actions on it:
- Login to the web console
- Goto the
Resource Filterspage - Select (or unselect) actions for filters
Actions are resource specific. Currently the following actions are supported:
- Container
- Send email notification on (unexpected) container exit
An email notification will be sent to your registered email address if a container exits unexpectedly:
- User-triggered container stops (CLI and API) are NOT included
- Normal container exit are NOT included (exit code 0), e.g. job finished
- Notification threshold is 5 minutes. All container exit events during this period will be put in one email
- The notification email will include container id, name, exit code and time
- If your container repeatedly restarts (with
--restart=alwaysflag), only one notification will be sent within a 5 minute window - If the container exit is caused by a platform incident, we will send the notification email as soon as possible
- The maximum length of filter name is 255
- The maximum number of filters is 50