smartd --attributelog : parsing the output

[Dan Langille]

Have you played with the output from —attributelog smartd?  It looks very suitable for parsing and logging to a database.

Here is a sample from my own drives:

2014-10-30 16:56:26;	1;100;0;	2;139;73;	3;149;34384445834;	4;100;27;	5;100;0;	7;100;0;	8;124;33;	9;99;11183;	10;100;0;	12;100;27;	192;100;27;	193;100;27;	194;193;201864642591;	196;100;0;	197;100;0;	198;100;0;	199;200;0;

The first field of each semicolon separated triplet is the ID of the S.M.A.R.T. attribute in question.

I haven’t found any existing code which parses this data, so I’m very keen to start coding this mini-project, but before I did, I figured I would post here in case any of you had seen something.

I can see parsing and storing this data in a database for logging, review, and graphing purposes.  I think this format is much easier to parse than the text fields supplied by smartctl

re:

https://www.freebsd.org/cgi/man.cgi?query=smartd&manpath=FreeBSD+9.0-RELEASE+and+Ports&format=html
https://www.freebsd.org/cgi/man.cgi?query=smartctl&manpath=FreeBSD+9.0-RELEASE+and+Ports&format=html
https://en.wikipedia.org/wiki/S.M.A.R.T.#ATA_S.M.A.R.T._attributes


— 
Dan Langille

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 333 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20141030/be9b96d2/attachment.sig>