Suggested patch

valid/not ?
maybe should be moved to the feature requests to allow runtime configuration of the mentioned REG_NEWLINE ?

8 years? still no one(Zabbix) notice this?

related : ZBXNEXT-846

a bit related ZBXNEXT-434

any update and/or workaround here?

Zabbix documentation links to Wikipedia Regular expressions article, section POSIX Extended Regular Expressions. (The section doesn't exist any more, should probably link to section POSIX extended.)

According to POSIX standard, Metacharacter . Normally matches any character except a newline.

The trick (workaround) is to include character class that contains newline, which seems to be [:space:] or [:cntrl:]. So the complete solution is to replace . with (.|[[:space:]]), which is mentioned also in ZBXNEXT-846.

majo, could you please create a new bugreport about the documentation link being wrong ?

Bug report ZBX-10930 created.

The possible solution (http://zabbix.org/wiki/Start_with_SNMP_traps_in_Zabbix#Create_items_for_linkUp.2FlinkDown_traps_with_LLD):

snmptrap["(IF-MIB::linkDown|IF-MIB::linkUp)(.|[[:space:]])*{#SNMPVALUE}"]

I can additionally confirm that [[:space:]] or [[:cntrl:]] include newline character and may be used in zabbix for multiline regexp match.

I don't think we need to keep this opened as it's actually possible.
Just remember that with ZBX-3924 (from v3.4) implemented we use PCRE.

Also remember that in case of log file monitoring and filtering on agent side, multiline filtering is not possible by design, when reading log file by zabbix agent.
The limit is because of nature and logic of zabbix agent - it takes a line first and then perform regexp match test for each line. ZBXNEXT-967 asks for that option.

Let's set resolution as Fixed, to indicate that it's actually possible.

Since nothing was actually done here let's consider it as duplicate of ZBX-3924 .