dd5751f335 | ||
---|---|---|
.github | ||
_meta | ||
beater | ||
cmd | ||
config | ||
data | ||
docs | ||
screenshots | ||
tests/system | ||
vendor/github.com/elastic/beats | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
AUTHORS | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
Makefile | ||
README.md | ||
RELEASE.md | ||
dashboards.yml | ||
fields.yml | ||
icingabeat.full.yml | ||
icingabeat.reference.yml | ||
icingabeat.yml | ||
main.go | ||
main_test.go | ||
version.yml |
README.md
Icingabeat
The Beats are lightweight data shippers, written in Go, that you install on your servers to capture all sorts of operational data (think of logs, metrics, or network packet data). The Beats send the operational data to Elasticsearch, either directly or via Logstash, so it can be visualized with Kibana.
Icingabeat is an Elastic Beat that fetches data from the Icinga 2 API and sends it either directly to Elasticsearch or Logstash.
Documentation
Please read the documentation on icinga.com/docs/icingabeat/latest for more information
Development
Building and running manually
Requirements
- Golang 1.9
Clone
To clone Icingabeat from the git repository, run the following commands:
mkdir -p ${GOPATH}/github.com/icinga
cd ${GOPATH}/github.com/icinga
git clone https://github.com/icinga/icingabeat
For further development check out the beat developer guide.
Build
Ensure that this folder is at the following location:
${GOPATH}/github.com/icinga
To build the binary for Icingabeat run the command below. This will generate a binary in the same directory with the name icingabeat.
make
Run
To run Icingabeat with debugging output enabled, run:
./icingabeat -c icingabeat.yml -e -d "*"
Test
To test Icingabeat, 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 etc/fields.yml
.
To generate etc/icingabeat.template.json and etc/icingabeat.asciidoc
make update
Cleanup
To clean Icingabeat source code, run the following commands:
make fmt
make simplify
To clean up the build directory and generated artifacts, run:
make clean
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 package
This will fetch and create all images required for the build process. The whole process can take several minutes to finish.
To disable snapshot packages or build specific packages, set the following environment variables:
export SNAPSHOT=false
export TARGETS="\"linux/amd64 linux/386\""
export PACKAGES=icingabeat/deb
make package
Dashboards
To be able to export dashboards with all their dependencies (visualizations and
searches) you have to name the dashboard with a icingabeat-
prefix.
Export dashboards:
export ES_URL=http://127.0.0.1:9200
make export-dashboards
After exporting, dashboards can be packaged:
export SNAPSHOT=false
make package-dashboards