Skip to main content
Sumo Logic

Collect Logs and Metrics for ActiveMQ

  1. Last updated
  2. Save as PDF

This page provides instructions for configuring log and metric collection for the Sumo Logic App for ActiveMQ. 

Collection Process Overview

Configuring log and metric collection for the ActiveMQ App includes the following tasks:

Step 1: Configure Fields in Sumo Logic

Create the following Fields in Sumo Logic prior to configuring collection. This ensures that your logs and metrics are tagged with relevant metadata, which is required by the app dashboards. For information on setting up fields, see the Fields help page.

If you are using ActiveMQ in a non-Kubernetes environment create the fields:

  • component
  • environment
  • messaging_system
  • messaging_cluster
  • pod

If you are using ActiveMQ in a Kubernetes environment create the fields:

  • pod_labels_component
  • pod_labels_environment
  • pod_labels_messaging_system
  • pod_labels_messaging_cluster

Sample Log Message

Kubernetes:

{
      timestamp:1624348918179,
      log:"2021-06-22 08:01:57,993 | DEBUG | Publishing: tcp://activemq-2:61616 for broker transport URI: tcp://activemq-2:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600 | org.apache.activemq.broker.TransportConnector | ActiveMQ Transport: tcp:///10.32.0.1:16932@61616",
      stream:"stdout",
      time:"2021-06-22T08:01:58.177654533Z"
}

Non-Kubernetes:

2021-06-22 15:00:41,922 | DEBUG | Stopping transport tcp:///192.168.100.8:36302@61616 | org.apache.activemq.transport.tcp.TcpTransport | ActiveMQ BrokerService[localhost] Task-15300
Host: broker-3-activemq Name: /opt/activemq/data/activemq.log Category:logfile