You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zabbix alerts often arrive without a host name attached, in both the polling and webhook-push paths of the Zabbix provider.
Polling (_get_alerts in keep/providers/zabbix_provider/zabbix_provider.py): the problem.get API call never requests host data (no selectHosts param), so pulled alerts have no host information at all.
Webhook push (_format_alert): the installed Zabbix script sends the host as host_name / host_ip (matching the parameter names configured in setup_webhook), but the code reads hostName / hostIp instead — these keys never exist in the payload. The primary source, service ({HOST.HOST}), can be empty for problems tied to multiple hosts, and the fallback then silently returns None due to this key mismatch.
Bug
Zabbix alerts often arrive without a host name attached, in both the polling and webhook-push paths of the Zabbix provider.
_get_alertsinkeep/providers/zabbix_provider/zabbix_provider.py): theproblem.getAPI call never requests host data (noselectHostsparam), so pulled alerts have no host information at all._format_alert): the installed Zabbix script sends the host ashost_name/host_ip(matching the parameter names configured insetup_webhook), but the code readshostName/hostIpinstead — these keys never exist in the payload. The primary source,service({HOST.HOST}), can be empty for problems tied to multiple hosts, and the fallback then silently returnsNonedue to this key mismatch.Fix
See linked PR.