-
Notifications
You must be signed in to change notification settings - Fork 582
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
[dev.icinga.com #6474] Column 'host_name' does not exist in table 'hosts' #1680
Comments
Updated by mfriedrich on 2014-06-12 07:56:49 +00:00 Hm. Does it work with 'name'? |
Updated by mopp on 2014-06-12 08:00:26 +00:00 "Filter: host = TEST123", returns almost the same error:
|
Updated by mopp on 2014-06-12 08:02:11 +00:00 It will work with "Filter: name = TEST123". |
Updated by mfriedrich on 2014-06-12 08:33:50 +00:00
Ok. Sounds like an ugly protocol bug as well. By default the 'host_' prefix will only be added if that table is joined with services or a different table. Thruk does it right, NagVis does not as it seems. Let's see how to fix that bug in a reasonable fashion to stay compatible. |
Updated by Anonymous on 2014-06-12 10:05:04 +00:00
Applied in changeset i2:627f96d85d10fa88b7e330fce6e55a3f7768c53a. |
Updated by mfriedrich on 2014-09-16 09:14:49 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/6474
Created by mopp on 2014-06-12 07:38:11 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2014-06-12 10:05:03 +00:00)
Target Version: 2.0.0
Last Update: 2014-09-16 09:14:49 +00:00 (in Redmine)
NagVis runs the query:
Result:
If you run the same query without "Filter: host_name" it will return the requested data for all hosts.
Changesets
2014-06-12 09:59:21 +00:00 by (unknown) 627f96d
The text was updated successfully, but these errors were encountered: