tree 37e86614d241245fc20eb45027e02b211d957517
parent 91da45310b8ba4d244ec0d9036c9e104d1b9f7c4
author Adriana Kobylak <anoo@us.ibm.com> 1475200088 -0500
committer Andrew Geissler <andrewg@us.ibm.com> 1477932710 -0500

Error / Event Log Framework

Framework to create an error log entry based on information
from the journal log.
1. elog.yaml - User defined reason codes for error scenarios that
   include description, priority level, and desired metadata fields.
2. elog_parser.py - Parser for the yaml file
3. elog-gen.hpp - Auto-generated file based created by the parser
   that includes the error log structures. Including for now for ref.
4. elog.hpp - Error log template to create (log a journal log
   entry with the predefined error log information).

Usage: elog<RC>(NAME(value), prev_entry<NAME>()...)
  where RC - Reason code, NAME - metadata name
  being logged to a journal entry, prev_entry - A Metadata entry that
  has previously being logged to a journal entry.
Example:
  log<level::DEBUG>(
        msg("Info trace to log filename"),
        entry(file_not_found::file_name::str, my_filename));
  elog<file_not_found>(file_not_found::errnum(2),
        file_not_found::file_path("/tmp/"),
        prev_entry<file_not_found::file_name>());

Change-Id: Ic51cee80b58e341c071c366c5e2146fd6694012c
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>