Hi,
I read your first post. I found it very interesting but was not able to
get a clear understanding of your needs. This second post would also
need additional details. The cn=ldbm database monitoring will mainly
return stats about DB activity and are IMHO a bit raw data.
In the posts you also mentioned, replication lag and "waves" of
replication session. More specifically what concerns are you trying to
fix ? Do you want to monitor, for reporting, to anticipate with a
corrective actions ?
best regards
thierry
On 4/20/23 05:11, dweller dweller wrote:
I wrote a really long post but now looking at it again and searching for
monitoring problems in mailing list it seems kind of vague and unrelated.
I found that records under cn=ldbm database,cn=plugins,cn=config expose
database metrics (I only knew about metrics under cn=monitor). So I will try to
expose them to monitoring system and see what I could find during high load
tasks.
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
