-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- NagiosQL -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- (c) 2005-2018 by Martin Willisegger -- -- Project : NagiosQL -- Component : Complete NagiosQL Database -- Website : https://sourceforge.net/projects/nagiosql/ -- Version : 3.4.0 -- GIT Repo : https://gitlab.com/wizonet/NagiosQL -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO"; SET NAMES 'utf8'; -- -- Structure for table `tbl_command` -- CREATE TABLE IF NOT EXISTS `tbl_command` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `command_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `command_line` text COLLATE utf8_unicode_ci NOT NULL, `command_type` tinyint(3) unsigned NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(10) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`command_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_command` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_configtarget` -- CREATE TABLE `tbl_configtarget` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `target` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `server` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `method` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `user` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `password` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `ssh_key_path` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `ftp_secure` tinyint(3) UNSIGNED NOT NULL DEFAULT '0', `basedir` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `hostconfig` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `serviceconfig` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `backupdir` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `hostbackup` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `servicebackup` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `nagiosbasedir` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `importdir` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `picturedir` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `commandfile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `binaryfile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `pidfile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `conffile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `cgifile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `resourcefile` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `version` tinyint(3) UNSIGNED NOT NULL DEFAULT '3', `access_group` int(10) UNSIGNED NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `nodelete` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `last_modified` datetime NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `target` (`target`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_configtarget` -- INSERT INTO `tbl_configtarget` (`id`, `target`, `alias`, `server`, `method`, `user`, `password`, `ssh_key_path`, `ftp_secure`, `basedir`, `hostconfig`, `serviceconfig`, `backupdir`, `hostbackup`, `servicebackup`, `nagiosbasedir`, `importdir`, `picturedir`, `commandfile`, `binaryfile`, `pidfile`, `conffile`, `cgifile`, `resourcefile`, `version`, `access_group`, `active`, `nodelete`, `last_modified`) VALUES (1, 'localhost', 'Local installation', 'localhost', '1', '', '', '', 0, '/etc/nagiosql/', '/etc/nagiosql/hosts/', '/etc/nagiosql/services/', '/etc/nagiosql/backup/', '/etc/nagiosql/backup/hosts/', '/etc/nagiosql/backup/services/', '/etc/nagios/', '/opt/nagios/etc/objects/', '', '/var/nagios/rw/nagios.cmd', '/opt/nagios/bin/nagios', '/var/nagios/nagios.lock', '/etc/nagios/nagios.cfg', '/etc/nagios/cgi.cfg', '/etc/nagios/resource.cfg', 3, 0, '1', '1', NOW()); -- -------------------------------------------------------- -- -- Structure for table `tbl_contact` -- CREATE TABLE IF NOT EXISTS `tbl_contact` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `contact_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `contactgroups` int(10) unsigned NOT NULL DEFAULT '0', `contactgroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `minimum_importance` int(11) DEFAULT NULL, `host_notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `host_notification_period` int(10) unsigned NOT NULL DEFAULT '0', `service_notification_period` int(10) unsigned NOT NULL DEFAULT '0', `host_notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `service_notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `host_notification_commands` int(10) unsigned NOT NULL DEFAULT '0', `host_notification_commands_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_notification_commands` int(10) unsigned NOT NULL DEFAULT '0', `service_notification_commands_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `can_submit_commands` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `pager` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address1` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address2` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address3` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address4` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address5` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address6` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(10) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`contact_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_contact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_contactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_contactgroup` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `contactgroup_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `members` int(10) unsigned NOT NULL DEFAULT '0', `contactgroup_members` int(10) unsigned NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(10) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`contactgroup_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_contactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_contacttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_contacttemplate` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `template_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `contactgroups` int(10) unsigned NOT NULL DEFAULT '0', `contactgroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `minimum_importance` int(11) DEFAULT NULL, `host_notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `host_notification_period` int(11) NOT NULL DEFAULT '0', `service_notification_period` int(11) NOT NULL DEFAULT '0', `host_notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `service_notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `host_notification_commands` int(10) unsigned NOT NULL DEFAULT '0', `host_notification_commands_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_notification_commands` int(10) unsigned NOT NULL DEFAULT '0', `service_notification_commands_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `can_submit_commands` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `pager` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address1` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address2` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address3` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address4` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address5` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address6` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(10) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`template_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_contacttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_datadomain` -- CREATE TABLE IF NOT EXISTS `tbl_datadomain` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `domain` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `targets` int(10) unsigned NOT NULL, `version` tinyint(3) unsigned NOT NULL DEFAULT '3', `enable_common` tinyint(3) unsigned NOT NULL DEFAULT '0', `utf8_decode` tinyint(3) unsigned NOT NULL DEFAULT '0', `access_group` int(10) unsigned NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `nodelete` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `last_modified` datetime NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `domain` (`domain`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_datadomain` -- INSERT INTO `tbl_datadomain` (`id`, `domain`, `alias`, `targets`, `version`, `enable_common`, `utf8_decode`, `access_group`, `active`, `nodelete`, `last_modified`) VALUES(0, 'common', 'Global common domain', 0, 3, 0, 0, 0, '1', '1', NOW()); UPDATE `tbl_datadomain` SET `id` = '0' WHERE `domain` = 'common'; ALTER TABLE `tbl_datadomain` AUTO_INCREMENT = 1; INSERT INTO `tbl_datadomain` (`id`, `domain`, `alias`, `targets`, `version`, `enable_common`, `utf8_decode`, `access_group`, `active`, `nodelete`, `last_modified`) VALUES(1, 'localhost', 'Local installation', 1, 3, 1, 0, 0, '1', '1', NOW()); -- -------------------------------------------------------- -- -- Structure for table `tbl_group` -- CREATE TABLE IF NOT EXISTS `tbl_group` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `groupname` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `description` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `users` tinyint(3) unsigned NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_group` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_host` -- CREATE TABLE IF NOT EXISTS `tbl_host` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `host_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `display_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `address` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `parents` tinyint(3) unsigned NOT NULL DEFAULT '0', `parents_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `importance` int(11) DEFAULT NULL, `hostgroups` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_command` text COLLATE utf8_unicode_ci NOT NULL, `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `initial_state` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `max_check_attempts` int(11) DEFAULT NULL, `check_interval` int(11) DEFAULT NULL, `retry_interval` int(11) DEFAULT NULL, `active_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `passive_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_period` int(11) NOT NULL DEFAULT '0', `obsess_over_host` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_freshness` tinyint(3) unsigned NOT NULL DEFAULT '2', `freshness_threshold` int(11) DEFAULT NULL, `event_handler` int(11) NOT NULL DEFAULT '0', `event_handler_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `low_flap_threshold` int(11) DEFAULT NULL, `high_flap_threshold` int(11) DEFAULT NULL, `flap_detection_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `flap_detection_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `process_perf_data` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `notification_interval` int(11) DEFAULT NULL, `notification_period` int(11) NOT NULL DEFAULT '0', `first_notification_delay` int(11) DEFAULT NULL, `notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `stalking_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `vrml_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `statusmap_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `2d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `3d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(10) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`host_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_host` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_hostdependency` -- CREATE TABLE IF NOT EXISTS `tbl_hostdependency` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `config_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `dependent_host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `dependent_hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `inherits_parent` tinyint(3) unsigned NOT NULL DEFAULT '0', `execution_failure_criteria` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notification_failure_criteria` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `dependency_period` int(11) NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`config_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_hostdependency` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_hostescalation` -- CREATE TABLE IF NOT EXISTS `tbl_hostescalation` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `config_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `first_notification` int(11) DEFAULT NULL, `last_notification` int(11) DEFAULT NULL, `notification_interval` int(11) DEFAULT NULL, `escalation_period` int(11) NOT NULL DEFAULT '0', `escalation_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`config_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_hostescalation` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_hostextinfo` -- CREATE TABLE IF NOT EXISTS `tbl_hostextinfo` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `host_name` int(11) NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `statistik_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `vrml_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `statusmap_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `2d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `3d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`host_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_hostextinfo` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_hostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_hostgroup` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `hostgroup_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `members` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_members` tinyint(3) unsigned NOT NULL DEFAULT '0', `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`hostgroup_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_hostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_hosttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_hosttemplate` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `template_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `parents` tinyint(3) unsigned NOT NULL DEFAULT '0', `parents_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `importance` int(11) DEFAULT NULL, `hostgroups` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_command` text COLLATE utf8_unicode_ci NOT NULL, `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `initial_state` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `max_check_attempts` int(11) DEFAULT NULL, `check_interval` int(11) DEFAULT NULL, `retry_interval` int(11) DEFAULT NULL, `active_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `passive_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_period` int(11) NOT NULL DEFAULT '0', `obsess_over_host` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_freshness` tinyint(3) unsigned NOT NULL DEFAULT '2', `freshness_threshold` int(11) DEFAULT NULL, `event_handler` int(11) NOT NULL DEFAULT '0', `event_handler_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `low_flap_threshold` int(11) DEFAULT NULL, `high_flap_threshold` int(11) DEFAULT NULL, `flap_detection_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `flap_detection_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `process_perf_data` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `notification_interval` int(11) DEFAULT NULL, `notification_period` int(11) NOT NULL DEFAULT '0', `first_notification_delay` int(11) DEFAULT NULL, `notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `stalking_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `vrml_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `statusmap_image` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `2d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `3d_coords` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`template_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_hosttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_info` -- CREATE TABLE IF NOT EXISTS `tbl_info` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `key1` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `key2` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `version` varchar(50) COLLATE utf8_unicode_ci NOT NULL, `language` varchar(50) COLLATE utf8_unicode_ci NOT NULL, `infotext` text COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), KEY `keypair` (`key1`,`key2`,`version`,`language`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_info` -- INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(1, 'domain', 'domain', 'all', 'default', 'Common name of this domain. This field is for internal use only.'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(2, 'domain', 'basedir', 'all', 'default', '

Absolute path to your NagiosQL configuration directory.

Examples:
/etc/nagiosql/
/usr/local/nagiosql/etc/

Be sure, that your configuration path settings are matching with your nagios.cfg! (cfg_file=/etc/nagiosql/timeperiods.cfg)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(3, 'domain', 'hostdir', 'all', 'default', 'NagiosQL writes one configuration file for every host. It is useful to store this files inside an own subdirectory below your Nagios configuration path.

Examples:
/etc/nagios/hosts
/usr/local/nagios/etc/hosts

Be sure, that your configuration settings are matching with your nagios.cfg!
(cfg_dir=/etc/nagios/hosts)'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(4, 'domain', 'servicedir', 'all', 'default', 'NagiosQL writes services grouped into files identified by the service configuration names. It is useful to store this files inside an own subdirectory below your Nagios configuration path.

Examples:
/etc/nagios/services
/usr/local/nagios/etc/services

Be sure, that your configuration settings are matching with your nagios.cfg!
(cfg_dir=/etc/nagios/services)'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(5, 'domain', 'backupdir', 'all', 'default', 'Absolute path to your NagiosQL configuration backup directory.

Examples:
/etc/nagios/backup
/usr/local/nagios/etc/backup

This directory is for internal configuration backups of NagiosQL and is not used by Nagios itself. '); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(6, 'domain', 'backuphostdir', 'all', 'default', 'Absolute path to your NagiosQL host configuration backup directory.

Examples:
/etc/nagios/backup/hosts
/usr/local/nagios/etc/backup/hosts

This directory is for internal configuration backups of NagiosQL only and is not used by Nagios itself.'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(7, 'domain', 'backupservicedir', 'all', 'default', 'Absolute path to your NagiosQL service configuration backup directory.

Examples:
/etc/nagios/backup/services
/usr/local/nagios/etc/backup/services

This directory is for internal configuration backups of NagiosQL only and is not used by Nagios itself.'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(8, 'domain', 'commandfile', 'all', 'default', 'Absolute path to your Nagios command file.

Examples:
/var/spool/nagios/nagios.cmd
/usr/local/nagios/var/rw/nagios.cmd

Be sure, that your command file path settings are matching with your nagios.cfg! (command_file=/var/spool/nagios/nagios.cmd)
(check_external_commands=1)

\r\nThis is used to reload Nagios directly from NagiosQL after changing a configuration.'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(9, 'common', 'accesskeys', 'all', 'default', '

Access key/keyholes

\r\n

NagiosQL uses a very simplified access control mechanism by using up to 8 keys.

\r\n

To access a secure object (menu, domain), a user must have a key for every defined keyhole.

\r\n

Example:

\r\n

User A has key 1,2,5,7 (can be defined in user management)
User B has key 3,5,7,8 (can be defined in user management)

\r\n

Menu 1 has keyhole 3,5
Menu 2 has keyhole 2,5,7
Menu 3 has no keyhole
Menu 4 has keyhole 4

User A has access to menu 2 and menu 3 (key 3 for menu 1 and key 4 for menu 4 are missing)
User B has access to menu 1 and menu 3 (key 2 for menu 2 and key 4 for menu 4 are missing)

\r\n

 

\r\n

 

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(10, 'user', 'webserverauth', 'all', 'default', '

User - webserver authentification

\r\n

If your webserver uses authentification and the NagiosQL user name is the same which is actually logged in - the NagiosQL login process will passed. This means, that NagiosQL no longer shows a login page if this user is already logged in by webserver authentification.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(11, 'domain', 'nagiosbasedir', 'all', 'default', '

Absolute path to your Nagios configuration directory.

Examples:
/etc/nagios/
/usr/local/nagios/etc/

\r\n

Be sure, that your nagios.cfg and cfg.cfg ist located inside this directory. NagiosQL uses this to handle this two files.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(12, 'domain', 'importdir', 'all', 'default', '

Absolute path to your configuration import directory.

Examples:
/etc/nagiosql/import/
/usr/local/nagios/etc/import/

\r\n

You can use this directory to store old or example configuration files in it which should be accessable by the importer of NagiosQL.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(13, 'domain', 'binary', 'all', 'default', '

Absolute path to your Nagios binary file.

Examples:
/usr/bin/nagios
/usr/local/nagios/bin/nagios

This is used to verify your configuration.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(14, 'domain', 'pidfile', 'all', 'default', '

Absolute path to your Nagios process file.

Examples:
/var/run/nagios/nagios.pid
/var/run/nagios/nagios.lock

This is used to check if nagios is running before sending a reload command to the nagios command file.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(15, 'domain', 'version', 'all', 'default', '

The nagios version which is running in this domain.

\r\n

Be sure you select the correct version here - otherwise not all configuration options are available or not supported options are shown.

\r\n

You can change this with a running configuration - NagiosQL will then upgrade or downgrade your configuration. Don\'t forget to write your complete configuration after a version change!

\r\n

Difference between version in data domain and configuration domain:

\r\n\r\n

This way you can create your data in a newer Nagios version and still write in an older version to keep the configuration compatible to the running Nagios version.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(16, 'host', 'hostname', 'all', 'default', '

Host - host name

This directive is used to define a short name used to identify the host. It is used in host group and service definitions to reference this particular host. Hosts can have multiple services (which are monitored) associated with them. When used properly, the $HOSTNAME$ macro will contain this short name.

\r\n

Parameter name: host_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(17, 'host', 'alias', 'all', 'default', '

Host - alias

This directive is used to define a longer name or description used to identify the host. It is provided in order to allow you to more easily identify a particular host. When used properly, the $HOSTALIAS$ macro will contain this alias/description.

\r\n

Parameter name: alias
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(18, 'host', 'address', 'all', 'default', '

Host - address

\r\n

This directive is used to define the address of the host. Normally, this is an IP address, although it could really be anything you want (so long as it can be used to check the status of the host). You can use a FQDN to identify the host instead of an IP address, but if DNS services are not availble this could cause problems. When used properly, the $HOSTADDRESS$ macro will contain this address.

\r\n

Note: If you do not specify an address directive in a host definition, the name of the host will be used as its address. A word of caution about doing this, however - if DNS fails, most of your service checks will fail because the plugins will be unable to resolve the host name.

\r\n

Parameter name: address
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(19, 'host', 'display_name', 'all', 'default', '

Host - display name

\r\n

This directive is used to define an alternate name that should be displayed in the web interface for this host. If not specified, this defaults to the value you specify for the host_name directive.

\r\n

Note: The current CGIs do not use this option, although future versions of the web interface will.

\r\n

Parameter name: display_name
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(20, 'host', 'parents', 'all', 'default', '

Host - parents

\r\n

This directive is used to define a comma-delimited list of short names of the "parent" hosts for this particular host. Parent hosts are typically routers, switches, firewalls, etc. that lie between the monitoring host and a remote hosts. A router, switch, etc. which is closest to the remote host is considered to be that host''s "parent". Read the "Determining Status and Reachability of Network Hosts" document for more information.

\r\n

If this host is on the same network segment as the host doing the monitoring (without any intermediate routers, etc.) the host is considered to be on the local network and will not have a parent host. Leave this value blank if the host does not have a parent host (i.e. it is on the same segment as the Nagios host). The order in which you specify parent hosts has no effect on how things are monitored.

\r\n

Parameter name: parents
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(21, 'host', 'hostgroups', 'all', 'default', '

Host - hostgroup names

\r\n

This directive is used to identify the short name(s) of the hostgroup(s) that the host belongs to. Multiple hostgroups should be separated by commas. This directive may be used as an alternative to (or in addition to) using the members directive in hostgroup definitions.

\r\n

NagiosQL: If a hostgroup is defined here - this host will not be selected inside the member field of the same hostgroup definition!

\r\n

Parameter name: hostgroups
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(22, 'common', 'tploptions', '3', 'default', '

Cancelling Inheritance of String Values

\r\n

In some cases you may not want your host, service, or contact definitions to inherit values of string variables from the templates they reference. If this is the case, you can specify "null" as the value of the variable that you do not want to inherit.

\r\n


Additive Inheritance of String Values

\r\n

Nagios gives preference to local variables instead of values inherited from templates. In most cases local variable values override those that are defined in templates. In some cases it makes sense to allow Nagios to use the values of inherited and local variables together.

\r\n

This "additive inheritance" can be accomplished by prepending the local variable value with a plus sign (+). This features is only available for standard (non-custom) variables that contain string values.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(23, 'host', 'check_command', 'all', 'default', '

Host - check command

This directive is used to specify the short name of the command that should be used to check if the host is up or down. Typically, this command would try and ping the host to see if it is "alive". The command must return a status of OK (0) or Nagios will assume the host is down.

\r\n

If you leave this argument blank, the host will not be actively checked. Thus, Nagios will likely always assume the host is up (it may show up as being in a "PENDING" state in the web interface). This is useful if you are monitoring printers or other devices that are frequently turned off. The maximum amount of time that the notification command can run is controlled by the host_check_timeout option.

\r\n

Parameter name: check_command
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(24, 'host', 'arguments', 'all', 'default', '

Host - arguments

\r\n

The values defined here will replace the according argument variable behind the selected command. Up to 8 argument variables are supported. Be sure, that you defines a valid value for each required argument variable.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(25, 'host', 'templateadd', 'all', 'default', '

Host - Templates

\r\n

You can add one or more host templates to a host configuration. Nagios will add the definitions from each template to a host configuration.

\r\n

If you add more than one template - the sort order will be used to overwrite configuration items which are defined inside templates before.

\r\n

The host configuration itselves will overwrite all values which are defined in templates before and pass all values which are not defined.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(26, 'host', 'initial_state', '3', 'default', '

Host - initial state

\r\n

By default Nagios will assume that all hosts are in UP states when in starts. You can override the initial state for a host by using this directive. Valid options are:
o
= UP,
d = DOWN, and
u = UNREACHABLE.

\r\n

Parameter name: initial_state
Required:
no

\r\n

 

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(27, 'host', 'retry_interval', '3', 'default', '

Host - retry interval

\r\n

This directive is used to define the number of "time units" to wait before scheduling a re-check of the hosts. Hosts are rescheduled at the retry interval when they have changed to a non-UP state. Once the host has been retried max_check_attempts times without a change in its status, it will revert to being scheduled at its "normal" rate as defined by the check_interval value. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.

\r\n

Parameter name: retry_interval
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(28, 'host', 'max_check_attempts', 'all', 'default', '

Host - max check attempts

\r\n

This directive is used to define the number of times that Nagios will retry the host check command if it returns any state other than an OK state. Setting this value to 1 will cause Nagios to generate an alert without retrying the host check again. Note: If you do not want to check the status of the host, you must still set this to a minimum value of 1. To bypass the host check, just leave the check_command option blank.

\r\n

Parameter name: max_check_attempts
Required:
yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(29, 'host', 'check_interval', 'all', 'default', '

Host - check interval

\r\n

This directive is used to define the number of "time units" between regularly scheduled checks of the host. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.

\r\n

Parameter name: check_interval
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(30, 'host', 'active_checks_enabled', 'all', 'default', '

Host - active checks enabled

\r\n

This directive is used to determine whether or not active checks (either regularly scheduled or on-demand) of this host are enabled. Values: 0 = disable active host checks, 1 = enable active host checks.

\r\n

Parameter name: active_checks_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(31, 'host', 'passive_checks_enabled', 'all', 'default', '

Host - passive checks enabled

\r\n

This directive is used to determine whether or not passive checks are enabled for this host. Values: 0 = disable passive host checks, 1 = enable passive host checks.

\r\n

Parameter name: passive_checks_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(32, 'host', 'check_period', 'all', 'default', '

Host - check period

\r\n

This directive is used to specify the short name of the time period during which active checks of this host can be made.

\r\n

Parameter name: check_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(33, 'host', 'freshness_threshold', 'all', 'default', '

Host - freshness threshold

\r\n

This directive is used to specify the freshness threshold (in seconds) for this host. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.

\r\n

Parameter name: freshness_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(34, 'host', 'check_freshness', 'all', 'default', '

Host - check freshness

\r\n

This directive is used to determine whether or not freshness checks are enabled for this host. Values: 0 = disable freshness checks, 1 = enable freshness checks.

\r\n

Parameter name: check_freshness
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(35, 'host', 'obsess_over_host', 'all', 'default', '

Host - obsess over host

\r\n

This directive determines whether or not checks for the host will be "obsessed" over using the ochp_command.

\r\n

Parameter name: obsess_over_host
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(36, 'host', 'event_handler', 'all', 'default', '

Host - event handler

\r\n

This directive is used to specify the short name of the command that should be run whenever a change in the state of the host is detected (i.e. whenever it goes down or recovers). Read the documentation on event handlers for a more detailed explanation of how to write scripts for handling events. The maximum amount of time that the event handler command can run is controlled by the event_handler_timeout option.

\r\n

Parameter name: event_handler
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(37, 'host', 'event_handler_enabled', 'all', 'default', '

Host - event handler enabled

\r\n

This directive is used to determine whether or not the event handler for this host is enabled. Values: 0 = disable host event handler, 1 = enable host event handler.

\r\n

Parameter name: event_handler_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(38, 'host', 'low_flap_threshold', 'all', 'default', '

Host - low flap threshold

\r\n

This directive is used to specify the low state change threshold used in flap detection for this host. If you set this directive to a value of 0, the program-wide value specified by the low_host_flap_threshold directive will be used.

\r\n

Parameter name: low_flap_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(39, 'host', 'high_flap_threshold', 'all', 'default', '

Host - high flap threshold

\r\n

This directive is used to specify the high state change threshold used in flap detection for this host. If you set this directive to a value of 0, the program-wide value specified by the high_host_flap_threshold directive will be used.

\r\n

Parameter name: high_flap_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(40, 'host', 'flap_detection_enabled', 'all', 'default', '

Host - flap detection enabled

\r\n

This directive is used to determine whether or not flap detection is enabled for this host. Values: 0 = disable host flap detection, 1 = enable host flap detection.

\r\n

Parameter name: flap_detection_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(41, 'host', 'flap_detection_options', '3', 'default', '

Host - flap detection options

\r\n

This directive is used to determine what host states the flap detection logic will use for this host. Valid options are a combination of one or more of the following:
o
= UP states,
d = DOWN states,
u = UNREACHABLE states.

\r\n

Parameter name: flap_detection_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(42, 'host', 'retain_status_information', 'all', 'default', '

Host - retain status information

\r\n

This directive is used to determine whether or not status-related information about the host is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable status information retention, 1 = enable status information retention.

\r\n

Parameter name: retain_status_information
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(43, 'host', 'retain_nonstatus_information', 'all', 'default', '

Host - retain nonstatus information

\r\n

This directive is used to determine whether or not non-status information about the host is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable non-status information retention, 1 = enable non-status information retention.

\r\n

Parameter name: retain_nonstatus_information
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(45, 'host', 'contacts', '3', 'default', '

Host - contacts

\r\n

This is a list of the short names of the contacts that should be notified whenever there are problems (or recoveries) with this host. Multiple contacts should be separated by commas. Useful if you want notifications to go to just a few people and don''t want to configure contact groups. You must specify at least one contact or contact group in each host definition.

\r\n

Parameter name: contacs
Required:
yes (at least one contact or contact group)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(46, 'host', 'contactgroups', 'all', 'default', '

Host - contact groups

\r\n

This is a list of the short names of the contact groups that should be notified whenever there are problems (or recoveries) with this host. Multiple contact groups should be separated by commas. You must specify at least one contact or contact group in each host definition.

\r\n

Parameter name: contact_groups
Required: yes (at least one contact or contact group)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(47, 'host', 'notification_period', 'all', 'default', '

Host - notification period

\r\n

This directive is used to specify the short name of the time period during which notifications of events for this host can be sent out to contacts. If a host goes down, becomes unreachable, or recoveries during a time which is not covered by the time period, no notifications will be sent out.

\r\n

Parameter name: notification_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(48, 'host', 'notification_options', 'all', 'default', '

Host - notification options

\r\n

This directive is used to determine when notifications for the host should be sent out. Valid options are a combination of one or more of the following:
d = send notifications on a DOWN state,
u = send notifications on an UNREACHABLE state,
r
= send notifications on recoveries (OK state),
f = send notifications when the host starts and stops flapping, and
s = send notifications when scheduled downtime starts and ends.
If you do not specify any notification options, Nagios will assume that you want notifications to be sent out for all possible states.

\r\n

Example: If you specify d,r in this field, notifications will only be sent out when the host goes DOWN and when it recovers from a DOWN state.

\r\n

Parameter name: notification_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(51, 'host', 'notification_enabled', 'all', 'default', '

Host - notification enabled

\r\n

This directive is used to determine whether or not notifications for this host are enabled. Values: 0 = disable host notifications, 1 = enable host notifications.

\r\n

Parameter name: notification_enabled
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(52, 'host', 'stalking_options', 'all', 'default', '

Host - stalking options

\r\n

This directive determines which host states "stalking" is enabled for. Valid options are a combination of one or more of the following:
o
= stalk on UP states,
d = stalk on DOWN states, and
u = stalk on UNREACHABLE states.

\r\n

Parameter name: stalking_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(53, 'host', 'process_perf_data', 'all', 'default', '

Host - process performance data

\r\n

This directive is used to determine whether or not the processing of performance data is enabled for this host. Values: 0 = disable performance data processing, 1 = enable performance data processing.

\r\n

Parameter name: process_perf_data
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(54, 'host', 'notification_intervall', 'all', 'default', '

Host - notification interval

\r\n

This directive is used to define the number of "time units" to wait before re-notifying a contact that this service is still down or unreachable. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will not re-notify contacts about problems for this host - only one problem notification will be sent out.

\r\n

Parameter name: notification_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(55, 'host', 'first_notification_delay', 'all', 'default', '

Host - first notification delay

\r\n

This directive is used to define the number of "time units" to wait before sending out the first problem notification when this host enters a non-UP state. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will start sending out notifications immediately.

\r\n

Parameter name: first_notification_delay
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(56, 'host', 'notes', '3', 'default', '

Host - notes

\r\n

This directive is used to define an optional string of notes pertaining to the host. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified host).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(57, 'host', 'vrml_image', '3', 'default', '

Host - vrml image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this host. This image will be used as the texture map for the specified host in the statuswrl CGI. Unlike the image you use for the icon_image variable, this one should probably not have any transparency.

\r\n

If it does, the host object will look a bit wierd. Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: vrml_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(58, 'host', 'notes_url', '3', 'default', '

Host - notes url

\r\n

This variable is used to define an optional URL that can be used to provide more information about the host. If you specify an URL, you will see a red folder icon in the CGIs (when you are viewing host information) that links to the URL you specify here. Any valid URL can be used.

\r\n

If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the host, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(59, 'host', 'status_image', '3', 'default', '

Host - statusmap image

\r\n

This variable is used to define the name of an image that should be associated with this host in the statusmap CGI. You can specify a JPEG, PNG, and GIF image if you want, although I would strongly suggest using a GD2 format image, as other image formats will result in a lot of wasted CPU time when the statusmap image is generated.

\r\n

GD2 images can be created from PNG images by using the pngtogd2 utility supplied with Thomas Boutell''s gd library . The GD2 images should be created in uncompressed format in order to minimize CPU load when the statusmap CGI is generating the network map image.

\r\n

The image will look best if it is 40x40 pixels in size. You can leave these option blank if you are not using the statusmap CGI. Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: statusmap_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(60, 'host', 'action_url', '3', 'default', '

Host - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the host. If you specify an URL, you will see a red "splat" icon in the CGIs (when you are viewing host information) that links to the URL you specify here. Any valid URL can be used.

\r\n

If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(61, 'host', 'icon_image', '3', 'default', '

Host - icon image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this host. This image will be displayed in the various places in the CGIs. The image will look best if it is 40x40 pixels in size. Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: icon_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(62, 'host', '2d_coords', '3', 'default', '

Host - 2D coords

\r\n

This variable is used to define coordinates to use when drawing the host in the statusmap CGI. Coordinates should be given in positive integers, as they correspond to physical pixels in the generated image. The origin for drawing (0,0) is in the upper left hand corner of the image and extends in the positive x direction (to the right) along the top of the image and in the positive y direction (down) along the left hand side of the image.

\r\n

For reference, the size of the icons drawn is usually about 40x40 pixels (text takes a little extra space). The coordinates you specify here are for the upper left hand corner of the host icon that is drawn. Note: Don''t worry about what the maximum x and y coordinates that you can use are. The CGI will automatically calculate the maximum dimensions of the image it creates based on the largest x and y coordinates you specify.

\r\n

Parameter name: 2d_coords
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(63, 'host', 'icon_image_alt_text', '3', 'default', '

Host - icon image alt

\r\n

This variable is used to define an optional string that is used in the ALT tag of the image specified by the icon image argument.

\r\n

Parameter name: icon_image_alt
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(64, 'host', '3d_coords', '3', 'default', '

Host - 3D coords

\r\n

This variable is used to define coordinates to use when drawing the host in the statuswrl CGI. Coordinates can be positive or negative real numbers. The origin for drawing is (0.0,0.0,0.0). For reference, the size of the host cubes drawn is 0.5 units on each side (text takes a little more space). The coordinates you specify here are used as the center of the host cube.

\r\n

Parameter name: 3d_coords
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(65, 'common', 'free_variables_name', 'all', 'default', '

Free variables (custom object variables)

\r\n

NagiosQL supports custom object variables.

\r\n

There are a few important things that you should note about custom variables:

\r\n\r\n

Examples

\r\n

define host{
       host_name linuxserver
       _mac_address 00:06:5B:A6:AD:AA ; <-- Custom MAC_ADDRESS variable
       _rack_number R32 ; <-- Custom RACK_NUMBER variable
       ...
}

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(66, 'common', 'free_variables_value', 'all', 'default', '

Free variables (custom object variables)

\r\n

NagiosQL supports custom object variables.

\r\n

There are a few important things that you should note about custom variables:

\r\n\r\n

Examples

\r\n

define host{
       host_name linuxserver
       _mac_address 00:06:5B:A6:AD:AA ; <-- Custom MAC_ADDRESS variable
       _rack_number R32 ; <-- Custom RACK_NUMBER variable
       ...
}

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(67, 'host', 'genericname', 'all', 'default', '

Host or Service - generic name

\r\n

It is possible to use a host definition as a template for other host configurations. If this definition should be used as template, a generic template name must be defined.

\r\n

We do not recommend to do this - it is more open to define a separate host template than to use this option.

\r\n

Parameter name: name
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(68, 'service', 'config_name', 'all', 'default', '

Service - config name

\r\n

This directive is used to specify a common config name for a group of service definitions. This is a NagiosQL parameter and it will not be written to the configuration file. Every service definitions with the same configuration name will stored in one file. The configuration name is also the file name of this configuration set.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(69, 'service', 'hosts', 'all', 'default', '

Service - host name

\r\n

This directive is used to specify the short name(s) of the host(s) that the service "runs" on or is associated with.

\r\n

Parameter name: host_name
Required: yes (no, if a hostgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(70, 'service', 'hostgroups', 'all', 'default', '

Service - hostgroup name

\r\n

This directive is used to specify the short name(s) of the hostgroup(s) that the service "runs" on or is associated with. The hostgroup_name may be used instead of, or in addition to, the host_name directive.

\r\n

Parameter name: hostgroup_name
Required: no (yes, if no host is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(71, 'service', 'service_description', 'all', 'default', '

Service - service description

\r\n

This directive is used to define the description of the service, which may contain spaces, dashes, and colons (semicolons, apostrophes, and quotation marks should be avoided). No two services associated with the same host can have the same description. Services are uniquely identified with their host_name and service_description directives.

\r\n

Parameter name: service_description
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(72, 'service', 'service_groups', 'all', 'default', '

Service - servicegroups

\r\n

This directive is used to identify the short name(s) of the servicegroup(s) that the service belongs to. Multiple servicegroups should be separated by commas. This directive may be used as an alternative to using the members directive in servicegroup definitions.

\r\n

NagiosQL: If a servicegroup is defined here - this service will not be selected inside the member field of the same servicegroup definition!

\r\n

Parameter name: servicegroups
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(73, 'service', 'display_name', 'all', 'default', '

Service - display name

\r\n

This directive is used to define an alternate name that should be displayed in the web interface for this service. If not specified, this defaults to the value you specify for the service_description directive. Note: The current CGIs do not use this option, although future versions of the web interface will.

\r\n

Parameter name: display_name
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(74, 'service', 'check_command', 'all', 'default', '

Service - check command

\r\n

This directive is used to specify the short name of the command that Nagios will run in order to check the status of the service. The maximum amount of time that the service check command can run is controlled by the service_check_timeout option.

\r\n

Parameter name: check_command
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(75, 'service', 'argument', 'all', 'default', '

Service - arguments

\r\n

The values defined here will replace the according argument variable behind the selected command. Up to 8 argument variables are supported. Be sure, that you defines a valid value for each required argument variable.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(76, 'service', 'templateadd', 'all', 'default', '

Service - Templates

\r\n

You can add one or more service templates to a service configuration. Nagios will add the definitions from each template to a service configuration.

\r\n

If you add more than one template - the sort order will be used to overwrite configuration items which are defined inside templates before.

\r\n

The host configuration itselves will overwrite all values which are defined in templates before and pass all values which are not defined.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(77, 'service', 'initial_state', '3', 'default', '

Service - initial state

\r\n

By default Nagios will assume that all services are in OK states when in starts. You can override the initial state for a service by using this directive. Valid options are:
o
= OK,
w = WARNING,
u
= UNKNOWN, and
c
= CRITICAL.

\r\n

Parameter name: initial_state
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(78, 'service', 'retry_interval', '3', 'default', '

Service - retry interval

\r\n

This directive is used to define the number of "time units" to wait before scheduling a re-check of the service. Services are rescheduled at the retry interval when they have changed to a non-OK state. Once the service has been retried max_check_attempts times without a change in its status, it will revert to being scheduled at its "normal" rate as defined by the check_interval value. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.

\r\n

Parameter name: retry_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(79, 'service', 'max_check_attempts', 'all', 'default', '

Service - max check attempts

\r\n

This directive is used to define the number of times that Nagios will retry the service check command if it returns any state other than an OK state. Setting this value to 1 will cause Nagios to generate an alert without retrying the service check again.

\r\n

Parameter name: max_check_attempts
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(80, 'service', 'check_interval', 'all', 'default', '

Service - check interval

\r\n

This directive is used to define the number of "time units" to wait before scheduling the next "regular" check of the service. "Regular" checks are those that occur when the service is in an OK state or when the service is in a non-OK state, but has already been rechecked max_check_attempts number of times. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. More information on this value can be found in the check scheduling documentation.

\r\n

Parameter name: check_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(81, 'service', 'active_checks_enabled', 'all', 'default', '

Service - active checks enabled

\r\n

This directive is used to determine whether or not active checks of this service are enabled. Values: 0 = disable active service checks, 1 = enable active service checks.

\r\n

Parameter name: active_checks_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(82, 'service', 'passive_checks_enabled', 'all', 'default', '

Service - passive checks enabled

\r\n

This directive is used to determine whether or not passive checks of this service are enabled. Values: 0 = disable passive service checks, 1 = enable passive service checks.

\r\n

Parameter name: passive_checks_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(83, 'service', 'parallelize_checks', '2', 'default', '

Service - parallelize check

\r\n

This directive is used to determine whether or not the service check can be parallelized. By default, all service checks are parallelized. Disabling parallel checks of services can result in serious performance problems. More information on service check parallelization can be found in the nagios documentation.

\r\n

Values: 0 = service check cannot be parallelized (use with caution!), 1 = service check can be parallelized.

\r\n

Parameter name: parallelize_check
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(84, 'service', 'check_period', 'all', 'default', '

Service - check period

\r\n

This directive is used to specify the short name of the time period during which active checks of this service can be made.

\r\n

Parameter name: check_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(85, 'service', 'freshness_threshold', 'all', 'default', '

Service - freshness threshold

\r\n

This directive is used to specify the freshness threshold (in seconds) for this service. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.

\r\n

Parameter name: freshness_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(86, 'service', 'check_freshness', 'all', 'default', '

Service - check freshness

\r\n

This directive is used to determine whether or not freshness checks are enabled for this service. Values: 0 = disable freshness checks, 1 = enable freshness checks.

\r\n

Parameter name: check_freshness
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(87, 'service', 'obsess_over_service', 'all', 'default', '

Service - obsess over service

\r\n

This directive determines whether or not checks for the service will be "obsessed" over using the ocsp_command.

\r\n

Parameter name: obsess_over_service
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(88, 'service', 'event_handler', 'all', 'default', '

Service - event handler

\r\n

This directive is used to specify the short name of the command that should be run whenever a change in the state of the service is detected (i.e. whenever it goes down or recovers). Read the documentation on event handlers for a more detailed explanation of how to write scripts for handling events. The maximum amount of time that the event handler command can run is controlled by the event_handler_timeout option.

\r\n

Parameter name: event_handler
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(89, 'service', 'event_handler_enabled', 'all', 'default', '

Service - event handler enabled

\r\n

This directive is used to determine whether or not the event handler for this service is enabled. Values: 0 = disable service event handler, 1 = enable service event handler.

\r\n

Parameter name: event_handler_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(90, 'service', 'low_flap_threshold', 'all', 'default', '

Service - low flap threshold

\r\n

This directive is used to specify the low state change threshold used in flap detection for this service. More information on flap detection can be found in the nagios documentation. If you set this directive to a value of 0, the program-wide value specified by the low_service_flap_threshold directive will be used.

\r\n

Parameter name: low_flap_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(91, 'service', 'high_flap_threshold', 'all', 'default', '

Service - high flap threshold

\r\n

This directive is used to specify the high state change threshold used in flap detection for this service. More information on flap detection can be found in the nagios documentation. If you set this directive to a value of 0, the program-wide value specified by the high_service_flap_threshold directive will be used.

\r\n

Parameter name: high_flap_threshold
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(92, 'service', 'flap_detection_enabled', 'all', 'default', '

Service - flap detection enabled

\r\n

This directive is used to determine whether or not flap detection is enabled for this service. More information on flap detection can be found in the nagios documentation. Values: 0 = disable service flap detection, 1 = enable service flap detection.

\r\n

Parameter name: flap_detection_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(93, 'service', 'flap_detection_options', '3', 'default', '

Service - flap detection options

\r\n

This directive is used to determine what service states the flap detection logic will use for this service. Valid options are a combination of one or more of the following:
o
= OK states,
w = WARNING states,
c = CRITICAL states,
u = UNKNOWN states.

\r\n

Parameter name: flap_detection_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(94, 'service', 'retain_status_information', 'all', 'default', '

Service - retain status information

\r\n

This directive is used to determine whether or not status-related information about the service is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable status information retention, 1 = enable status information retention.

\r\n

Parameter name: retain_status_information
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(95, 'service', 'retain_nonstatus_information', 'all', 'default', '

Service - retain nonstatus information

\r\n

This directive is used to determine whether or not non-status information about the service is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable non-status information retention, 1 = enable non-status information retention.

\r\n

Parameter name: retain_nonstatus_information
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(96, 'service', 'process_perf_data', 'all', 'default', '

Service - process perf data

\r\n

This directive is used to determine whether or not the processing of performance data is enabled for this service. Values: 0 = disable performance data processing, 1 = enable performance data processing.

\r\n

Parameter name: process_perf_data
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(97, 'service', 'is_volatile', 'all', 'default', '

Service - is volatile

\r\n

This directive is used to denote whether the service is "volatile". Services are normally not volatile. More information on volatile service and how they differ from normal services can be found in the nagios documentation. Value: 0 = service is not volatile, 1 = service is volatile.

\r\n

Parameter name: is_volatile
Required:no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(98, 'service', 'contacts', '3', 'default', '

Service - contacts

\r\n

This is a list of the short names of the contacts that should be notified whenever there are problems (or recoveries) with this service. Multiple contacts should be separated by commas. Useful if you want notifications to go to just a few people and don''t want to configure contact groups. You must specify at least one contact or contact group in each service definition.

\r\n

Parameter name: contacts
Required: yes (no, if a contact group is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(99, 'service', 'contactgroups', 'all', 'default', '

Service - contact groups

\r\n

This is a list of the short names of the contact groups that should be notified whenever there are problems (or recoveries) with this service. Multiple contact groups should be separated by commas. You must specify at least one contact or contact group in each service definition.

\r\n

Parameter name: contact_groups
Required: yes (no, if a contact is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(100, 'service', 'notification_period', 'all', 'default', '

Service - notification period

\r\n

This directive is used to specify the short name of the time period during which notifications of events for this service can be sent out to contacts. No service notifications will be sent out during times which is not covered by the time period.

\r\n

Parameter name: notification_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(101, 'service', 'notification_options', 'all', 'default', '

Service - notification options

\r\n

This directive is used to determine when notifications for the service should be sent out. Valid options are a combination of one or more of the following:

w
= send notifications on a WARNING state,
u = send notifications on an UNKNOWN state,
c
= send notifications on a CRITICAL state,
r = send notifications on recoveries (OK state),
f
= send notifications when the service starts and stops flapping, and
s = send notifications when scheduled downtime starts and ends.

\r\n

If you do not specify any notification options, Nagios will assume that you want notifications to be sent out for all possible states.

\r\n

Example: If you specify w,r in this field, notifications will only be sent out when the service goes into a WARNING state and when it recovers from a WARNING state.

\r\n

Parameter name: notification_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(102, 'service', 'notification_intervall', 'all', 'default', '

Service - notification interval

\r\n

This directive is used to define the number of "time units" to wait before re-notifying a contact that this service is still in a non-OK state. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will not re-notify contacts about problems for this service - only one problem notification will be sent out.

\r\n

Parameter name: notification_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(103, 'service', 'first_notification_delay', 'all', 'default', '

Service - first notification delay

\r\n

This directive is used to define the number of "time units" to wait before sending out the first problem notification when this service enters a non-OK state. Unless you''ve changed the interval_length directive from the default value of 60, this number will mean minutes. If you set this value to 0, Nagios will start sending out notifications immediately.

\r\n

Parameter name: first_notification_delay
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(104, 'service', 'notification_enabled', 'all', 'default', '

Service - notifications enabled

\r\n

This directive is used to determine whether or not notifications for this service are enabled. Values: 0 = disable service notifications, 1 = enable service notifications.

\r\n

Parameter name: notifications_enabled
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(105, 'service', 'stalking_options', 'all', 'default', '

Service - stalking options

\r\n

This directive determines which service states "stalking" is enabled for. Valid options are a combination of one or more of the following:
o
= stalk on OK states,
w = stalk on WARNING states,
u
= stalk on UNKNOWN states, and
c
= stalk on CRITICAL states.

\r\n

More information on state stalking can be found in the nagios documentation.

\r\n

Parameter name: stalking_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(106, 'service', 'notes', '3', 'default', '

Service - notes

\r\n

This directive is used to define an optional string of notes pertaining to the service. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified service).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(107, 'service', 'icon_image', '3', 'default', '

Service - icon image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this service. This image will be displayed in the status and extended information CGIs. The image will look best if it is 40x40 pixels in size. Images for services are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: icon_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(108, 'service', 'notes_url', '3', 'default', '

Service - notes url

\r\n

This directive is used to define an optional URL that can be used to provide more information about the service. If you specify an URL, you will see a red folder icon in the CGIs (when you are viewing service information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the service, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(109, 'service', 'icon_image_alt_text', '3', 'default', '

Service - icon image alt

\r\n

This variable is used to define an optional string that is used in the ALT tag of the image specified by the <icon_image> argument. The ALT tag is used in the status, extended information and statusmap CGIs.

\r\n

Parameter name: icon_image_alt
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(110, 'service', 'action_url', '3', 'default', '

Service - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the service. If you specify an URL, you will see a red "splat" icon in the CGIs (when you are viewing service information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(111, 'hostgroup', 'hostgroup_name', 'all', 'default', '

Hostgroup - hostgroup name

\r\n

This directive is used to define a short name used to identify the host group.

\r\n

Parameter name: hostgroup_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(112, 'hostgroup', 'members', 'all', 'default', '

Hostgroup - members

\r\n

This is a list of the short names of hosts that should be included in this group. Multiple host names should be separated by commas. This directive may be used as an alternative to (or in addition to) the hostgroups directive in host definitions.

\r\n

NagiosQL: If you select a hostgroup inside a host definition using the hostgroups directive in host definition, this host will not be selected here because these are two different ways to specify a hostgroup!

\r\n

Parameter name: members
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(113, 'hostgroup', 'description', 'all', 'default', '

Hostgroup - alias

\r\n

This directive is used to define is a longer name or description used to identify the host group. It is provided in order to allow you to more easily identify a particular host group.

\r\n

Parameter name: alias
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(114, 'hostgroup', 'notes', '3', 'default', '

Hostgroup - notes

\r\n

This directive is used to define an optional string of notes pertaining to the host. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified host).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(115, 'hostgroup', 'notes_url', '3', 'default', '

Hostgroup - notes url

\r\n

This variable is used to define an optional URL that can be used to provide more information about the host group. If you specify an URL, you will see a red folder icon in the CGIs (when you are viewing hostgroup information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the host group, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(116, 'hostgroup', 'action_url', '3', 'default', '

Hostgroup - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the host group. If you specify an URL, you will see a red "splat" icon in the CGIs (when you are viewing hostgroup information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(117, 'hostgroup', 'hostgroup_members', 'all', 'default', '

Hostgroup - hostgroup members

\r\n

This optional directive can be used to include hosts from other "sub" host groups in this host group. Specify a comma-delimited list of short names of other host groups whose members should be included in this group.

\r\n

Parameter name: hostgroup_members
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(118, 'servicegroup', 'servicegroup_name', 'all', 'default', '

Servicegroup - servicegroup name

\r\n

This directive is used to define a short name used to identify the service group.

\r\n

Parameter name: servicegroup_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(119, 'servicegroup', 'members', 'all', 'default', '

Servicegroup - members

\r\n

This is a list of the descriptions of services (and the names of their corresponding hosts) that should be included in this group. Host and service names should be separated by commas. This directive may be used as an alternative to the servicegroups directive in service definitions.

\r\n

NagiosQL: If you select a servicegroup inside a service definition using the servicegroups directive in service definition, this service will not be selected here because these are two different ways to specify a servicegroup!

\r\n

Parameter name: members
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(120, 'servicegroup', 'description', 'all', 'default', '

Servicegroup - alias

\r\n

This directive is used to define is a longer name or description used to identify the service group. It is provided in order to allow you to more easily identify a particular service group.

\r\n

Parameter name: alias
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(121, 'servicegroup', 'notes', '3', 'default', '

Servicegroup - notes

\r\n

This directive is used to define an optional string of notes pertaining to the service group. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified service group).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(122, 'servicegroup', 'notes_url', '3', 'default', '

Servicegroup - notes url

\r\n

This directive is used to define an optional URL that can be used to provide more information about the service group. If you specify an URL, you will see a red folder icon in the CGIs (when you are viewing service group information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the service group, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(123, 'servicegroup', 'action_url', '3', 'default', '

Servicegroup - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the service group. If you specify an URL, you will see a red "splat" icon in the CGIs (when you are viewing service group information) that links to the URL you specify here. Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(124, 'servicegroup', 'servicegroup_members', 'all', 'default', '

Servicegroup - servicegroup members

\r\n

This optional directive can be used to include services from other "sub" service groups in this service group. Specify a comma-delimited list of short names of other service groups whose members should be included in this group.

\r\n

Parameter name: servicegroup_members
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(125, 'hosttemplate', 'template_name', 'all', 'default', '

Hosttemplate - template name

\r\n

This directive is used to define a short name used to identify the host template.

\r\n

Parameter name: name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(126, 'servicetemplate', 'template_name', 'all', 'default', '

Servicetemplate - template name

\r\n

This directive is used to define a short name used to identify the service template.

\r\n

Parameter name: name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(127, 'contact', 'contact_name', 'all', 'default', '

Contact - contact name

\r\n

This directive is used to define a short name used to identify the contact. It is referenced in contact group definitions. Under the right circumstances, the $CONTACTNAME$ macro will contain this value.

\r\n

Parameter name: contact_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(128, 'contact', 'contactgroups', 'all', 'default', '

Contact - contactgroups

\r\n

This directive is used to identify the short name(s) of the contactgroup(s) that the contact belongs to. Multiple contactgroups should be separated by commas. This directive may be used as an alternative to (or in addition to) using the members directive in contactgroup definitions.

\r\n

NagiosQL: If a contactgroup is defined here - this contact will not be selected inside the member field of the same contactgroup definition!

\r\n

Parameter name: contactgroups
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(129, 'contact', 'alias', 'all', 'default', '

Contact - alias

\r\n

This directive is used to define a longer name or description for the contact. Under the rights circumstances, the $CONTACTALIAS$ macro will contain this value. If not specified, the contact_name will be used as the alias.

\r\n

Parameter name: alias
Required: no (yes in Nagios 2.x)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(130, 'contact', 'email', 'all', 'default', '

Contact - email

\r\n

This directive is used to define an email address for the contact. Depending on how you configure your notification commands, it can be used to send out an alert email to the contact. Under the right circumstances, the $CONTACTEMAIL$ macro will contain this value.

\r\n

Parameter name: email
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(131, 'contact', 'pager', 'all', 'default', '

Contact - pager

\r\n

This directive is used to define a pager number for the contact. It can also be an email address to a pager gateway (i.e. pagejoe@pagenet.com). Depending on how you configure your notification commands, it can be used to send out an alert page to the contact. Under the right circumstances, the $CONTACTPAGER$ macro will contain this value.

\r\n

Parameter name: pager
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(132, 'contact', 'address', 'all', 'default', '

Contact - addressx

\r\n

Address directives are used to define additional "addresses" for the contact. These addresses can be anything - cell phone numbers, instant messaging addresses, etc. Depending on how you configure your notification commands, they can be used to send out an alert o the contact. Up to six addresses can be defined using these directives (address1 through address6). The $CONTACTADDRESSx$ macro will contain this value.

\r\n

Parameter name: addressx (x as number from 1 to 6)
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(133, 'contact', 'host_notifications_enabled', '3', 'default', '

Contact - host notifications enabled

\r\n

This directive is used to determine whether or not the contact will receive notifications about host problems and recoveries. Values: 0 = don''t send notifications, 1 = send notifications.

\r\n

Parameter name: host_notifications_enabled
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(134, 'contact', 'service_notifications_enabled', '3', 'default', '

Contact - service notifications enabled

\r\n

This directive is used to determine whether or not the contact will receive notifications about service problems and recoveries. Values: 0 = don''t send notifications, 1 = send notifications.

\r\n

Parameter name: service_notifications_enabled
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(135, 'contact', 'host_notification_period', 'all', 'default', '

Contact - host notification period

\r\n

This directive is used to specify the short name of the time period during which the contact can be notified about host problems or recoveries. You can think of this as an "on call" time for host notifications for the contact. Read the documentation on time periods for more information on how this works and potential problems that may result from improper use.

\r\n

Parameter name: host_notification_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(136, 'contact', 'service_notification_period', 'all', 'default', '

Contact - service notification period

\r\n

This directive is used to specify the short name of the time period during which the contact can be notified about service problems or recoveries. You can think of this as an "on call" time for service notifications for the contact. Read the documentation on time periods for more information on how this works and potential problems that may result from improper use.

\r\n

Parameter name: service_notification_period
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(137, 'contact', 'host_notification_options', '2', 'default', '

Contact - host notification options

\r\n

This directive is used to define the host states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
d
= notify on DOWN host states,
u = notify on UNREACHABLE host states,
r
= notify on host recoveries (UP states), and
f
= notify when the host starts and stops flapping.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

\r\n

Parameter name: host_notification_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(138, 'contact', 'host_notification_options', '3', 'default', '

Contact - host notification options

\r\n

This directive is used to define the host states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
d = notify on DOWN host states,
u
= notify on UNREACHABLE host states,
r
= notify on host recoveries (UP states),
f
= notify when the host starts and stops flapping, and
s = send notifications when host or service scheduled downtime starts and ends.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

\r\n

Parameter name: host_notification_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(139, 'contact', 'service_notification_options', '2', 'default', '

Contact - service notification options

\r\n

This directive is used to define the service states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
w
= notify on WARNING service states,
u
= notify on UNKNOWN service states,
c
= notify on CRITICAL service states,
r = notify on service recoveries (OK states), and
f = notify when the servuce starts and stops flapping.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

\r\n

Parameter name: service_notification_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(140, 'contact', 'service_notification_options', '3', 'default', '

Contact - service notification options

\r\n

This directive is used to define the service states for which notifications can be sent out to this contact. Valid options are a combination of one or more of the following:
w
= notify on WARNING service states,
u = notify on UNKNOWN service states,
c = notify on CRITICAL service states,
r
= notify on service recoveries (OK states), and
f = notify when the host starts and stops flapping, and
s
= send notifications when host or service scheduled downtime starts and ends.
If you specify n (none) as an option, the contact will not receive any type of host notifications.

\r\n

Parameter name: service_notification_options
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(141, 'contact', 'host_notification_commands', 'all', 'default', '

Contact - host notification commands

\r\n

This directive is used to define a list of the short names of the commands used to notify the contact of a host problem or recovery. Multiple notification commands should be separated by commas. All notification commands are executed when the contact needs to be notified. The maximum amount of time that a notification command can run is controlled by the notification_timeout option.

\r\n

Parameter name: host_notification_commands
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(142, 'contact', 'service_notification_commands', 'all', 'default', '

Contact - service notification commands

\r\n

This directive is used to define a list of the short names of the commands used to notify the contact of a service problem or recovery. Multiple notification commands should be separated by commas. All notification commands are executed when the contact needs to be notified. The maximum amount of time that a notification command can run is controlled by the notification_timeout option.

\r\n

Parameter name: service_notification_commands
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(143, 'contact', 'retain_status_information', '3', 'default', '

Contact - retain status information

\r\n

This directive is used to determine whether or not status-related information about the contact is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable status information retention, 1 = enable status information retention.

\r\n

Parameter name: retain_status_information
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(144, 'contact', 'can_submit_commands', '3', 'default', '

Contact - can submit commands

\r\n

This directive is used to determine whether or not the contact can submit external commands to Nagios from the CGIs. Values: 0 = don''t allow contact to submit commands, 1 = allow contact to submit commands.

\r\n

Parameter name: can_submit_commands
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(145, 'contact', 'retain_nostatus_information', '3', 'default', '

Contact - retain nonstatus information

\r\n

This directive is used to determine whether or not non-status information about the contact is retained across program restarts. This is only useful if you have enabled state retention using the retain_state_information directive. Value: 0 = disable non-status information retention, 1 = enable non-status information retention.

\r\n

Parameter name: retain_nonstatus_information
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(146, 'contact', 'templateadd', 'all', 'default', '

Contact - Templates

\r\n

You can add one or more contact templates to a contact configuration. Nagios will add the definitions from each template to a contact configuration.

\r\n

If you add more than one template - the sort order will be used to overwrite configuration items which are defined inside templates before.

\r\n

The host configuration itselves will overwrite all values which are defined in templates before and pass all values which are not defined.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(147, 'contact', 'genericname', 'all', 'default', '

Contact - generic name

\r\n

It is possible to use a contact definition as a template for other contact configurations. If this definition should be used as template, a generic template name must be defined.

\r\n

We do not recommend to do this - it is more open to define a separate contact template than use this option.

\r\n

Parameter name: name
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(148, 'contactgroup', 'contactgroup_name', 'all', 'default', '

Contactgroup - contactgroup name

\r\n

This directive is a short name used to identify the contact group.

\r\n

Parameter name: contactgroup_name
Required:
yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(149, 'contactgroup', 'members', 'all', 'default', '

Contactgroup - members

\r\n

This directive is used to define a list of the short names of contacts that should be included in this group. Multiple contact names should be separated by commas. This directive may be used as an alternative to (or in addition to) using the contactgroups directive in contact definitions.

\r\n

NagiosQL: If you select a contactgroup inside a contact definition using the contactgroups directive in contact definition, this contact will not be selected here because these are two different ways to specify a contactgroup!

\r\n

Parameter name: members
Required:
yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(150, 'contactgroup', 'alias', 'all', 'default', '

Contactgroup - alias

\r\n

This directive is used to define a longer name or description used to identify the contact group.

\r\n

Parameter name: alias
Required:
yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(151, 'contactgroup', 'contactgroup_members', 'all', 'default', '

Contactgroup - contactgroup members

\r\n

This optional directive can be used to include contacts from other "sub" contact groups in this contact group. Specify a comma-delimited list of short names of other contact groups whose members should be included in this group.

\r\n

Parameter name: contactgroup_members
Required:
no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(152, 'timeperiod', 'timeperiod_name', 'all', 'default', '

Timeperiod - timeperiod name

\r\n

This directives is the short name used to identify the time period.

\r\n

Parameter name: timeperiod_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(153, 'timeperiod', 'exclude', '3', 'default', '

Timeperiod - exclude

\r\n

This directive is used to specify the short names of other timeperiod definitions whose time ranges should be excluded from this timeperiod. Multiple timeperiod names should be separated with a comma.

\r\n

Parameter name: exclude
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(154, 'timeperiod', 'alias', 'all', 'default', '

Timeperiod - alias

\r\n

This directive is a longer name or description used to identify the time period.

\r\n

Parameter name: alias
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(155, 'timeperiod', 'templatename', '3', 'default', '

Timeperiod - template name

\r\n

Not yet implemented.

\r\n

Parameter name: name
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(156, 'timeperiod', 'weekday', '2', 'default', '

Timeperiod - time definition

\r\n

The sunday through saturday directives are comma-delimited lists of time ranges that are "valid" times for a particular day of the week. Notice that there are seven different days for which you can define time ranges (Sunday through Saturday).

\r\n

Parameter name: [weekday] [exception]
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(157, 'timeperiod', 'timerange', '2', 'default', '

Timeperiod - time range

\r\n

Each time range is in the form of HH:MM-HH:MM, where hours are specified on a 24 hour clock. For example, 00:15-24:00 means 12:15am in the morning for this day until 12:20am midnight (a 23 hour, 45 minute total time range). If you wish to exclude an entire day from the timeperiod, simply do not include it in the timeperiod definition.

\r\n

Parameter name: [weekday] [exception]
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(158, 'timeperiod', 'weekday', '3', 'default', '

Timeperiod - time definition

\r\n

The weekday directives ("sunday" through "saturday")are comma-delimited lists of time ranges that are "valid" times for a particular day of the week. Notice that there are seven different days for which you can define time ranges (Sunday through Saturday). 

\r\n

You can also specify several different types of exceptions to the standard rotating weekday schedule. Exceptions can take a number of different forms including single days of a specific or generic month, single weekdays in a month, or single calendar dates. You can also specify a range of days/dates and even specify skip intervals to obtain functionality described by "every 3 days between these dates". Rather than list all the possible formats for exception strings, Weekdays and different types of exceptions all have different levels of precedence, so its important to understand how they can affect each other. More information on this can be found in the documentation on timeperiods.

\r\n

Parameter name: [weekday] [exception]
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(159, 'timeperiod', 'timerange', '3', 'default', '

Timeperiod - time range

\r\n

Each time range is in the form of HH:MM-HH:MM, where hours are specified on a 24 hour clock. For example, 00:15-24:00 means 12:15am in the morning for this day until 12:00am midnight (a 23 hour, 45 minute total time range). If you wish to exclude an entire day from the timeperiod, simply do not include it in the timeperiod definition.

\r\n

Parameter name: [weekday] [exception]
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(160, 'contacttemplate', 'template_name', 'all', 'default', '

Contacttemplate - template name

\r\n

This directive is used to define a short name used to identify the contact template.

\r\n

Parameter name: name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(161, 'command', 'command_name', 'all', 'default', '

Command - command name

\r\n

This directive is the short name used to identify the command. It is referenced in contact, host, and service definitions (in notification, check, and event handler directives), among other places.

\r\n

Parameter name: command_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(162, 'command', 'command_line', 'all', 'default', '

Command - command line

\r\n

This directive is used to define what is actually executed by Nagios when the command is used for service or host checks, notifications, or event handlers. Before the command line is executed, all valid macros are replaced with their respective values. See the documentation on macros for determining when you can use different macros. Note that the command line is not surrounded in quotes. Also, if you want to pass a dollar sign ($) on the command line, you have to escape it with another dollar sign.

\r\n

NOTE: You may not include a semicolon (;) in the command_line directive, because everything after it will be ignored as a config file comment. You can work around this limitation by setting one of the $USER$ macros in your resource file to a semicolon and then referencing the appropriate $USER$ macro in the command_line directive in place of the semicolon.

\r\n

If you want to pass arguments to commands during runtime, you can use $ARGn$ macros in the command_line directive of the command definition and then separate individual arguments from the command name (and from each other) using bang (!) characters in the object definition directive (host check command, service event handler command, etc) that references the command. More information on how arguments in command definitions are processed during runtime can be found in the documentation on macros.

\r\n

Parameter name: command_line
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(163, 'command', 'command_type', 'all', 'default', '

Command - command type

\r\n

This directive is used to differ checks and misc commands. Its a NagiosQL definition only.

\r\n

Commands tagged as "check command" will be displayed in services and hosts as check command.

\r\n

Commands tagged as "misc command" will be displayed in contacts, services and hosts as event command.

\r\n

Not classified commands will be displayed everywhere.

\r\n

This definition is only used to reduce the amount of commands shown in the selection fields and to have a more clear view.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(164, 'hostdependency', 'dependent_host', 'all', 'default', '

Hostdependency - dependent host name

\r\n

This directive is used to identify the short name(s) of the dependent host(s). Multiple hosts should be separated by commas

\r\n

Parameter name: dependent_host_name
Required: yes (no, if a dependent hostgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(165, 'hostdependency', 'dependent_hostgroups', 'all', 'default', '

Hostdependency - dependent hostgroup name

\r\n

This directive is used to identify the short name(s) of the dependenthostgroup(s). Multiple hostgroups should be separated by commas. The dependent_hostgroup_name may be used instead of, or in addition to, the dependent_host_name directive.

\r\n

Parameter name: dependent_hostgroup_name
Required: no (yes, if no dependent host is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(166, 'hostdependency', 'host', 'all', 'default', '

Hostdependency - host name

\r\n

This directive is used to identify the short name(s) of the host(s) that is being depended upon (also referred to as the master host). Multiple hosts should be separated by commas.

\r\n

Parameter name: host_name
Required: yes (no, if  a hostgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(167, 'hostdependency', 'hostgroup', 'all', 'default', '

Hostdependency - hostgroup name

\r\n

This directive is used to identify the short name(s) of the host(s) that is being depended upon (also referred to as the master host). Multiple hosts should be separated by commas.

\r\n

Parameter name: hostgroup_name
Required: no (yes, if a no host is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(168, 'hostdependency', 'config_name', 'all', 'default', '

Hostdependency - config name

\r\n

This directive is used to specify a common config name for a hostdependency configration. This is a NagiosQL parameter and it will not be written to the configuration file.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(169, 'hostdependency', 'inherit_parents', 'all', 'default', '

Hostdependency - inherits parent

\r\n

This directive indicates whether or not the dependency inherits dependencies of the host that is being depended upon (also referred to as the master host). In other words, if the master host is dependent upon other hosts and any one of those dependencies fail, this dependency will also fail.

\r\n

Parameter name: inherits_parent
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(170, 'hostdependency', 'dependency_period', '3', 'default', '

Hostdependency - dependency_period

\r\n

This directive is used to specify the short name of the time period during which this dependency is valid. If this directive is not specified, the dependency is considered to be valid during all times.

\r\n

Parameter name: dependency_period
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(171, 'hostdependency', 'execution_failure_criteria', 'all', 'default', '

Hostdependency - execution failure criteria

\r\n

This directive is used to specify the criteria that determine when the dependent host should not be actively checked. If the master host is in one of the failure states we specify, the dependent host will not be actively checked. Valid options are a combination of one or more of the following (multiple options are separated with commas):
o = fail on an UP state,
d = fail on a DOWN state,
u = fail on an UNREACHABLE state, and
p
= fail on a pending state (e.g. the host has not yet been checked).

\r\n

If you specify n (none) as an option, the execution dependency will never fail and the dependent host will always be actively checked (if other conditions allow for it to be).

\r\n

Example: If you specify u,d in this field, the dependent host will not be actively checked if the master host is in either an UNREACHABLE or DOWN state.

\r\n

Parameter name: execution_failure_criteria
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(172, 'hostdependency', 'notification_failure_criteria', 'all', 'default', '

Hostdependency - notification failure criteria

\r\n

This directive is used to define the criteria that determine when notifications for the dependent host should not be sent out. If the master host is in one of the failure states we specify, notifications for the dependent host will not be sent to contacts. Valid options are a combination of one or more of the following:
o = fail on an UP state,
d = fail on a DOWN state,
u = fail on an UNREACHABLE state, and
p = fail on a pending state (e.g. the host has not yet been checked).

\r\n

If you specify n (none) as an option, the notification dependency will never fail and notifications for the dependent host will always be sent out.

\r\n

Example: If you specify d in this field, the notifications for the dependent host will not be sent out if the master host is in a DOWN state.

\r\n

Parameter name: notification_failure_criteria
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(173, 'hostescalation', 'host', 'all', 'default', '

Hostescalation - host name

\r\n

This directive is used to identify the short name of the host that the escalation should apply to.

\r\n

Parameter name: host_name
Required: yes (no, if a hostgroup name is defined

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(174, 'hostescalation', 'hostgroup', 'all', 'default', '

Hostescalation - hostgroup name

\r\n

This directive is used to identify the short name(s) of the hostgroup(s) that the escalation should apply to. Multiple hostgroups should be separated by commas. If this is used, the escalation will apply to all hosts that are members of the specified hostgroup(s).

\r\n

Parameter name: hostgroup_name
Required: no (yes, if no host ist defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(175, 'hostescalation', 'contact', 'all', 'default', '

Hostescalation - contacts

\r\n

This is a list of the short names of the contacts that should be notified whenever there are problems (or recoveries) with this host. Multiple contacts should be separated by commas. Useful if you want notifications to go to just a few people and don''t want to configure contact groups. You must specify at least one contact or contact group in each host escalation definition.

\r\n

Parameter name: contacts
Required: yes (no, if a contactgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(176, 'hostescalation', 'contactgroup', 'all', 'default', '

Hostescalation - contact groups

\r\n

This directive is used to identify the short name of the contact group that should be notified when the host notification is escalated. Multiple contact groups should be separated by commas. You must specify at least one contact or contact group in each host escalation definition.

\r\n

Parameter name: contact_groups
Required: yes (no, if a contact is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(177, 'hostescalation', 'config_name', 'all', 'default', '

Hostescalation - config name

\r\n

This directive is used to specify a common config name for a hostescalation configration. This is a NagiosQL parameter and it will not be written to the configuration file.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(178, 'hostescalation', 'escalation_period', 'all', 'default', '

Hostescalation - escalation period

\r\n

This directive is used to specify the short name of the time period during which this escalation is valid. If this directive is not specified, the escalation is considered to be valid during all times.

\r\n

Parameter name: escalation_period
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(179, 'hostescalation', 'escalation_options', 'all', 'default', '

Hostescalation - escalation options

\r\n

This directive is used to define the criteria that determine when this host escalation is used. The escalation is used only if the host is in one of the states specified in this directive. If this directive is not specified in a host escalation, the escalation is considered to be valid during all host states. Valid options are a combination of one or more of the following:
r = escalate on an UP (recovery) state,
d = escalate on a DOWN state, and
u
= escalate on an UNREACHABLE state.

\r\n

Example: If you specify d in this field, the escalation will only be used if the host is in a DOWN state.

\r\n

Parameter name: escalation_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(180, 'hostescalation', 'first_notification', 'all', 'default', '

Hostescalation - first notification

\r\n

This directive is a number that identifies the first notification for which this escalation is effective. For instance, if you set this value to 3, this escalation will only be used if the host is down or unreachable long enough for a third notification to go out.

\r\n

Parameter name: first_notification
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(181, 'hostescalation', 'last_notification', 'all', 'default', '

Hostescalation - last notification

\r\n

This directive is a number that identifies the last notification for which this escalation is effective. For instance, if you set this value to 5, this escalation will not be used if more than five notifications are sent out for the host. Setting this value to 0 means to keep using this escalation entry forever (no matter how many notifications go out).

\r\n

Parameter name: last_notification
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(182, 'hostescalation', 'notification_intervall', 'all', 'default', '

Hostescalation - notification interval

\r\n

This directive is used to determine the interval at which notifications should be made while this escalation is valid. If you specify a value of 0 for the interval, Nagios will send the first notification when this escalation definition is valid, but will then prevent any more problem notifications from being sent out for the host. Notifications are sent out again until the host recovers.

\r\n

This is useful if you want to stop having notifications sent out after a certain amount of time. Note: If multiple escalation entries for a host overlap for one or more notification ranges, the smallest notification interval from all escalation entries is used.

\r\n

Parameter name: notification_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(183, 'hostextinfo', 'host_name', 'all', 'default', '

Hostextinfo - host name

\r\n

This variable is used to identify the short name of the host which the data is associated with.

\r\n

Parameter name: host_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(184, 'hostextinfo', 'icon_image', 'all', 'default', '

Hostextinfo - icon image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this host. This image will be displayed in the status and extended information CGIs. The image will look best if it is 40x40 pixels in size.

\r\n

Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: icon_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(185, 'hostextinfo', 'notes', 'all', 'default', '

Hostextinfo - notes

\r\n

This directive is used to define an optional string of notes pertaining to the host. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified host).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(186, 'hostextinfo', 'icon_image_alt_text', 'all', 'default', '

Hostextinfo - icon image alt

\r\n

This variable is used to define an optional string that is used in the ALT tag of the image specified by the <icon_image> argument. The ALT tag is used in the status, extended information and statusmap CGIs.

\r\n

Parameter name: icon_image_alt
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(187, 'hostextinfo', 'notes_url', 'all', 'default', '

Hostextinfo - notes url

\r\n

This variable is used to define an optional URL that can be used to provide more information about the host. If you specify an URL, you will see a link that says "Extra Host Notes" in the extended information CGI (when you are viewing information about the specified host). Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the host, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(188, 'hostextinfo', 'vrml_image', 'all', 'default', '

Hostextinfo - vrml image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this host. This image will be used as the texture map for the specified host in the statuswrl CGI. Unlike the image you use for the icon_image variable, this one should probably not have any transparency. If it does, the host object will look a bit wierd.

\r\n

Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: vrml_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(189, 'hostextinfo', 'action_url', 'all', 'default', '

Hostextinfo - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the host. If you specify an URL, you will see a link that says "Extra Host Actions" in the extended information CGI (when you are viewing information about the specified host). Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(190, 'hostextinfo', 'status_image', 'all', 'default', '

Hostextinfo - statusmap image

\r\n

This variable is used to define the name of an image that should be associated with this host in the statusmap CGI. You can specify a JPEG, PNG, and GIF image if you want, although I would strongly suggest using a GD2 format image, as other image formats will result in a lot of wasted CPU time when the statusmap image is generated.

\r\n

GD2 images can be created from PNG images by using the pngtogd2 utility supplied with Thomas Boutell''s gd library. The GD2 images should be created in uncompressed format in order to minimize CPU load when the statusmap CGI is generating the network map image.

\r\n

The image will look best if it is 40x40 pixels in size. You can leave these option blank if you are not using the statusmap CGI. Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: statusmap_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(191, 'hostextinfo', '2d_coords', 'all', 'default', '

Hostextinfo - 2d coords

\r\n

This variable is used to define coordinates to use when drawing the host in the statusmap CGI. Coordinates should be given in positive integers, as they correspond to physical pixels in the generated image. The origin for drawing (0,0) is in the upper left hand corner of the image and extends in the positive x direction (to the right) along the top of the image and in the positive y direction (down) along the left hand side of the image. For reference, the size of the icons drawn is usually about 40x40 pixels (text takes a little extra space). The coordinates you specify here are for the upper left hand corner of the host icon that is drawn.

\r\n

Note: Don''t worry about what the maximum x and y coordinates that you can use are. The CGI will automatically calculate the maximum dimensions of the image it creates based on the largest x and y coordinates you specify.

\r\n

Parameter name: 2d_coords
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(192, 'hostextinfo', '3d_coords', 'all', 'default', '

Hostextinfo - 3d coords

\r\n

This variable is used to define coordinates to use when drawing the host in the statuswrl CGI. Coordinates can be positive or negative real numbers. The origin for drawing is (0.0,0.0,0.0). For reference, the size of the host cubes drawn is 0.5 units on each side (text takes a little more space). The coordinates you specify here are used as the center of the host cube.

\r\n

Parameter name: 3d_coords
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(193, 'serviceescalation', 'host', 'all', 'default', '

Serviceescalation - host name

\r\n

This directive is used to identify the short name(s) of the host(s) that the service escalation should apply to or is associated with.

\r\n

Parameter name: host_name
Required: yes (no, if a hostgroup name is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(194, 'serviceescalation', 'hostgroup', 'all', 'default', '

Serviceescalation - hostgroup name

\r\n

This directive is used to specify the short name(s) of the hostgroup(s) that the service escalation should apply to or is associated with. Multiple hostgroups should be separated by commas. The hostgroup_name may be used instead of, or in addition to, the host_name directive.

\r\n

Parameter name: hostgroup_name
Required: yes (no, if a host name is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(195, 'serviceescalation', 'contact', 'all', 'default', '

Serviceescalation - contacts

\r\n

This is a list of the short names of the contacts that should be notified whenever there are problems (or recoveries) with this service. Multiple contacts should be separated by commas. Useful if you want notifications to go to just a few people and don''t want to configure contact groups. You must specify at least one contact or contact group in each service escalation definition.

\r\n

Parameter name: contacts
Required: yes (no, if a contact group is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(196, 'serviceescalation', 'contactgroup', 'all', 'default', '

Serviceescalation - contact groups

\r\n

This directive is used to identify the short name of the contact group that should be notified when the service notification is escalated. Multiple contact groups should be separated by commas. You must specify at least one contact or contact group in each service escalation definition.

\r\n

Parameter name: contact_groups
Required: yes (no, if a contact is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(197, 'serviceescalation', 'config_name', 'all', 'default', '

Serviceescalation - config name

\r\n

This directive is used to specify a common config name for a serviceescalation configration. This is a NagiosQL parameter and it will not be written to the configuration file.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(198, 'serviceescalation', 'service', 'all', 'default', '

Serviceescalation - service description

\r\n

This directive is used to identify the description of the service the escalation should apply to.

\r\n

Parameter name: service_description
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(199, 'serviceescalation', 'first_notification', 'all', 'default', '

Serviceescalation - first notification

\r\n

This directive is a number that identifies the first notification for which this escalation is effective. For instance, if you set this value to 3, this escalation will only be used if the service is in a non-OK state long enough for a third notification to go out.

\r\n

Parameter name: first_notification
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(200, 'serviceescalation', 'last_notification', 'all', 'default', '

Serviceescalation - last notification

\r\n

This directive is a number that identifies the last notification for which this escalation is effective. For instance, if you set this value to 5, this escalation will not be used if more than five notifications are sent out for the service. Setting this value to 0 means to keep using this escalation entry forever (no matter how many notifications go out).

\r\n

Parameter name: last_notification
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(201, 'serviceescalation', 'notification_intervall', 'all', 'default', '

Serviceescalation - notification interval

\r\n

This directive is used to determine the interval at which notifications should be made while this escalation is valid. If you specify a value of 0 for the interval, Nagios will send the first notification when this escalation definition is valid, but will then prevent any more problem notifications from being sent out for the host. Notifications are sent out again until the host recovers.

\r\n

This is useful if you want to stop having notifications sent out after a certain amount of time. Note: If multiple escalation entries for a host overlap for one or more notification ranges, the smallest notification interval from all escalation entries is used.

\r\n

Parameter name: notification_interval
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(202, 'serviceescalation', 'escalation_period', 'all', 'default', '

Serviceescalation - escalation period

\r\n

This directive is used to specify the short name of the time period during which this escalation is valid. If this directive is not specified, the escalation is considered to be valid during all times.

\r\n

Parameter name: escalation_period
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(203, 'serviceescalation', 'escalation_options', 'all', 'default', '

Serviceescalation - escalation options

\r\n

This directive is used to define the criteria that determine when this service escalation is used. The escalation is used only if the service is in one of the states specified in this directive. If this directive is not specified in a service escalation, the escalation is considered to be valid during all service states. Valid options are a combination of one or more of the following:
r
= escalate on an OK (recovery) state,
w = escalate on a WARNING state,
u
= escalate on an UNKNOWN state, and
c = escalate on a CRITICAL state.

\r\n

Example: If you specify w in this field, the escalation will only be used if the service is in a WARNING state.

\r\n

Parameter name: escalation_options
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(204, 'servicedependency', 'dependent_host', 'all', 'default', '

Servicedependency - dependent host

\r\n

This directive is used to identify the short name(s) of the host(s) that the dependent service "runs" on or is associated with. Multiple hosts should be separated by commas. Leaving this directive blank can be used to create "same host" dependencies.

\r\n

Parameter name: dependent_host
Required: yes (no, if a dependent hostgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(205, 'servicedependency', 'host', 'all', 'default', '

Servicedependency - host name

\r\n

This directive is used to identify the short name(s) of the host(s) that the service that is being depended upon (also referred to as the master service) "runs" on or is associated with. Multiple hosts should be separated by commas.

\r\n

Parameter name: host_name
Required: yes (no, if a hostgroup is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(206, 'servicedependency', 'dependent_hostgroup', 'all', 'default', '

Servicedependency - dependent hostgroup

\r\n

This directive is used to specify the short name(s) of the hostgroup(s) that the dependent service "runs" on or is associated with. Multiple hostgroups should be separated by commas. The dependent_hostgroup may be used instead of, or in addition to, the dependent_host directive.

\r\n

Parameter name: dependent_hostgroup
Required: yes (no, if a dependent host is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(207, 'servicedependency', 'hostgroup', 'all', 'default', '

Servicedependency - hostgroup name

\r\n

This directive is used to identify the short name(s) of the hostgroup(s) that the service that is being depended upon (also referred to as the master service) "runs" on or is associated with. Multiple hostgroups should be separated by commas. The hostgroup_name may be used instead of, or in addition to, the host_name directive.

\r\n

Parameter name: hostgroup_name
Required: yes (no, if a host is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(208, 'servicedependency', 'dependent_services', 'all', 'default', '

Servicedependency - dependent service description

\r\n

This directive is used to identify the description of the dependent service.

\r\n

Parameter name: dependent_service_description
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(209, 'servicedependency', 'services', 'all', 'default', '

Servicedependency - service description

\r\n

This directive is used to identify the description of the service that is being depended upon (also referred to as the master service).

\r\n

Parameter name: service_description
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(210, 'servicedependency', 'config_name', 'all', 'default', '

Servicedependency - config name

\r\n

This directive is used to specify a common config name for a servicedependency configration. This is a NagiosQL parameter and it will not be written to the configuration file.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(211, 'servicedependency', 'inherit_parents', 'all', 'default', '

Servicedependency - inherits parent

\r\n

This directive indicates whether or not the dependency inherits dependencies of the service that is being depended upon (also referred to as the master service). In other words, if the master service is dependent upon other services and any one of those dependencies fail, this dependency will also fail.

\r\n

Parameter name: inherits_parent
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(212, 'servicedependency', 'dependency_period', 'all', 'default', '

Servicedependency - dependency period

\r\n

This directive is used to specify the short name of the time period during which this dependency is valid. If this directive is not specified, the dependency is considered to be valid during all times.

\r\n

Parameter name: dependency_period
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(213, 'servicedependency', 'execution_failure_criteria', 'all', 'default', '

Servicedependency - execution failure criteria

\r\n

This directive is used to specify the criteria that determine when the dependent service should not be actively checked. If the master service is in one of the failure states we specify, the dependent service will not be actively checked. Valid options are a combination of one or more of the following (multiple options are separated with commas):
o = fail on an OK state,
w = fail on a WARNING state,
u
= fail on an UNKNOWN state,
c = fail on a CRITICAL state, and
p = fail on a pending state (e.g. the service has not yet been checked).
If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be).

\r\n

Example: If you specify o,c,u in this field, the dependent service will not be actively checked if the master service is in either an OK, a CRITICAL, or an UNKNOWN state.

\r\n

Parameter name: execution_failure_criteria
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(214, 'servicedependency', 'notification_failure_criteria', 'all', 'default', '

Servicedependency - notification failure criteria

\r\n

This directive is used to define the criteria that determine when notifications for the dependent service should not be sent out. If the master service is in one of the failure states we specify, notifications for the dependent service will not be sent to contacts. Valid options are a combination of one or more of the following:
o
= fail on an OK state,
w = fail on a WARNING state,
u
= fail on an UNKNOWN state,
c = fail on a CRITICAL state, and
p = fail on a pending state (e.g. the service has not yet been checked).
If you specify n (none) as an option, the notification dependency will never fail and notifications for the dependent service will always be sent out.

\r\n

Example: If you specify w in this field, the notifications for the dependent service will not be sent out if the master service is in a WARNING state.

\r\n

Parameter name: notification_failure_criteria
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(216, 'serviceextinfo', 'host_name', 'all', 'default', '

Serviceextinfo - host name

\r\n

This directive is used to identify the short name of the host that the service is associated with.

\r\n

Parameter name: host_name
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(217, 'serviceextinfo', 'icon_image', 'all', 'default', '

Serviceextinfo - icon image

\r\n

This variable is used to define the name of a GIF, PNG, or JPG image that should be associated with this host. This image will be displayed in the status and extended information CGIs.

\r\n

The image will look best if it is 40x40 pixels in size. Images for hosts are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

Parameter name: icon_image
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(218, 'serviceextinfo', 'service_description', 'all', 'default', '

Serviceextinfo - service description

\r\n

This directive is description of the service which the data is associated with.

\r\n

Parameter name: service_description
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(219, 'serviceextinfo', 'notes', 'all', 'default', '

Serviceextinfo - notes

\r\n

This directive is used to define an optional string of notes pertaining to the service. If you specify a note here, you will see the it in the extended information CGI (when you are viewing information about the specified service).

\r\n

Parameter name: notes
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(220, 'serviceextinfo', 'action_url', 'all', 'default', '

Serviceextinfo - action url

\r\n

This directive is used to define an optional URL that can be used to provide more actions to be performed on the service. If you specify an URL, you will see a link that says "Extra Service Actions" in the extended information CGI (when you are viewing information about the specified service). Any valid URL can be used. If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

\r\n

Parameter name: action_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(221, 'serviceextinfo', 'notes_url', 'all', 'default', '

Serviceextinfo - notes url

\r\n

This directive is used to define an optional URL that can be used to provide more information about the service. If you specify an URL, you will see a link that says "Extra Service Notes" in the extended information CGI (when you are viewing information about the specified service). Any valid URL can be used.

\r\n

If you plan on using relative paths, the base path will the the same as what is used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want to make detailed information on the service, emergency contact methods, etc. available to other support staff.

\r\n

Parameter name: notes_url
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(222, 'serviceextinfo', 'icon_image_alt', 'all', 'default', '

Serviceextinfo - icon image alt

\r\n

This variable is used to define an optional string that is used in the ALT tag of the image specified by the <icon_image> argument. The ALT tag is used in the status, extended information and statusmap CGIs.

\r\n

Parameter name: icon_image_alt
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(223, 'host', 'services', 'all', 'default', '

Host - service settings

\r\n

This box can be used to allocate already existing services to a host. 

\r\n

This is an internal function of NagiosQL.

\r\n

Note: To activate the changes, the corresponding service definitions have to be rewritten!

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(224, 'timeperiod', 'name', 'all', 'default', '

Timeperiod - name

\r\n

Its just a "template" name that can be referenced in other object definitions so they can inherit the objects properties/variables. Template names must be unique amongst objects of the same type, so you can''t have two or more time definitions that have "mytemplate" as their template name.

\r\n

Parameter name: name
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(225, 'timeperiod', 'include', '3', 'default', '

Timeperiod - include

\r\n

This directive is used to specify the short names (template names) of other timeperiod definitions whose time ranges should be included to this timeperiod. Multiple timeperiod names should be separated with a comma.

\r\n

Parameter name: use
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(226, 'user', 'adminenable', 'all', 'default', '

User - enable group administration

\r\n

If this option is selected, the specified user is able to modify the access group for every object definition. This should be restricted only to administrators; otherwise a user might be able to lock himself out.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(227, 'group', 'userrights', 'all', 'default', '

Group - user rights

\r\n

Define the object access rights for a user.

\r\n

READ = The user can see the objects belong to this group
WRITE = The user can modify the objects belong to this group
LINK = The user can use the objects belong to this group to link them in other objects*

* Example: If a time object belongs to this group - the user can add (link) this time object to his contact objects.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(228, 'domain', 'conffile', 'all', 'default', '

Absolute path to your Nagios config file.

Examples:
/etc/nagios/nagios.cfg
/usr/local/nagios/etc/nagios.cfg

This is used to verify your Nagios configuration directly from NagiosQL.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(229, 'domain', 'enable_common', 'all', 'default', '

This option is used to enable or disable the global common domain functionality.

\r\n

If this option is enabled, all objects from the global common domain will be added to this domains configuration files. The global common domain can be used to define objects like timeperiods or contacts that are used in all domains the same.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(230, 'domain', 'utf8_decode', 'all', 'default', '

This is an experimental option!

\r\n

If this option is enabled, UTF8 data from database will be translated to ISO in configuration file. So, the configuration files will be in ISO mode. This could be helpful, if nagios does not understand the UTF8 data from NagiosQL.

\r\n

Tested only with western european configurations!

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(231, 'domain', 'picturedir', 'all', 'default', '

Relative path to your nagios icon images.

Example:
/my/own/images/

\r\n

This path is based on your nagios standard image path. Images are assumed to be in the logos/ subdirectory in your HTML images directory (i.e. /usr/local/nagios/share/images/logos).

\r\n

So in the example above, the images are located in:

\r\n

/usr/local/nagios/share/images/logos/my/own/images/

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(232, 'common', 'accessgroup', 'all', 'default', '

Access group

\r\n

Select an access group name to restrict this object to the group members.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(233, 'common', 'registered', 'all', 'default', '

Register

\r\n

This variable is used to indicate whether or not the object definition should be "registered" with Nagios. By default, all object definitions are registered. If you are using a partial object definition as a template, you would want to prevent it from being registered (an example of this is provided later). Values are as follows: 0 = do NOT register object definition, 1 = register object definition (this is the default). This variable is NOT inherited; every (partial) object definition used as a template must explicitly set the register directive to be 0. This prevents the need to override an inherited register directive with a value of 1 for every object that should be registered.

\r\n

Parameter name: register
Required: yes

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(234, 'servicedependency', 'dependent_servicegroup_name', 'all', 'default', '

Servicedependency - dependent servicegroup name

\r\n

This directive is used to identify the name of the dependent servicegroup.

\r\n

Parameter name: dependent_servicegroup_name
Required: yes (no, if a dependent service is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(235, 'servicedependency', 'servicegroup_name', 'all', 'default', '

Servicedependency - servicegroup name

\r\n

This directive is used to identify the name of the servicegroup that is being depended upon (also referred to as the master service).

\r\n

Parameter name: servicegroup_name
Required: yes (no, if a service is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(236, 'serviceescalation', 'servicegroup', 'all', 'default', '

Serviceescalation - servicegroup name

\r\n

This directive is used to identify the name of the servicegroup the escalation should apply to.

\r\n

Parameter name: servicegroup_name
Required: yes (no, if a service is defined)

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(237, 'user', 'language', 'all', 'default', '

User - language

\r\n

Defines a default UI language for the user.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(238, 'user', 'standarddomain', 'all', 'default', '

User - standard domain

\r\n

Defines a standard domain for the user. After the user has logged in, the defined domain is pre-selected.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(239, 'domain', 'targets', 'all', 'default', '

Select a configuration domain which is assigned to this data domain

\r\n

The settings where to store the configuration files are defined in a configuration domain. Select here the desired target for your configuration files.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(240, 'domain', 'ssh_host_key', 'all', 'default', 'Absolute path to the ssh key directory for the defined ssh user.

Examples:
/etc/nagiosql/ssh/
/usr/local/nagios/etc/.ssh/

This directory includes the key file (id_rsa) for the user to connect to the remote system. Note, that the file name is set to id_rsa!'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(241, 'contact', 'minimum_importance', 'all', 'default', '

Contact - minimum importance

\r\n

This directive is used as the value that the host or service importance value must equal before notification is sent to this contact. The importance values are intended to represent the value of a host or service to an organization. For example, you could set this value and the importance value of a host such that a system administrator would be notified when a development server goes down, but the CIO would only be notified when the company\'s production ecommerce database server was down. The minimum_importance value defaults to zero.

\r\n

In Nagios Core 4.0.0 to 4.0.3 this was known as minimum_value but has been replaced with minimum_importance.

\r\n

Parameter name: minimum_importance
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(242, 'domain', 'ftps_option', 'all', 'default', 'Use encrypted FTP (FTPS) to connect to the remote server. '); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(243, 'domain', 'cgifile', 'all', 'default', '

Absolute path to your Nagios CGI config file.

Examples:
/etc/nagios/cgi.cfg
/usr/local/nagios/etc/cgi.cfg

This is used to edit Nagios website options directly from NagiosQL.

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(244, 'domain', 'resourcefile', 'all', 'default', '

Absolute path to your Nagios resource config file.

Examples:
/etc/nagios/resource.cfg
/usr/local/nagios/etc/resource.cfg

This file is used to verify your configuration in Nagios 4.x. Be sure this file is readably by your webserver\'s user!

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(245, 'host', 'importance', 'all', 'default', '

Host - importance

This directive is used to represent the importance of the host to your organization. The importance is used when determining whether to send notifications to a contact. If the host\'s importance value plus the importance values of all of the host\'s services is greater than or equal to the contact\'s minimum_importance, the contact will be notified. For example, you could set this value and the minimum_importance of contacts such that a system administrator would be notified when a development server goes down, but the CIO would only be notified when the company\'s production ecommerce database server was down. The importance could also be used as a sort criteria when generating reports or for calculating a good system administrator\'s bonus. The importance value defaults to zero. In Nagios Core 4.0.0 to 4.0.3 this was known as hourly_value but has been replaced with importance.

Parameter name: importance
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(246, 'service', 'importance', 'all', 'default', '

Service - importance

\r\n

This directive is used to represent the importance of the service to your organization. The importance is used when determining whether to send notifications to a contact. If the service\'s importance value is greater than or equal to the contact\'s minimum_importance, the contact will be notified. For example, you could set this value and the minimum_importance of contacts such that a system administrator would be notified of a disk full event on a development server, but the CIO would only be notified when the company\'s production ecommerce database was down. The importance could also be used as a sort criteria when generating reports or for calculating a good system administrator\'s bonus. The importance value defaults to zero. In Nagios Core 4.0.0 to 4.0.3 this was known as hourly_value but has been replaced with importance.

\r\n

Parameter name: importance
Required: no

'); INSERT INTO `tbl_info` (`id`, `key1`, `key2`, `version`, `language`, `infotext`) VALUES(247, 'service', 'parents', 'all', 'default', '

Service - parents

\r\n

This directive is used to define a comma-delimited list of short names of the \"parent\" services for this particular service. Parent services are typically other services that need to be available in order for a check of this service to occur. For example, if a service checks the status of a disk using SSH, the disk check service would have the SSH service as a parent. If the service has no parent services, simply omit the \"parents\" directive. More complex service dependencies may be specified with service dependency objects.

\r\n

Parameter name: parents
Required: no

'); -- -------------------------------------------------------- -- -- Structure for table `tbl_language` -- CREATE TABLE IF NOT EXISTS `tbl_language` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `language` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `locale` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL, `last_modified` datetime NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_language` -- INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(1, 'English', 'en_GB', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(2, 'German', 'de_DE', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(3, 'Chinese (Simplified)', 'zh_CN', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(5, 'Italian', 'it_IT', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(6, 'French', 'fr_FR', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(7, 'Russian', 'ru_RU', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(8, 'Spanish', 'es_ES', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(9, 'Portuguese (Brazilian)', 'pt_BR', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(11, 'Dutch', 'nl_NL', '1', NOW()); INSERT INTO `tbl_language` (`id`, `language`, `locale`, `active`, `last_modified`) VALUES(13, 'Danish', 'da_DK', '1', NOW()); -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactgroupToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactgroupToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactgroupToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactgroupToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactgroupToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactgroupToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContacttemplateToCommandHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContacttemplateToCommandHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContacttemplateToCommandHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContacttemplateToCommandService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContacttemplateToCommandService` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContacttemplateToCommandService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContacttemplateToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContacttemplateToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContacttemplateToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContacttemplateToContacttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContacttemplateToContacttemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContacttemplateToContacttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContacttemplateToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContacttemplateToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContacttemplateToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactToCommandHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactToCommandHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactToCommandHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactToCommandService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactToCommandService` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactToCommandService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactToContacttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactToContacttemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactToContacttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkContactToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkContactToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkContactToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkGroupToUser` -- CREATE TABLE IF NOT EXISTS `tbl_lnkGroupToUser` ( `idMaster` int(10) unsigned NOT NULL, `idSlave` int(10) unsigned NOT NULL, `read` enum('0','1') NOT NULL DEFAULT '1', `write` enum('0','1') NOT NULL DEFAULT '1', `link` enum('0','1') NOT NULL DEFAULT '1', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkGroupToUser` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostdependencyToHostgroup_DH` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostdependencyToHostgroup_DH` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostdependencyToHostgroup_DH` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostdependencyToHostgroup_H` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostdependencyToHostgroup_H` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostdependencyToHostgroup_H` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostdependencyToHost_DH` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostdependencyToHost_DH` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostdependencyToHost_DH` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostdependencyToHost_H` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostdependencyToHost_H` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostdependencyToHost_H` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostescalationToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostescalationToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostescalationToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostescalationToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostescalationToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostescalationToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostescalationToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostescalationToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostescalationToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostescalationToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostescalationToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostescalationToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostgroupToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostgroupToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostgroupToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostgroupToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostgroupToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostgroupToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToHosttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToHosttemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToHosttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHosttemplateToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHosttemplateToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHosttemplateToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToHosttemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToHosttemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToHosttemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkHostToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkHostToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkHostToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToHostgroup_DH` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToHostgroup_DH` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToHostgroup_DH` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToHostgroup_H` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToHostgroup_H` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToHostgroup_H` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToHost_DH` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToHost_DH` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToHost_DH` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToHost_H` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToHost_H` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToHost_H` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToService_DS` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToService_DS` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `strSlave` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToService_DS` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToService_S` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToService_S` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `strSlave` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToService_S` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToServicegroup_DS` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToServicegroup_DS` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToServicegroup_DS` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicedependencyToServicegroup_S` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicedependencyToServicegroup_S` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicedependencyToServicegroup_S` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToService` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `strSlave` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceescalationToServicegroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceescalationToServicegroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceescalationToService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicegroupToService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicegroupToService` ( `idMaster` int(11) NOT NULL, `idSlaveH` int(11) NOT NULL, `idSlaveHG` int(11) NOT NULL, `idSlaveS` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlaveH`,`idSlaveHG`,`idSlaveS`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicegroupToService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicegroupToServicegroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicegroupToServicegroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicegroupToServicegroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToService` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idHost` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToServicegroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToServicegroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToServicegroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToServicetemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToServicetemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToServicetemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServicetemplateToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServicetemplateToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServicetemplateToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToContact` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToContact` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToContact` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToContactgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToContactgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToContactgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToHost` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToHost` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToHost` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToHostgroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToHostgroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToHostgroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToService` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToService` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idHost` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToService` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToServicegroup` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToServicegroup` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToServicegroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToServicetemplate` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToServicetemplate` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `idSort` int(11) NOT NULL, `idTable` tinyint(4) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`,`idTable`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToServicetemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkServiceToVariabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_lnkServiceToVariabledefinition` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkServiceToVariabledefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkTimeperiodToTimeperiod` -- CREATE TABLE IF NOT EXISTS `tbl_lnkTimeperiodToTimeperiod` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkTimeperiodToTimeperiod` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_lnkTimeperiodToTimeperiodUse` -- CREATE TABLE IF NOT EXISTS `tbl_lnkTimeperiodToTimeperiodUse` ( `idMaster` int(11) NOT NULL, `idSlave` int(11) NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`idMaster`,`idSlave`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Datasets for table `tbl_lnkTimeperiodToTimeperiodUse` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_logbook` -- CREATE TABLE IF NOT EXISTS `tbl_logbook` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `time` datetime NOT NULL, `user` varchar(255) NOT NULL, `ipadress` varchar(255) NOT NULL, `domain` varchar(255) NOT NULL, `entry` tinytext NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_logbook` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_menu` -- CREATE TABLE IF NOT EXISTS `tbl_menu` ( `mnuId` int(10) unsigned NOT NULL AUTO_INCREMENT, `mnuTopId` int(10) unsigned NOT NULL, `mnuGrpId` int(10) unsigned NOT NULL DEFAULT '0', `mnuCntId` int(10) unsigned NOT NULL, `mnuName` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `mnuLink` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `mnuActive` tinyint(3) unsigned NOT NULL DEFAULT '1', `mnuOrderId` int(10) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`mnuId`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_menu` -- INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(1, 0, 0, 1, 'Main page', 'admin.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(2, 0, 0, 1, 'Supervision', 'admin/monitoring.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(3, 0, 0, 1, 'Alarming', 'admin/alarming.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(4, 0, 0, 1, 'Commands', 'admin/commands.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(5, 0, 0, 1, 'Specialties', 'admin/specials.php', 1, 5); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(6, 0, 0, 1, 'Tools', 'admin/tools.php', 1, 6); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(7, 0, 0, 1, 'Administration', 'admin/administration.php', 1, 7); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(8, 2, 0, 1, 'Host', 'admin/hosts.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(9, 2, 0, 1, 'Services', 'admin/services.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(10, 2, 0, 1, 'Host groups', 'admin/hostgroups.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(11, 2, 0, 1, 'Service groups', 'admin/servicegroups.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(12, 2, 0, 1, 'Host templates', 'admin/hosttemplates.php', 1, 5); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(13, 2, 0, 1, 'Service templates', 'admin/servicetemplates.php', 1, 6); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(14, 3, 0, 1, 'Contact data', 'admin/contacts.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(15, 3, 0, 1, 'Contact groups', 'admin/contactgroups.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(16, 3, 0, 1, 'Time periods', 'admin/timeperiods.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(17, 3, 0, 1, 'Contact templates', 'admin/contacttemplates.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(18, 4, 0, 1, 'Definitions', 'admin/checkcommands.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(19, 5, 0, 1, 'Host dependency', 'admin/hostdependencies.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(20, 5, 0, 1, 'Host escalation', 'admin/hostescalations.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(21, 5, 0, 1, 'Extended Host', 'admin/hostextinfo.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(22, 5, 0, 1, 'Service dependency', 'admin/servicedependencies.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(23, 5, 0, 1, 'Service escalation', 'admin/serviceescalations.php', 1, 5); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(24, 5, 0, 1, 'Extended Service', 'admin/serviceextinfo.php', 1, 6); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(25, 6, 0, 1, 'Data import', 'admin/import.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(26, 6, 0, 1, 'Delete backup files', 'admin/delbackup.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(27, 6, 0, 1, 'Delete config files', 'admin/delconfig.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(28, 6, 0, 1, 'Nagios config', 'admin/nagioscfg.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(29, 6, 0, 1, 'CGI config', 'admin/cgicfg.php', 1, 5); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(30, 6, 0, 1, 'Nagios control', 'admin/verify.php', 1, 6); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(31, 7, 0, 1, 'New password', 'admin/password.php', 1, 1); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(32, 7, 0, 1, 'User admin', 'admin/user.php', 1, 2); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(33, 7, 0, 1, 'Group admin', 'admin/group.php', 1, 3); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(34, 7, 0, 1, 'Menu access', 'admin/menuaccess.php', 1, 4); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(35, 7, 0, 1, 'Data domains', 'admin/datadomain.php', 1, 5); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(36, 7, 0, 1, 'Config targets', 'admin/configtargets.php', 1, 6); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(37, 7, 0, 1, 'Logbook', 'admin/logbook.php', 1, 7); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(38, 7, 0, 1, 'Settings', 'admin/settings.php', 1, 8); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(39, 7, 0, 1, 'Help editor', 'admin/helpedit.php', 1, 9); INSERT INTO `tbl_menu` (`mnuId`, `mnuTopId`, `mnuGrpId`, `mnuCntId`, `mnuName`, `mnuLink`, `mnuActive`, `mnuOrderId`) VALUES(40, 7, 0, 1, 'Support', 'admin/support.php', 1, 10); -- -------------------------------------------------------- -- -- Structure for table `tbl_relationinformation` -- CREATE TABLE IF NOT EXISTS `tbl_relationinformation` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `master` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `tableName1` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `tableName2` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `fieldName` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `linkTable` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `target1` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `target2` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `targetKey` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `fullRelation` tinyint(3) unsigned NOT NULL DEFAULT '0', `flags` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `type` tinyint(3) unsigned NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_relationinformation` -- INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(1, 'tbl_timeperiod', 'tbl_timeperiod', '', 'exclude', 'tbl_lnkTimeperiodToTimeperiod', 'timeperiod_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(2, 'tbl_contact', 'tbl_command', '', 'host_notification_commands', 'tbl_lnkContactToCommandHost', 'command_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(3, 'tbl_contact', 'tbl_command', '', 'service_notification_commands', 'tbl_lnkContactToCommandService', 'command_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(4, 'tbl_contact', 'tbl_contactgroup', '', 'contactgroups', 'tbl_lnkContactToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(5, 'tbl_contact', 'tbl_timeperiod', '', 'host_notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(6, 'tbl_contact', 'tbl_timeperiod', '', 'service_notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(7, 'tbl_contact', 'tbl_contacttemplate', 'tbl_contact', 'use_template', 'tbl_lnkContactToContacttemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(8, 'tbl_contact', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkContactToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(9, 'tbl_contacttemplate', 'tbl_command', '', 'host_notification_commands', 'tbl_lnkContacttemplateToCommandHost', 'command_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(10, 'tbl_contacttemplate', 'tbl_command', '', 'service_notification_commands', 'tbl_lnkContacttemplateToCommandService', 'command_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(11, 'tbl_contacttemplate', 'tbl_contactgroup', '', 'contactgroups', 'tbl_lnkContacttemplateToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(12, 'tbl_contacttemplate', 'tbl_timeperiod', '', 'host_notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(13, 'tbl_contacttemplate', 'tbl_timeperiod', '', 'service_notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(14, 'tbl_contacttemplate', 'tbl_contacttemplate', 'tbl_contact', 'use_template', 'tbl_lnkContacttemplateToContacttemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(15, 'tbl_contacttemplate', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkContacttemplateToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(16, 'tbl_contactgroup', 'tbl_contact', '', 'members', 'tbl_lnkContactgroupToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(17, 'tbl_contactgroup', 'tbl_contactgroup', '', 'contactgroup_members', 'tbl_lnkContactgroupToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(18, 'tbl_hosttemplate', 'tbl_host', '', 'parents', 'tbl_lnkHosttemplateToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(19, 'tbl_hosttemplate', 'tbl_hostgroup', '', 'hostgroups', 'tbl_lnkHosttemplateToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(20, 'tbl_hosttemplate', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkHosttemplateToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(21, 'tbl_hosttemplate', 'tbl_contact', '', 'contacts', 'tbl_lnkHosttemplateToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(22, 'tbl_hosttemplate', 'tbl_timeperiod', '', 'check_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(23, 'tbl_hosttemplate', 'tbl_command', '', 'check_command', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(24, 'tbl_hosttemplate', 'tbl_timeperiod', '', 'notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(25, 'tbl_hosttemplate', 'tbl_command', '', 'event_handler', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(26, 'tbl_hosttemplate', 'tbl_hosttemplate', 'tbl_host', 'use_template', 'tbl_lnkHosttemplateToHosttemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(27, 'tbl_hosttemplate', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkHosttemplateToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(28, 'tbl_host', 'tbl_host', '', 'parents', 'tbl_lnkHostToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(29, 'tbl_host', 'tbl_hostgroup', '', 'hostgroups', 'tbl_lnkHostToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(30, 'tbl_host', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkHostToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(31, 'tbl_host', 'tbl_contact', '', 'contacts', 'tbl_lnkHostToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(32, 'tbl_host', 'tbl_timeperiod', '', 'check_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(33, 'tbl_host', 'tbl_command', '', 'check_command', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(34, 'tbl_host', 'tbl_timeperiod', '', 'notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(35, 'tbl_host', 'tbl_command', '', 'event_handler', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(36, 'tbl_host', 'tbl_hosttemplate', 'tbl_host', 'use_template', 'tbl_lnkHostToHosttemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(37, 'tbl_host', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkHostToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(38, 'tbl_hostgroup', 'tbl_host', '', 'members', 'tbl_lnkHostgroupToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(39, 'tbl_hostgroup', 'tbl_hostgroup', '', 'hostgroup_members', 'tbl_lnkHostgroupToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(40, 'tbl_servicetemplate', 'tbl_host', '', 'host_name', 'tbl_lnkServicetemplateToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(41, 'tbl_servicetemplate', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkServicetemplateToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(42, 'tbl_servicetemplate', 'tbl_servicegroup', '', 'servicegroups', 'tbl_lnkServicetemplateToServicegroup', 'servicegroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(43, 'tbl_servicetemplate', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkServicetemplateToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(44, 'tbl_servicetemplate', 'tbl_contact', '', 'contacts', 'tbl_lnkServicetemplateToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(45, 'tbl_servicetemplate', 'tbl_timeperiod', '', 'check_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(46, 'tbl_servicetemplate', 'tbl_command', '', 'check_command', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(47, 'tbl_servicetemplate', 'tbl_timeperiod', '', 'notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(48, 'tbl_servicetemplate', 'tbl_command', '', 'event_handler', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(49, 'tbl_servicetemplate', 'tbl_servicetemplate', 'tbl_service', 'use_template', 'tbl_lnkServicetemplateToServicetemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(50, 'tbl_servicetemplate', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkServicetemplateToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(51, 'tbl_service', 'tbl_host', '', 'host_name', 'tbl_lnkServiceToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(52, 'tbl_service', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkServiceToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(53, 'tbl_service', 'tbl_servicegroup', '', 'servicegroups', 'tbl_lnkServiceToServicegroup', 'servicegroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(54, 'tbl_service', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkServiceToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(55, 'tbl_service', 'tbl_contact', '', 'contacts', 'tbl_lnkServiceToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(56, 'tbl_service', 'tbl_timeperiod', '', 'check_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(57, 'tbl_service', 'tbl_command', '', 'check_command', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(58, 'tbl_service', 'tbl_timeperiod', '', 'notification_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(59, 'tbl_service', 'tbl_command', '', 'event_handler', '', 'command_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(60, 'tbl_service', 'tbl_servicetemplate', 'tbl_service', 'use_template', 'tbl_lnkServiceToServicetemplate', 'template_name', 'name', '', 0, '', 3); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(61, 'tbl_service', 'tbl_variabledefinition', '', 'use_variables', 'tbl_lnkServiceToVariabledefinition', 'name', '', '', 0, '', 4); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(62, 'tbl_servicegroup', 'tbl_host', 'tbl_service', 'members', 'tbl_lnkServicegroupToService', 'host_name', 'service_description', '', 0, '', 5); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(63, 'tbl_servicegroup', 'tbl_servicegroup', '', 'servicegroup_members', 'tbl_lnkServicegroupToServicegroup', 'servicegroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(64, 'tbl_hostdependency', 'tbl_host', '', 'dependent_host_name', 'tbl_lnkHostdependencyToHost_DH', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(65, 'tbl_hostdependency', 'tbl_host', '', 'host_name', 'tbl_lnkHostdependencyToHost_H', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(66, 'tbl_hostdependency', 'tbl_hostgroup', '', 'dependent_hostgroup_name', 'tbl_lnkHostdependencyToHostgroup_DH', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(67, 'tbl_hostdependency', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkHostdependencyToHostgroup_H', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(68, 'tbl_hostdependency', 'tbl_timeperiod', '', 'dependency_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(69, 'tbl_hostescalation', 'tbl_host', '', 'host_name', 'tbl_lnkHostescalationToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(70, 'tbl_hostescalation', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkHostescalationToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(71, 'tbl_hostescalation', 'tbl_contact', '', 'contacts', 'tbl_lnkHostescalationToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(72, 'tbl_hostescalation', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkHostescalationToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(73, 'tbl_hostescalation', 'tbl_timeperiod', '', 'escalation_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(74, 'tbl_hostextinfo', 'tbl_host', '', 'host_name', '', 'host_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(75, 'tbl_servicedependency', 'tbl_host', '', 'dependent_host_name', 'tbl_lnkServicedependencyToHost_DH', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(76, 'tbl_servicedependency', 'tbl_host', '', 'host_name', 'tbl_lnkServicedependencyToHost_H', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(77, 'tbl_servicedependency', 'tbl_hostgroup', '', 'dependent_hostgroup_name', 'tbl_lnkServicedependencyToHostgroup_DH', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(78, 'tbl_servicedependency', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkServicedependencyToHostgroup_H', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(79, 'tbl_servicedependency', 'tbl_service', '', 'dependent_service_description', 'tbl_lnkServicedependencyToService_DS', 'service_description', '', '', 0, '', 6); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(80, 'tbl_servicedependency', 'tbl_service', '', 'service_description', 'tbl_lnkServicedependencyToService_S', 'service_description', '', '', 0, '', 6); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(81, 'tbl_servicedependency', 'tbl_timeperiod', '', 'dependency_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(82, 'tbl_serviceescalation', 'tbl_host', '', 'host_name', 'tbl_lnkServiceescalationToHost', 'host_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(83, 'tbl_serviceescalation', 'tbl_hostgroup', '', 'hostgroup_name', 'tbl_lnkServiceescalationToHostgroup', 'hostgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(84, 'tbl_serviceescalation', 'tbl_service', '', 'service_description', 'tbl_lnkServiceescalationToService', 'service_description', '', '', 0, '', 6); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(85, 'tbl_serviceescalation', 'tbl_contact', '', 'contacts', 'tbl_lnkServiceescalationToContact', 'contact_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(86, 'tbl_serviceescalation', 'tbl_contactgroup', '', 'contact_groups', 'tbl_lnkServiceescalationToContactgroup', 'contactgroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(87, 'tbl_serviceescalation', 'tbl_timeperiod', '', 'escalation_period', '', 'timeperiod_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(88, 'tbl_serviceextinfo', 'tbl_host', '', 'host_name', '', 'host_name', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(89, 'tbl_serviceextinfo', 'tbl_service', '', 'service_description', '', 'service_description', '', '', 0, '', 1); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(90, 'tbl_command', 'tbl_lnkContacttemplateToCommandHost', '', 'idSlave', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(91, 'tbl_command', 'tbl_lnkContacttemplateToCommandService', '', 'idSlave', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(92, 'tbl_command', 'tbl_lnkContactToCommandHost', '', 'idSlave', '', 'tbl_contact', '', 'contact_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(93, 'tbl_command', 'tbl_lnkContactToCommandService', '', 'idSlave', '', 'tbl_contact', '', 'contact_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(94, 'tbl_command', 'tbl_host', '', 'check_command', '', '', '', 'host_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(95, 'tbl_command', 'tbl_host', '', 'event_handler', '', '', '', 'host_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(96, 'tbl_command', 'tbl_service', '', 'check_command', '', '', '', 'config_name,service_description', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(97, 'tbl_command', 'tbl_service', '', 'event_handler', '', '', '', 'config_name,service_description', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(98, 'tbl_contact', 'tbl_lnkContactgroupToContact', '', 'idSlave', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '1,2,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(99, 'tbl_contact', 'tbl_lnkContactToCommandHost', '', 'idMaster', '', 'tbl_command', '', 'command_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(100, 'tbl_contact', 'tbl_lnkContactToCommandService', '', 'idMaster', '', 'tbl_command', '', 'command_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(101, 'tbl_contact', 'tbl_lnkContactToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(102, 'tbl_contact', 'tbl_lnkContactToContacttemplate', '', 'idMaster', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(103, 'tbl_contact', 'tbl_lnkContactToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(104, 'tbl_contact', 'tbl_lnkHostescalationToContact', '', 'idSlave', '', 'tbl_hostescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(105, 'tbl_contact', 'tbl_lnkHosttemplateToContact', '', 'idSlave', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(106, 'tbl_contact', 'tbl_lnkHostToContact', '', 'idSlave', '', 'tbl_host', '', 'host_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(107, 'tbl_contact', 'tbl_lnkServiceescalationToContact', '', 'idSlave', '', 'tbl_serviceescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(108, 'tbl_contact', 'tbl_lnkServicetemplateToContact', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(109, 'tbl_contact', 'tbl_lnkServiceToContact', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(110, 'tbl_contactgroup', 'tbl_lnkContactgroupToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(111, 'tbl_contactgroup', 'tbl_lnkContactgroupToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(112, 'tbl_contactgroup', 'tbl_lnkContactgroupToContactgroup', '', 'idSlave', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(113, 'tbl_contactgroup', 'tbl_lnkContacttemplateToContactgroup', '', 'idSlave', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(114, 'tbl_contactgroup', 'tbl_lnkContactToContactgroup', '', 'idSlave', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(115, 'tbl_contactgroup', 'tbl_lnkHostescalationToContactgroup', '', 'idSlave', '', 'tbl_hostescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(116, 'tbl_contactgroup', 'tbl_lnkHosttemplateToContactgroup', '', 'idSlave', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(117, 'tbl_contactgroup', 'tbl_lnkHostToContactgroup', '', 'idSlave', '', 'tbl_host', '', 'host_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(118, 'tbl_contactgroup', 'tbl_lnkServiceescalationToContactgroup', '', 'idSlave', '', 'tbl_serviceescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(119, 'tbl_contactgroup', 'tbl_lnkServicetemplateToContactgroup', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(120, 'tbl_contactgroup', 'tbl_lnkServiceToContactgroup', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(121, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToCommandHost', '', 'idMaster', '', 'tbl_command', '', 'command_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(122, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToCommandService', '', 'idMaster', '', 'tbl_command', '', 'command_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(123, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(124, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToContacttemplate', '', 'idMaster', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(125, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToContacttemplate', '', 'idSlave', '', 'tbl_contacttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(126, 'tbl_contacttemplate', 'tbl_lnkContacttemplateToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(127, 'tbl_contacttemplate', 'tbl_lnkContactToContacttemplate', '', 'idSlave', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(128, 'tbl_host', 'tbl_lnkHostdependencyToHost_DH', '', 'idSlave', '', 'tbl_hostdependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(129, 'tbl_host', 'tbl_lnkHostdependencyToHost_H', '', 'idSlave', '', 'tbl_hostdependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(130, 'tbl_host', 'tbl_lnkHostescalationToHost', '', 'idSlave', '', 'tbl_hostescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(131, 'tbl_host', 'tbl_lnkHosttemplateToHost', '', 'idSlave', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(132, 'tbl_host', 'tbl_lnkHostToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(133, 'tbl_host', 'tbl_lnkHostToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(134, 'tbl_host', 'tbl_lnkHostToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(135, 'tbl_host', 'tbl_lnkHostToHost', '', 'idSlave', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(136, 'tbl_host', 'tbl_lnkHostToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(137, 'tbl_host', 'tbl_lnkHostgroupToHost', '', 'idSlave', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(138, 'tbl_host', 'tbl_lnkHostToHosttemplate', '', 'idMaster', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(139, 'tbl_host', 'tbl_lnkHostToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(140, 'tbl_host', 'tbl_lnkServicedependencyToHost_DH', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(141, 'tbl_host', 'tbl_lnkServicedependencyToHost_H', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(142, 'tbl_host', 'tbl_lnkServiceescalationToHost', '', 'idSlave', '', 'tbl_serviceescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(143, 'tbl_host', 'tbl_lnkServicetemplateToHost', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(144, 'tbl_host', 'tbl_lnkServiceToHost', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(145, 'tbl_host', 'tbl_lnkServicegroupToService', '', 'idSlaveH', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(146, 'tbl_host', 'tbl_hostextinfo', '', 'host_name', '', '', '', 'host_name', 1, '0,0,0,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(147, 'tbl_host', 'tbl_serviceextinfo', '', 'host_name', '', '', '', 'host_name', 1, '0,0,0,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(148, 'tbl_hostdependency', 'tbl_lnkHostdependencyToHostgroup_DH', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(149, 'tbl_hostdependency', 'tbl_lnkHostdependencyToHostgroup_H', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(150, 'tbl_hostdependency', 'tbl_lnkHostdependencyToHost_DH', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(151, 'tbl_hostdependency', 'tbl_lnkHostdependencyToHost_H', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(152, 'tbl_hostescalation', 'tbl_lnkHostescalationToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(153, 'tbl_hostescalation', 'tbl_lnkHostescalationToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(154, 'tbl_hostescalation', 'tbl_lnkHostescalationToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(155, 'tbl_hostescalation', 'tbl_lnkHostescalationToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(156, 'tbl_hostgroup', 'tbl_lnkHostdependencyToHostgroup_DH', '', 'idSlave', '', 'tbl_hostdependency', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(157, 'tbl_hostgroup', 'tbl_lnkHostdependencyToHostgroup_H', '', 'idSlave', '', 'tbl_hostdependency', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(158, 'tbl_hostgroup', 'tbl_lnkHostescalationToHostgroup', '', 'idSlave', '', 'tbl_hostescalation', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(159, 'tbl_hostgroup', 'tbl_lnkHostgroupToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(160, 'tbl_hostgroup', 'tbl_lnkHostgroupToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(161, 'tbl_hostgroup', 'tbl_lnkHostgroupToHostgroup', '', 'idSlave', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(162, 'tbl_hostgroup', 'tbl_lnkHosttemplateToHostgroup', '', 'idSlave', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(163, 'tbl_hostgroup', 'tbl_lnkHostToHostgroup', '', 'idSlave', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(164, 'tbl_hostgroup', 'tbl_lnkServicedependencyToHostgroup_DH', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(165, 'tbl_hostgroup', 'tbl_lnkServicedependencyToHostgroup_H', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(166, 'tbl_hostgroup', 'tbl_lnkServiceescalationToHostgroup', '', 'idSlave', '', 'tbl_serviceescalation', '', 'config_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(167, 'tbl_hostgroup', 'tbl_lnkServicetemplateToHostgroup', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(168, 'tbl_hostgroup', 'tbl_lnkServiceToHostgroup', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(169, 'tbl_hostgroup', 'tbl_lnkServicegroupToService', '', 'idSlaveHG', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(170, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(171, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(172, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(173, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(174, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToHosttemplate', '', 'idMaster', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(175, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToHosttemplate', '', 'idSlave', '', 'tbl_hosttemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(176, 'tbl_hosttemplate', 'tbl_lnkHosttemplateToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(177, 'tbl_hosttemplate', 'tbl_lnkHostToHosttemplate', '', 'idSlave', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(178, 'tbl_service', 'tbl_lnkServicedependencyToService_DS', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(179, 'tbl_service', 'tbl_lnkServicedependencyToService_S', '', 'idSlave', '', 'tbl_servicedependency', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(180, 'tbl_service', 'tbl_lnkServiceescalationToService', '', 'idSlave', '', 'tbl_serviceescalation', '', 'config_name', 1, '1,1,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(181, 'tbl_service', 'tbl_lnkServicegroupToService', '', 'idSlaveS', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(182, 'tbl_service', 'tbl_lnkServiceToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(183, 'tbl_service', 'tbl_lnkServiceToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(184, 'tbl_service', 'tbl_lnkServiceToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(185, 'tbl_service', 'tbl_lnkServiceToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(186, 'tbl_service', 'tbl_lnkServiceToServicegroup', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(187, 'tbl_service', 'tbl_lnkServiceToServicetemplate', '', 'idMaster', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(188, 'tbl_service', 'tbl_lnkServiceToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(189, 'tbl_service', 'tbl_serviceextinfo', '', 'service_description', '', '', '', 'host_name', 1, '0,0,0,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(190, 'tbl_servicedependency', 'tbl_lnkServicedependencyToHostgroup_DH', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(191, 'tbl_servicedependency', 'tbl_lnkServicedependencyToHostgroup_H', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(192, 'tbl_servicedependency', 'tbl_lnkServicedependencyToHost_DH', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(193, 'tbl_servicedependency', 'tbl_lnkServicedependencyToHost_H', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(194, 'tbl_servicedependency', 'tbl_lnkServicedependencyToService_DS', '', 'idMaster', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(195, 'tbl_servicedependency', 'tbl_lnkServicedependencyToService_S', '', 'idMaster', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(196, 'tbl_serviceescalation', 'tbl_lnkServiceescalationToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(197, 'tbl_serviceescalation', 'tbl_lnkServiceescalationToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(198, 'tbl_serviceescalation', 'tbl_lnkServiceescalationToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(199, 'tbl_serviceescalation', 'tbl_lnkServiceescalationToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(200, 'tbl_serviceescalation', 'tbl_lnkServiceescalationToService', '', 'idMaster', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(201, 'tbl_servicegroup', 'tbl_lnkServicegroupToService', '', 'idMaster', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(202, 'tbl_servicegroup', 'tbl_lnkServicegroupToServicegroup', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(203, 'tbl_servicegroup', 'tbl_lnkServicegroupToServicegroup', '', 'idSlave', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(204, 'tbl_servicegroup', 'tbl_lnkServicetemplateToServicegroup', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(205, 'tbl_servicegroup', 'tbl_lnkServiceToServicegroup', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(206, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToContact', '', 'idMaster', '', 'tbl_contact', '', 'contact_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(207, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToContactgroup', '', 'idMaster', '', 'tbl_contactgroup', '', 'contactgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(208, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToHost', '', 'idMaster', '', 'tbl_host', '', 'host_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(209, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToHostgroup', '', 'idMaster', '', 'tbl_hostgroup', '', 'hostgroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(210, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToServicegroup', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(211, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToServicetemplate', '', 'idMaster', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(212, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToServicetemplate', '', 'idSlave', '', 'tbl_servicetemplate', '', 'template_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(213, 'tbl_servicetemplate', 'tbl_lnkServicetemplateToVariabledefinition', '', 'idMaster', '', 'tbl_variabledefinition', '', 'name', 1, '0,0,0,2', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(214, 'tbl_servicetemplate', 'tbl_lnkServiceToServicetemplate', '', 'idSlave', '', 'tbl_service', '', 'config_name,service_description', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(215, 'tbl_timeperiod', 'tbl_lnkTimeperiodToTimeperiod', '', 'idMaster', '', 'tbl_timeperiod', '', 'timeperiod_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(216, 'tbl_timeperiod', 'tbl_lnkTimeperiodToTimeperiod', '', 'idSlave', '', 'tbl_timeperiod', '', 'timeperiod_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(217, 'tbl_timeperiod', 'tbl_contact', '', 'host_notification_period', '', '', '', 'contact_name', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(218, 'tbl_timeperiod', 'tbl_contact', '', 'service_notification_period', '', '', '', 'contact_name', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(219, 'tbl_timeperiod', 'tbl_contacttemplate', '', 'host_notification_period', '', '', '', 'template_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(220, 'tbl_timeperiod', 'tbl_contacttemplate', '', 'service_notification_period', '', '', '', 'template_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(221, 'tbl_timeperiod', 'tbl_host', '', 'check_period', '', '', '', 'host_name', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(222, 'tbl_timeperiod', 'tbl_host', '', 'notification_period', '', '', '', 'host_name', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(223, 'tbl_timeperiod', 'tbl_hosttemplate', '', 'check_period', '', '', '', 'template_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(224, 'tbl_timeperiod', 'tbl_hosttemplate', '', 'notification_period', '', '', '', 'template_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(225, 'tbl_timeperiod', 'tbl_hostdependency', '', 'dependency_period', '', '', '', 'config_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(226, 'tbl_timeperiod', 'tbl_hostescalation', '', 'escalation_period', '', '', '', 'config_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(227, 'tbl_timeperiod', 'tbl_service', '', 'check_period', '', '', '', 'config_name,service_description', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(228, 'tbl_timeperiod', 'tbl_service', '', 'notification_period', '', '', '', 'config_name,service_description', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(229, 'tbl_timeperiod', 'tbl_servicetemplate', '', 'check_period', '', '', '', 'template_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(230, 'tbl_timeperiod', 'tbl_servicetemplate', '', 'notification_period', '', '', '', 'template_name', 1, '1,1,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(231, 'tbl_timeperiod', 'tbl_servicedependency', '', 'dependency_period', '', '', '', 'config_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(232, 'tbl_timeperiod', 'tbl_serviceescalation', '', 'escalation_period', '', '', '', 'config_name', 1, '0,2,2,0', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(233, 'tbl_timeperiod', 'tbl_timedefinition', '', 'tipId', '', '', '', 'id', 1, '0,0,0,3', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(234, 'tbl_timeperiod', 'tbl_timeperiod', '', 'use_template', 'tbl_lnkTimeperiodToTimeperiodUse', 'timeperiod_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(235, 'tbl_timeperiod', 'tbl_lnkTimeperiodToTimeperiodUse', '', 'idMaster', '', 'tbl_timeperiod', '', 'timeperiod_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(236, 'tbl_timeperiod', 'tbl_lnkTimeperiodToTimeperiodUse', '', 'idSlave', '', 'tbl_timeperiod', '', 'timeperiod_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(237, 'tbl_group', 'tbl_user', '', 'users', 'tbl_lnkGroupToUser', 'username', '', '', 0, '', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(238, 'tbl_group', 'tbl_lnkGroupToUser', '', 'idMaster', '', 'tbl_user', '', 'username', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(239, 'tbl_servicedependency', 'tbl_servicegroup', '', 'dependent_servicegroup_name', 'tbl_lnkServicedependencyToServicegroup_DS', 'servicegroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(240, 'tbl_servicedependency', 'tbl_servicegroup', '', 'servicegroup_name', 'tbl_lnkServicedependencyToServicegroup_S', 'servicegroup_name', '', '', 0, '', 2); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(241, 'tbl_servicedependency', 'tbl_lnkServicedependencyToServicegroup_DS', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES(242, 'tbl_servicedependency', 'tbl_lnkServicedependencyToServicegroup_S', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', 1, '0,0,0,1', 0); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES (243,'tbl_serviceescalation', 'tbl_servicegroup', '', 'servicegroup_name', 'tbl_lnkServiceescalationToServicegroup', 'servicegroup_name', '', '', '0', '', '2'); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES (244,'tbl_serviceescalation', 'tbl_lnkServiceescalationToServicegroup', '', 'idMaster', '', 'tbl_servicegroup', '', 'servicegroup_name', '1', '0,0,0,1', '0'); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES (NULL, 'tbl_service', 'tbl_service', '', 'parents', 'tbl_lnkServiceToService', 'service_description', '', '', '0', '', '7'); INSERT INTO `tbl_relationinformation` (`id`, `master`, `tableName1`, `tableName2`, `fieldName`, `linkTable`, `target1`, `target2`, `targetKey`, `fullRelation`, `flags`, `type`) VALUES (NULL, 'tbl_servicetemplate', 'tbl_service', '', 'parents', 'tbl_lnkServicetemplateToService', 'service_description', '', '', '0', '', '7'); -- -------------------------------------------------------- -- -- Structure for table `tbl_service` -- CREATE TABLE IF NOT EXISTS `tbl_service` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `config_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `host_name_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_description` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `display_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `parents` tinyint(3) unsigned NOT NULL DEFAULT '0', `parents_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `importance` int(11) DEFAULT NULL, `servicegroups` tinyint(3) unsigned NOT NULL DEFAULT '0', `servicegroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_command` text COLLATE utf8_unicode_ci NOT NULL, `is_volatile` tinyint(3) unsigned NOT NULL DEFAULT '2', `initial_state` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `max_check_attempts` int(11) DEFAULT NULL, `check_interval` int(11) DEFAULT NULL, `retry_interval` int(11) DEFAULT NULL, `active_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `passive_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_period` int(11) NOT NULL DEFAULT '0', `parallelize_check` tinyint(3) unsigned NOT NULL DEFAULT '2', `obsess_over_service` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_freshness` tinyint(3) unsigned NOT NULL DEFAULT '2', `freshness_threshold` int(11) DEFAULT NULL, `event_handler` int(11) NOT NULL DEFAULT '0', `event_handler_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `low_flap_threshold` int(11) DEFAULT NULL, `high_flap_threshold` int(11) DEFAULT NULL, `flap_detection_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `flap_detection_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `process_perf_data` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `notification_interval` int(11) DEFAULT NULL, `first_notification_delay` int(11) DEFAULT NULL, `notification_period` int(11) NOT NULL DEFAULT '0', `notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `stalking_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_service` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_servicedependency` -- CREATE TABLE IF NOT EXISTS `tbl_servicedependency` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `config_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `dependent_host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `dependent_hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `dependent_service_description` tinyint(3) unsigned NOT NULL DEFAULT '0', `dependent_servicegroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `service_description` tinyint(3) unsigned NOT NULL DEFAULT '0', `servicegroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `inherits_parent` tinyint(3) unsigned NOT NULL DEFAULT '0', `execution_failure_criteria` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notification_failure_criteria` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `dependency_period` int(11) NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`config_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_servicedependency` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_serviceescalation` -- CREATE TABLE IF NOT EXISTS `tbl_serviceescalation` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `config_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `service_description` tinyint(3) unsigned NOT NULL DEFAULT '0', `servicegroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `first_notification` int(11) DEFAULT NULL, `last_notification` int(11) DEFAULT NULL, `notification_interval` int(11) DEFAULT NULL, `escalation_period` int(11) NOT NULL DEFAULT '0', `escalation_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), KEY `config_name` (`config_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_serviceescalation` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_serviceextinfo` -- CREATE TABLE IF NOT EXISTS `tbl_serviceextinfo` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `host_name` int(11) NOT NULL, `service_description` int(11) NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `statistic_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`host_name`,`service_description`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_serviceextinfo` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_servicegroup` -- CREATE TABLE IF NOT EXISTS `tbl_servicegroup` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `servicegroup_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `members` tinyint(3) unsigned NOT NULL DEFAULT '0', `servicegroup_members` tinyint(3) unsigned NOT NULL DEFAULT '0', `notes` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`servicegroup_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_servicegroup` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_servicetemplate` -- CREATE TABLE IF NOT EXISTS `tbl_servicetemplate` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `template_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `host_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `host_name_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `hostgroup_name` tinyint(3) unsigned NOT NULL DEFAULT '0', `hostgroup_name_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `service_description` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `display_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `parents` tinyint(3) unsigned NOT NULL DEFAULT '0', `parents_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `importance` int(11) DEFAULT NULL, `servicegroups` tinyint(3) unsigned NOT NULL DEFAULT '0', `servicegroups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_command` text COLLATE utf8_unicode_ci NOT NULL, `is_volatile` tinyint(3) unsigned NOT NULL DEFAULT '2', `initial_state` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `max_check_attempts` int(11) DEFAULT NULL, `check_interval` int(11) DEFAULT NULL, `retry_interval` int(11) DEFAULT NULL, `active_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `passive_checks_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_period` int(11) NOT NULL DEFAULT '0', `parallelize_check` tinyint(3) unsigned NOT NULL DEFAULT '2', `obsess_over_service` tinyint(3) unsigned NOT NULL DEFAULT '2', `check_freshness` tinyint(3) unsigned NOT NULL DEFAULT '2', `freshness_threshold` int(11) DEFAULT NULL, `event_handler` int(11) NOT NULL DEFAULT '0', `event_handler_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `low_flap_threshold` int(11) DEFAULT NULL, `high_flap_threshold` int(11) DEFAULT NULL, `flap_detection_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `flap_detection_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `process_perf_data` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_status_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `retain_nonstatus_information` tinyint(3) unsigned NOT NULL DEFAULT '2', `notification_interval` int(11) DEFAULT NULL, `first_notification_delay` int(11) DEFAULT NULL, `notification_period` int(11) NOT NULL DEFAULT '0', `notification_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notifications_enabled` tinyint(3) unsigned NOT NULL DEFAULT '2', `contacts` tinyint(3) unsigned NOT NULL DEFAULT '0', `contacts_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `contact_groups` tinyint(3) unsigned NOT NULL DEFAULT '0', `contact_groups_tploptions` tinyint(3) unsigned NOT NULL DEFAULT '2', `stalking_options` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `notes` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `notes_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `action_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `icon_image` varchar(500) COLLATE utf8_unicode_ci NOT NULL, `icon_image_alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `use_variables` tinyint(3) unsigned NOT NULL DEFAULT '0', `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', `import_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `config_name` (`template_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_servicetemplate` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_settings` -- CREATE TABLE IF NOT EXISTS `tbl_settings` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `category` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `name` varchar(30) COLLATE utf8_unicode_ci NOT NULL, `value` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `name` (`name`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_settings` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_tablestatus` -- CREATE TABLE IF NOT EXISTS `tbl_tablestatus` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `tableName` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `domainId` int(11) NOT NULL, `updateTime` datetime NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_tablestatus` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_timedefinition` -- CREATE TABLE IF NOT EXISTS `tbl_timedefinition` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `tipId` int(10) unsigned NOT NULL, `definition` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `range` text COLLATE utf8_unicode_ci NOT NULL, `last_modified` datetime NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_timedefinition` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_timeperiod` -- CREATE TABLE IF NOT EXISTS `tbl_timeperiod` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `timeperiod_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `exclude` tinyint(3) unsigned NOT NULL DEFAULT '0', `use_template` tinyint(3) unsigned NOT NULL DEFAULT '0', `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `register` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '1', `last_modified` datetime NOT NULL, `access_group` int(8) unsigned NOT NULL DEFAULT '0', `config_id` tinyint(3) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`id`), UNIQUE KEY `timeperiod_name` (`timeperiod_name`,`config_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_timeperiod` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_user` -- CREATE TABLE IF NOT EXISTS `tbl_user` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `username` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `password` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `admin_enable` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `wsauth` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `active` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `nodelete` enum('0','1') COLLATE utf8_unicode_ci NOT NULL DEFAULT '0', `language` varchar(20) COLLATE utf8_unicode_ci NOT NULL, `domain` int(10) unsigned NOT NULL DEFAULT '1', `last_login` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `last_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `username` (`username`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_user` -- -- -------------------------------------------------------- -- -- Structure for table `tbl_variabledefinition` -- CREATE TABLE IF NOT EXISTS `tbl_variabledefinition` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `value` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `last_modified` datetime NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ; -- -- Datasets for table `tbl_variabledefinition` --