[rabbitmq-discuss] Monitoring Question

Mon Jan 12 23:34:28 GMT 2009

You could also do this via ruby, but the protocol only gives you the #
of consumers and the # of messages on the queue:

require 'rubygems'
require 'mq'

AMQP.start(:host => 'localhost', :port => 5672) do
  EM.add_periodic_timer(30){

    MQ.queue('name').status{ |n_messages, n_consumers|
      send_email if n_messages > 100
    }

  }
end

  Aman

On Mon, Jan 12, 2009 at 3:24 PM, Jason J. W. Williams
<jasonjwwilliams at gmail.com> wrote:
> Hi Ben,
>
> There's a lot of things that are very attractive about Erlang. Not
> least of which is OTP.
>
> -J
>
> On Mon, Jan 12, 2009 at 4:18 PM, Ben Hood <0x6e6562 at gmail.com> wrote:
>> Jason,
>>
>> On Mon, Jan 12, 2009 at 11:13 PM, Jason J. W. Williams
>> <jasonjwwilliams at gmail.com> wrote:
>>> Erlang was already on my list of things to learn before RabbitMQ. :-)
>>> Still is, just need to get this project done first. We've got the rule
>>> if you can't monitor it you can't deploy it. :-)
>>
>> Fair point.
>>
>> IMHO Erlang is one of the most monitorable things that I've seen:
>>
>> http://erlang.org/doc/apps/appmon/part_frame.html
>>
>> ...and many more: remote Erlang shells, remoting OOTB, protocols,
>> SNMP, etc, etc.....it is a language for continuously running
>> applications.
>>
>> Ben
>>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>