-
New Feature Request
-
Resolution: Unresolved
-
Trivial
-
None
-
Prev.Sprint, S25-W10/11, S25-W12/13, S25-W14/15, S25-W16/17, S25-W18/19, S25-W20/21, S25-W22/23, S25-W26/27
-
15
in some cases one-level lld is not enough. for example, one might want to discover all databases and then discover all tables for them, to monitor some statistic for all of them.
this might be doable by creating some sort of "lld rule prototype", which could then cascade almost indefinitely (although i can't think of more than 2 level practical application right now)
- causes
-
ZBXNEXT-7527 Nested host prototypes
-
- Closed
-
-
ZBXNEXT-10103 Info icon for prototypes list tables under discovered LLD rules
-
- Open
-
-
ZBX-26651 Importing a template modifies every discovered item ids from it
-
- In Progress
-
-
ZBX-26523 Mass update button for trigger prototypes in nested lld is not working
-
- Closed
-
-
ZBX-26517 Options create trigger prototype / dependent item are enabled in context menu for discovered nested item prototype
-
- Closed
-
-
ZBX-26530 Fatal error opening trigger and graph prototype list pages if user is not logged in
-
- Closed
-
-
ZBX-26512 "Execute now" button is present for discovery prototype
-
- Closed
-
-
ZBX-26645 All prototypes are removed from no longer discovered LLD rules not depending on the "Delete lost resources" parameter value
-
- READY TO DEVELOP
-
- is duplicated by
-
ZBX-12436 Graph prototype process create only the lastest value sent by the Json object
-
- Closed
-
-
ZBX-9762 Nested LLD
-
- Closed
-
-
ZBX-11111 Smarter nested LLD?
-
- Closed
-
- related to
-
ZBX-26252 A PHP runtime error occurs when attempting to add a discovery rule at the template level
-
- READY TO DEVELOP
-