Hi Rob, I found the issue - I needed to specify a routing_key - once I did this things worked fine.
Thanks again for your help. Ian On Thu, Jun 4, 2015 at 12:26 PM, Rob Miller <[email protected]> wrote: > I don't see anything obviously wrong with your config, but I'm far from an > expert on AMQP so that might not mean much. > > They're not much, but I do have a couple of debugging suggestions: > > * Temporarily dd a `CounterFilter` stanza to your config so you'll see > output re: how many messages are flowing through the Heka pipeline. > > * Temporarily switch from PayloadEncoder to RstEncoder with your LogOutput > to ensure that you don't have messages that are flowing through that happen > to have empty payloads. > > * Set up an alternate AMQP client of some sort on the same machine, > pointed at the same IP (i.e. `amqp://localhost/`), with the same > configuration to make sure that there is, in fact, traffic flowing through > the server on the exchange and the topic that you've specified. > > -r > > > On 06/03/2015 07:52 AM, Ian Reeve wrote: > >> I am running Heka 0.9.1 on Centos 6.5 and am trying to get data from an >> AMQP (RabbitMQ) exchange into heka so I can do some processing on the >> data. I see the heka internals information get logged but nothing that >> is sent to the events exchange. Based on the provided rabbitmq >> configuration and the heka configuration file, is there something that I >> am missing or doing incorrectly? Any recommendations for debugging this >> would be greatly appreciated. >> >> Thanks, >> Ian >> >> The configuration file is as follows: >> >> [hekad] >> maxprocs = 4 >> poolsize = 200 >> max_message_loops = 10 >> >> [amqp_events] >> type = "AMQPInput" >> url = "amqp://localhost/" >> exchange = "events" >> exchange_type = "topic" >> exchange_durability = false >> exchange_auto_delete = false >> queue = "events" >> prefetch_count = 0 >> queue_auto_delete = false >> >> [PayloadEncoder] >> append_newlines = true >> >> [metrics_output] >> type = "LogOutput" >> message_matcher = "TRUE" >> encoder = "PayloadEncoder" >> >> [DashboardOutput] >> ticker_interval = 5 >> >> >> The RabbitMQ queue and exchange configuration (to confirm the names used >> in the configuration file) is follows >> >> [root@nexus ~]# rabbitmqctl list_queues >> Listing queues ... >> amq.gen-KcgCQEFgBIyYzWddttYrqA 0 >> events 0 >> federation: queries -> rabbit@srv001 0 >> federation: queries -> rabbit@srv002 0 >> federation: queries -> rabbit@srv003 0 >> srv1-commands 0 >> srv2-commands 0 >> srv3-commands 0 >> >> [root@nexus ~]# rabbitmqctl list_exchanges >> Listing exchanges ... >> direct >> amq.direct direct >> amq.fanout fanout >> amq.headers headers >> amq.match headers >> amq.rabbitmq.log topic >> amq.rabbitmq.trace topic >> amq.topic topic >> events topic >> federation: queries -> rabbit@srv001 B x-federation-upstream >> federation: queries -> rabbit@srv002 B x-federation-upstream >> federation: queries -> rabbit@srv003 B x-federation-upstream >> heka-test topic >> queries topic >> >> >> _______________________________________________ >> Heka mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/heka >> >> >
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
