[ZBX-25494] Optimize LLD macro value extraction Created: 2024 Oct 25 Updated: 2025 Jan 15 Resolved: 2025 Jan 15 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Andris Zeila | Assignee: | Vladislavs Sokurenko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
The custom LLD macro usage is quite inefficient. In the case of LLD macros defined in LLD rule with jsonpaths server will first parse lld row into json object, perform jsonpath query and then free the object. This could be optimized by caching the object associated to LLD row. Even further - the LLD data could be parsed into object in beginning and this json object tree could be used directly. Adding caching might also improve LLD macro lookups, but most likely that would depend on custom LLD macro jsonpath complexity.
|