我如何阅读/理解目标主机上的 ansible 日志(由 syslog 编写) [英] How do I read / understand ansible logs on target host (written by syslog)

问题描述

当您在某个主机上执行 ansible 时，它​​会写入该主机上的 syslog，如下所示:

When you execute ansible on some host, it will write to syslog on that host, something like this:

Dec  1 15:00:22 run-tools python: ansible-<stdin> Invoked with partial=False links=None copy_links=None perms=None owner=False rsync_path=None dest_port=22 _local_rsync_path=rsync group=False existing_only=False archive=True _substitute_controller=False verify_host=False dirs=False private_key=None dest= compress=True rsync_timeout=0 rsync_opts=None set_remote_user=True recursive=None src=/etc/ansible/repo/external/golive/ checksum=False times=None mode=push ssh_args=None delete=False 
Dec  1 15:00:22 run-tools python: ansible-<stdin> Invoked with partial=False links=None copy_links=None perms=None owner=False rsync_path=None dest_port=22 _local_rsync_path=rsync group=False existing_only=False archive=True _substitute_controller=False verify_host=False dirs=False private_key=None dest= compress=True rsync_timeout=0 rsync_opts=None set_remote_user=True recursive=None src=/etc/ansible/repo/external/golive/ checksum=False times=None mode=push ssh_args=None delete=False 
Dec  1 15:00:22 run-tools python: ansible-<stdin> Invoked with partial=False links=None copy_links=None perms=None owner=False rsync_path=None dest_port=22 _local_rsync_path=rsync group=False existing_only=False archive=True _substitute_controller=False verify_host=False dirs=False private_key=None dest= compress=True rsync_timeout=0 rsync_opts=None set_remote_user=True recursive=None src=/etc/ansible/repo/external/golive/ checksum=False times=None mode=push ssh_args=None delete=False 
Dec  1 15:00:56 run-tools python: ansible-<stdin> Invoked with filter=* fact_path=/etc/ansible/facts.d 
Dec  1 15:09:56 run-tools python: ansible-<stdin> Invoked with checksum_algorithm=sha1 mime=False get_checksum=True path=/usr/local/bin/check_open_files_generic.sh checksum_algo=sha1 follow=False get_md5=False 
Dec  1 15:09:56 run-tools python: ansible-<stdin> Invoked with directory_mode=None force=False remote_src=None path=/usr/local/bin/check_open_files_generic.sh owner=root follow=False group=root state=None content=NOT_LOGGING_PARAMETER serole=None diff_peek=None setype=None dest=/usr/local/bin/check_open_files_generic.sh selevel=None original_basename=check_open_files_generic.sh regexp=None validate=None src=check_open_files_generic.sh seuser=None recurse=False delimiter=None mode=0755 backup=None 
Dec  1 15:20:03 run-tools python: ansible-<stdin> Invoked with warn=True executable=None _uses_shell=False _raw_params=visudo -c removes=None creates=None chdir=None 

是否有这些日志的任何文档或解释可以帮助我理解如何阅读它们?具体来说，我希望能够看到 ansible 究竟做了什么，它触及了哪些文件等.是否可以在那里找到它?或者重新配置ansible，让它在那里写这种信息?

Is there any documentation or explanation of these logs that would help me understand how to read them? Specifically I would like to be able to see what exactly ansible did, which files it touched etc. Is it possible to find it there? Or reconfigure ansible so that it writes this kind of information in there?

是否可以配置这些日志?怎么样?

Is it possible to configure these logs at all? How?

推荐答案

我不知道专门解释系统日志消息内容的文档.但是，您可以查看 AnsibleModule.log() 看看发生了什么.基本上，它报告模块名称和调用它们的参数.

I am not aware of documentation that explains the contents of syslog messages specifically. However, you can look at some of the logging code in AnsibleModule.log() to see what's going on. Basically, it's reporting module names and the parameters they were called with.

对于配置日志，有一些很好的建议响应这个相关问题.总而言之，您可以通过指定日志路径并使用详细的 -v 标志运行来获取更多信息 - 包括您对 ansible 做了什么的请求.对于更细粒度的控制，你可以从两个不同的角度来解决问题:

For configuring logs, there are some good suggestions in response to this related question. The summary is that you can get more information - including your request about what ansible did - by specifying a log path and running with the verbose -v flag. For more fine-grained control, you can attack the problem from two different angles:

• 从剧本方面，您可以使用 debug 模块或调整您对更改/失败结果的处理以满足您的需求.这两项更改都可以为您的日志输出添加有用的上下文.

• From the playbook side, you can use the debug module or tailor your handling of changed/failed results to suit your needs. Both of those changes can add useful context to your log output.

在剧本之外，您可以使用 Ansible 回调插件 控制日志记录.这里是一个回调插件的例子，它拦截日志并输出更易读的内容.>

Outside of playbooks, you can use Ansible callback plugins to control logging. Here is an example of a callback plugin which intercepts logs and outputs something more human readable.

这篇关于我如何阅读/理解目标主机上的 ansible 日志(由 syslog 编写)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！