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:49.400755 | While I can do message:"configure-unbound : Check for IPv6" I want to correlate that with a result, looking also for the matching skipping: Conditional result was False as the result of the task. AFAICT, there is no way in kibana to enforce a match on consecutive lines like this (as it has no concept they are consecutive). I considered a few things. We could conceivably group everything between "TASK" and a blank " | " into a single entry with a multiline filter. It was pointed out that this would make, for example, the entire devstack log as a single entry, however. 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. So I'm at a bit of a loss as to how we could effectively index ansible tasks so we can determine the intermediate values or results of individual tasks? Any ideas? -i [1] https://www.elastic.co/guide/en/logstash/current/plugins-filters-aggregate.html _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
