ZenPacks : LDAP Monitor : Comments

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 01:27:53 GMT

Zenoss 3.1.0 on SUSE11

Just installed the LDAP Core ZenPack. Seems to be working great so far.

But I have some new LDAP servers that use a non-standard port for LDAP. I notice there are only 3 zproperties for the LDAP ZenPack

zLDAPBaseDN, zLDAPBindDN, zLDAPBindPassword

It's really a bummer that there is not a "zLDAPPort". This means that I need to create a local copy of the monitoring template for each server and basically recreate the template datasource, threasholds, etc... I looked at what it takes to create a new zProperty and I'm not interested in doing any code changing/customizations just to add a new zPropertiy.

I was wondering if there would be a way to add the port number to the end of the "zLDAPBaseDN" zProperty separated by a delimiter. Something like the following:

OU=portal,DC=external,DC=companyname,DC=com|12345

The delimiter is the "|" pipe symbol and the port is 12345.

Would there be a way to split this in the Monitoring Template datasource? Currently the LDAP template datasource has "${here/zLDAPBaseDN}" in the "Base Distinguished Name:" field. Would there be some way to add a function to split off the part before the "|" and then in the port field spilt off the part after the "|"? Can these be Python expressions here?

This would save a ton of work copying templates local.

Thanks!!!!

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 15:55:18 GMT

Try this line of thought:

First, read the docs about the LDAPMonitor ZenPack

In there it mentions that the datasource has a port distinction.

What you can try here is to create a custom zProperty (often called cProperties) and put it into the datasources Port field as "${here/cLDAPPort}"

You can create custom properties in the GUI by navigating to a device and clicking the 'Custom Properties' text. You can add one to a device class by clicking on Details button at top and clicking on Custom Schema. Make your cLDAPPort property here, differing it per device or class, and reference the custom property in the datasource which will stay the same.

Let me know how it works!

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 16:27:49 GMT

Perfect! I'll give that a shot! I'm still learning new things about Zenoss every day!

I notice that I can't add a cProperty at the device level. Looks like it has to be at the Device Class level and I have to select "Custom Schema".

Is that right?

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 16:31:19 GMT

You should be able to do a cProperty at the device level too. See how I explained to it differently for device or device class?

Look on the left menu when inside a device and see the 'Custom Properties' menu item.

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 16:43:51 GMT

Yes, that's the location I'm going to on a device. But then I don't see an add option anywhere.

Although, I think I may have another problem. I added the cProperty at the class level. Then while trying to edit the field "Port" on the Edit Data Source dialog, it will only let me enter numeric values. When I paste in ${here/cLDAPPort}, the save button disables. It also does not allow me to type anything other than numbers.

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 17:00:49 GMT

This is unfortunate - we will not be able to go this nice route without some code changes.

What you can likely do instead is to copy the template to other device classes, and go in and change that port in the copied templates.

Copying templates is called 'Override Template' in the UI. See screenshot:

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 17:22:27 GMT

That is unfortunate, make a perfectly good ZenPack difficult to use!

It's also a bummer that when you copy a template local, it loses the datasource and all the charts, etc... Any way around that?

RE: LDAP Monitor

community@zenoss.org — Fri, 20 May 2011 17:37:31 GMT

Can we move this convo to http://community.zenoss.org/thread/16081 ?

RE: LDAP Monitor

community@zenoss.org — Thu, 20 Sep 2012 19:28:31 GMT

How can this package be usable with Core 4.2 ?