manual:config:items:item:custom_intervals

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
Next revision Both sides next revision
manual:config:items:item:custom_intervals [2016/02/16 15:25]
127.0.0.1 external edit
manual:config:items:item:custom_intervals [2020/03/12 11:58]
martins-v contrasting frontend and API syntax
Line 1: Line 1:
-==== - #2 Custom intervals ====+==== 2 Custom intervals ====
  
 === Overview === === Overview ===
Line 20: Line 20:
 |10 |1-5,​09:​00-18:​00| Item will be checked every 10 seconds during working hours.| |10 |1-5,​09:​00-18:​00| Item will be checked every 10 seconds during working hours.|
 |0 |1-7,​00:​00-7:​00 |Item will not be checked during the night.| |0 |1-7,​00:​00-7:​00 |Item will not be checked during the night.|
 +|0 |7-7,​00:​00-24:​00 |Item will not be checked on Sundays.|
 |60 | 1-7,​12:​00-12:​01| Item will be checked at 12:00 every day. Note that this was used as a workaround for scheduled checks and starting with Zabbix 3.0 it is recommended to use scheduling intervals for such checks.| |60 | 1-7,​12:​00-12:​01| Item will be checked at 12:00 every day. Note that this was used as a workaround for scheduled checks and starting with Zabbix 3.0 it is recommended to use scheduling intervals for such checks.|
  
Line 37: Line 38:
  
 While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the //<​step>//​ value defined. While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the //<​step>//​ value defined.
 +
 +An empty filter matches either '​0'​ if no lower-level filter is defined or all possible values otherwise. For example, if the hour filter is omitted then only '​0'​ hour will match, provided minute and seconds filters are omitted too, otherwise an empty hour filter will match all hour values.
  
 Valid ''<​from>''​ and ''<​to>''​ values for their respective filter prefix are:  Valid ''<​from>''​ and ''<​to>''​ values for their respective filter prefix are: 
Line 50: Line 53:
 Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example ''​md01-31''​ and ''​h/​02''​ are valid intervals, but ''​md01-031''​ and ''​wd01-07''​ are not.  Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example ''​md01-31''​ and ''​h/​02''​ are valid intervals, but ''​md01-031''​ and ''​wd01-07''​ are not. 
  
-Multiple ​scheduling intervals ​can be used by separating them with a semicolon '';''​. If a time is matched by several intervals it is executed only once. For example, ''​wd1h9;​h9''​ will be executed only once on Monday at 9am. +In Zabbix frontend, multiple ​scheduling intervals ​​are entered in separate rows. In Zabbix API, they are concatenated into a single string ​with a semicolon '';'' ​​as a separator. 
 + 
 +If a time is matched by several intervals it is executed only once. For example, ''​wd1h9;​h9''​ will be executed only once on Monday at 9am. 
  
 Examples: Examples:
  
-^Interval^Description+^Interval^Will be executed
-|m0-59|execute ​every minute| +|m0-59|every minute| 
-|h9-17/2|execute ​every 2 hours starting with 9:00 (9:00, 11:00 ...)| +|h9-17/​2|every 2 hours starting with 9:00 (9:00, 11:00 ...)| 
-|m0,30 or m/30|execute ​hourly at hh:00 and hh:30|+|m0,30 or m/30|hourly at hh:00 and hh:30|
 |m0,​5,​10,​15,​20,​25,​30,​35,​40,​45,​50,​55 or m/5|every five minutes| |m0,​5,​10,​15,​20,​25,​30,​35,​40,​45,​50,​55 or m/5|every five minutes|
 |wd1-5h9|every Monday till Friday at 9:00| |wd1-5h9|every Monday till Friday at 9:00|
Line 64: Line 69:
 |md1h9m30|every 1st day of each month at 9:30| |md1h9m30|every 1st day of each month at 9:30|
 |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday| |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday|
-|h9m/30|execute ​at 9:00, 9:30| +|h9m/30|every day at 9:00, 9:30| 
-|h9m0-59/​30|execute ​at 9:00, 9:30| +|h9m0-59/​30|every day at 9:00, 9:30| 
-|h9,10m/30|execute ​at 9:00, 9:30, 10:00, 10:30| +|h9,10m/30|every day at 9:00, 9:30, 10:00, 10:30| 
-|h9-10m30|execute ​at 9:30, 10:30| +|h9-10m30|every day at 9:30, 10:30| 
-|h9m10-40/​30|execute ​at 9:10, 9:40| +|h9m10-40/​30|every day at 9:10, 9:40| 
-|h9,​10m10-40/​30|execute ​at 9:10, 9:40, 10:10, 10:40| +|h9,​10m10-40/​30|every day at 9:10, 9:40, 10:10, 10:40| 
-|h9-10m10-40/​30|execute ​at 9:10, 9:40, 10:10, 10:40| +|h9-10m10-40/​30|every day at 9:10, 9:40, 10:10, 10:40| 
-|h9m10-40|execute ​at 9:10, 9:11, 9:12, ... 9:40| +|h9m10-40|every day at 9:10, 9:11, 9:12, ... 9:40| 
-|h9m10-40/​1|execute ​at 9:10, 9:11, 9:12, ... 9:40| +|h9m10-40/​1|every day at 9:10, 9:11, 9:12, ... 9:40| 
-|h9-12,15|execute ​at 9:00, 10:00, 11:00, 12:00, 15:00| +|h9-12,15|every day at 9:00, 10:00, 11:00, 12:00, 15:00| 
-|h9-12,​15m0|execute ​at 9:00, 10:00, 11:00, 12:00, 15:00| +|h9-12,​15m0|every day at 9:00, 10:00, 11:00, 12:00, 15:00| 
-|h9-12,15m0s0|execute ​at 9:00, 10:00, 11:00, 12:00, 15:00| +|h9-12,15m0s30|every day at 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30
-|h9-12s30|execute ​at 9:​00:​30, ​10:00:30, 11:00:30, 12:00:30| +|h9-12s30|every day at 9:​00:​30, ​9:01:30, 9:02:30 ... 12:58:30, 12:59:30| 
-|h9m/​30;​h10|execute ​at 9:00, 9:30, 10:00|+|h9m/30; h10 (//​API-specific syntax//)|every day at 9:00, 9:30, 10:00| 
 +|h9m/30\\ h10 (//add this as another row in frontend//​)|every day at 9:00, 9:30, 10:00|