Problem: For an eDirectory administrator, or especially for an application developer who is using eDirectory on a backend, to determine if a query is completely broken, perhaps contradictory resulting in no results returned, or just very slow due to inefficiency.

Once up on a time Predicate Statistics would help with optimization as long as somebody looked at those. Since eDirectory 8.8 this functionality has been lost, and competing products have tools that help with this very problem, making eDirectory hard to use in larger environments where competitors start to shine more than they should.

With cn=monitor present in eDirectory 9+, it may be nice to have eDirectory do some watching of slow queries, queries returning no results, users who make a lot of queries (application accounts, etc.) and then be retrievable via cn=monitor today. Slow queries that may be needing indexes, or queries returning no objects when the filters are complex, would possibly be useful to most consultants and administrators immediately.

by: Aaron B. | over a year ago | Other