To expose the newly stored system-level event logs, we will want to add a cli to retrieve them.
This task is to define the user experience around the cli, and implement it. Use cases that should be served are:
- As a user, I want to see all the system-level event logs for my tool in real time
- As a user, I want to see all the times my webservice was restarted
- As a user, I want to see when my tool was deployed (triggered), and if it finished ok (deployment completed)
- As a user, I want to see when my webservice was started or stopped and by who
Note: we already have different interfaces for accessing different types of logs; in the future, we want to unify them under a toolforge logs command, but this doesn't have to be done as part of this task (only if it's easy, otherwise should be separated into another task).
Implementation
We are using cli options, for example --since, in parallel to the options that the API allows for the logs endpoint (see https://api-docs.toolforge.org).
The options to implement are:
- --since/--until
- --job-names
- --build-ids
- --deployment-ids
- --sources
- --lines
- --direction
We are going for parity with the API for this new cli: https://phabricator.wikimedia.org/T432572#12318897