This project enables Apache RocketMQ integrate directly with Elastic Beats.

This project is developed and tested using Apache RocketMQ Go Client v2.1.0 and Beats 7.17.0

The Beats platform provides several Beats, like Filebeat , Heartbeat , Metricbeat, etc. So you can choose to build one or more Beats according to different sources you want to capture.

At present Beats Platform does not provide ways to integrate a custom output at runtime, so you must build Beats with this codebase to generate a new Beat to support output to Apache RocketMQ.

You can obtain a copy of the Beat codebase with the following git command:

git clone --branch <branch_name> --single-branch https://github.com/elastic/beats.git <target_folder>

The branch_name should be the version of Beats you want to use. In the following <target_folder> is denoted by $BEATS_HOME.

1.2.1 clone this codebase to your local repository, then copy the folder rocketmq under libbeat/output to $BEATS_HOME/libbeat/output/.

1.2.2 add _ "github.com/elastic/beats/v7/libbeat/outputs/rocketmq" in the import part of $BEATS_HOME/libbeat/publisher/includes/includes.go:

import (
	// import queue types
	_ "github.com/elastic/beats/v7/libbeat/outputs/codec/format"
	_ "github.com/elastic/beats/v7/libbeat/outputs/codec/json"
	_ "github.com/elastic/beats/v7/libbeat/outputs/console"
	_ "github.com/elastic/beats/v7/libbeat/outputs/elasticsearch"
	_ "github.com/elastic/beats/v7/libbeat/outputs/fileout"
	_ "github.com/elastic/beats/v7/libbeat/outputs/kafka"
	_ "github.com/elastic/beats/v7/libbeat/outputs/logstash"
	_ "github.com/elastic/beats/v7/libbeat/outputs/redis"
	
	_ "github.com/elastic/beats/v7/libbeat/outputs/rocketmq"
	
	_ "github.com/elastic/beats/v7/libbeat/publisher/queue/diskqueue"
	_ "github.com/elastic/beats/v7/libbeat/publisher/queue/memqueue"
	_ "github.com/elastic/beats/v7/libbeat/publisher/queue/spool"
)

1.2.3 run go mod tidy to import dependencies of RocketMQ go client, or add the following instruction to $BEATS_HOME/go.mode:

require github.com/apache/rocketmq-client-go/v2 v2.1.0

1.2.4 build your Beats

For example, if you want to build filebeat, run the following command:

cd $BEATS_HOME/filebeat/ && make

After that, a new executable filebeat is generated, and you can use it to send events to Apache RocketMQ.

If you want to build other Beats, just enter the specified folder and run make.

For example:

cd $BEATS_HOME/auditbeat/ && make
cd $BEATS_HOME/heartbeat/ && make
cd $BEATS_HOME/metricbeat/ && make
cd $BEATS_HOME/packetbeat/ && make
cd $BEATS_HOME/winlogbeat/ && make

After you have built your Beats, you can run them to send events to Apache RocketMQ.

Here is a simple configuration that can be used to test that if the content of /var/log/messages would be sent to RocketMQ successfully.

filebeat.inputs:
  - type: filestream
    enabled: true
    paths:
      - /var/log/messages

output.rocketmq:
  nameservers: [ "127.0.0.1:9876" ]
  topic: TopicTest

As you can see above, the only required configuration options are nameservers and topic, which denotes the name server address array of Apache RocketMQ and the topic where you want to publish the event, respectively. For more details, please reference the next section.

Copy the above Filebeat configuration to a file such as rocketmq_output.yml. Filebeat should then be started with:

./filebeat -c rocketmq_output.yml -e

All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.

Programming is not a required skill. Whatever you've seen about open source and maintainers or community members saying "send patches or die" - you will not see that here.

It is more important to the community that you are able to contribute.

Apache License, Version 2.0 Copyright (C) Apache Software Foundation