[ZBXNEXT-3562] Make boolean mapping for 'numeric (unsigned)' customizable Created: 2016 Nov 21 Updated: 2020 Nov 19 Resolved: 2020 Nov 19 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | API (A), Frontend (F), Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Minor |
Reporter: | Raymond Kuiper | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 5 |
Labels: | api, export, import, valuemapping, xml | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
As we already have the possibility to map various strings and numeric values to 0 or 1 in the boolean data type, it would make sense to allow a user to specify their own mapping, much like valuemaps achieve the reverse. A new type of custom mapping could be introduced to allow for customization of these mappings or perhaps this could be done on regexp matching. Please also take integration within the API and import/export into account. |
Comments |
Comment by Raymond Kuiper [ 2016 Nov 21 ] |
Current builtin mappings: Boolean - textual representation translated into either 0 or 1. Thus, 'TRUE' is stored as 1 and 'FALSE' is stored as 0. All values are matched in a case-insensitive way. Currently recognized values are, for: |
Comment by Raymond Kuiper [ 2016 Nov 21 ] |
Related to |
Comment by finalbeta [ 2017 Sep 28 ] |
Example (They way I see it). I receive a textual value from SNMP, using preprocessing I can process the value like: Match: "Value result is A" = 1 And store the result as a Numeric (unsigned) type of information. |
Comment by Alexei Vladishev [ 2020 Nov 17 ] |
qix, I believe it can be done using preprocessing, correct? Shall we keep this ticked open or we may close it? |
Comment by Raymond Kuiper [ 2020 Nov 18 ] |
I think preprocessing will work fine for this, feel free to close! |
Comment by Alexei Vladishev [ 2020 Nov 19 ] |
qix, thanks for the prompt response, I am closing it! |