iml_sos_plugin

A sosreport plugin for collecting IML data.

iml_sos_plugin's People

Contributors

Watchers

iml_sos_plugin's Issues

Add module-tools

Add module-tools to this repo and publish to Copr.

add tests

Would be good to get some tests around this plugin to ensure that it works in our target environments and avoids bugs like 2ae336a fixed.

don't collect fully exploded journal files

In our SOS reports, in sos_commands/logs/journalctl_--no-pager_--all_--boot_--output_verbose we seem to be collecting some fully exploded journalctl files:

-- Logs begin at Mon 2017-12-18 04:39:23 KST, end at Thu 2018-01-11 16:41:52 KST. --
Mon 2017-12-18 04:39:23.811422 KST [s=7de630bfb8714169bc6c629dbcd6a6c0;i=8c652;b=318a66b8ebdf46c0b24a6c1a45cb4f0a;m=5c360e38f7;t=5608e640e29c4;x=3adefc90250b9598]
    _TRANSPORT=syslog
    PRIORITY=6
    SYSLOG_FACILITY=23
    MESSAGE=iml nginx: 10.1.1.152 - - [18/Dec/2017:04:39:23 +0900] "POST /agent/message/ HTTP/1.1" 200 5 "-" "python-requests/2.6.0 CPython/2.7.5 Linux/3.10.0-693.2.2.el7_lustre.x86_64"
    _PID=1480
    _UID=994
    _GID=993
    _COMM=nginx
    _EXE=/usr/sbin/nginx
    _CMDLINE=nginx: worker proces
    _CAP_EFFECTIVE=0
    _SYSTEMD_CGROUP=/system.slice/nginx.service
    _SYSTEMD_UNIT=nginx.service
    _SYSTEMD_SLICE=system.slice
    _SOURCE_REALTIME_TIMESTAMP=1513539563811422
    _BOOT_ID=318a66b8ebdf46c0b24a6c1a45cb4f0a
    _MACHINE_ID=7d55375764d740b9bd8f67a5c329b1f4
    _HOSTNAME=iml
Mon 2017-12-18 04:39:23.815045 KST [s=7de630bfb8714169bc6c629dbcd6a6c0;i=8c653;b=318a66b8ebdf46c0b24a6c1a45cb4f0a;m=5c360e3a0b;t=5608e640e2ad9;x=2a668b3ae5de2d66]
    _TRANSPORT=syslog
    _SYSTEMD_SLICE=system.slice
    _BOOT_ID=318a66b8ebdf46c0b24a6c1a45cb4f0a
    _MACHINE_ID=7d55375764d740b9bd8f67a5c329b1f4
    _HOSTNAME=iml
    PRIORITY=3
    SYSLOG_FACILITY=5
    SYSLOG_IDENTIFIER=rsyslogd
    MESSAGE=imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
    _PID=721
    _UID=0
    _GID=0
    _COMM=rsyslogd
    _EXE=/usr/sbin/rsyslogd
    _CMDLINE=/usr/sbin/rsyslogd -n
    _CAP_EFFECTIVE=1fffffffff
    _SYSTEMD_CGROUP=/system.slice/rsyslog.service
    _SYSTEMD_UNIT=rsyslog.service
    _SOURCE_REALTIME_TIMESTAMP=1513539563815045

I don't think we need this level of detail.

Recommend Projects