Digging deeper into the access log, I see that certain operations return with non-zero
error codes. The most prolific are 14 and 32. These are LDAP_SASL_BIND_IN_PROGRESS and
LDAP_NO_SUCH_OBJECT respectively. So *maybe* the SNMP counter is incremented on those
error codes. I’m currently looking at the source code trying to confirm that. I couldn’t
find the definitions of those codes in the 389-ds-base source base. I found them here (of
all places):
https://docs.oracle.com/cd/E19957-01/817-6707/resultcodes.html#wp30446
<
https://docs.oracle.com/cd/E19957-01/817-6707/resultcodes.html#wp30446> I know it’s
a totally different code base, but it appears to share some standards with the 389-ds
implementation.
On Jan 3, 2018, at 10:16 AM, Sergei Gerasenko
<gerases(a)gmail.com> wrote:
So does anybody have more details on the errors attribute under cn=snmp,cn=monitor?
Should I increase the log level to see what the errors are? If so, can you tell me how?
> On Dec 24, 2017, at 10:46 AM, Sergei Gerasenko <gerases(a)gmail.com
<mailto:gerases@gmail.com>> wrote:
>
>> What is an "error" in your data?
>
> The “error” graph graphs the “errors” attribute from cn=snmp,cn=monitor. I don’t know
what conditions actually increment that value.