# Multiline stack trace not working **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [May 19, 2025, 10:00pm UTC](https://discuss.elastic.co/t/multiline-stack-trace-not-working/378316 "2025-05-19T22:00:04Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [May 19, 2025, 11:50pm UTC](https://discuss.elastic.co/t/multiline-stack-trace-not-working/378316/2 "2025-05-19T23:50:20Z")
No you're multi-line syntax is not correct. That syntax is from the old deprecated log type input. > **[Manage multiline messages | Elastic Documentation](https://www.elastic.co/docs/reference/beats/filebeat/multiline-examples)** > > The files harvested by Filebeat may contain messages that span multiple lines of text. For example, multiline messages are common in files that contain... > [@Filebeat multi line pattern not working](https://discuss.elastic.co/t/filebeat-multi-line-pattern-not-working/378301/6): > > You are using the wrong syntax for filestream that is old log type syntax - type: filestream # Change to true to enable this input configuration. enabled: true # Paths that should be crawled and fetched. Glob based paths. paths: - /Users/sbrown/workspace/sample-data/discuss/filebeat-multiline/test-log-378301.log #- c:\programdata\elasticsearch\logs\* parsers: - multiline: type: pattern pattern: '^\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2} (AM|PM)' ne… --- _[View the full topic](https://discuss.elastic.co/t/multiline-stack-trace-not-working/378316)._