[ZBXNEXT-2217] Graph titles created with item prototype from LLD showing only 20 first characters Created: 2013 Jul 09 Updated: 2015 Sep 18 Resolved: 2015 Sep 18 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Minor |
Reporter: | Matjaž Š | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 0 |
Labels: | graphs, lld | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Debian Linux |
Attachments: | Graph.png item_value.png | ||||||||
Issue Links: |
|
Description |
When using item prototype for graph title only 20 first characters. For example: if item value is 123456789012345678901234567890 in graph title you will see 12345678901234567890... (see attached pictures). |
Comments |
Comment by Matjaž Š [ 2013 Jul 09 ] |
I tried it using Zabbix 2.1.0 (first alpha) and latest nightly build Pre-2.1.1 (alpha) (revision 36810). |
Comment by Alexander Vladishev [ 2013 Aug 20 ] |
In the frontend values of macros like {ITEM.VALUE}, {ITEM.LASTVALUE} and {<host>:<key>.last(0)} are trimmed to 20 characters. It's expected behaviour. I'm closing the issue. |
Comment by Dale Bewley [ 2014 Mar 21 ] |
Perhaps this is an RFE rather than bug. We have very long descriptions on switch ports that are not disambiguated until several characters in, sometimes. Volter helped me find the following in v2.2.2 include/items.inc.php. Perhaps 20 could at least be moved to a constant somewhere, if not a config option. I've raised the value to 50 on my installation. switch ($item['value_type']) { case ITEM_VALUE_TYPE_STR: $mapping = getMappedValue($value, $item['valuemapid']); // break; is not missing here case ITEM_VALUE_TYPE_TEXT: case ITEM_VALUE_TYPE_LOG: if ($trim && zbx_strlen($value) > 20) { $value = zbx_substr($value, 0, 20).'...'; } if ($mapping !== false) { $value = $mapping.' ('.$value.')'; } break; |
Comment by Marc [ 2015 Jul 13 ] |
Distantly related to ZBXNEXT-1016 |
Comment by richlv [ 2015 Sep 18 ] |
let's handle all latest value trimming in ZBXNEXT-1016 thanks to asaveljevs for coming up with a list of related issues |