Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Presentation issues when message contains unbroken sequences of punctuation #21155

Open
dhedberg opened this issue Dec 10, 2024 · 0 comments
Open
Labels

Comments

@dhedberg
Copy link

dhedberg commented Dec 10, 2024

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 BREAKS
echo '{ "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 OK
echo '{ "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
@dhedberg dhedberg added the bug label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant