Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.9.1 (alpha)
    • Fix Version/s: 2.0.0
    • Component/s: Frontend (F), Server (S)
    • Labels:
      None

      Description

      Zabbix should automatically fill host profiles by the information collected by Zabbix Server and Proxies. It would be nice to have both automatic and manual filling of profile details or a combination of both.

      1. import_test_host.xml
        3 kB
        Aleksandrs Saveljevs
      1. bug_11.png
        42 kB
      2. bug_16.png
        15 kB
      3. bug_22.png
        31 kB
      4. bug_24.png
        59 kB
      5. bug_26.png
        51 kB
      6. bug_27.png
        22 kB
      7. bug_4.png
        24 kB
      8. bug_5.png
        14 kB
      9. bug_9.png
        43 kB

        Issue Links

          Activity

          Hide
          richlv added a comment -

          also see ZBXNEXT-616 and ZBXNEXT-294
          additional keyword : inventory

          Show
          richlv added a comment - also see ZBXNEXT-616 and ZBXNEXT-294 additional keyword : inventory
          Hide
          Alexander Vladishev added a comment - - edited

          1. Database changes:

          Table 'items':

          FIELD |profile_link |t_integer |'0' |NOT NULL |ZBX_SYNC

          profile_link: pointer to one of profile fields, 1-N. 0 - not used for profiles. Numbering will match field number in table structure.

          Table 'hosts_profiles':

          FIELD |profile_mode |t_integer |'0' |NOT NULL |ZBX_SYNC

          profile_mode: 0 - manual, 1 - automatic

          2. Configuration of item form will be extended to have an optional selection of a host profile field. If set, the item value will overwrite information stored in the corresponding profile field (for example, Device type, MAC Address, etc)

          The selection will be available for items of any type except of value type 'Log'.

          It will look like:

          Use in profiles [X]
          Update profile field [<here is a drop-down of all profile fields>]

          This selection will be located before Description field

          3. Template linkage should be extended to verify that there are no two items pointing to the same profile field.

          4. It should be possible to change profile linkage even if an item is linked to a template.

          5. Host profile may have the following states: Disabled - no host profile information available, Manual - manually entered host profile information, Automatic - linked fields are updated automatically, other fields can be manually modified.

          The profile state is configurable on per host level as it is in 1.8.x

          6. Host mass-updated will be extended to support setting of different profile modes (manual, automatic, disabled).

          7. Not supported and Disabled items are treated as a normal items, i.e. the linkage will be preserved.

          8. Item prototypes are not affected

          9. If a host profile in Automatic mode and a profile field has a linkage, the profile field should be disabled, show actual value and display information about linked item (as a item name linked to configuration of the item).

          ----------------------------------
          TODO later:

          N. New report will be introduced to display inventory information and number of hosts grouped by one of inventory fields.For example, grouping by OS: Linux: 450 hosts, Windows: 5 hosts.

          The existing Inventory report will be extended to support this. Additional drop-down "Aggregate by" will be introduced to select a host profile field for grouping purposes. Only fields having varchar() type can be used due to performance considerations. By default, drop-down selection is set to <no aggregation>.
          ---------------------------------- will be introduced later

          Show
          Alexander Vladishev added a comment - - edited 1. Database changes: Table 'items': FIELD |profile_link |t_integer |'0' |NOT NULL |ZBX_SYNC profile_link: pointer to one of profile fields, 1-N. 0 - not used for profiles. Numbering will match field number in table structure. Table 'hosts_profiles': FIELD |profile_mode |t_integer |'0' |NOT NULL |ZBX_SYNC profile_mode: 0 - manual, 1 - automatic 2. Configuration of item form will be extended to have an optional selection of a host profile field. If set, the item value will overwrite information stored in the corresponding profile field (for example, Device type, MAC Address, etc) The selection will be available for items of any type except of value type 'Log'. It will look like: Use in profiles [X] Update profile field [<here is a drop-down of all profile fields>] This selection will be located before Description field 3. Template linkage should be extended to verify that there are no two items pointing to the same profile field. 4. It should be possible to change profile linkage even if an item is linked to a template. 5. Host profile may have the following states: Disabled - no host profile information available, Manual - manually entered host profile information, Automatic - linked fields are updated automatically, other fields can be manually modified. The profile state is configurable on per host level as it is in 1.8.x 6. Host mass-updated will be extended to support setting of different profile modes (manual, automatic, disabled). 7. Not supported and Disabled items are treated as a normal items, i.e. the linkage will be preserved. 8. Item prototypes are not affected 9. If a host profile in Automatic mode and a profile field has a linkage, the profile field should be disabled, show actual value and display information about linked item (as a item name linked to configuration of the item). ---------------------------------- TODO later: N. New report will be introduced to display inventory information and number of hosts grouped by one of inventory fields.For example, grouping by OS: Linux: 450 hosts, Windows: 5 hosts. The existing Inventory report will be extended to support this. Additional drop-down "Aggregate by" will be introduced to select a host profile field for grouping purposes. Only fields having varchar() type can be used due to performance considerations. By default, drop-down selection is set to <no aggregation>. ---------------------------------- will be introduced later
          Hide
          richlv added a comment - - edited

          maybe "Update profile field" ? just "Update profile" might be confusing

          additional data, supported by the linux agent, will be available as items, right ?

          Show
          richlv added a comment - - edited maybe "Update profile field" ? just "Update profile" might be confusing additional data, supported by the linux agent, will be available as items, right ?
          Hide
          richlv added a comment -

          4. seemingly split out as ZBXNEXT-677

          Show
          richlv added a comment - 4. seemingly split out as ZBXNEXT-677
          Hide
          richlv added a comment -

          7. also listed at ZBXNEXT-676

          Show
          richlv added a comment - 7. also listed at ZBXNEXT-676
          Hide
          Alexander Vladishev added a comment - - edited

          (1) [DB] Error while upgrading database (MySQL):
          ERROR 1136 (21S01) at line 260: Column count doesn't match value count at row 1

          <KB> Fixed
          <sasha> also fixed errors in PostgreSQL upgrade path. Please review.

          ERROR: insert or update on table "opgroup" violates foreign key constraint "c_opgroup_1"
          DETAIL: Key (operationid)=(5) is not present in table "operations".
          UPDATE 0
          ERROR: insert or update on table "optemplate" violates foreign key constraint "c_optemplate_1"
          DETAIL: Key (operationid)=(6) is not present in table "operations".
          UPDATE 0

          <KB> Looks good, CLOSED.

          Show
          Alexander Vladishev added a comment - - edited (1) [DB] Error while upgrading database (MySQL): ERROR 1136 (21S01) at line 260: Column count doesn't match value count at row 1 <KB> Fixed <sasha> also fixed errors in PostgreSQL upgrade path. Please review. ERROR: insert or update on table "opgroup" violates foreign key constraint "c_opgroup_1" DETAIL: Key (operationid)=(5) is not present in table "operations". UPDATE 0 ERROR: insert or update on table "optemplate" violates foreign key constraint "c_optemplate_1" DETAIL: Key (operationid)=(6) is not present in table "operations". UPDATE 0 <KB> Looks good, CLOSED.
          Hide
          Alexander Vladishev added a comment - - edited

          (3) [DB] Please see my changes in db schema. Now the 'profile_mode' field location after the 'hostid' field

          <KB> Tested, works good. CLOSED.

          Show
          Alexander Vladishev added a comment - - edited (3) [DB] Please see my changes in db schema. Now the 'profile_mode' field location after the 'hostid' field <KB> Tested, works good. CLOSED.
          Hide
          Gergely Czuczy added a comment -

          If i may suggest, it'd be very nice, if this profile filling could work from SNMP OIDs as well.

          Some information also available over snmp, a few for an example:
          sysDescr.0
          sysName.0
          sysLocation.0
          sysContact.0

          And a few vendor-specific extensions, like cisco exports the running image's name, which is the software version practically.

          Would be very nice if some of the profile could be populated using SNMP information.

          Show
          Gergely Czuczy added a comment - If i may suggest, it'd be very nice, if this profile filling could work from SNMP OIDs as well. Some information also available over snmp, a few for an example: sysDescr.0 sysName.0 sysLocation.0 sysContact.0 And a few vendor-specific extensions, like cisco exports the running image's name, which is the software version practically. Would be very nice if some of the profile could be populated using SNMP information.
          Hide
          richlv added a comment -

          i believe that any item would be able to be set as a source for profile field data, which does not exclude snmp items

          Show
          richlv added a comment - i believe that any item would be able to be set as a source for profile field data, which does not exclude snmp items
          Hide
          Konstantin Buravcov added a comment -

          Merger to trunk rev 19442

          Show
          Konstantin Buravcov added a comment - Merger to trunk rev 19442

            People

            • Assignee:
              Unassigned
              Reporter:
              Alexander Vladishev
            • Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: