Summarizes unresponsive hosts that users have tried to connect to over the past 24 hours
There may be two steps involved when a user tries to connect to a host. First is resolving the the host/resource name into an IP address and second is sending/receiving traffic to/from that host. App Health Reports covers both of these eventualities.
When any type of resolver is used then if they return errors, then these will appear in an App Health Report. For instance a cloud resolver might report invalid credentials or API quota issues, a DNS server might report NXDOMAIN.
Once an IP address is obtained and a user attempts to connect to an App using an Action defined with a specific host definition (/32 or /128), using an ALLOW rule and the TCP up protocol; then the Gateway monitors the return traffic from the host to make sure there is a response. When there is no response within 30 seconds then an unresponsive report is generated.
NOTE
It is not possible to monitor ranges of IP addresses as there is no deterministic way to say if a range is responsive or not based on user's traffic.
The list summarizes the number of unresponsive reports generated over the past 24 hours where at least 5 users have experienced problems with the same app.
Background information
This is part of the Digital Experience Monitoring which is a separately licensable option. For information about how licensing works, refer to Licenses.
The Active Sessions details for each user will show if they have triggered any unresponsive host reports. There is both a global report for this, as well as a Site/Gateway specific report.
The Troubleshooting user/device access topic provides comprehensive guidance that will help you track down any access issues.
Viewing specific
Click on any row to access specific details about the reports relating to the affected Entitlement.
App Reports identify the IP address of the unresponsive host and the port the user was connecting on. It also provides the Action reference number which allows for easy way to reference back to the original Entitlement configuration.
.png?sv=2022-11-02&spr=https&st=2026-04-17T01%3A23%3A29Z&se=2026-04-17T01%3A35%3A29Z&sr=c&sp=r&sig=GsCSkZI4Su5QVZMQ1LkDowjoLr9YcmjLDVMwsRtPF1g%3D)
Name Reports detail any error and the intended target.
Remember, these are 'app health' reports and an Entitlement may contain many Actions - each representing an App. So when an Entitlement appears on the list, the issue might only relate to one of the Actions specified and within that, only one of the hosts listed there.