Managing events
How to manage events using the CLI. For a list of events, see List of events in the Content Software for File User Guide.
Viewing events using the CLI
Commandweka events
Use the following command line to list events in the Content Software for File cluster:
weka events [--num-results num-results] [--start-time <start-time>] [--end-time <end-time>] [--severity severity] [--direction direction] [--fetch-order fetch-order] [--type-list type-list] [--exclude-type-list exclude-type-list] [--category-list category-list] [--cloud-time] [--show-internal] [--raw-units] [--UTC]
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
| num-results | Integer | Maximum number of events to display | Positive integer. 0 shows all events | No | 50 |
| start-time | String | Include events that occurred at this start time and later | Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12-31T10:00, 9:15Z, 10:00+2:00 | No | -365 days |
| end-time | String | Include events that occurred up to this time | Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12-31T10:00, 9:15Z, 10:00+2:00 | No | Set to a time represents 'now' |
| severity | String | Include events with this level of severity and higher | 'info', 'warning', 'minor', 'major' or 'critical' | No | INFO |
| direction | String | Sort events by ascending or descending time | 'asc' or 'dsc' | No | asc |
| fetch-order | String | Fetch from end-time backwards or from start-time forwards | 'fw' or 'bw' | No | bw |
| type-list | String | Filter events by type (can be used multiple times) | Use weka events list-types to see available types | No | None |
| exclude-type-list | String | Filter-out events by type (can be used multiple times) | Use weka events list-types to see available types | ||
| category-list | String | Include only events matching the defined category | Categories can be Alerts, Cloud, Clustering, Drive, Events, Filesystem, IO, InterfaceGroup, Licensing, NFS, Network, Node, ObjectStorage, Raid, Statistics, System, Upgrade, and User | No | All |
| cloud-time | Boolean | Query and sort results by the digested time in the cloud | No | False | |
| show-internal | Boolean | Also displays internal events | No | False | |
| raw-units | Boolean | Print values in raw units (bytes, seconds, among others) | No | Human-readable format, for example, 1KiB 234MiB 2GiB | |
| UTC | Boolean | Print times in UTC | No | Host's local time |
Listing local events using the CLI
Commandweka events list-local
Use the following command line to list recent events on the specific host running the command from.
This command is helpful for the following cases:
- No connectivity to the central monitoring site
- No connectivity from a specific host
- Hosts that are not part of the cluster
weka events list-local [--start-time <start-time>] [--end-time <end-time>] [--next next] [--stem-mode] [--show-internal] [--raw-units] [--UTC]
Parameters
| Name | Type | Value | Limitations | Mandatory | Default |
| start-time | String | Include events that occurred at this start time and later | Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12- 31T10:00, 9:15Z, 10:00+2:00 | no | -365 days |
| end-time | String | Include events that occurred up to this time | Format: 5m, -5m, -1d, -1w, 1:00, 01:00, 18:30, 18:30:07, 2018-12-31 10:00, 2018/12/31 10:00, 2018-12- 31T10:00, 9:15Z, 10:00+2:00 | No | Set to a time represents 'now' |
| next | String | Identifier to the next page of events | As returned in the previous call to weka events list-local | No | |
| stem-mode | Boolean | Displays events when the host has not been attached to the cluster | No | False | |
| show-internal | Boolean | Also displays internal events | No | False | |
| raw-units | Boolean | Print values in raw units (bytes, seconds, among others.) | No | Human-readable format, for example, 1KiB 234MiB 2GiB | |
| UTC | Boolean | Print times in UTC | No | Host's local time |
Triggering a custom event using the CLI
Commandweka events trigger-event
It can be useful to mark specific activities, maintenance work, or important changes/new usage of the system, and see that as part of the system events timeline.
To trigger a custom event, use:
weka events trigger-event <text>