Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #3838] add initial status data for the IDO database #1236

Closed
icinga-migration opened this issue Mar 12, 2013 · 8 comments
Closed
Milestone

Comments

@icinga-migration
Copy link

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

Created by mfrosch on 2013-03-12 09:04:28 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2013-10-02 22:05:35 +00:00)
Target Version: 1.10
Last Update: 2014-12-08 14:38:04 +00:00 (in Redmine)

Icinga Version: 1.10.0
OS Version: any

Currently a service- or hoststatus is only inserted into the database when:

  • reading retention data
  • a service check event occurs

The idea is to end the config dump with a query that inserts every none existing status row into the database, with a query like:

INSERT INTO icinga_servicestatus (SELECT () FROM icinga_services LEFT JOIN icinga_servicestatus ON <...> WHERE ss.servicestatus_id IS NULL)

Of course this requires massive testing, but theoretically it should work with every RDBMS and should be quite fast.

Attachments

Changesets

2013-10-02 22:04:56 +00:00 by (unknown) 3c3b635

core: dump host/service initial states on event loop initialization again

fixes #3838

Signed-off-by: Michael Friedrich <Michael.Friedrich@netways.de>

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-03-13 23:19:12 +00:00

  • Subject changed from Introduce initial status data for the IDO database to add initial status data for the IDO database

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-04-06 21:57:53 +00:00

  • Target Version changed from 1.9 to 1.10

requires further investigation, rescheduling due to feature freeze.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-09-14 17:32:03 +00:00

  • Status changed from Assigned to Feedback

status?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-09-29 15:02:55 +00:00

a more generic approach would be a call to the status update queries after config dump although this would decrease the config dump performance afterall.

modify

  • current_state=4
  • has_been_checked=0
  • state_type=1

and pass the other attributes onto data[] and ido2db_query_insert_or_update_servicestatusdata_add() and ido2db_query_insert_or_update_hoststatusdata_add()

though i do fear the performance impact here.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-10-02 14:56:37 +00:00

  • File added 0001-patch.patch
  • Status changed from Feedback to Assigned
  • Assigned to changed from mfrosch to mfriedrich
  • restore core init_timing_loop() update_{host,service}_status() calls
  • disable retention data status_{host,service}_update()
  • change config option dump_....
  • add to changed configs, changelog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-10-02 22:01:45 +00:00

  • Tracker changed from Feature to Bug
  • Icinga Version set to 1
  • (unknown custom field) set to 1
  • (unknown custom field) set to MySQL
  • (unknown custom field) set to ---

@icinga-migration
Copy link
Author

Updated by Anonymous on 2013-10-02 22:05:35 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset icinga-core:3c3b635603936a683e9706769f79c1401c80f473.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-12-08 14:38:04 +00:00

  • Project changed from 18 to Core, Classic UI, IDOUtils
  • Category changed from 103 to IDOUtils
  • Icinga Version changed from 1 to 1
  • OS Version set to any

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant