commit | e4b0b77180adc4c2f63e83abbf849f09fd399055 | [log] [tgz] |
---|---|---|
author | Nagaraju Goruganti <ngorugan@in.ibm.com> | Thu Nov 30 02:12:45 2017 -0600 |
committer | Nagaraju Goruganti <ngorugan@in.ibm.com> | Fri Dec 01 06:26:40 2017 -0600 |
tree | f0f9a1bd84561134dbbdcffc81fe534ab6f94bf4 | |
parent | 979ed1cce24fa0cffd4fe414b8a56e17ec032b14 [diff] |
Roll errors after reaching Cap size Fixes openbmc/openbmc#2687 -cap on error exists to deal with small flashes, right now the cap is 100 for high severity errors and it is 10 for info(and below) severity) errors. -previous policy was to stop logging new errors once cap is reached for high severity errors. -based on feedback from field engineers, it's better to log new errors, external tools will typically periodically read and store errors, so we won't lose them.so the new policy now is to roll errors. Change-Id: I18b509d81c076fcb80667300cbfda050027bb422 Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
phosphor logging provides mechanism for common event and logging creation based on information from the journal log.
To build this package, do the following steps: 1. ./bootstrap.sh 2. ./configure ${CONFIGURE_FLAGS} 3. make To clean the repository run `./bootstrap.sh clean`.
curl -c cjar -k -X POST -H "Content-Type: application/json" \ -d '{"data": [ "root", "<root password>" ] }' https://<BMC IP>/login curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \ -d '{"data": []}' \ https://<BMC IP>/xyz/openbmc_project/logging/entry/<entry num>/action/Delete
curl -c cjar -k -X POST -H "Content-Type: application/json" \ -d '{"data": [ "root", "<root password>" ] }' https://<<BMC IP>/login curl -c cjar -b cjar -k -H "Content-Type: application/json" \ -X POST https://<<BMC IP>/xyz/openbmc_project/logging/action/deleteAll \ -d "{\"data\": [] }"