manual:introduction:whatsnew320

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:introduction:whatsnew320 [2017/11/06 07:51]
martins-v better list of 'see also' links
manual:introduction:whatsnew320 [2021/11/13 16:58] (current)
Line 35: Line 35:
  
   * it is possible to tag events and correlate them   * it is possible to tag events and correlate them
-  * tag data is visible in //​Monitoring// ​-> //​Problems//​+  * tag data is visible in //​Monitoring// ​→ //​Problems//​
   * tag-based filtering is available for actions. You can get notified only on events matched by the tag/tag value.   * tag-based filtering is available for actions. You can get notified only on events matched by the tag/tag value.
  
Line 46: Line 46:
 ==== - View problems more clearly ==== ==== - View problems more clearly ====
  
-The monitoring part of Zabbix frontend has gained a new dedicated "​Problems"​ view. This section is for displaying problems only and it follows immediately after //​Monitoring// ​-> //​Dashboard//​. The new section is intended to give users a much clearer view of problems in comparison to the two //​Monitoring// ​-> //​Triggers//​ and //​Monitoring// ​-> //Events// sections used for this purpose previously.+The monitoring part of Zabbix frontend has gained a new dedicated "​Problems"​ view. This section is for displaying problems only and it follows immediately after //​Monitoring// ​→ //​Dashboard//​. The new section is intended to give users a much clearer view of problems in comparison to the two //​Monitoring// ​→ //​Triggers//​ and //​Monitoring// ​→ //Events// sections used for this purpose previously.
  
 {{:​manual:​introduction:​problems_new.png?​600|}} {{:​manual:​introduction:​problems_new.png?​600|}}
  
-In a related development,​ //​Monitoring// ​-> //Events// has been removed from the frontend. To access event details, use the new section for problems.+In a related development,​ //​Monitoring// ​→ //Events// has been removed from the frontend. To access event details, use the new section for problems.
  
 ==== - Close problems manually ==== ==== - Close problems manually ====
Line 181: Line 181:
 Host groups, templates and global scripts can now be searched by name in: Host groups, templates and global scripts can now be searched by name in:
  
-  * //​Configuration// ​-> //Host groups// +  * //​Configuration// ​→ //Host groups// 
-  * //​Configuration// ​-> //​Templates//​ +  * //​Configuration// ​→ //​Templates//​ 
-  * //​Administration// ​-> //Scripts//+  * //​Administration// ​→ //Scripts//
  
 {{:​manual:​introduction:​templates_filter.png|}} {{:​manual:​introduction:​templates_filter.png|}}
Line 191: Line 191:
 Several frontend sections have gained a filter allowing to search by name as well as status, type or mode: Several frontend sections have gained a filter allowing to search by name as well as status, type or mode:
  
-  * //​Configuration// ​-> //​Maintenance//​ +  * //​Configuration// ​→ //​Maintenance//​ 
-  * //​Configuration// ​-> //​Actions//​ +  * //​Configuration// ​→ //​Actions//​ 
-  * //​Configuration// ​-> //​Discovery//​ +  * //​Configuration// ​→ //​Discovery//​ 
-  * //​Administration// ​-> //​Proxies//​ +  * //​Administration// ​→ //​Proxies//​ 
-  * //​Administration// ​-> //User groups// +  * //​Administration// ​→ //User groups// 
-  * //​Administration// ​-> //Users// +  * //​Administration// ​→ //Users// 
-  * //​Administration// ​-> //Media types//+  * //​Administration// ​→ //Media types//
  
 {{:​manual:​introduction:​new_filters.png?​600|}} {{:​manual:​introduction:​new_filters.png?​600|}}
Line 276: Line 276:
 The history_text.id and history_log.id fields were removed from the corresponding history tables. Those fields were redundant and removing them will simplify history table structures and will remove unnecessary overhead when inserting values. The history_text.id and history_log.id fields were removed from the corresponding history tables. Those fields were redundant and removing them will simplify history table structures and will remove unnecessary overhead when inserting values.
  
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]