Ah, that makes sense. Thanks! --David Reagan
On Tue, Jul 7, 2015 at 1:19 PM, Brian Coca <[email protected]> wrote: > status will be OK in both cases, you need to look at changed : true/false > > On Tue, Jul 7, 2015 at 2:26 PM, David Reagan <[email protected]> wrote: > > With some work I have almost exactly what I want. See: > > http://pastebin.com/G819PEZY > > > > Questions: The status of that restart apache 2 task should be "CHANGED", > > since it actually did change during the play run. But it seems like the > > value for changed tasks is always "OK". Is there a way to change that? > > > > > > > > --David Reagan > > > > On Mon, Jul 6, 2015 at 5:37 PM, David Reagan <[email protected]> wrote: > >> > >> The default log_plays doesn't actually output all the information I > need. > >> > >> I have lots of stuff going to syslog and then into ELK already, but in > >> this case, I figured I'd just let logstash-forwarder watch the ansible > log > >> file. Then format the output so that logstash doesn't have to filter it > at > >> all. > >> > >> Currently, I figured out how to get valid json out per line. But I'm > stuck > >> figuring out how to get the task name, the role name, and the command > line > >> command information. > >> > >> Are there global vars I can reference from the plugin? Where could I > find > >> a list of them? > >> > >> > >> --David Reagan > >> > >> On Mon, Jul 6, 2015 at 5:25 PM, Brian Coca <[email protected]> wrote: > >>> > >>> log_plays was designed to drop the json to syslog-ng which would then > >>> push it to elastic search w/o need for logstash, probably easier to > >>> just setup syslog-ng to do the same. > >>> > >>> > >>> -- > >>> Brian Coca > >>> > >>> -- > >>> You received this message because you are subscribed to a topic in the > >>> Google Groups "Ansible Project" group. > >>> To unsubscribe from this topic, visit > >>> > https://groups.google.com/d/topic/ansible-project/zOjsYxLN578/unsubscribe. > >>> To unsubscribe from this group and all its topics, send an email to > >>> [email protected]. > >>> To post to this group, send email to [email protected]. > >>> To view this discussion on the web visit > >>> > https://groups.google.com/d/msgid/ansible-project/CAJ5XC8n722sXnV547ZCjrTxBeaDQOqxzxQ1QEs0fYeq5AuQ6Sg%40mail.gmail.com > . > >>> For more options, visit https://groups.google.com/d/optout. > >> > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Ansible Project" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/ansible-project/CANo%2B_AfMFvypiqYdFWbOopLNNa3yx_Y-vxQBmY%2BHiY85fYCSYg%40mail.gmail.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Brian Coca > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/zOjsYxLN578/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAJ5XC8nvqO_3HKZmfBD_NhxW6nY7mfoZHPCuZTfz%2B2QiRM1QJQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CANo%2B_Ae%2B5uS3PPHo7S984HvP%2B6oGLMt4zcHUfCcPPfN-noQxJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
