[collectd] ldap plugin for collectd ?

[Kimo Rosenbaum]

Here is the doc: https://github.com/kimor79/collectd/blob/kimor79/openldap/src/collectd.conf.pod#plugin-openldap

What errors do you get (if any)?


It's been a very long while since I've had to work with LDAP so I'm a bit rusty. Something to try is to workout the URL and query using the ldapsearch command line first. Looking at the plugin code, it only does an anonymous bind and here is what it tries to retrieve:

base: cn=Monitor
scope: subtree
filter: (!(cn=* *))
attrs: monitorCounter, monitorOpCompleted, monitorOpInitiated

I do remember that my first iteration was just an exec plugin shell script which did the ldapsearch and then a bunch of awk/sed/grep commands. That might be something to look into if you don't get the C plugin working.


Thanks
Kimo



----- Original Message -----
> From: GRAY Andrew G (SPARQ) <andrew.gray1 at sparq.com.au>
> To: 'Kimo Rosenbaum' <kimor79 at yahoo.com>; "'collectd at verplant.org'" <collectd at verplant.org>
> Cc: 
> Sent: Thursday, June 5, 2014 10:18 PM
> Subject: RE: [collectd] ldap plugin for collectd ?
> 
> Having perused the code (I'm not a C programmer) ... this is what I came up 
> with, which doesn’t work
> 
> <Plugin openldap>
>         <Instance "Instance1">
>                 Version         3
>                 Timeout         3
>                 # URL          
> "ldap://localhost:389/uid=otag090,ou=People,dc=support,dc=ex"
>                 URL            
> "ldap://localhost:389/support.ex?uidNumber?one"
>                 StartTLS        true
>                 CACert          "/etc/pki/tls/certs/ca-bundle.crt"
>                 VerifyHost      true
>         #  uid=otag090,ou=People,dc=support,dc=ex"
>         #  tls_cacert      /etc/pki/tls/certs/ca-bundle.crt
>         #  tls_cert        /etc/pki/tls/certs/localhost.crt
>         #  tls_key         /etc/pki/tls/private/localhost.key
>         </Instance>
> </Plugin>
> 
> Any pointers ??? 
> 
> Regards,
> 
> Andrew Gray.
> RHCSA, Professional Unix Administration.
> 
> 
> 
> -----Original Message-----
> From: GRAY Andrew G (SPARQ) 
> Sent: Friday, 6 June 2014 11:41 AM
> To: 'Kimo Rosenbaum'; collectd at verplant.org
> Subject: RE: [collectd] ldap plugin for collectd ?
> 
> Thanks Kimo, 
> I have managed to compile it and added a LoadPlugin directive, is there any docs 
> on how to configure the plugin ?? 
> I assume it needs an ldap bind account, hostname etc etc ?
> 
> 
> LoadPlugin openldap
> ...
> <Plugin openldap>
> ???
> </Plugin>
> 
> 
> Regards,
> 
> Andrew Gray.
> RHCSA, Professional Unix Administration.
> 
> -----Original Message-----
> From: Kimo Rosenbaum [mailto:kimor79 at yahoo.com] 
> Sent: Thursday, 5 June 2014 1:56 AM
> To: GRAY Andrew G (SPARQ); collectd at verplant.org
> Subject: Re: [collectd] ldap plugin for collectd ?
> 
> 
> A few years ago I started on an openldap plugin:
> 
> http://mailman.verplant.org/pipermail/collectd/2011-January/004336.html 
> (although this seems to have truncated the email)
> 
> Here is the original email and patch I sent:
> 
> https://gist.github.com/kimor79/684e2e7777f4f48037e9
> 
> Thanks
> Kimo
> 
>> ________________________________
>>  From: GRAY Andrew G (SPARQ) <andrew.gray1 at sparq.com.au>
>> To: "collectd at verplant.org" <collectd at verplant.org>
>> Sent: Wednesday, June 4, 2014 12:55 AM
>> Subject: [collectd] ldap plugin for collectd ?
>> 
>> 
>> 
>> 
>> I’d like to measure how fast the ldap server is answering queries …. Any 
> pointers would be appreciated.
>>  
>> Regards,
>>  
>> Andrew Gray.
>> Professional Unix Administration.
>>  
>> 
>> ***********************************************************************
>> **************
> This email message (including any file attachments transmitted with it) is for 
> the sole use of the intended recipient(s) and may contain confidential and 
> legally privileged information. Any unauthorised review, use, alteration, 
> disclosure or distribution of this email (including any attachments) by an 
> unintended recipient is prohibited. If you have received this email in error, 
> please notify the sender by return email and destroy all copies of the original 
> message. Any confidential or legal professional privilege is not waived or lost 
> by any mistaken delivery of the email. SPARQ Solutions accepts no responsibility 
> for the content of any email which is sent by an employee which is of a personal 
> nature. Sender Details: SPARQ Solutions PO Box 15760 City East, Brisbane QLD 
> Australia 4002 +61 7 4931 2222 SPARQ Solutions policy is to not send unsolicited 
> electronic messages. Suspected breaches of this policy can be reported by 
> replying to this message  including the original message and the word 
> "UNSUBSCRIBE" in the 
> subject.  ************************************************************************************* 
> 
>> 
>> _______________________________________________
>> collectd mailing list
>> collectd at verplant.org
>> http://mailman.verplant.org/listinfo/collectd
>> 
>> 
>> 
> To report this email as spam, please forward to asa at websense.com
> 
> *************************************************************************************
> This email message (including any file attachments transmitted with it) is for 
> the sole use of the intended recipient(s) and may contain confidential and 
> legally privileged information. Any unauthorised review, use, alteration, 
> disclosure or distribution of this email (including any attachments) by an 
> unintended recipient is prohibited. If you have received this email in error, 
> please notify the sender by return email and destroy all copies of the original 
> message. Any confidential or legal professional privilege is not waived or lost 
> by any mistaken delivery of the email. SPARQ Solutions accepts no responsibility 
> for the content of any email which is sent by an employee which is of a personal 
> nature.
> 
> Sender Details:
>   SPARQ Solutions
>   PO Box 15760 City East, Brisbane QLD Australia 4002
>   +61 7 4931 2222
> 
> SPARQ Solutions policy is to not send unsolicited electronic messages. Suspected 
> breaches of this policy can be reported by replying to this message including 
> the original message and the word "UNSUBSCRIBE" in the subject. 
> *************************************************************************************
>