https://bugs.openldap.org/show_bug.cgi?id=10293
--- Comment #7 from [email protected] <[email protected]> --- > Hi Marty, > on the consumer, we only see what is received not what provider > performed. Even more so in a refresh. This matters and it's why I keep > asking what you *need*. To remind others: in the sylog project and the ollrpt project on our gitlab instance I looked for lines whose bodies began with: syncrepl_message_to_op: rid=002 be_modify and created a pseudo-request. In `ollrpt` I added artificial "tag" values. I created a record in my temporary file(s) were used and included these pseudo-request counts in the summary report. `ollrpt` is the better of the two for this. I asked @nivanova to produce, in the STATS log a record with RID, tag, etime, etc. which she did and I reviewed the output. It would simplify log reduction and feed a reporting tool we use extensively to judge system activity. Similar reports have been done with mtail as I remember, gathering these pseudo-requests and their etimes and merging them internally (as COULD be done in `ollrpt`. The original ask was to merge @nivanova's work at least in a test build to evaluate and consider shipping as an improvement in STATS level reporting. I am well aware that syncrepl is complex and much of what has been mentioned implies I was asking for much more which I was not. -- You are receiving this mail because: You are on the CC list for the issue.
