it doesn't like the (?s) you've added after <message>
This works just fine for me: \[%{TIMESTAMP_ISO8601:timestamp}\] \[%{DATA:glassfish_version}\] \[%{LOGLEVEL:loglevel}\] \[\] \[%{DATA:logger}\] \[tid: _ThreadID=%{NUMBER:thread_id} _ThreadName=%{DATA:thread_name}\] \[levelValue: %{NUMBER:level_value}\] \[\[\n(?<message>.*?)\]\]
different lines in a log would have a \n between them
If your pipeline is producing two events from the message because it's on two lines in the log file then you need to setup a multi-line reader to ensure that both lines end up in the message field of the log.
your grok pattern already has a \n in it to handle this
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.