IBM MQ Metricbeat module

[felix-lessoer]

This is the metricbeat module for IBM MQ. Which will be the transformation of this standalone beat

@ruflin is helping to integrate this as this is the first x-pack module for metricbeat

[felix-lessoer]

The module is now able to collect the MQ metrics.
A few things are open:

1.) In the module each metricseat is collected in parallel. This is not possible with the MQ lib at the moment. @ruflin Is there a way to collect the metricsets sequentially without putting everything in one fetch metricset?
If not I need to change the way I connect to MQ. Each metricset needs to connect to its own command / reply queue .

2.) To build metricbeat with ibmmq module it needs to have the MQ C library available locally under

for Linux

• cgo !windows CFLAGS: -I/opt/mqm/inc -D_REENTRANT
• cgo !windows LDFLAGS: -L/opt/mqm/lib64 -lmqm_r -Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64

for Windows

• cgo windows CFLAGS: -I"C:/Program Files/IBM/MQ/Tools/c/include"
• cgo windows LDFLAGS: -L "C:/Program Files/IBM/MQ/bin64" -lmqm

This needs to be switched to dynamic linking in mqi.go

3.) The PubSub metricset needs to be added

4.) The imports are pointing to my repo. This needs to be switched when it will be merged into Elastic repo

[ruflin]

That all metricset fetches are made in parallel is by design. To run it sequentially it would require quite fundamental changes. I would definitively recommend that each metricset maintains it's own connection, so if one metricset is blocked it does not impact others. Are there some advantages to this?

[ruflin]

Some notes on my end for this PR:

• We need to add a docker file for testing and generate the some expected outputs
• Perhaps split PR up per metricset
• Check what the impact of the dependencies on the size of the binary is
• Add libraries with govendor to make sure they are properly vendored and in the correct directory.

[ruflin]

Here is the docker image that can be used for testing: https://hub.docker.com/r/ibmcom/mq/

[felix-lessoer]

Here is the docker image that can be used for testing: https://hub.docker.com/r/ibmcom/mq/

You need to create it with a Queue Manager Name
MQ_QMGR_NAME - Set this to the name you want your Queue Manager to be created with.

This Queue Manager Name needs to be in the configuration.
The connection config (cc) for Docker needs to look something like this to get a result:

cc:
clientMode: true
mqServer: "DEV.ADMIN.SVRCONN/TCP/127.0.0.1 (1416)"
userId: "admin"
password: "passw0rd"

[ruflin]

Leaving some comments for whoever follows up with the fixes to not forget about things.

[ruflin]

This must be pulled in as vendor directory to make the separation clear.

[ruflin]

Complete the TODO in the docs

[mtojek]

I believe we can close this PR in favor of a simple light module implementation.