[ZBXNEXT-1008] more advanced filtering for lld Created: 2011 Oct 21  Updated: 2014 Oct 22  Resolved: 2014 Oct 22

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

Type: Change Request Priority: Trivial
Reporter: richlv Assignee: Unassigned
Resolution: Duplicate Votes: 16
Labels: flexibility, lld
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-581 Ability to filter by multiple LLD macros Closed

 Description   

currently regexp filtering for lld rules only allows to filter on a single POSIX regexp for a single macro. this has several limitations, thus several things would be desired (may be split out in separate issues).

a) ability to add multiple filters. for example, one to filter on fsname and exclude some custom filsesystem, one to filter on fstype.
b) ability to negate strings. one way might be to allow specifying "not" for individual filter rules (depends on a) ), another might be to support PCRE or similar everywhere in server, thus allowing regexp lookarounds



 Comments   
Comment by Oleksii Zagorskyi [ 2011 Oct 22 ]

a) is a duplicate of 2. in the ZBXNEXT-581

Comment by Oleksii Zagorskyi [ 2011 Oct 30 ]

b) Do not forget about ZBX-3924

added:
note that b) can be reached by using a global regexp with a "Result is FALSE" expression type.

<richlv> this definitely works as a workaround, but in many cases that's an excessive configuration - ability to mark parts as "not" in rule itself would be useful still

Comment by Simon Kowallik [ 2012 Mar 04 ]

PCRE would be great to have everywhere in zabbix_server.
It is extremely flexible and used in most products.
POSIX ERE has a lot of limitations which are solved by PCRE.

Multiple Filter Macros would also be very nice.

Comment by richlv [ 2014 Oct 22 ]

main concern is a duplicate of multiple lld filters, implemented in 2.4, other issues duplicate some other issues - closing as a duplicate

Generated at Thu Mar 28 12:52:58 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.