manual:config:event_correlation:trigger:event_tags

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:config:event_correlation:trigger:event_tags [2019/04/02 06:04]
127.0.0.1 external edit
manual:config:event_correlation:trigger:event_tags [2020/11/11 07:44]
martins-v remove non-specific performance/storage effects
Line 18: Line 18:
  
   MySQL, Service:​MySQL,​ Services, Services:​Customer,​ Applications,​ Application:​Java,​ Priority:​High ​   MySQL, Service:​MySQL,​ Services, Services:​Customer,​ Applications,​ Application:​Java,​ Priority:​High ​
 +  ​
 +An entity (trigger, template, host or event) may have several tags with the same name, but different values - these tags will not be considered '​duplicates'​. Similarly, a tag with no value and the same tag with a value can be used simultaneously. ​
  
 <​note>​Tags are not supported for host prototypes and hosts created from prototypes.</​note>​ <​note>​Tags are not supported for host prototypes and hosts created from prototypes.</​note>​
Line 108: Line 110:
 Note that the order in which tags are displayed is affected by tag filtering and the //Tag display priority// option in the filter of //​Monitoring//​ -> //​Problems//​ or the //​Problems//​ dashboard widget. Note that the order in which tags are displayed is affected by tag filtering and the //Tag display priority// option in the filter of //​Monitoring//​ -> //​Problems//​ or the //​Problems//​ dashboard widget.
  
-=== Performance and storage effects === 
  
-It is expected that the use of event tags may have the following effects: 
- 
-  * Event processing will be slower due to the creation of new records in the event tag table. 
-  * Operations related to manipulations with triggers inherited from templates will be slower since it's necessary to create one record per tag in the trigger tag table. Therefore the creation, update and removal of triggers will be slower. ​ 
-  * Synchronization of configuration cache will be slower due to trigger tags. 
-  * Storage of event tags will require additional disk space which may be comparable to the size of existing trigger and event tables. Precise storage requirements depend very much on the number of tags created per trigger and event.