Open dpasupathi opened 6 years ago
If you run something like st2 execution get 5a78f7d299c96b793e5c2493 -d
, that shows start & end timestamps. Does that help?
extreme@EWC:~$ st2 execution get 5a78f7d299c96b793e5c2493 -d
+-----------------+--------------------------------------------------------------+
| Property | Value |
+-----------------+--------------------------------------------------------------+
| id | 5a78f7d299c96b793e5c2493 |
| action.ref | core.local |
| context.user | st2admin |
| parameters | { |
| | "cmd": "id" |
| | } |
| status | succeeded (1s elapsed) |
| start_timestamp | Tue, 06 Feb 2018 00:33:22 UTC |
| end_timestamp | Tue, 06 Feb 2018 00:33:23 UTC |
| result | { |
| | "succeeded": true, |
| | "failed": false, |
| | "return_code": 0, |
| | "stderr": "", |
| | "stdout": "uid=1001(stanley) gid=1001(stanley) |
| | groups=1001(stanley)" |
| | } |
| liveaction | { |
| | "runner_info": { |
| | "hostname": "EWC", |
| | "pid": 2178 |
| | }, |
| | "parameters": { |
| | "cmd": "id" |
| | }, |
| | "action_is_workflow": false, |
| | "callback": {}, |
| | "action": "core.local", |
| | "id": "5a78f7d299c96b793e5c2492" |
| | } |
+-----------------+--------------------------------------------------------------+
extreme@EWC:~$
@LindsayHill : i think this is not giving timestamp at all levels. e.g.{ "status" : "running", "timestamp" : ISODate("2018-02-06T00:04:30.013Z") }, { "status" : "succeeded", "timestamp" : ISODate("2018-02-06T00:04:34.080Z") }
I have raised this defect based on the request from @lakshmi-kannan
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.
Currently to debug the execution time i need to login to mongo db to view the details. Can we expose some CLI or debug option to print the details?