-
Type:
New Feature Request
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
Component/s: Frontend (F)
Today tags are very important but also very open for any value. There is no option to limit or control what users can define as value.
I would like to propose an enhancement request to implement a TAG validation, for scenarios presented below.
- Parameter validation or input validation → checking that the value passed into a TAG meets certain rules.
- Example: AGE not lower than 0 and not bigger than 120.
- Domain restriction → ensuring the parameter belongs to a defined set of acceptable values.
- Example: Weekdays in {"Monday", "Tuesday", "Wednesday", "Thursday", "Friday"}
- Enumeration (enum) → using a type that explicitly lists the only allowed values.
- Example: Color: red as 1, green as 2, blue as 3
- Whitelist validation → allowing only values from a predefined list, rejecting everything else.
- Example: Country: only predefined will be allowed
- Constraint checking → applying rules (constraints) to limit what values are valid.
- Example: Time: not older than current time or size limited to 3 characters + 2 numbers or not empty.
- related to
-
ZBXNEXT-10526 Make Zabbix complain about tags that don't match the zabbix Tag name and value format
-
- Confirmed
-