All Apps and Add-ons

How to monitor Rabbitmq topic and queue via JMS message Modular Input

rock_kang
New Member

hi All
I am relatively new to RabbitMQ and JMS.
I have tried reading all the documentation (https://www.rabbitmq.com/jms-client.html#jms-connection-factory) and https://www.fiorano.com/documentation/display/PUB/Creating+the+.bindings+file+for+Rabbit+MQ+JMS+Prov..., but I am still unable to figure out what went wrong.
I am trying to poll from a queue using JMS Messaging Modular Input.
https://splunkbase.splunk.com/app/1317/#/details
The following was done:

1) Enable the plugin using the rabbitmq-plugins command
rabbitmq-plugins enable rabbitmq_jms_topic_exchange
2) Created .binding txt file and placed it (a) as a jar file in $SPLUNK_HOME\etc\apps\jms_ta\bin\lib. Please check the attached document.
2) Included following Jar file in $SPLUNK_HOME\etc\apps\jms_ta\bin\lib\

3) Configured inputs.conf in launcher app. But we are not sure if they are correct or not.
1. #[jms]
2. #activation_key=YOURKEY
3. #jndi_initialcontext_factory = org.apache.activemq.jndi.ActiveMQInitialContextFactory
4. #jndi_provider_url = tcp:// 10.10.43.132:61616
5. #jndi_user = ? where should I inputs?
6. #jndi_pass = ? where should I inputs?
7. #jms_connection_factory_name = someConnectionFactory
8. #index = jmsIndex
9. #index_message_properties = true
10. #index_message_header = true
11. #strip_newlines = true
12. #init_mode = jndi
13. #init_mode = local
14. #local_init_mode_resource_factory_impl = com.foo.zoo.MyImplementation
15. #local_init_mode_resource_factory_params = key1=value1,key2=value2,key3=value3
16.
17. #[jms://queue/cn.api.handler.email]
18. #sourcetype = jms_api_handler.email
19. #disabled = true
20.
21. #[jms://topic/amp.rabbitmq.event]
22. #sourcetype = jms_rabbitmq_event
23. #disabled = true
24.
Can anyone advise me on what went wrong? Thank you!

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...