On 03/28/2018 11:30 AM, James E. Blair wrote:
> As soon as I say that, it makes me think that the solution to this
> really should be in the log processor. Whether it's a grok filter, or
> just us parsing the lines looking for task start/stop -- that's where we
> can associate the extra data with
Ian Wienand writes:
> The closest other thing I could find was "aggregate" [1]; but this
> relies on having a unique task-id to group things together with.
> Ansible doesn't give us this in the logs and AFAIK doesn't have a
> concept of a uuid for tasks.
We control the log output format in Zuul
I wanted to query for a failing ansible task; specifically what would
appear in the console log as
2018-03-27 15:07:49.294630 |
2018-03-27 15:07:49.295143 | TASK [configure-unbound : Check for IPv6]
2018-03-27 15:07:49.368062 | primary | skipping: Conditional result was False
2018-03-27 15:07
