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 #8241] Take display_name into account when searching for host and service names #1315
Comments
Updated by vaisov on 2015-01-16 10:01:11 +00:00 I have service with values taken from loop:
Also I have another check for uwsgi port 9006 which doesn't use loop's values:
When I try to search for 'uwsgi' in WebUI I get results only for port 9006. |
Updated by elippmann on 2015-01-19 16:32:47 +00:00
|
Updated by elippmann on 2015-01-20 14:55:21 +00:00 Hi, Currently we only use the name1 and name2 columns for searching. In your example 9003 and 9004 are written to the name2 column. I'll add display_name as second search column. But you should fix your config because actually the name1 and name2 columns are intended to be the object names:
Notice the "uswgi " prefix before the for loop. You may remove the display_name attribute then. Cheers, |
Updated by vaisov on 2015-01-20 15:32:13 +00:00 Hi, does that mean that each object has to be described as in your example? Or it won't be needed after you'll add display_name as second search column? I want to avoid both this bug and this: https://dev.icinga.org/issues/8242, what is the best way to describe object to have proper sorting in ClassicUI and proper search in Web2? |
Updated by elippmann on 2015-01-20 15:51:51 +00:00 This is how to properly configure Icinga 2:
|
Updated by vaisov on 2015-01-20 15:55:55 +00:00 So general advice would be to avoid display_name where possible? |
Updated by elippmann on 2015-01-20 16:40:52 +00:00 Hi, vaisov wrote:
I would say, use display_name only where it makes sense. For example when using IP addresses or fully qualified domain names for host names, it is perfectly valid to define a display_name for those objects. Icinga Web 2 does not yet use the display_name attribute everywhere for display purposes though. But I'll implement that tomorrow. If you do not specify display_name then the object's name automatically maps to display_name. Hope this helps. Cheers, |
Updated by elippmann on 2015-01-21 08:39:50 +00:00
|
Updated by elippmann on 2015-01-22 10:34:50 +00:00
|
Updated by elippmann on 2015-01-22 10:34:53 +00:00
Hi, I'll close this one as duplicate for #8241. Cheers, |
Updated by tobiasvdk on 2015-01-22 10:42:35 +00:00 @lippser: Please re-open, you accidentally closed the wrong one. |
Updated by elippmann on 2015-01-22 11:38:25 +00:00
tobiasvdk wrote:
Ooops. Thanks for the heads up :) |
Updated by elippmann on 2015-02-04 08:34:04 +00:00
Hi, This one didn't make into our second beta. But we'll fix it asap. Cheers, |
Updated by elippmann on 2015-02-10 11:47:47 +00:00
|
Updated by arcade on 2015-03-16 08:04:13 +00:00 This seems not to work anymore with the latest git pull. |
Updated by elippmann on 2015-03-30 10:26:58 +00:00
|
Updated by elippmann on 2015-05-19 09:05:51 +00:00
|
Updated by aklimov on 2015-05-19 12:10:03 +00:00
Applied in changeset 75b004d. |
Updated by aklimov on 2015-05-19 16:23:30 +00:00
|
Updated by aklimov on 2015-05-20 08:49:50 +00:00
|
Updated by elippmann on 2015-05-21 11:59:11 +00:00
|
Updated by elippmann on 2015-05-21 12:10:03 +00:00
Applied in changeset 47f21ee. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8241
Created by vaisov on 2015-01-16 09:58:40 +00:00
Assignee: elippmann
Status: Resolved (closed on 2015-05-21 12:10:03 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-05-21 12:10:03 +00:00 (in Redmine)
Changesets
2015-05-19 12:01:18 +00:00 by aklimov 85dd496
2015-05-19 12:04:23 +00:00 by aklimov a2b262e
2015-05-19 12:05:33 +00:00 by aklimov 75b004d
2015-05-19 15:36:23 +00:00 by aklimov 3243f9a
2015-05-19 15:36:23 +00:00 by aklimov 36713fb
2015-05-19 15:36:24 +00:00 by aklimov cc050ed
2015-05-19 15:36:24 +00:00 by aklimov 2ed1d6c
2015-05-19 16:17:40 +00:00 by aklimov 6ba07b0
2015-05-19 16:17:40 +00:00 by aklimov 93db1d1
2015-05-19 16:17:41 +00:00 by aklimov 0b937c8
2015-05-20 08:43:54 +00:00 by aklimov 9b4f08e
2015-05-20 13:29:45 +00:00 by elippmann 2493535
2015-05-20 13:50:06 +00:00 by elippmann 41e7239
2015-05-20 13:50:13 +00:00 by elippmann 5efbad3
2015-05-20 13:50:19 +00:00 by elippmann d379b27
2015-05-20 14:07:49 +00:00 by elippmann 2dc6d54
2015-05-20 14:09:30 +00:00 by elippmann a9d6a94
2015-05-20 14:15:38 +00:00 by elippmann f9952cf
2015-05-20 14:16:21 +00:00 by elippmann 80b174f
2015-05-20 15:03:23 +00:00 by elippmann cfb819e
2015-05-21 09:19:58 +00:00 by elippmann ce463d1
2015-05-21 09:23:55 +00:00 by elippmann bbed2cf
2015-05-21 09:24:31 +00:00 by elippmann 37abc72
2015-05-21 09:26:10 +00:00 by elippmann a52264a
2015-05-21 10:26:27 +00:00 by elippmann 58b3192
2015-05-21 10:36:05 +00:00 by elippmann 4b9f7eb
2015-05-21 10:37:53 +00:00 by elippmann 73eb8cc
2015-05-21 10:38:20 +00:00 by elippmann 89bac33
2015-05-21 10:38:58 +00:00 by elippmann e7396ea
2015-05-21 10:41:29 +00:00 by elippmann 1a1f93d
2015-05-21 10:41:59 +00:00 by elippmann 0db7cfc
2015-05-21 10:42:53 +00:00 by elippmann e0c6ce5
2015-05-21 10:43:27 +00:00 by elippmann ad5ab16
2015-05-21 10:46:47 +00:00 by elippmann 0c72686
2015-05-21 11:58:54 +00:00 by elippmann 57328aa
2015-05-21 12:04:04 +00:00 by elippmann c47465a
2015-05-21 12:05:49 +00:00 by elippmann 47f21ee
Relations:
The text was updated successfully, but these errors were encountered: