An Event is a record generated during engine execution. Such an event captures what has happened inside the senlin-engine. The senlin-engine service generates event records when it is performing some actions or checking policies.
An event has a level property which can be interpreted as the severity level value of the event:
The following command lists the events by the Senlin engine:
$ senlin event-list
+----------+---------------------+---------------+----------+----------------------------+-----------------------+-----------+--------------------------------+-------+
| id | timestamp | obj_type | obj_id | obj_name | action | status | status_reason | level |
+----------+---------------------+---------------+----------+----------------------------+-----------------------+-----------+--------------------------------+-------+
| 1f72eb5e | 2015-12-17T15:41:48 | NODE | 427e64f3 | node-7171861e-002 | update | ACTIVE | Creation succeeded | 20 |
| 20b8eb9a | 2015-12-17T15:41:49 | NODE | 6da22a49 | node-7171861e-001 | update | ACTIVE | Creation succeeded | 20 |
| 23721815 | 2015-12-17T15:42:51 | NODEACTION | 5e9a9d3d | node_delete_3e91023e | NODE_DELETE | START | The action is being processed. | 20 |
| 54f9eae4 | 2015-12-17T15:41:36 | CLUSTERACTION | 1bffa11d | cluster_create_7171861e | CLUSTER_CREATE | SUCCEEDED | Cluster creation succeeded. | 20 |
| 7e30df62 | 2015-12-17T15:42:51 | CLUSTERACTION | d3cef701 | cluster_delete_64048b01 | CLUSTER_DELETE | START | The action is being processed. | 20 |
| bf51f23c | 2015-12-17T15:41:54 | CLUSTERACTION | d4dbbcea | cluster_scale_out_7171861e | CLUSTER_SCALE_OUT | START | The action is being processed. | 20 |
| c58063e9 | 2015-12-17T15:42:51 | NODEACTION | b2292bb1 | node_delete_59da99f0 | NODE_DELETE | START | The action is being processed. | 20 |
| ca7d30c6 | 2015-12-17T15:41:38 | CLUSTERACTION | 0be70b0f | attach_policy_7171861e | CLUSTER_ATTACH_POLICY | START | The action is being processed. | 20 |
| cfe5d0d7 | 2015-12-17T15:42:51 | CLUSTERACTION | 42cf5baa | cluster_delete_352e1b6b | CLUSTER_DELETE | START | The action is being processed. | 20 |
| fe2fc810 | 2015-12-17T15:41:49 | CLUSTERACTION | 0be70b0f | attach_policy_7171861e | CLUSTER_ATTACH_POLICY | SUCCEEDED | Policy attached. | 20 |
+----------+---------------------+---------------+----------+----------------------------+-----------------------+-----------+--------------------------------+-------+
The senlin command line supports various options when listing the events.
You can specify the sorting keys and sorting direction when list events, using the option --sort (or -o). The --sort option accepts a string of format key1[:dir1],key2[:dir2],key3[:dir3], where the keys used are event properties and the dirs can be one of asc and desc. When omitted, Senlin sorts a given key using asc as the default direction.
For example, the following command instructs the senlin command line to sort events using the timestamp property in descending order:
$ senlin event-list -o timestamp:desc
When sorting the list of events, you can use one of timestamp, level, obj_type, obj_name, user, action and status.
You can filter the list of events using the --filters` (or -f). For example, the following command filters the event list by the obj_type property:
$ senlin action-list -f obj_type=NODE
The option --filters accepts a list of key-value pairs separated by semicolon (;), where each pair is expected to be of format key=val. The valid keys for filtering include obj_name, obj_type, obj_id, cluster_id, action or any combination of them.
In case you have a huge collection of events (which is highly likely the case), you can limit the number of events returned using the option --limit (or --l). For example:
$ senlin event-list -l 10
Another option you can specify is the ID of an event after which you want to see the returned list starts. In other words, you don’t want to see those events with IDs that is or come before the one you specify. You can use the option --marker (or -m) for this purpose. For example:
$ senlin event-list -l 20 -m 2959122e-11c7-4e82-b12f-f49dc5dac270
At most 20 action records will be returned in this example and its UUID comes after the the one specified from the command line.
You can use the senlin command line to show the details about an event you are interested in. When specifying the identity of the event, you can use its name, its ID or its “short ID” . Senlin API and engine will verify if the identifier you specified can uniquely identify an event. An error message will be returned if there is no event matching the identifier or if more than one event matching it.
An example is shown below:
$ senlin event-show 19ba155a
+---------------+--------------------------------------+
| Property | Value |
+---------------+--------------------------------------+
| action | delete |
| cluster_id | ce85d842-aa2a-4d83-965c-2cab5133aedc |
| id | 19ba155a-d327-490f-aa0f-589f67194b2c |
| level | 20 |
| obj_id | cd9f519a-5589-4cbf-8a74-03b12fd9436c |
| obj_name | node-ce85d842-003 |
| obj_type | NODE |
| project | 42d9e9663331431f97b75e25136307ff |
| status | DELETING |
| status_reason | Deletion in progress |
| timestamp | 2015-12-17T15:43:26 |
| user | 5e5bf8027826429c96af157f68dc9072 |
+---------------+--------------------------------------+
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.