Details
-
New Feature Request
-
Resolution: Fixed
-
Trivial
-
None
-
None
-
Team A
-
Sprint 73 (Feb 2021), Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021)
-
5
Description
Summary
Currently aggregate checks are limited to filtering by host group(s) and item key, which is very narrow set of conditions. It makes aggregate checks impossible to use for LLD.
Lack of filtering by tags and item keys with wildcards is a major barrier to efficient cloud and kubernetes monitoring powered by service-discovery.
Aggregated items should switch to a new syntax proposed under New unified syntax for triggers, aggregated and calculated checks
Attachments
Issue Links
- causes
-
ZBX-19368 High CPU usage by history syncer due to very frequent sorting and checking for unique values
-
- Closed
-
- depends on
-
ZBXNEXT-6456 Frontend changes to support new syntax for aggregated checks
-
- Closed
-
(1 mentioned in)