Metricbeat from source builds x-pack modules but doesnt contain directories in image

Elastic Stack Beats
,
1

Hello,

I have recently built Metricbeat from source code after following the developer guides. I noticed it builds all of the x-pack modules, but at the end of the day the image doesnt contain these module directories.

Ultimately, I need to make just a few line updates to the AWS module for the normal metricbeat:7.14.0 image to work in my desired destination environment. I thought I could build this from source after making those updates to the x-pack/metricbeat/aws code.

I pulled the 7.14.0 code, updated the aws.go code, and everything built fine ... but at the end of the day, there was no module, module.d directories to configure with YAMLs.

Please Help!

2

Hello! How are you building it after changing the aws code? What I usually do is under x-pack/metricbeat, I run mage update; mage build. Then you can run ./metricbeat modules enable aws to enable aws module specifically for testing.

3

Yes, you are totally right!

My mistake was I was building from the beat/metricbeat directory (hence creating the OSS version). When I built from beat/x-pack/metricbeat, it was the image Metricbeat image I was expecting.

Thank you so much!

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.