I have a clustered IBM MQ, where both Queue Managers have different jndi provider , but same queue names. Data from both the Queue Managers should have the same sourcetype, should go to same set of indexes and use same transforms. Since both QMs have same topic names but different jndi, how should I configure inputs.conf ? is there any role of queue prefix in creating different stanzas ?Saying that, if two stanzas in inputs.conf are entirely same except for the queue prefix and jndi provider, will they be processed differently and will data land into indexes from both sources ? Thanks! Manisha ... View more

Hi, I am trying to configure JMS Modular App to read messages from ActiveMQ Topic. MQ runs locally on the machine and there is a java code that uses jndi and pushes messages into topic called MyTopic. MQ is working fine, each time I run the code, message count in Topic increases (verified on ActiveMQ Web Console). Problem is that , I am still unable to index the messages in Splunk. Please let me know where I am wrong. Configuration on the UI is as below : Initialisation Mode : jndi JMS Connection Factory JNDI Name : connectionFactory JNDI Initial Context Factory Name : org.apache.activemq.jndi.ActiveMQInitialContextFactory JNDI Provider URL : tcp://localhost:61616 (Also tried with file:/home/user/MQJNDI/) jndi.properties file is placed at /home/user/MQJNDI/ Index message property values , Index message property values and Index message property values are checked. Sourcetype : mqTopic (manual) After saving the changes, I push messages again in the Topic , but nothing gets indexed. jndi.properties is as below: START SNIPPET: jndi java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory use the following property to configure the default connector java.naming.provider.url = tcp://localhost:61616 use the following property to specify the JNDI name the connection factory should appear as. connectionFactoryNames = connectionFactory, queueConnectionFactory, topicConnectionFactry register some queues in JNDI using the form queue.[jndiName] = [physicalName] queue.MyQueue = MyQueue register some topics in JNDI using the form topic.[jndiName] = [physicalName] topic.MyTopic = MyTopic END SNIPPET: jndi Java code that writes messages to Topic Arguments : MyTopic 100 package com.humana.splunk.jms; import javax.jms.Connection; import javax.jms.ConnectionFactory; import javax.jms.Destination; import javax.jms.JMSException; import javax.jms.MessageProducer; import javax.jms.Session; import javax.jms.TextMessage; import javax.naming.Context; import javax.naming.InitialContext; import javax.naming.NamingException; import org.slf4j.Logger; import org.slf4j.LoggerFactory; /** * A simple polymorphic JMS producer which can work with Queues or Topics which * uses JNDI to lookup the JMS connection factory and destination * * */ public final class SimpleProducer { private static final Logger LOG = LoggerFactory.getLogger(SimpleProducer.class); private SimpleProducer() { } /** * @param args the destination name to send to and optionally, the number of * messages to send */ public static void main(String[] args) { Context jndiContext = null; ConnectionFactory connectionFactory = null; Connection connection = null; Session session = null; Destination destination = null; MessageProducer producer = null; String destinationName = null; final int numMsgs; if ((args.length < 1) || (args.length > 2)) { LOG.info("Usage: java SimpleProducer <destination-name> [<number-of-messages>]"); System.out.println("args : " + args[0]); System.exit(1); } destinationName = args[0]; LOG.info("Destination name is " + destinationName); if (args.length == 2) { numMsgs = (new Integer(args[1])).intValue(); } else { numMsgs = 1; } /* * Create a JNDI API InitialContext object */ try { jndiContext = new InitialContext(); } catch (NamingException e) { LOG.info("Could not create JNDI API context: " + e.toString()); System.exit(1); } /* * Look up connection factory and destination. */ try { connectionFactory = (ConnectionFactory)jndiContext.lookup("topicConnectionFactory"); destination = (Destination)jndiContext.lookup(destinationName); } catch (NamingException e) { LOG.info("JNDI API lookup failed: " + e); System.exit(1); } /* * Create connection. Create session from connection; false means * session is not transacted. Create sender and text message. Send * messages, varying text slightly. Send end-of-messages message. * Finally, close connection. */ try { connection = connectionFactory.createConnection(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); producer = session.createProducer(destination); TextMessage message = session.createTextMessage(); for (int i = 0; i < numMsgs; i++) { message.setText("This is message " + (i + 1)); LOG.info("Sending message: " + message.getText()); producer.send(message); } /* * Send a non-text control message indicating end of messages. */ producer.send(session.createMessage()); } catch (JMSException e) { LOG.info("Exception occurred: " + e); } finally { if (connection != null) { try { connection.close(); } catch (JMSException e) { } } } } } Could you please help me identify/resolve the issue. Thanks in advance. ... View more

Is it possible to use collect command to collect data from one index and move it to another, where destiation index is not a summary index ? index=whatever host=whatever source=whatever whatever | collect index=foo Where foo is pre-configured index in indexes.conf. ... View more