Thank you for the ref to the post. In absense of anything else, I might go with the python
solution. If there’s an easier way though, I’m also interested.
On Dec 14, 2017, at 6:23 PM, Marc Sauton <msauton(a)redhat.com>
wrote:
There is no collectd 389-ds plug-in, but there was a post with an example:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
<
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
May be other users already run some similar plug-in?
Should we have such plug-in?
Thanks,
M.
On Thu, Dec 14, 2017 at 2:45 PM, Sergei Gerasenko <gerases(a)gmail.com
<mailto:gerases@gmail.com>> wrote:
Hello,
I’m trying to set up collectd to monitor 389-ds by using the values under cn=monitor. Is
there something out there (e.g., a collectd plugin?) that could do this? I’ve seen this:
http://directory.fedoraproject.org/docs/389ds/howto/howto-cn-equals-monit...
<
http://directory.fedoraproject.org/docs/389ds/howto/howto-cn-equals-monit...;,
but that requires MySQL or Postgres.
Thanks,
Sergei
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
<mailto:389-users@lists.fedoraproject.org>
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
<mailto:389-users-leave@lists.fedoraproject.org>
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org