[ZBX-15591] Host status unknown when host has only active items Created: 2019 Feb 05  Updated: 2024 Apr 10  Resolved: 2019 Mar 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: 4.2 (plan)

Type: Documentation task Priority: Trivial
Reporter: Andrejs Sitals (Inactive) Assignee: Antons Sincovs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team D
Sprint: Sprint 49 (Feb 2019), Sprint 50 (Mar 2019)
Story Points: 0.125

 Description   

Steps to reproduce:

  1. Create a host with Agent interface
  2. Create an item with "Zabbix agent (active)" type
  3. Wait until some data appears in Monitoring -> Latest data
  4. Observe host's availability in Configuration -> Hosts

Result:

Availability icon is gray which indicates that host's status is unknown (as per https://www.zabbix.com/documentation/current/manual/web_interface/frontend_sections/configuration/hosts). Though, documentation doesn't state that host status is unknown when only active items are being monitored.

Expected:

Either availability icon should be green (if data arrives), or documentation should state that host status is unknown when only active items are being monitored on the host.



 Comments   
Comment by richlv [ 2019 Feb 05 ]

While documented at https://www.zabbix.com/documentation/4.0/manual/appendix/items/unreachability , mentioning it for the icons would indeed be great.

Note that Zabbix agent active checks do not influence host availability in any way.

Comment by dimir [ 2019 Feb 15 ]

Would be nice to have agent parameter like ActiveUnavailable where you can define the longest time no data from active agent was received. And based on that set host availability to green/gray.

ZBXNEXT-5088 asks for this feature.

Comment by Martins Valkovskis [ 2019 Mar 04 ]

Documentation about host availability icons updated for the supported versions.

Generated at Mon Aug 11 06:43:43 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.