Results 1 to 4 of 4

Thread: Shinken 1.2.4 + NDO + Icinga-Web

  1. #1
    Junior Member
    Join Date
    Apr 2013
    Posts
    9

    Shinken 1.2.4 + NDO + Icinga-Web

    Hi

    I am testing Shinken + ToNdodb_Mysql + Icinga-Web 1.8.3.

    The MySQL DB is running on a separated host. This is my ToNdodb_Mysql configuration:

    Code:
    define module {
     database shinken
     prefix icinga_
     character_set utf8
     host 192.168.177.14
     module_type ndodb_mysql
     user shinken
     module_name ToNdodb_Mysql
     password shinken
     port 3306
     synchronize_database_id 1
    }
    The DB structure was imported like described in the Icinga documentation.

    Code:
     #> cd /path/to/icinga-src/module/idoutils/db/mysql
     #> mysql -u root -p shinken < mysql.sql
    The broker writes to the DB and elements like hosts and instances are stored:

    Code:
    mysql> select * from icinga_instances \G
    *************************** 1. row ***************************
         instance_id: 1
        instance_name: app2-ewmon-stage
    instance_description: app2-ewmon-stage
    1 row in set (0.00 sec)
    
    mysql> select * from icinga_hosts \G
    *************************** 1. row ***************************
                 host_id: 1
               instance_id: 1
               config_type: 0
              host_object_id: 14
                  alias: ews68
               display_name: ews68
                 address: 212.71.111.68
                 address6: 
         check_command_object_id: 0
            check_command_args: NULL
      eventhandler_command_object_id: 0
        eventhandler_command_args: NULL
    notification_timeperiod_object_id: 0
        check_timeperiod_object_id: 0
        failure_prediction_options: 0
              check_interval: 3
              retry_interval: 1
            max_check_attempts: 5
         first_notification_delay: 0
          notification_interval: 60
              notify_on_down: 0
          notify_on_unreachable: 0
            notify_on_recovery: 0
            notify_on_flapping: 0
            notify_on_downtime: 0
               stalk_on_up: 0
              stalk_on_down: 0
           stalk_on_unreachable: 0
          flap_detection_enabled: 1
           flap_detection_on_up: 0
          flap_detection_on_down: 0
      flap_detection_on_unreachable: 0
            low_flap_threshold: 25
           high_flap_threshold: 50
         process_performance_data: 1
         freshness_checks_enabled: 0
           freshness_threshold: 0
          passive_checks_enabled: 1
          event_handler_enabled: 1
          active_checks_enabled: 1
        retain_status_information: 0
       retain_nonstatus_information: 0
          notifications_enabled: 1
             obsess_over_host: 0
        failure_prediction_enabled: 0
                  notes: 
                notes_url: 
                action_url: NULL
                icon_image: NULL
              icon_image_alt: NULL
                vrml_image: NULL
             statusmap_image: NULL
              have_2d_coords: 0
                   x_2d: 0
                   y_2d: 0
              have_3d_coords: 0
                   x_3d: 0
                   y_3d: 0
                   z_3d: 0
    1 row in set (0.00 sec)

    But the Web UI does only display the Instance - no other item like hosts or services. Any Idea why? How complex would it be to make the shinken ndo module icinga-web compatible (create a shinken ido module)?

    Regards,
    Flo

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: Shinken 1.2.4 + NDO + Icinga-Web

    It mainly depends how far ido is from ndo now. It can be long to look at all webui query and look for all fields are here.
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    Apr 2013
    Posts
    9

    Re: Shinken 1.2.4 + NDO + Icinga-Web

    [quote author=naparuba link=topic=868.msg4777#msg4777 date=1366100310]
    It mainly depends how far ido is from ndo now. It can be long to look at all webui query and look for all fields are here.
    [/quote]

    OK I will try to ask the Icinga-Web team about that gap. After a quick look in the DB there a some values not filled by shinken NDO:

    Code:
     select * from icinga_services join icinga_objects on service_object_id=object_id where name1='ews68' and name2='NTP' and is_active=1\G

    IDOMOD IDODB:


    Code:
    *************************** 1. row ***************************
                service_id: 612056
               instance_id: 1
               config_type: 1
              host_object_id: 80
            service_object_id: 319
               display_name: NTP
         check_command_object_id: 28
            check_command_args: check_ntp!-a "212.71.111.18" "60" "300"
      eventhandler_command_object_id: 0
        eventhandler_command_args: 
    notification_timeperiod_object_id: 365
        check_timeperiod_object_id: 18
        failure_prediction_options: 
              check_interval: 15
              retry_interval: 3
            max_check_attempts: 3
         first_notification_delay: 0
          notification_interval: 0
            notify_on_warning: 1
            notify_on_unknown: 1
            notify_on_critical: 1
            notify_on_recovery: 1
            notify_on_flapping: 0
            notify_on_downtime: 0
               stalk_on_ok: 0
             stalk_on_warning: 0
             stalk_on_unknown: 0
            stalk_on_critical: 0
               is_volatile: 0
          flap_detection_enabled: 1
           flap_detection_on_ok: 1
        flap_detection_on_warning: 1
        flap_detection_on_unknown: 1
        flap_detection_on_critical: 1
            low_flap_threshold: 0
           high_flap_threshold: 0
         process_performance_data: 1
         freshness_checks_enabled: 0
           freshness_threshold: 0
          passive_checks_enabled: 1
          event_handler_enabled: 1
          active_checks_enabled: 1
        retain_status_information: 1
       retain_nonstatus_information: 1
          notifications_enabled: 1
           obsess_over_service: 1
        failure_prediction_enabled: 1
                  notes: 
                notes_url: 
                action_url: /nagiosgraph/show.cgi?host=$HOSTNAME$&service=$SERVICEDESC$
                icon_image: 
              icon_image_alt: 
                object_id: 319
               instance_id: 1
              objecttype_id: 2
                  name1: ews68
                  name2: NTP
                is_active: 1
    1 row in set (0.00 sec)
    Shinken NDO:

    Code:
    *************************** 1. row ***************************
                service_id: 166
               instance_id: 1
               config_type: 0
              host_object_id: 14
            service_object_id: 54
               display_name: NTP
         check_command_object_id: 0
            check_command_args: NULL
      eventhandler_command_object_id: 0
        eventhandler_command_args: NULL
    notification_timeperiod_object_id: 0
        check_timeperiod_object_id: 0
        failure_prediction_options: 0
              check_interval: 15
              retry_interval: 3
            max_check_attempts: 3
         first_notification_delay: 0
          notification_interval: 0
            notify_on_warning: 0
            notify_on_unknown: 0
            notify_on_critical: 0
            notify_on_recovery: 0
            notify_on_flapping: 0
            notify_on_downtime: 0
               stalk_on_ok: 0
             stalk_on_warning: 0
             stalk_on_unknown: 0
            stalk_on_critical: 0
               is_volatile: 0
          flap_detection_enabled: 1
           flap_detection_on_ok: 0
        flap_detection_on_warning: 0
        flap_detection_on_unknown: 0
        flap_detection_on_critical: 0
            low_flap_threshold: -1
           high_flap_threshold: -1
         process_performance_data: 1
         freshness_checks_enabled: 0
           freshness_threshold: 0
          passive_checks_enabled: 1
          event_handler_enabled: 1
          active_checks_enabled: 1
        retain_status_information: 0
       retain_nonstatus_information: 0
          notifications_enabled: 1
           obsess_over_service: 1
        failure_prediction_enabled: 0
                  notes: 
                notes_url: 
                action_url: NULL
                icon_image: NULL
              icon_image_alt: NULL
                object_id: 54
               instance_id: 1
              objecttype_id: 2
                  name1: ews68
                  name2: NTP
                is_active: 1
    1 row in set (0.00 sec)

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: Shinken 1.2.4 + NDO + Icinga-Web

    I think the reason why it is not on the Icinga ui is not about just one element and it's property, but more about links between objects. One missing filed (0 or 1) won't break an UI I think, but if there is a foreign key missing, it can be a real problem (or like for hostgroups or things like this).

    This module was design to make Centreon work, so yes it will miss some fields, but from now I think we should focus on the global object links, and then hunt for the missing fields (at least the one that are important ).
    No direct support by personal message. Please open a thread so everyone can see the solution

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •