We are using Splunk Add-on for Java Management Extensions (JMX)
Application: Splunk_TA_jmx
We are monitoring JMX data from two environments -- ENV_A and ENV_B
Both environments have several weblogic servers and connections were created for each of them.
We have 3 templates to subset the JMX data to be collected – T1, T2, and T3.
Each environment has two tasks:
ENV_A – T1, T2 (interval 60)
ENV_A – T3 (interval 86400)
ENV_B – T1, T2 (interval 300)
ENV_B – T3 (interval 86400)
ENV_A is an environment that goes up and down. When ENV_A goes down, no JMX data from ENV_B is sent to the indexer. There are no errors in the log file other than those indicating that a port from the ENV_A is not available.
I have to restart the Splunk forwarder for the JMX data to resume.
Anyone know why the availability of ENV_A impacts the collection of data from ENV_B?
