# Long message is truncated by logstash **URL:** \ **Category:** Logstash\ **Created:** [February 18, 2025, 2:48pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691 "2025-02-18T14:48:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Misakiz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/misakiz/32/141448_2.png) [@Misakiz](https://discuss.elastic.co/u/Misakiz)\ **Post date:** [February 18, 2025, 2:48pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/1 "2025-02-18T14:48:36Z")
`"8.17.2", "jruby.version"=>"jruby 9.4.9.0 (3.1.4) 2024-11-04 547c6b150e OpenJDK 64-Bit Server VM 21.0.6+7-LTS on 21.0.6+7-LTS +indy +jit [x86_64-linux]"} [2025-02-18T22:38:22,690][INFO][logstash.runner] JVM bootstrap flags: [-Xms8g, -Xmx8g, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djruby.compile.invokedynamic=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true, -Dlogstash.jackson.stream-read-constraints.max-string-length=200000000, -Dlogstash.jackson.stream-read-constraints.max-number-length=30000, -Djruby.regexp.interruptible=true, -Djdk.io.File.enableADS=true, --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED, --add-opens=java.base/java.security=ALL-UNNAMED, --add-opens=java.base/java.io=ALL-UNNAMED, --add-opens=java.base/java.nio.channels=ALL-UNNAMED, --add-opens=java.base/sun.nio.ch=ALL-UNNAMED, --add-opens=java.management/sun.management=ALL-UNNAMED, -Dio.netty.allocator.maxOrder=11] [2025-02-18T22:38:22,720][INFO][org.logstash.jackson.StreamReadConstraintsUtil] Jackson default value override `logstash.jackson.stream-read-constraints.max-string-length`configured to`200000000`[2025-02-18T22:38:22,720][INFO][org.logstash.jackson.StreamReadConstraintsUtil] Jackson default value override`logstash.jackson.stream-read-constraints.max-number-length`configured to`30000`[2025-02-18T22:38:22,826][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified [2025-02-18T22:38:23,166][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=>9603, :ssl_enabled=>false} [2025-02-18T22:38:23,290][INFO][org.reflections.Reflections] Reflections took 81 ms to scan 1 urls, producing 152 keys and 530 values [2025-02-18T22:38:23,427][INFO][logstash.javapipeline] Pipeline`main`is configured with`pipeline.ecs\_compatibility: v8`setting. All plugins in this pipeline will default to`ecs\_compatibility =\> v8` unless explicitly configured otherwise. [2025-02-18T22:38:23,449][INFO][logstash.javapipeline][main] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>32, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>4000, "pipeline.sources"=>["/opt/logstash-8.17.2/config/test2.conf"], :thread=>"#"} [2025-02-18T22:38:24,022][INFO][logstash.javapipeline][main] Pipeline Java execution initialization time {"seconds"=>0.57} [2025-02-18T22:38:24,045][INFO][logstash.javapipeline][main] Pipeline started {"pipeline.id"=>"main"} The stdin plugin is now waiting for input: [2025-02-18T22:38:24,058][INFO][logstash.agent] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]} >` this is my test file: input { stdin { } } output { stdout { codec =\> rubydebug } }` input message is : `{"testesteste":{"domain":"testestestetestestestetestestestetestestestetestestestetestestestetestesteste","request_url":"/api/v1/prtestestestete","@version":"1","http_referer":"-","via":"-","protocol":"http","status":"200","client_ip":"10.26.2.2.","upstream_addr":"1.1.1.1","size":"0","xff":"-","@timestamp":"2025-02-18T22:39:05+08:00","remote_user":"-","request_method":"POST","slb_req_id":"","host":"abidahidnifasfdasfda","user_agent":"Prometheus/2.28.1testestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestesteste2.28.1testestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestesteaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa2.28.1testestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestesteste2.28.1testestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestestetestestesteaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","cookie_id":"-","upstream_status":"200","request_time":"0.014","idc_tag":"dsda","cluster":"dfaasfdasfdsaf","upstream_response_time":"0.013"}}` ![1739889917088](https://us1.discourse-cdn.com/elastic/original/3X/c/c/cc2b75817607de6094e7c89fe8fd590a20404745.png) you can find the message was truncated by filter plugins or others How do I fix this? Are there any restrictions that can be adjusted? ---
**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\ **Post date:** [February 18, 2025, 3:20pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/2 "2025-02-18T15:20:46Z")
Try to set params in [jvm.options](https://github.com/elastic/logstash/blob/main/config/jvm.options): ```auto -Dlogstash.jackson.stream-read-constraints.max-nesting-depth=1000 -Dlogstash.jackson.stream-read-constraints.max-string-length=200000000 ``` ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [February 18, 2025, 4:03pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/3 "2025-02-18T16:03:12Z")
Your message is 7447 bytes long. If I put that in a file and read it using a stdin input then ``` input { stdin { } } filter { ruby { code => 'puts event.get("message").length' } } output { stdout { codec => rubydebug } } ``` tells me message is 7447 bytes. However, if I run logstash and let it read from the tty, if I paste the 7447 byte message into the terminal then [message] is 4095 bytes. It's not breaking the line into two, it's just truncating it. According to [this](https://unix.stackexchange.com/questions/643777/is-there-any-limit-on-line-length-when-pasting-to-a-terminal-in-linux) SE post, you can change this using `stty -icanon icrnl`, and it works for me (make sure you understand what it is turning off). This is all nothing to do with logstash, it's a limit on cut and paste in a tty. icanon keeps getting re-enabled for me, so the 4095 limit keeps returning. Not sure why. ---
**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\ **Post date:** [February 18, 2025, 5:16pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/4 "2025-02-18T17:16:33Z")
> [@Misakiz](#): > > `[INFO][org.logstash.jackson.StreamReadConstraintsUtil] Jackson default value override `logstash.jackson.stream-read-constraints.max-string-length`configured to`200000000`[2025-02-18T22:38:22,720][INFO][org.logstash.jackson.StreamReadConstraintsUtil] Jackson default value override`logstash.jackson.stream-read-constraints.max-number-length`configured to`30000`[2025-02-18T22:38:22,826][WARN]` Badger, can be this issue? ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [February 18, 2025, 5:29pm UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/5 "2025-02-18T17:29:25Z")
> [@Rios](#): > > can be this issue? I don't think those messages are related to this problem. [This](https://github.com/elastic/logstash/issues/16683) issue on github links to other issues and PRs related to why these get logged. I didn't dig through the history to see when they started being logged. I think it was recently (a few months at most), but I could be wrong. ---
**Author:** ![Misakiz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/misakiz/32/141448_2.png) [@Misakiz](https://discuss.elastic.co/u/Misakiz)\ **Post date:** [February 19, 2025, 9:53am UTC](https://discuss.elastic.co/t/long-message-is-truncated-by-logstash/374691/6 "2025-02-19T09:53:50Z")
thank you so mush! I understand what you mean. It's indeed the issue of tty restrictions.