Currently there is an argument `expandExpression` which expands both functions and macros, but I would like the functions to be expanded by default and not the macros.
The reason I prefer this is to have the trigger.get API call return the same contents for the expression as the website does when viewing a trigger. Functions are hidden when using the webinterface, and as such, the webinterface shows the expression with the functions expanded, but with the macros as they are.
To summarize: I would move to to always expand functions in the (trigger.get) API, and use `expandExpression` to only (additionally) expand macros.
- is duplicated by
-
ZBXNEXT-8512 Ability to get trigger parameters with unexpanded user macros
- Closed