[checkmk-commits] [Checkmk/checkmk] f29149: Moved processLogEntries to where it belongs

Branch: refs/heads/master Home: https://github.com/Checkmk/checkmk Commit: f29149f93fcb610ec0d651d26bcd7fa9e10e78d7 https://github.com/Checkmk/checkmk/commit/f29149f93fcb610ec0d651d26bcd7fa9e… Author: Sven Panne <sven.panne(a)checkmk.com> Date: 2024-10-22 (Tue, 22 Oct 2024) Changed paths: M packages/livestatus/include/livestatus/Logfile.h M packages/livestatus/src/Logfile.cc M packages/livestatus/src/TableLog.cc Log Message: ----------- Moved processLogEntries to where it belongs The LogCache/Logfile "API" is weird and is used very differently in the implementations of the "statehist" and "log" tables. So let's move stuff out of that "API" into its use sites and try to come up with a sane API later. "No" API is better than a broken API. :-} Change-Id: Id1436c2f19a456d651fe19332c7618e5e00311fb Commit: f5d9c4732d25debae03ecf0f69ccd3dcf68f6f83 https://github.com/Checkmk/checkmk/commit/f5d9c4732d25debae03ecf0f69ccd3dcf… Author: Sven Panne <sven.panne(a)checkmk.com> Date: 2024-10-22 (Tue, 22 Oct 2024) Changed paths: M packages/livestatus/src/TableLog.cc Log Message: ----------- Inlined processLogEntries, it's actually clearer. In the end, the fiddling with the two iterators should be hidden behind a sane API of the LogCache. What we really want is a stream of LogEntries going chronologically backwards in a given time interval, filtered by LogEntry classes. Change-Id: I9d0c4106e1cc09ca01666e77c2a15ea96c9cb79a Compare: https://github.com/Checkmk/checkmk/compare/1a7420f47c98...f5d9c4732d25 To unsubscribe from these emails, change your notification settings at https://github.com/Checkmk/checkmk/settings/notifications