Apache ActiveMQ

This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect metrics from Apache ActiveMQ. This document shows you how to do the following:

Set up the exporter for ActiveMQ to report metrics.
Access a predefined dashboard in Cloud Monitoring to view the metrics.
Configure alerting rules to monitor the metrics.

These instructions apply only if you are using managed collection with Managed Service for Prometheus. If you are using self-deployed collection, then see the source repository for the JMX exporter for installation information.

These instructions are provided as an example and are expected to work in most Kubernetes environments. If you are having trouble installing an application or exporter due to restrictive security or organizational policies, then we recommend you consult open-source documentation for support.

For information about Apache ActiveMQ, see ActiveMQ.

Prerequisites

To collect metrics from ActiveMQ by using Managed Service for Prometheus and managed collection, your deployment must meet the following requirements:

Your cluster must be running Google Kubernetes Engine version 1.28.15-gke.2475000 or later.
You must be running Managed Service for Prometheus with managed collection enabled. For more information, see Get started with managed collection.
To use dashboards available in Cloud Monitoring for the ActiveMQ integration, you must use jmx-exporter version 0.17.0 or later.
For more information about available dashboards, see View dashboards.

ActiveMQ Brokers can be configured for JMX by setting the ACTIVEMQ_JMX and ACTIVEMQ_OPTS environment variables.

Install the ActiveMQ exporter

We recommend that you install the ActiveMQ exporter, jmx-exporter, as a sidecar to your ActiveMQ workload. For information about using sidecars, see Extended applications on Kubernetes with multi-container pods.

To install jmx-exporter as a sidecar to ActiveMQ, modify your ActiveMQ configuration as shown in the following example:

#Copyright2022GoogleLLC
#
#LicensedundertheApacheLicense,Version2.0(the"License");
#youmaynotusethisfileexceptincompliancewiththeLicense.
#YoumayobtainacopyoftheLicenseat
#
#https://www.apache.org/licenses/LICENSE-2.0
#
#Unlessrequiredbyapplicablelaworagreedtoinwriting,software
#distributedundertheLicenseisdistributedonan"AS IS"BASIS,
#WITHOUTWARRANTIESORCONDITIONSOFANYKIND,eitherexpressorimplied.
#SeetheLicenseforthespecificlanguagegoverningpermissionsand
#limitationsundertheLicense.
apiVersion:v1
kind:ConfigMap
metadata:
name:activemq-exporter
data:
config.yaml:|
hostPort:localhost:1099
lowercaseOutputName:true
lowercaseOutputLabelNames:true
blacklistObjectNames:
-"org.apache.activemq:clientId=*,*"
whitelistObjectNames:
-"org.apache.activemq:destinationType=Queue,*"
-"org.apache.activemq:destinationType=Topic,*"
-"org.apache.activemq:type=Broker,brokerName=*"
-"org.apache.activemq:type=Topic,brokerName=*"
rules:
-pattern:org.apache.activemq<type=Broker,brokerName=(\S*),destinationType=Queue,destinationName=(\S*)><>(\w+)
name:activemq_queue_$3
attrNameSnakeCase:true
labels:
destination:$2
-pattern:org.apache.activemq<type=Broker,brokerName=(\S*),destinationType=Topic,destinationName=(\S*)><>(\w+)
name:activemq_topic_$3
attrNameSnakeCase:true
labels:
destination:$2
-pattern:org.apache.activemq<type=Broker,brokerName=(\S*)><>CurrentConnectionsCount
name:activemq_connections
type:GAUGE
-pattern:org.apache.activemq<type=Broker,brokerName=(\S*)><>Total(.*)Count
name:activemq_$2_total
type:COUNTER
-pattern:org.apache.activemq<type=Broker,brokerName=(\S*)><>(.*)PercentUsage
name:activemq_$2_usage_ratio
type:GAUGE
valueFactor:0.01
---
apiVersion:apps/v1
kind:Deployment
metadata:
name:activemq
spec:
selector:
matchLabels:
+app.kubernetes.io/name:activemq
template:
metadata:
labels:
+app.kubernetes.io/name:activemq
spec:
containers:
-name:activemq
image:rmohr/activemq:5.15.9-alpine
+ports:
+-containerPort:1099
+name:jmx
+env:
+-name:ACTIVEMQ_JMX
+value:"1099"
+-name:ACTIVEMQ_OPTS
+value:"-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
+-name:exporter
+image:bitnami/jmx-exporter:0.17.0
+command:
+-java
+--jar
+-jmx_prometheus_httpserver.jar
+args:
+-"9000"
+-config.yaml
+ports:
+-containerPort:9000
+name:prometheus
+volumeMounts:
+-mountPath:/opt/bitnami/jmx-exporter/config.yaml
+subPath:config.yaml
+name:activemq-exporter
+volumes:
+-name:activemq-exporter
+configMap:
+name:activemq-exporter
+items:
+-key:config.yaml
+path:config.yaml

You must add any lines preceded by the + symbol to your configuration.

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

Define a PodMonitoring resource

For target discovery, the Managed Service for Prometheus Operator requires a PodMonitoring resource that corresponds to the JMX exporter in the same namespace.

You can use the following PodMonitoring configuration:

# Copyright 2022 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
apiVersion:monitoring.googleapis.com/v1
kind:PodMonitoring
metadata:
name:activemq
labels:
app.kubernetes.io/name:activemq
app.kubernetes.io/part-of:google-cloud-managed-prometheus
spec:
endpoints:
-port:prometheus
scheme:http
interval:30s
path:/metrics
selector:
matchLabels:
app.kubernetes.io/name:activemq

Ensure that the label selectors and the port match the selectors and port used in Install the ActiveMQ exporter.

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

Define rules and alerts

You can use the following Rules configuration to define alerts on your ActiveMQ metrics:

# Copyright 2022 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
apiVersion:monitoring.googleapis.com/v1
kind:Rules
metadata:
name:activemq-rules
labels:
app.kubernetes.io/component:rules
app.kubernetes.io/name:activemq-rules
app.kubernetes.io/part-of:google-cloud-managed-prometheus
spec:
groups:
-name:activemq
interval:30s
rules:
-alert:ActiveMQNoConnections
annotations:
description:|-
ActiveMQ no connections
VALUE = {{ $value }}
LABELS: {{ $labels }}
summary:ActiveMQ down (instance {{ $labels.instance }})
expr:activemq_connections_total{job="activemq"} == 0
for:5m
labels:
severity:warning
-alert:ActiveMQHighStoreUsage
annotations:
description:|-
ActiveMQ high store usage
VALUE = {{ $value }}
LABELS: {{ $labels }}
summary:ActiveMQ high store usage (instance {{ $labels.instance }})
expr:activemq_store_usage_ratio{job="activemq"} > 0.9
for:5m
labels:
severity:warning
-alert:ActiveMQHighTempStoreUsage
annotations:
description:|-
ActiveMQ high temp store usage
VALUE = {{ $value }}
LABELS: {{ $labels }}
summary:ActiveMQ high temp store usage (instance {{ $labels.instance }})
expr:activemq_temp_usage_ratio{job="activemq"} > 0.9
for:5m
labels:
severity:warning

To apply configuration changes from a local file, run the following command:

kubectl apply -n NAMESPACE_NAME -f FILE_NAME

You can also use Terraform to manage your configurations.

For more information about applying rules to your cluster, see Managed rule evaluation and alerting.

Verify the configuration

You can use Metrics Explorer to verify that you correctly configured the JMX exporter. It might take one or two minutes for Cloud Monitoring to ingest your metrics.

To verify the metrics are ingested, do the following:

In the Google Cloud console, go to the Metrics explorer page:
Go to Metrics explorer

If you use the search bar to find this page, then select the result whose subheading is Monitoring.
In the toolbar of the query-builder pane, select the button whose name is either MQL or PromQL.
Verify that PromQL is selected in the Language toggle. The language toggle is in the same toolbar that lets you format your query.

Enter and run the following query:

up{job="activemq", cluster="CLUSTER_NAME", namespace="NAMESPACE_NAME"}

View dashboards

The Cloud Monitoring integration includes the ActiveMQ Prometheus Overview dashboard. Dashboards are automatically installed when you configure the integration. You can also view static previews of dashboards without installing the integration.

To view an installed dashboard, do the following:

In the Google Cloud console, go to the Dashboards page:
Go to Dashboards

If you use the search bar to find this page, then select the result whose subheading is Monitoring.
Select the Dashboard List tab.
Choose the Integrations category.
Click the name of the dashboard, for example, ActiveMQ Prometheus Overview.

To view a static preview of the dashboard, do the following:

In the Google Cloud console, go to the Integrations page:
Go to Integrations

If you use the search bar to find this page, then select the result whose subheading is Monitoring.
Click the Kubernetes Engine deployment-platform filter.
Locate the Apache ActiveMQ integration and click View Details.
Select the Dashboards tab.

Troubleshooting

For information about troubleshooting metric ingestion problems, see Problems with collection from exporters in Troubleshooting ingestion-side problems.