Comment on page
StackState Self-hosted v4.5.x
This page describes StackState v4.5.x. The StackState 4.5 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.5 version range to upgrade to a more recent release.
A lightweight Java plugin named JMXFetch is called by the Stackstate Agent to connect to the MBean Server and to collect these metrics. This plugin sends metrics to the Stackstate Agent using the Stsstatsd server running within the Agent. This functionality is also leveraged in the integrations for ActiveMQ, Cassandra, Solr, and Tomcat.
JMXFetch also sends service checks that report on the status of your monitored instances.
JMX Checks have a limit of 350 metrics per instance which should be enough to satisfy your needs as it's easy to customize which metrics you want to collect.
A remote connection is required for the StackState Agent to connect to the JVM, even when the two are on the same host.
- 1.Configure the Agent to connect using JMX and edit it according to your needs. Here is a sample
custom_jar_paths: # optional
- host: localhost
jmx_url: "service:jmx:rmi:///jndi/rmi://myhost.host:9999/custompath" # optional
name: jmx_instance # optional
java_options: "-Xmx200m -Xms50m"
refresh_beans: 600 # optional (in seconds)
custom_jar_paths(Optional) - Allows specifying custom jars that will be added to the classpath of the agent's JVM.
jmx_url- (Optional) - If the agent needs to connect to a non-default JMX URL, specify it here instead of a host and a port. If you use this you need to specify a 'name' for the instance.
is_jmx(Optional) - Allows creating different configuration files for each application rather than using a single long jmx file. Include the option in each configuration file.
name- (Optional) - Used in conjunction with
java_bin_path- (Optional) - Should be set if the agent cannot find your java executable.
java_options- (Optional) - Java JVM options
trust_store_password- (Optional) - Should be set if ssl is enabled.
process_name_regex- (Optional) - Instead of specifying a host and port or jmx_url, the agent can connect using the attach api. This requires the JDK to be installed and the path to tools.jar to be set.
tools_jar_path- (Optional) - To be set when process_name_regex is set.
refresh_beans- (Optional) - Refresh period for refreshing the matching MBeans list. Default is 600 seconds. Decreasing this value may result in increased CPU usage.
confparameter is a list of dictionaries. Only 2 keys are allowed in this dictionary:
include(mandatory): Dictionary of filters, any attribute that matches these filters will be collected unless it also matches the "exclude" filters (see below)
exclude(optional): Another dictionary of filters. Attributes that match these filters won't be collected
Tags are automatically added to metrics based on the actual MBean name. You can explicitly specify supplementary tags. For instance, assuming the following MBean is exposed by your monitored application:
It would create a metric called
mydomain(or some variation depending on the attribute inside the bean) with tags:
attr0:val0, attr1:val1, domain:mydomain, simple:val0, raw_value:my_chosen_value, multiple:val0-val1.
If you specify an alias in an
includekey that is formatted as camel case, it will be converted to snake case. For example,
MyMetricNamewill be shown in Stackstate as
excludedictionary supports the following keys:
domain: a list of domain names (e.g.
domain_regex: a list of regexes on the domain name (e.g.
bean_name: A list of full bean names (e.g.
bean_regex: A list of regexes on the full bean names (e.g.
attribute: A list or a dictionary of attribute names (see below for more details)
bean_regexfilters were added in version 5.5.0.
On top of these parameters, the filters support "custom" keys which means that you can filter by bean parameters. For example, if you want to collect metrics regarding the Cassandra cache, you could use the
type: - Cachesfilter:
attributefilter can accept two types of values:
- A dictionary whose keys are attributes names:conf:- include:attribute:maxThreads:alias: tomcat.threads.maxmetric_type: gaugecurrentThreadCount:alias: tomcat.threads.countmetric_type: gaugebytesReceived:alias: tomcat.bytes_rcvdmetric_type: counterIn that case you can specify an alias for the metric that will become the metric name in Stackstate. You can also specify the metric type either a gauge or a counter. If you choose counter, a rate per second will be computed for this metric.
- A list of attributes names:conf:- include:domain: org.apache.cassandra.dbattribute:- BloomFilterDiskSpaceUsed- BloomFilterFalsePositives- BloomFilterFalseRatio- Capacity- CompressionRatio- CompletedTasks- ExceptionCount- Hits- RecentHitRate
In that case:
- The metric type will be a gauge
- The metric name will be jmx.[DOMAIN_NAME].[ATTRIBUTE_NAME]
Here is another filtering example:
- host: 127.0.0.1
# Older StackState Agent versions
JMX Checks have a default configuration that will collect 11 metrics from your JMX application. A few of these metrics are:
jvm.gc.cms.count... So seeing these metrics is a sign that JMXFetch is properly running.
- List attributes that match at least one of your instances configuration:
sudo /etc/init.d/stackstate-agent jmx list_matching_attributes
- List attributes that do match one of your instances configuration but that are not being collected because it would exceed the number of metrics that can be collected:
sudo /etc/init.d/stackstate-agent jmx list_limited_attributes
- List attributes that will actually be collected by your current instances configuration:
sudo /etc/init.d/stackstate-agent jmx list_collected_attributes
- List attributes that don't match any of your instances configuration:
sudo /etc/init.d/stackstate-agent jmx list_not_matching_attributes
- List every attributes available that has a type supported by JMXFetch:
sudo /etc/init.d/stackstate-agent jmx list_everything
- Start the collection of metrics based on your current configuration and display them in the console:
sudo /etc/init.d/stackstate-agent jmx collect
Due to the nature of these integrations, it is possible to submit an extremely high number of metrics directly to Stackstate. What we've found in speaking with many customers is that some of these metrics are not needed; thus, we've set the limit at 350 metrics.
To see what you're collecting and get below the limit, begin by using the commands seen above to investigate what metrics are available. We then recommend creating filters to refine what metrics are collected. If you believe you need more than 350 metrics, please reach out to our technical support.
The agent does not come with a bundled JVM, but will use the one installed on your system. Therefore you must make sure that the Java home directory is present in the path of the user running the agent.
Alternatively, you can specify the JVM path in the integration's configuration file:
JBoss/WildFly applications expose JMX over a specific protocol (Remoting JMX) that is not bundled by default with JMXFetch. To allow JMXFetch to connect to these applications, configure it as follows:
- 1.Locate the
jboss-cli-client.jarfile on your JBoss/WildFly server (by default, its path should be
- 2.If JMXFetch is running on a different host than the JBoss/WildFly application, copy
jboss-cli-client.jarto a location on the host JMXFetch is running on.
- 3.Add the path of the jar to the
init_configsection of your configuration:init_config:custom_jar_paths:- /path/to/jboss-cli-client.jar
- 4.Specify a custom URL that JMXFetch will connect to, in the
instancessection of your configuration:# The jmx_url may be different depending on the version of JBoss/WildFly you're using# and the way you've set up JMX on your server# Please refer to the relevant documentation of JBoss/WildFly for more informationinstances:+ jmx_url: "service:jmx:remoting-jmx://localhost:9999"name: jboss-application # Mandatory, but can be set to any value,# will be used to tag the metrics pulled from
- 5.Restart the agent:
If you're using Tomcat with JMX Remote Lifecycle Listener enabled (see the Tomcat documentation for more information), JMXFetch will need some extra setup to be able to connect to your Tomcat application.
- 1.Locate the
catalina-jmx-remote.jarfile on your Tomcat server (by default, its path should be
- 2.If JMXFetch is running on a different host than the Tomcat application, copy
catalina-jmx-remote.jarto a location on the host JMXFetch is running on.
- 3.Add the path of the jar to the
init_configsection of your configuration:
- 1.Specify a custom URL that JMXFetch will connect to, in the
instancessection of your configuration:
# The jmx_url may be different depending on the way you've set up JMX on your Tomcat server
- jmx_url: "service:jmx:rmi://:10002/jndi/rmi://:10001/jmxrmi"
name: tomcat-application # Mandatory, but can be set to any arbitrary value,
# will be used to tag the metrics pulled from that instance
- 1.Restart the agent: