<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-logging/elog.hpp, branch master</title>
<subtitle>OpenBMC Phosphor logging library sources (not useful for felling trees)</subtitle>
<id>https://git.raptorcs.com/git/phosphor-logging/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-logging/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/'/>
<updated>2017-02-20T13:06:27+00:00</updated>
<entry>
<title>Moved log.hpp and elog.hpp to a folder under phosphor-logging</title>
<updated>2017-02-20T13:06:27+00:00</updated>
<author>
<name>Saqib Khan</name>
<email>khansa@us.ibm.com</email>
</author>
<published>2017-02-13T19:19:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/commit/?id=2bb15195dbed122ed327c2659f18323a8ed5c0f5'/>
<id>urn:sha1:2bb15195dbed122ed327c2659f18323a8ed5c0f5</id>
<content type='text'>
Now these files are copied to a folder under phosphor-logging,
other repositories will need to be fixed. I'm leaving the files in
the base dir as well until I work on fixing all projects that
utilizes log.hpp and elog.hpp

Change-Id: Ie4640852727c1572325e974548737bc70a6db7c2
Signed-off-by: Saqib Khan &lt;khansa@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Implement Commit client interface</title>
<updated>2017-02-16T21:55:13+00:00</updated>
<author>
<name>Adriana Kobylak</name>
<email>anoo@us.ibm.com</email>
</author>
<published>2017-02-07T02:15:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/commit/?id=205b11368d69fce12ed2bf347bf8ae7b5b7dfd3f'/>
<id>urn:sha1:205b11368d69fce12ed2bf347bf8ae7b5b7dfd3f</id>
<content type='text'>
Implement the Commit client interface to take the
exception unique name and call the dbus Commit interface
to create the error log.

Change-Id: Id780e98efd32b9806ea24e4e551f786a055cc05c
Signed-off-by: Adriana Kobylak &lt;anoo@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Create libphosphor-logging library</title>
<updated>2017-02-16T21:53:08+00:00</updated>
<author>
<name>Adriana Kobylak</name>
<email>anoo@us.ibm.com</email>
</author>
<published>2017-02-15T19:44:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/commit/?id=c20dae8656898888505df589c32e9f672e03c648'/>
<id>urn:sha1:c20dae8656898888505df589c32e9f672e03c648</id>
<content type='text'>
The commit function would be too big to hold on the
header file. Move it to a library and update the
phosphos-logging.pc file for users to link against it.
Add dependency to libsdbusplus as the commit interface
would make use of the transaction id support.

Change-Id: I237b15e35a633f1da9bf3401b5bf754154f132db
Signed-off-by: Adriana Kobylak &lt;anoo@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add exception generation to error logging</title>
<updated>2016-11-02T20:45:19+00:00</updated>
<author>
<name>Andrew Geissler</name>
<email>andrewg@us.ibm.com</email>
</author>
<published>2016-10-17T01:49:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/commit/?id=6d910ad9e2b3c83d7dccbcf25f9bdce9e4b13a58'/>
<id>urn:sha1:6d910ad9e2b3c83d7dccbcf25f9bdce9e4b13a58</id>
<content type='text'>
This commit puts basic exception support into the elog class.
All errors will generate an exception with this commit.

This will most likely change over to using the dbus exception
class as a base in the future but that change will be transperent
to the users.

Change-Id: Ibd02d4c204393a0cfb156805360161759cb6631e
Signed-off-by: Andrew Geissler &lt;andrewg@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Error / Event Log Framework</title>
<updated>2016-10-31T16:51:50+00:00</updated>
<author>
<name>Adriana Kobylak</name>
<email>anoo@us.ibm.com</email>
</author>
<published>2016-09-30T01:48:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-logging/commit/?id=f855c3e54f2c06da0649a7dfc31f60d7a36bcd6f'/>
<id>urn:sha1:f855c3e54f2c06da0649a7dfc31f60d7a36bcd6f</id>
<content type='text'>
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&lt;RC&gt;(NAME(value), prev_entry&lt;NAME&gt;()...)
  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&lt;level::DEBUG&gt;(
        msg("Info trace to log filename"),
        entry(file_not_found::file_name::str, my_filename));
  elog&lt;file_not_found&gt;(file_not_found::errnum(2),
        file_not_found::file_path("/tmp/"),
        prev_entry&lt;file_not_found::file_name&gt;());

Change-Id: Ic51cee80b58e341c071c366c5e2146fd6694012c
Signed-off-by: Adriana Kobylak &lt;anoo@us.ibm.com&gt;
Signed-off-by: Andrew Geissler &lt;andrewg@us.ibm.com&gt;
</content>
</entry>
</feed>
