Skip to content
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 #2762] Implement livestatus component #163

Closed
icinga-migration opened this issue Jun 30, 2012 · 18 comments
Closed

[dev.icinga.com #2762] Implement livestatus component #163

icinga-migration opened this issue Jun 30, 2012 · 18 comments
Labels
area/livestatus Legacy interface enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2762

Created by gbeutner on 2012-06-30 14:22:06 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2013-11-06 15:39:49 +00:00)
Target Version: 0.0.4
Last Update: 2014-09-16 09:14:30 +00:00 (in Redmine)


This might be useful if we want to support other UIs like Thruk.

Changesets

2013-07-29 09:18:41 +00:00 by (unknown) 5167626

livestatus: rename address to host (same as ido)

refs #2762

2013-07-30 11:07:13 +00:00 by (unknown) 603ceb9

livestatus: import test queries and script

refs #2762

2013-11-07 16:29:45 +00:00 by (unknown) 7d28e95

Livestatus: Add servive_checks(_rate) columns to status table.

Refs #4655
Refs #2762

Relations:

@icinga-migration
Copy link
Author

Updated by gbeutner on 2012-07-26 09:57:25 +00:00

  • Target Version changed from Milestone 2 to 87

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-09-01 11:07:34 +00:00

  • Subject changed from CIB: Implement livestatus support to Compat/CIB: Implement livestatus support

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-09-07 09:57:35 +00:00

  • Subject changed from Compat/CIB: Implement livestatus support to Compat: Implement livestatus support

https://wiki.icinga.org/display/icinga2/Livestatus

@icinga-migration
Copy link
Author

Updated by gbeutner on 2013-05-14 08:03:10 +00:00

  • Target Version changed from 87 to 119

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-07-05 20:02:34 +00:00

  • Subject changed from Compat: Implement livestatus support to Implement livestatus component
  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Priority changed from Low to Normal

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-07-29 12:17:21 +00:00

  • Target Version changed from 119 to 138
  • Done % changed from 0 to 50

moving main issue to next milestone (history). config and status queries are working, based on that list: https://wiki.icinga.org/display/icinga2/Livestatus#Livestatus-Attributes (primary tests with thruk)

@icinga-migration
Copy link
Author

Updated by chaen on 2013-08-28 16:48:40 +00:00

Hi,

I guess this is the proper place to ask about the current status of the livestatus component? :-) If not, apologies!

I wrote a benchmarking tool (reusing part of what Sven did for its tests) that makes use of the livestatus API. Unfortunately, some of the most important info (like the service_checks for example) are missing, as reported on the link you give above. I was wondering if you had the slightest idea when they will be implemented?

In any case, it all looks extremely promising and I am looking forward to test it further! Congrats! :-)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-08-28 17:07:24 +00:00

If you mean the historical tables, those are postponed until there's a solution found for the historical backend (as well as the events triggering historical stuff).

the config and status tables are working so far. so in terms of querying a service for its current state and check output, you'll get your results.

@icinga-migration
Copy link
Author

Updated by chaen on 2013-08-29 06:47:18 +00:00

No I mean the status table which is half empty as of now (https://wiki.icinga.org/display/icinga2/Livestatus#Livestatus-StatusTable)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-08-29 08:11:14 +00:00

that's livestatus specific stuff intercepting the callbacks for servicechecksin icinga 1.x.
since they do not exist in icinga2 (checks will be delegated and executed in a different manner) those counters remain useless (or will be 0 if the current master does not execute any checks if we would find an event "service has been checked" to count for).

generally speaking, all options have been evaluated if they make sense in the icinga2 architecture. those with an (x) are currently not supported.

though, retrieving such statistics might be necessary in the future, but is handled in a different issue #3598

@icinga-migration
Copy link
Author

Updated by chaen on 2013-08-29 08:19:32 +00:00

oops, indeed, this other ticket might have been more appropriate to post, sorry.

In any case, if I can give my opinion as a lambda user (and even if I have a good idea of how complicated this is for the implementation :-) ), it would be cool to be able to get global statistics easily (in addition to the per-instance one).

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-08-29 08:22:24 +00:00

#4655

@icinga-migration
Copy link
Author

Updated by chaen on 2013-08-29 08:24:24 +00:00

Thanks! :-)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-09-23 10:26:14 +00:00

  • Project changed from Icinga 2 to 34
  • Target Version changed from 138 to 0.0.4

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-10-22 09:02:55 +00:00

  • Target Version deleted 0.0.4

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-10-22 09:09:21 +00:00

  • Target Version set to 0.0.4

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-11-06 15:39:50 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 50 to 100
  • Estimated Hours set to 300

all tables, filters, stats aggregators have been implemented so far. some bugs and additional columns may be fixed/added in future issues.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-09-16 09:14:30 +00:00

  • Category set to Livestatus
  • Project changed from 34 to Icinga 2

@icinga-migration icinga-migration added enhancement New feature or request area/livestatus Legacy interface labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 0.0.4 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/livestatus Legacy interface enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant