You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once there is an error event in the database it will apparently be reported every single time. It would be very useful to clear events so that they either are removed from the database or stay there but are excluded from reports like ras-mc-ctl --errors and ras-mc-ctl --summary.
A possible solution would be to include a column, "is_new", in the event database, that can be set to false to indicate that the event in question is old and should not be reported anymore (i.e., the queries used by the reports would add a ... WHERE is_new clause). Another possibility would be to have a global variable, "last_seen_id" which indicates that only events with id > last_seen_id should be reported.
The text was updated successfully, but these errors were encountered:
Once there is an error event in the database it will apparently be reported every single time. It would be very useful to clear events so that they either are removed from the database or stay there but are excluded from reports like
ras-mc-ctl --errors
andras-mc-ctl --summary
.A possible solution would be to include a column,
"is_new"
, in the event database, that can be set tofalse
to indicate that the event in question is old and should not be reported anymore (i.e., the queries used by the reports would add a... WHERE is_new
clause). Another possibility would be to have a global variable,"last_seen_id"
which indicates that only events withid > last_seen_id
should be reported.The text was updated successfully, but these errors were encountered: