[ZBX-25467] Item history widget - new lines issue Created: 2024 Oct 28 Updated: 2025 Jan 22 Resolved: 2025 Jan 22 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 7.0.4, 7.0.5 |
Fix Version/s: | 7.0.8rc1, 7.2.3rc1, 7.4.0alpha1 |
Type: | Problem report | Priority: | Minor |
Reporter: | Leonardo Savoini | Assignee: | Dmitrijs Fofanovs |
Resolution: | Fixed | Votes: | 0 |
Labels: | frontend, widget | ||
Remaining Estimate: | 0h | ||
Time Spent: | 8h | ||
Original Estimate: | 8h |
Attachments: |
![]() ![]() ![]() ![]() ![]() |
Team: | |
Sprint: | S24-W46/47, S24-W48/49, S24-W50/51/52/1, S25-W2/3, S25-W4/5 |
Story Points: | 1 |
Description |
I'm using zabbix sender (via official python zabbix tools). Before 7.0, I sent a large text (stdout of Ansible with some extras) that includes newlines, and in the history widget I could see without issue. Same case happened while gathering data from Kubernetes API (http agent). I tried using "as is" "html" and "monospace" font. Before 7.0 using "as is" worked well.{} For now I'm using "single line", then click on the line to show a popup with the full text. |
Comments |
Comment by Leonardo Savoini [ 2024 Oct 28 ] |
Let me add another example from Kubernetes. Using HTTP agent item type, then preprocessing jsonpath to get the text I need. |
Comment by Alexander Vladishev [ 2024 Oct 28 ] |
Which version of Zabbix frontend are you currently using? This issue seems very similar to one that was fixed in |
Comment by Alexander Vladishev [ 2024 Oct 28 ] |
Is the "Use monospace font" option enabled in the configuration of this widget? |
Comment by Leonardo Savoini [ 2024 Oct 28 ] |
Last week I upgraded from 7.0.4 to 7.0.5, still the same. Here is the widget. Confirmed, that are not only new lines, but tabs are missing too. with "monospace" got the same results. Debug: |
Comment by Leonardo Savoini [ 2024 Oct 28 ] |
Sorry, the newlines are good. What are missing are multiple spaces. Just checked the JSON. There are no problem with special chars. Monospace doesn't seem to resolve the issue. |
Comment by Alexander Vladishev [ 2024 Oct 28 ] |
I confirm this issue. Thank you for the report! We will fix it. |
Comment by Dmitrijs Fofanovs [ 2024 Dec 19 ] |
Available in versions:
|