Activity Feed
- Got Karma for Splunk Add-on for Java Management Extensions: Why does JMX data stop for all servers when one goes down?. 06-05-2020 12:49 AM
- Posted Monitoring of Java Virtual Machines with JMX - how to specify an encrypted password on All Apps and Add-ons. 11-07-2018 12:25 PM
- Tagged Monitoring of Java Virtual Machines with JMX - how to specify an encrypted password on All Apps and Add-ons. 11-07-2018 12:25 PM
- Tagged Monitoring of Java Virtual Machines with JMX - how to specify an encrypted password on All Apps and Add-ons. 11-07-2018 12:25 PM
- Tagged Monitoring of Java Virtual Machines with JMX - how to specify an encrypted password on All Apps and Add-ons. 11-07-2018 12:25 PM
- Posted Splunk Add-on for Java Management Extensions: Why does JMX data stop for all servers when one goes down? on All Apps and Add-ons. 09-21-2018 01:55 PM
- Tagged Splunk Add-on for Java Management Extensions: Why does JMX data stop for all servers when one goes down? on All Apps and Add-ons. 09-21-2018 01:55 PM
- Tagged Splunk Add-on for Java Management Extensions: Why does JMX data stop for all servers when one goes down? on All Apps and Add-ons. 09-21-2018 01:55 PM
- Tagged Splunk Add-on for Java Management Extensions: Why does JMX data stop for all servers when one goes down? on All Apps and Add-ons. 09-21-2018 01:55 PM
Topics I've Started
11-07-2018
12:25 PM
Configuring Monitoring of Java Virtual Machines with JMX.
The “jmxuser” and “jmxpass” are included in the configuration file. I understand that these are optional. However, all weblogic specific data requires connecting to the main weblogic port where authentication is enabled. “jxmpass” is not encrypted in the config file and this is a security issue.
Is there a workaround for this or perhaps I’m missing something?
... View more
09-21-2018
01:55 PM
1 Karma
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?
... View more
