Summary

Add support for wildcard or regular expression (regex) matching when configuring Map Link Indicators and map object filters (Hosts, Host Groups, Items, and Triggers) in Zabbix maps.

Problem Statement

Currently, when configuring Link Indicators in Zabbix Maps, triggers must be selected from a specific host. This creates a significant operational challenge in large environments where the same generic trigger exists across hundreds or thousands of hosts.

For example, commonly used triggers such as:

• Ping Failure
• Zabbix agent unreachable
• Other standardized template-based triggers

must be selected individually from a specific host, making the configuration non-scalable and difficult to maintain.

As a result:

• Link indicators cannot easily represent the status of all relevant hosts.
• Administrators must manually update map configurations whenever infrastructure changes.
• Large environments require unnecessary manual effort and duplicate configuration.

Proposed Enhancement

Allow Link Indicators to reference triggers using wildcard or regex matching instead of requiring a single host-specific trigger selection.

Example approaches:

• Trigger name regex:
  • ^Ping Failure$
  • .Zabbix agent unreachable.
• Trigger tag filtering (if applicable).

The map would evaluate all matching triggers and apply the configured line color based on the defined indicator logic.

Additional Enhancement Request

Similarly, provide wildcard/regex-based filtering when selecting:

• Hosts
• Host Groups
• Items
• Triggers

instead of requiring manual selection from a fixed list.

Example use cases:

• Host: prod-web-.*
• Host Group: Production/.*
• Item: icmpping.*
• Trigger: .agent unreachable.

This would greatly simplify the management of dynamic infrastructures where hosts are frequently added, removed, or renamed.

Benefits

• Significantly improves scalability for large deployments.
• Reduces manual maintenance of maps.
• Simplifies management of template-based monitoring.
• Enables dynamic maps that automatically include newly added hosts matching a naming convention.
• Improves consistency and reduces configuration errors.
• Makes Zabbix Maps more practical for enterprise-scale environments.

Use Case

An environment contains over 20,000+ hosts using the same monitoring templates.

An administrator wants a network link on a map to turn red if any connected device has a "Ping Failure" or "Zabbix agent unreachable" trigger.

Today, this requires selecting a trigger from a single host, which does not scale and does not dynamically apply to all relevant hosts.

With wildcard/regex support, the administrator could configure the indicator once using a trigger pattern (for example, ^Ping Failure$) and have it automatically apply to all matching hosts, including newly onboarded systems.

Expected Outcome

Introduce regex/wildcard-based matching for Map Link Indicators and map object selection, enabling scalable, dynamic, and low-maintenance map configurations for enterprise environments.