Hey Stewart,
First of all, I hope you had a nice holiday.
I wanted to let you know I've updated the mysql agent again; I did some
tests with 5.1.11-beta as well as 4.1.18 and its working now. Changes
are minor, a few bugs fixed and the logevents are now properly received
and converted into SNMP traps.
As always, updated version available from
http://www.reverze.net/mysql_snmp.tar.gz
Can you tell me if there's been any progress with regards to the policy
for 3rd party submissions to MySQL?
Lastly, I've sent mr. Marc Paley an email several weeks ago (5-7-2006 to
be exact). He has not responded. Can you tell me if there is someone
with that name working for MySQL, Inc?
Cheers,
Michel Stam
Michel Stam wrote:
> Ok, slight update here;
>
> Preliminary support for the logevents available in MySQL NDB cluster
> 5.0 and later has been added. It compiles, but I cannot tell if it
> will work until I have a proper 5.0/5.1 cluster setup here (which will
> probably take some time).
>
> Node ID's should now also be sent along with every cluster SNMP Trap,
> so you can see what node the event concerns.
>
> MIB has been updated to accomodate all this.
>
> http://www.reverze.net/mysql_snmp.tar.gz
>
> Cheers,
>
> Michel
>
> Michel Stam wrote:
>> Hey Stewart,
>>
>>> Great - this is probably best. It is highly unlikely that anybody is
>>> going to deploy 4.1 Cluster at this stage (5.0 at least). However, some
>>> may want to add this on... but I would say most people these days are
>>> going with 5.0 or plan to upgrade soon.
>>
>> True enough. Comments have been added to the INSTRUCTIONS file. As
>> before;
>> http://www.reverze.net/mysql_snmp.tar.gz
>>
>>> Have a look at the (recently uploaded) NDB API docs in the MGM API.
>>>
>>> http://dev.mysql.com/doc/ndbapi/en/struct-ndb-logevent.html
>>>
>>> Each event has different information, but most have all that you would
>>> need.
>>
>> This was what I was looking for :)
>> I'll see if I can code this in; Unfortunately we don't have anything
>> else than 4.1 cluster here, so I don't know if I can test it
>> properly. I haven't seen those functions in 4.1.
>> Shouldn't be too difficult, I think.
>>
>> (I know, we should really upgrade our MySQL cluster - This will
>> probably happen if/when the agent is in the MySQL code, be it version
>> 5.0.x or later)
>>
>> Another thing; I send an email to mr. Paley regarding the SNMP OID
>> (to check he's not using it for anything). No response so far, I
>> assume he still works for MySQL, Inc.
>>
>> And last, but not least - Have a great holiday next week!
>>
>> Cheers,
>>
>> Michel
>>
>> Stewart Smith wrote:
>>> On Thu, 2006-07-06 at 10:28 +0200, Michel Stam wrote:
>>>
>>>> Ok, in that case I'll refrain from posting the bugs so as not to
>>>> needlessly bother the mysql developers. I can work around the problem
>>>> easily enough, anyway.
>>>>
>>>> I'll make a couple of additions to the INSTRUCTIONS file with these
>>>> issues, so that people running 4.1 wanting to compile this don't have
>>>> to figure it out for themselves.
>>>>
>>>
>>> Great - this is probably best. It is highly unlikely that anybody is
>>> going to deploy 4.1 Cluster at this stage (5.0 at least). However, some
>>> may want to add this on... but I would say most people these days are
>>> going with 5.0 or plan to upgrade soon.
>>>
>>>
>>>> Another thing that came to mind yesterdaynight;
>>>> I know that its possible to get events from the NDB cluster. However,
>>>> as far as I know this is only in the form of a character string. Is it
>>>> possible to read these events out in more detail (perhaps a structure
>>>> with information pertaining to the node(s) involved)?
>>>>
>>>> Given that, it might be an idea to send out SNMP traps for these too?
>>>> That way you can see when for instance a disk node dies, or perhaps
>>>> when a backup is started / completed.
>>>>
>>>
>>> Have a look at the (recently uploaded) NDB API docs in the MGM API.
>>>
>>> http://dev.mysql.com/doc/ndbapi/en/struct-ndb-logevent.html
>>>
>>> Each event has different information, but most have all that you would
>>> need.
>>>
>>>>
>>
>
--
Michel Stam ing.
Software Development Engineer
michel@stripped <mailto:michel@stripped>
Houtweg 29
1251 CS Laren
The Netherlands
t: +31 (0)35 548 98 58
f: +31 (0)35 531 65 61
www.teleconcept.nl <http://www.teleconcept.nl>
