[Fedora-directory-users] SNMP Monitoring - What's available

[DeMarco, Dennis]

Thank you all. Exactly what I needed.

-----Original Message-----
From: fedora-directory-users-bounces at redhat.com [mailto:fedora-directory-users-bounces at redhat.com] On Behalf Of Tom Throckmorton
Sent: Friday, May 23, 2008 2:14 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] SNMP Monitoring - What's available

On 5/23/08 1:27 PM, DeMarco, Dennis wrote:
> Thanks,
>
> I already looked through that information. I can not see any snmp way of
> asking for # of current connections.
>
> That piece of info would work great to monitor for floods or some other
> problem.
>
> The performance counters are stored somewhere, as the admin console
> displays them. I just need to track where.

Dennis,

Assuming you've already seen this HowTo:

http://directory.fedoraproject.org/wiki/Howto:SNMPMonitoring

I was looking for the same thing some time ago, and eventually decided
that the objects offered via SNMP weren't cutting it, and so switched to
fetching that info directly out of the monitor branch using ldapsearch,
which provides, among other interesting bits, currentconnections,
totalconnections and connectionpeak, e.g.:

> me at somehost% ldapsearch -H ldap://my.ldap.host -b 'cn=monitor' -v -x -LLL cn='monitor'
> ldap_initialize( ldap://my.ldap.host )
> filter: cn=monitor
> requesting: ALL
> dn: cn=monitor
> objectClass: top
> objectClass: extensibleObject
> cn: monitor
> connectionpeak: 1260
> version: Sun-Java(tm)-System-Directory/6.2_GP_6597523 B2007.264.1019
> threads: 30
> currentconnections: 199
> totalconnections: 454235
> dtablesize: 65536
> readwaiters: 0
> opsinitiated: 5735651
> opscompleted: 5735650
> request-que-backlog: 0
> entriessent: 1359462
> bytessent: 1148150533
> cache-avail-bytes: 7282450432
> heapmaxhighhits: 0
> heapmaxlowhits: 0
> currenttime: 20080523175805Z
> starttime: 20080521135633Z
> nbackends: 12
> currentpsearches: 0

...which is basically what the helper script mentioned on that page is
doing.  As you can see the example above is against Sun JDS 6, but IIRC,
  it works the same on FDS (sorry, don't have an instance available at
the moment for testing.)

HTH,

-tt


> -----Original Message-----
> From: fedora-directory-users-bounces at redhat.com
> [mailto:fedora-directory-users-bounces at redhat.com] On Behalf Of Rich
> Megginson
> Sent: Friday, May 23, 2008 10:18 AM
> To: General discussion list for the Fedora Directory server project.
> Subject: Re: [Fedora-directory-users] SNMP Monitoring - What's available
>
> DeMarco, Dennis wrote:
>> I've got a question I've been trying to hunt down.
>>
>> Is there any way for snmp to monitor connections to the directory
>> server?
>>
>> I see there are entries for snmp to see things like # of entries added
>> since restart.. However are there any good resource summaries I can
>> monitor?  Ie the Performance counters in the admin console?
>>
> This might help - *http://tinyurl.com/667xpc*
>> Thanks,
>> Dennis
>>
>> This message (including any attachments) contains confidential
> information intended for a specific individual and purpose, and is
> protected by law.  If you are not the intended recipient, you should
> delete this message.  Any disclosure, copying, or distribution of this
> message, or the taking of any action based on it, is strictly
> prohibited.
>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

--
Fedora-directory-users mailing list
Fedora-directory-users at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message.  Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.