From: Gris Ge <fge@redhat.com>
To: rhel-sysmgt <rhel-sysmgt@redhat.com>,
springfield@sourceware.org, eng-common-logging@redhat.com
Subject: [RFC] Daemon to provide structured storage events: peripety
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <20180516135253.GA12920@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]
Hi Guys,
In order to provide structured event for storage subsystem.
I created a daemon for append structured data and device ID to
systems logs:
https://github.com/cathay4t/peripety/
Features:
* Use sysfs and devfs for information query only. Designed to handle
log burst.
* Saves logs in journald with structured data. Log are hide by default
to eliminate the duplicate entry. Try `journalctl -o json-pretty
IS_PERIPETY=TRUE`
* Provides consistent id for device of the log.
* Provides extra information like mount point on fs mount, FC/iSCSI
path information on multipath path failure:
https://github.com/cathay4t/peripety/blob/master/examples/fs/ext4_mount_lv_mpath_scsi.json
https://github.com/cathay4t/peripety/blob/master/examples/mpath/mpath_fc_path_offline.json
* Provides device dependency information. E.g. LV over mpath over SCSI.
Could query all related logs(fs, lvm, mpath, scsi) of physical device
by command:
journalctl DEV_WWID=<WWID> + OWNERS_WWIDS=<WWID>
* Allows user defined regex in /etc/peripetyd.conf.
* TBD: C/python/rust lightweight library for query block information
on all kind of dev string(major:minor, scsi_id, nvme ctrl_id+ns_id,
etc).
* TODO: Varlink(json) interface.
* TODO: Handle user space tool logs like mulitpathd, iscsid.
Example JSON event of multipath FC path failure:
{
"hostname": "storageqe-18.rhts.eng.bos.redhat.com",
"severity": "Warning",
"sub_system": "Multipath",
"timestamp": 1526053021631595,
"event_id": "",
"event_type": "DM_MPATH_PATH_FAILED",
"dev_wwid": "360a98000324669436c2b45666c567946",
"dev_path": "/dev/mapper/360a98000324669436c2b45666c567946",
"owners_wwids": [
"t10.NETAPP-LUN-2FiCl+EflVyF"
],
"owners_paths": [
"/dev/sdd"
],
"kdev": "8:48",
"msg": "device-mapper: multipath: Failing path 8:48.",
"extention": {
"blk_major_minor": "8:48",
"transport": "FC",
"port_state": "Online",
"target_wwpn": "0x500a0982891b8dc5",
"host_wwpn": "0x10000000c9a02834",
"speed": "8 Gbit",
"driver_name": "lpfc"
}
}
I have also created some kernel patches to improve this:
* Provides WWID by kernel on every log to fix the race issue.
* Provides event type by kernel to save the use space regex captures.
https://github.com/cathay4t/linux/commits/structured_log
Thank you for your time.
Best regards.
--
Gris Ge
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-05-16 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Gris Ge [this message]
2018-01-01 0:00 ` [ECL] " Rich Megginson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180516135253.GA12920@redhat.com \
--to=fge@redhat.com \
--cc=eng-common-logging@redhat.com \
--cc=rhel-sysmgt@redhat.com \
--cc=springfield@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).