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>

1 files changed, 13 insertions, 0 deletions

diff --git a/elog.yaml b/elog.yaml
new file mode 100644
index 0000000..79307a3
--- /dev/null
+++ b/elog.yaml
@@ -0,0 +1,13 @@
+---
+SW:
+    FILE_NOT_FOUND_ERROR:
+        msg: "A required file was not found"
+        level: INFO
+        meta_i: [ ERRNUM ]
+        meta_s: [ FILE_PATH, FILE_NAME ]
+    GETSCOM_ERROR:
+        msg: "Getscom call failed"
+        level: ERR
+        meta_i: [ DEV_ADDR,
+                  DEV_ID ]
+        meta_s: [ DEV_NAME ]