You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the message field of a log message contains a long string of ".", the message list table breaks by being rendered extremely wide. The same thing does not happen if the message contains a similarly long string of another character like "a".
The breakage can be easily seen by performing a search that contains the message in the results. Any extra fields added to the message table "disappears" (out to the side). The edit functionality for the table is also similarly broken.
Steps to Reproduce
I can reproduce the issue by adding a GELF TCP input and running:
# Create a message with 50k "."; this BREAKSecho'{ "version": "1.1", "host": "test.com", "short_message": "'$(head -c 50000 < /dev/zero | sed 's/././g')'", "level": 5 }'| nc 127.0.0.1 12201
# Create a message with 50k "a"; this is OKecho'{ "version": "1.1", "host": "test.com", "short_message": "'$(head -c 50000 < /dev/zero | sed 's/./a/g')'", "level": 5 }'| nc 127.0.0.1 12201
Possible solution
Experimenting with word-wrap: anywhere on relevant <div>s seems to make things behave better in this scenario.
Your Environment
Graylog Version: 6.1.4 (the official docker image)
OpenSearch Version: 2.17.0
MongoDB Version: 6.0.19
Browser version: Tested with Firefox 133, Chromium 131.0.6778.108
The text was updated successfully, but these errors were encountered:
When the message field of a log message contains a long string of ".", the message list table breaks by being rendered extremely wide. The same thing does not happen if the message contains a similarly long string of another character like "a".
The breakage can be easily seen by performing a search that contains the message in the results. Any extra fields added to the message table "disappears" (out to the side). The edit functionality for the table is also similarly broken.
Steps to Reproduce
I can reproduce the issue by adding a GELF TCP input and running:
Possible solution
Experimenting with
word-wrap: anywhere
on relevant<div>
s seems to make things behave better in this scenario.Your Environment
The text was updated successfully, but these errors were encountered: