Handle more than 100 error logs
Added new Cap for info(and below) severity errors, if cap size reaches,
next commited error of severity:info(and below) will replace the first
entry of severity:info(and below).
Resolves openbmc/openbmc#2381
Change-Id: I2e56c28a934bf3139e57b36d252bd5ad3e1dd90f
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
diff --git a/elog_entry.hpp b/elog_entry.hpp
index 24d93cf..8dcc2a2 100644
--- a/elog_entry.hpp
+++ b/elog_entry.hpp
@@ -111,6 +111,13 @@
*/
void delete_() override;
+ /** @brief Severity level to check in cap.
+ * @details Errors with severity lesser than this will be
+ * considered as low priority and maximum ERROR_INFO_CAP
+ * number errors of this category will be captured.
+ */
+ static constexpr auto sevLowerLimit = Entry::Level::Informational;
+
private:
/** @brief This entry's associations */
AssociationList assocs = {};