Start your 14-day free trial today

No Credit Card Required

Try Free

Already have an account? Sign In

Send data via ActiveMQ to your Logstash instance provided by


Collect and Ship ActiveMQ application logs to Logstash and Elasticsearch

Filebeat is a lightweight shipper that enables you to send your ActiveMQ application logs to Logstash and Elasticsearch. Configure Filebeat using the pre-defined examples below to start sending and analysing your ActiveMQ application logs.

Step 1 - Install FilebeatCopy

To get started first follow the steps below:

  • Install
  • Root access
  • Verify the required port is open

Older versions can be found here 7, 6, 5

Step 2 - Locate Configuration FileCopy

deb/rpm /etc/filebeat/filebeat.yml

Step 3 - Add ActiveMQ Log LocationCopy

Filebeat does not currently have a module to process the ActiveMQ application logs.

Therefore we need to add the ActiveMQ application log location to the filebeat inputs.

Add the following to the end of the log input example, before the filebeat.config.modules section.

- type: log
  enabled: true
    - /path/to/log/activemq/data/activemq.log*
    type: activemq
  multiline.pattern: ^\=
  multiline.match: before

If you’re running Filebeat 8.1+ filebeat.inputs needs to be filestream instead of logs:


- type: filestream
  enabled: true
    - /path/to/log/activemq/data/activemq.log*
    type: activemq
  multiline.pattern: ^\=
  multiline.match: before

Step 4 - Enable the inputCopy

We need to ensure that any inputs we are using are enabled


- type: log
  enabled: false

Enable the filebeat input, so it should look like the following


- type: log
  enabled: true

Step 5 - Configure OutputCopy

We will be shipping to Logstash so that we have the option to run filters before the data is indexed.

Comment out the elasticsearch output block.

## Comment out elasticsearch output
#  hosts: ["localhost:9200"]
No input available! Your stack is missing the required input for this data source Talk to support to add the input

Step 6 - Validate ConfigurationCopy

Let's check the configuration file is syntactically correct.


filebeat -e -c /etc/filebeat/filebeat.yml

Step 7 - Start filebeatCopy

Start or restart to apply the configuration changes.

Step 8 - Launch to view your logsCopy

Now you should view your logs:

Launch Dashboard

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Step 9 - how to diagnose no data in StackCopy

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Toggle View

Expand View

Return to Search

© 2023 Ltd, All rights reserved.