-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Icingabeat v.6.3.3 does not send the hostname for the check, instead send own hostname #25
Comments
I can confirm this issue. We had to downgrade to 6.1.1 as a workaround. |
on my end downgrade makes elastic reject the fields from 6.1.1 |
Aparently this seems to be connected to the upgrade to libbeat 6.3:
|
Since Moving it out could be as simple as
which will populate Since Any thoughts? Renaming to avoid collision might make more sense, with the rest of the fields (e.g., |
Same issue as in #26 |
After installing icingabeat (6.3.3) on a complete new machine, with minimal changes to the icingabeat.yml and outputting to a completely new elasticsearch index (5.5), accessing an icinga2 (2.9.1), icingabeat will log checkresults with the name of the host running icingabeat as host.name:
![screenshot_2018-09-12 kibana](https://user-images.githubusercontent.com/1584089/45442823-5f62f980-b6c3-11e8-8abf-5f55eb1b06fa.png)
My icingabeat.yml (with comments, hostnames and credentials redacted):
Representative checkresult (in json):
Expected Behavior
Somewhere in the document should the hostname for the checkresult (notification, ...) be analog to the service.
Current Behavior
All hostnames will be the icingabeat hostname
Steps to Reproduce (for bugs)
icingabeat setup
Context
We can not use icingabeat 6.3.3 as there is no way to know to which of our hosts the messages are related to.
Your Environment
icingabeat -version
): icingabeat version 6.3.3 (amd64), libbeat 6.3.3icinga2 --version
): r2.9.1-1curl -XGET 'localhost:9200'
): 5.5.0bin/logstash -V
): 5.6.7 (not configured to be used)curl -XGET http://localhost:5601/status -I
): 5.5.0The text was updated successfully, but these errors were encountered: