[ZBXNEXT-1306] LLD macros do not seem to work in Flexible Interval definitions Created: 2012 Jul 09  Updated: 2017 Jun 13  Resolved: 2017 Jun 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.0.1
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Alessandro De Maria Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: flexibleintervals, lld
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos


Issue Links:
Duplicate
duplicates ZBXNEXT-1675 Add macros support for update intervals Closed

 Description   

Hello,

I have defined LDD rule which receives the following JSON

{
    "data":[
        {
            "{#SERVICE}":"Zabbix Agent",
            "{#DESCRIPTION}":"Zabbix Agent",
            "{#TIME}":"1-5,05:59-20:58",

        }
    ]
}

and I was expecting the time definition to be picked up in the Flexible interval definition.

The GUI accepts the {#TIME} value as a correct time interval (actually I think it does not do any validation at all, but then the
1) You cannot click on the LDD created item to validate the macro expansion
2) The behaviour shows that the Flexible Interval with the {#TIME} macro is ignored.
3) Log shows the macro expansion did not happened.

29274:20120709:122203.603 wrong delay period format [50/{#TIME}]

Is it possible to enable it? It is essential to monitor services that are only available at certain time, and instead of doing it manually, LDD makes it much easies to handle

Regards
Alessandro



 Comments   
Comment by richlv [ 2012 Jul 09 ]

i assume you are creating item prototypes and placing {#TIME} in the flexible interval ?
even if this was supported, it would be hard to add multiple flexible intervals for items...

Comment by Alessandro De Maria [ 2012 Jul 09 ]

I would be happy with one as well, but yes I understand what you mean.

Any chance to have "arrays of macros"

Another (long) solution would be to have under general an "Interval profile" defined the way regexps are now.
So you would have @time_service_1 that includes all the different flexible intervals. This could also be used for normal items

Regards
Alessandro

Comment by Glebs Ivanovskis (Inactive) [ 2017 Jun 13 ]

Implemented in ZBXNEXT-1675, closing as Duplicate.

Generated at Sat Apr 20 05:05:49 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.