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 #7185] Stats grouping by columns in Livestatus missing #1970
Comments
Updated by mfriedrich on 2014-09-16 09:14:51 +00:00
|
Updated by mfriedrich on 2015-02-16 14:13:22 +00:00 That's reproducible though I currently have no idea how to fix the aggregator to deal with these column combinations. in livestatusquery.cpp:530 else tree
|
Updated by mfriedrich on 2015-02-16 14:14:26 +00:00
|
Updated by LaMi on 2015-04-28 15:25:23 +00:00 Wanted to push this issue. In my opinion this is not just a missing feature, because it breaks NagVis or at least makes NagVis showing wrong information. NagVis makes use of these kind of queries to keep the number of queries low. They are used to get the summary state of multiple hosts and their services at once. For users which use NagVis this may be a show stopper. Some example query used by NagVis:
|
Updated by dnotivol on 2015-04-29 11:22:27 +00:00
I'm having the same problem with livestatus. When running the Nagvis queries, I get different results in livestatus for icinga1 and icinga2. I guess this will psotpone my migration to icinga2 (although I have everything set up, and I'm really wanting to use all the new features in production). This is making Nagvis response is unpredictable because it shows random number of services in each host. The output in icinga1's livestatus:
The output in icinga2's livestatus:
I'm attaching the query launched by NagVis (I think it's the same one than the one LaMi's posted). |
Updated by mfriedrich on 2015-05-08 16:31:00 +00:00
|
Updated by mfriedrich on 2015-06-23 13:26:15 +00:00
|
Updated by mfriedrich on 2016-01-29 14:46:30 +00:00
I currently neither have the time nor resources to look into Livestatus specific stuff involving multiple days of development. If anyone else is capable of sending in a patch, I'll gladly review and merge it. |
Updated by mfriedrich on 2016-02-03 17:07:19 +00:00 The problem is located in this section:
One would need to
|
Updated by mfriedrich on 2016-03-18 14:56:56 +00:00
|
Updated by gbeutner on 2016-03-29 07:01:13 +00:00
|
Updated by byb39 on 2016-07-21 01:51:42 +00:00 Hi, I am using Nagvis 1.9b8 with Icinga 2.3.3 and this issue seems to be resolved when using IDO as a backend. It may be the same for livestatus. I was getting the same issue with random hosts/services when using Nagvis 1.85 stable. Best Regards, |
Updated by mfriedrich on 2016-07-21 06:18:18 +00:00 DB IDO uses a different Nagvis code to fetch the data. One thing which recently changed there - I've sent them a patch fixing inactive db objects. That should make the IDO backend the preferred one in combination with Icinga and Icinga Web 2. Nonetheless the Livestatus bug still exists, and isn't easy to tackle. |
Updated by velin on 2016-09-08 07:55:07 +00:00
Hi, I'm using icinga (and icingaweb2) with postgresql. Nagvis seems to support only mysql db ido and livestatus, so this bug is quite important for environments, where postgresql is used. |
Updated by mfriedrich on 2016-12-07 22:01:33 +00:00
To be honest, I will not fix it and so does no-one else. Livestatus isn't our primary protocol inside the Icinga stack, neither is Compat for instance. I'm closing this - unfortunately - as wontfix. If you really want NagVis to work with Icinga 2/Icinga Web 2, wrap your head around either writing an Icinga 2 or Icinga Web 2 API backend. Or extend the MySQL backend for PostgreSQL usage and contribute upstream. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7185
Created by tgelf on 2014-09-11 08:00:21 +00:00
Assignee: (none)
Status: Closed (closed on 2016-12-07 22:01:33 +00:00)
Target Version: (none)
Last Update: 2016-12-07 22:01:33 +00:00 (in Redmine)
Test query:
Expected result:
Got:
This is the related livestatus documentation snippet about Grouping
Cheers,
Thomas
Attachments
Relations:
The text was updated successfully, but these errors were encountered: