Ian Wienand <[email protected]> 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 (both job-output.txt and job-output.json). So we could include a unique ID for tasks if we wished. However, we should not put that on every line, so that still would require some handling in the log processor. 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 every line from a task. We can even generate a uuid right there in the log processor. -Jim _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
