Zabbix Documentation 2.2

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:items:mapping

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:config:items:mapping [2014/09/25 14:40]
sasha Page moved from 2.2:manual:config:items:mapping to manual:config:items:mapping
manual:config:items:mapping [2014/09/26 11:32] (current)
sasha Links adapted because of a move operation
Line 17: Line 17:
   * '​I'​ -> '​Incremental'​   * '​I'​ -> '​Incremental'​
  
-Thus, when [[:​2.2/​manual/​config/​items/​item|configuring items]] you can use a value map to "​humanize"​ the way an item value will be displayed. To do that, you refer to the name of a previously defined value map in the //Show value// field.+Thus, when [[item|configuring items]] you can use a value map to "​humanize"​ the way an item value will be displayed. To do that, you refer to the name of a previously defined value map in the //Show value// field.
  
 <​note>​Before Zabbix 2.2 value mapping could only be used with items having a //Numeric (unsigned)//​ type of information. Starting with Zabbix 2.2, //Numeric (float)// and //​Character//​ information types are also supported for value mapping. <​note>​Before Zabbix 2.2 value mapping could only be used with items having a //Numeric (unsigned)//​ type of information. Starting with Zabbix 2.2, //Numeric (float)// and //​Character//​ information types are also supported for value mapping.
Line 30: Line 30:
   * Click on //Create value map// (or on the name of an existing map)   * Click on //Create value map// (or on the name of an existing map)
  
-{{:​2.2/​manual/​config/​items/​2.0.3_value_map.png|}}+{{2.0.3_value_map.png|}}
  
 Parameters of a value map: Parameters of a value map:
Line 43: Line 43:
 For example, one of the predefined agent items 'Ping to the server (TCP)' uses an existing value map called '​Service state' to display its values. ​ For example, one of the predefined agent items 'Ping to the server (TCP)' uses an existing value map called '​Service state' to display its values. ​
  
-{{:​2.2/​manual/​config/​items/​2.0.3_value_map2.png|}}+{{2.0.3_value_map2.png|}}
  
-In the item [[:​2.2/​manual/​config/​items/​item|configuration form]] you can see a reference to this value map in the //Show value// field:+In the item [[item|configuration form]] you can see a reference to this value map in the //Show value// field:
  
-{{:​2.2/​manual/​config/​items/​2.0.3_show_value.png|}}+{{2.0.3_show_value.png|}}
  
 So in //​Monitoring -> Latest data// the mapping is put to use to display '​Up'​ (with the raw value in parentheses). So in //​Monitoring -> Latest data// the mapping is put to use to display '​Up'​ (with the raw value in parentheses).
  
-{{:​2.2/​manual/​config/​items/​1.9.7_value_display.png?​600|}}+{{1.9.7_value_display.png?​600|}}
  
 In the //Latest data// section displayed values are shortened to 20 symbols. If value mapping is used, this shortening is not applied to the mapped value, but only to the raw value separately (displayed in parenthesis). In the //Latest data// section displayed values are shortened to 20 symbols. If value mapping is used, this shortening is not applied to the mapped value, but only to the raw value separately (displayed in parenthesis).
Line 59: Line 59:
 Without a predefined value map you would only get this: Without a predefined value map you would only get this:
  
-{{:​2.2/​manual/​config/​items/​1.9.7_value_display2.png?​600|}}+{{1.9.7_value_display2.png?​600|}}
  
 So in this case you would either have to guess what the '​1'​ stands for or do a search of documentation to find out. So in this case you would either have to guess what the '​1'​ stands for or do a search of documentation to find out.