Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #2616] check_ido2db_procs.cfg should not depend on local-service template #975

Closed
icinga-migration opened this issue May 16, 2012 · 3 comments
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented May 16, 2012

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

Created by mfriedrich on 2012-05-16 15:54:32 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2012-06-12 16:11:52 +00:00)
Target Version: 1.7.1
Last Update: 2012-06-12 16:11:52 +00:00 (in Redmine)


on initial install, the template might be there, but when people invoke the upgrade by calling make install-idoutils, this will get placed into objects dir again, causing troubles.

better - use a different template shipped solely in the file itsself.

Changesets

2012-05-16 15:56:17 +00:00 by mfriedrich 8d7dc92

check_ido2db_procs.cfg should not depend on local-service template #2616

refs #2616

2012-06-11 12:26:16 +00:00 by mfriedrich dfcb88f

update Changelog from previous commits & fixes

refs #2616
refs #2637
refs #2671
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented May 16, 2012

Updated by mfriedrich on 2012-05-16 15:56:00 +00:00

# Define a service to check the number of currently running ido2db process
# 1 parent, 1 child for each connection
# default is 2, 1 is warning, 0 is critical

#service definition template - This is NOT a real service, just a template!
define service{
        name                            ido2db-proc-service     ; The 'name' of this service template
        active_checks_enabled           1                       ; Active service checks are enabled
        passive_checks_enabled          1                       ; Passive service checks are enabled/accepted
        parallelize_check               1                       ; Active service checks should be parallelized (disabling this can lead to major performance problems)
        obsess_over_service             1                       ; We should obsess over this service (if necessary)
        check_freshness                 0                       ; Default is to NOT check service 'freshness'
        notifications_enabled           1                       ; Service notifications are enabled
        event_handler_enabled           1                       ; Service event handler is enabled
        flap_detection_enabled          1                       ; Flap detection is enabled
        failure_prediction_enabled      1                       ; Failure prediction is enabled
        process_perf_data               1                       ; Process performance data
        retain_status_information       1                       ; Retain status information across program restarts
        retain_nonstatus_information    1                       ; Retain non-status information across program restarts
        is_volatile                     0                       ; The service is not volatile
        check_period                    24x7                    ; The service can be checked at any time of the day
        max_check_attempts              3                       ; Re-check the service up to 3 times in order to determine its final (hard) state
        normal_check_interval           10                      ; Check the service every 10 minutes under normal conditions
        retry_check_interval            2                       ; Re-check the service every two minutes until a hard state can be determined
        #contact_groups                 admins                  ; Notifications get sent out to everyone in the 'admins' group
        notification_options            w,u,c,r                 ; Send notifications about warning, unknown, critical, and recovery events
        notification_interval           60                      ; Re-notify about service problems every hour
        notification_period             24x7                    ; Notifications can be sent out at any time
        register                        0                      ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
        }

#command
define command{
        command_name    check_local_ido2db
        command_line    $USER1$/check_procs -w $ARG1$ -c $ARG2$ -C ido2db
        }

#service definition
define service{
        use                             ido2db-proc-service      ; Name of service template to use
        host_name                       localhost
        service_description             ido2db Process
        check_command                   check_local_ido2db!2:2!1:3
        }
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented May 17, 2012

Updated by mfriedrich on 2012-05-17 11:13:01 +00:00

  • Target Version changed from 1.8 to 1.7.1
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Jun 12, 2012

Updated by mfriedrich on 2012-06-12 16:11:52 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.