# Host Availability Dashboard Pane

**URL:** <https://community.dynatrace.com/t/host-availability-dashboard-pane/51404>\
**Category:** DQL\
**Tags:** dql, dynatrace-managed, notebooks\
**Created:** [April 28, 2025, 9:49pm UTC](https://community.dynatrace.com/t/host-availability-dashboard-pane/51404 "2025-04-28T21:49:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![m\_laurie\_az](https://avatars.discourse-cdn.com/v4/letter/m/e47774/32.png) [@m\_laurie\_az](https://community.dynatrace.com/u/m_laurie_az)\
**Post date:** [April 28, 2025, 9:49pm UTC](https://community.dynatrace.com/t/host-availability-dashboard-pane/51404/1 "2025-04-28T21:49:31Z")

</div>

I’m having trouble creating a pane for a help desk that shows when a host goes down. The problem I seem to be running into is that when a host goes down for something like a power failure, the agent stops reporting, and there is no data to indicate a “down” status, which seems to “remove” it from dashboards. Ultimately, when a host changes its availability state to something other than “up,” I would like it to appear in a table until it’s back “up”. Thanks!

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [April 29, 2025, 5:25am UTC](https://community.dynatrace.com/t/host-availability-dashboard-pane/51404/2 "2025-04-29T05:25:11Z")

</div>

[@m\_laurie\_az](https://community.dynatrace.com/user/88689)&nbsp;There are a few ways to get around this issue , if you want to report some data when “no data” is being reported , you can use the&nbsp;nonempty parameter in DQL.

See below link for some details around the usage

[https://community.dynatrace.com/t5/Open-Q-A/Host-availability-state-metric-of-no-data/m-p/270961](https://community.dynatrace.com/post/270961)

Alternatively, you can also report the Availability data in % in a table and list least available servers. Any drop in availability will be reported less than 100%. Here is a example DQL

```markup
fetch dt.entity.host
| fieldsAdd tags
| filter in(tags, "TIER:PRIORITY")
| filterOut isMonitoringCandidate == true or standalone == true
| lookup [
timeseries m1=max(dt.host.availability, rollup: sum),
filter:availability.state == "up",
by:{availability.state,dt.entity.host},from: toTimestamp($dt_timeframe_from), to: toTimestamp($dt_timeframe_to)-2m
| parse replaceString(toString(m1),"null","0"), """'['ARRAY{ DOUBLE:i ', '}{1,10000}:m1Pop"""
| fieldsAdd intervalToMinutes = toLong(interval)/60000000000 
| fieldsAdd availability= toDouble(arraySum(m1Pop)/(arraySize(m1Pop))*100)/intervalToMinutes],
sourceField: id, lookupField: dt.entity.host, fields: {availability}
| fields dt.entity.host = id, Host=entity.name,`Availability %`=coalesce(availability, 0)
| sort `Availability %` asc
| limit 10

```
