Following the official guide to generate Beat
in general, the logic to collect lm metric remain the same, but implementation has changed to fit new Beat lib:
use new beat framework code to get config paramenter use new datasturture beat.Event to compose event It is tested in Centos 7.5.
To build it, package lm_sensors-devel needs to be installed. to run it, package lm_sensors needs to be installed.
{Beat}
Welcome to {Beat}.
Ensure that this folder is at the following location:
${GOPATH}/src/github.com/wgui1/lmsensors
Getting Started with {Beat}
Requirements
- Golang 1.7
Init Project
To get running with {Beat} and also install the dependencies, run the following command:
make setup
It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.
To push {Beat} in the git repository, run the following commands:
git remote set-url origin https://github.com/wgui1/lmsensors
git push origin master
For further development, check out the beat developer guide.
Build
To build the binary for {Beat} run the command below. This will generate a binary in the same directory with the name lmsensors.
make
Run
To run {Beat} with debugging output enabled, run:
./lmsensors -c lmsensors.yml -e -d "*"
Test
To test {Beat}, run the following command:
make testsuite
alternatively:
make unit-tests
make system-tests
make integration-tests
make coverage-report
The test coverage is reported in the folder ./build/coverage/
Update
Each beat has a template for the mapping in elasticsearch and a documentation for the fields
which is automatically generated based on fields.yml
by running the following command.
make update
Cleanup
To clean {Beat} source code, run the following command:
make fmt
To clean up the build directory and generated artifacts, run:
make clean
Clone
To clone {Beat} from the git repository, run the following commands:
mkdir -p ${GOPATH}/src/github.com/wgui1/lmsensors
git clone https://github.com/wgui1/lmsensors ${GOPATH}/src/github.com/wgui1/lmsensors
For further development, check out the beat developer guide.
Packaging
The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker and vendoring as described above. To build packages of your beat, run the following command:
make release
This will fetch and create all images required for the build process. The whole process to finish can take several minutes.