Reference: Application service status¶
You can monitor your application services for health issues and active alerts to mitigate potential impact on the application services. Evaluating application service data provides insights, based on its service type. If you identify an issue with your services you can edit your application service, or objects connected to your application service, such as policies and profiles.
For more information about application endpoint observability, see Reference: Application endpoint data metrics.
For information about creating or managing applications, see How to: Manage applications using BIG-IP Next Central Manager and FAST templates.
For more information about filtering application service information in the dashboard, see filtering application services
Health¶
Pool member health¶
The following table provides information about pool members’ status and their descriptions.
| Status | Description |
|---|---|
| Good | The pool member's status is set to Enabled or Disabled, and the pool member is reachable or not. |
| Critical | The pool member is unreachable or unresponsive. This can happen in several situations, such as:
|
| Unknown | When an application service is created and deployed for the first time, the pool member is not monitored initially, so it appears as Unknown. It might take up to 3 minutes for the status to change from Unknown to Good or Critical. Note: If the status is still showing Unknown after five minutes, check the configuration of the application service and check whether the instance's license is Activated. |
For more information about Pool Member statuses, see Status of the pool members
Pool Health¶
Pool Health is a combination of all pool members health. For more information, see Pool member health.
| Status | Description |
|---|---|
| Good | All pool members in the pool are Good. |
| Moderate | The pool has several pool members, with at least one member being either Critical or Unknown, and at least one member being Good. |
| Critical | All pool members in the pool are Critical. |
| Unknown | When an application service is created and deployed for the first time, the pool members of the pool are not monitored initially, so the pool appears as Unknown. It might take up to 3 minutes for the status to change from Unknown to Good, Moderate or Critical. Note: If the status is still showing Unknown after five minutes, check the configuration of the application service and check whether the instance's license is Activated. |
Application service health¶
The health of an application shown in the My Application Services dashboard is a cumulative calculation of the statuses of each application’s pool and pool members.
Application service health is based on the following:
Changes in traffic patterns.
Changes in pool member (endpoint) status. Status is either offline or unknown.
The following table describes why an application service is assigned a specific health status when observing applications in the application dashboard:
| Status | Description |
|---|---|
| Critical | If there is at least one pool that is Critical (and none are Good). |
| Moderate | If all pools are moderate. If there are multiple pools that are Unknown and/or Critical but have at least one Good. |
| Good | If all pools are Good. |
| Unknown | When an application service is created and deployed for the first time, the pools are not monitored initially, so the application appears as Unknown. It might take up to 3 minutes for the status to change from Unknown to Good, Moderate or Critical. Note: If the status is still showing Unknown after five minutes, check the configuration of the application service and check whether the instance's license is Activated. |
Application service alerts and status¶
The My Application Services dashboard provides a total number of active alerts to all your applications. Active alerts indicate events impacting your applications’ health status. An event that impacts your application health is determined by status changes to your application’s: virtual servers, pools, and pool members, or traffic to the pool member.
The alert level is determined by whether the event partially/potentially impacts performance (warning) or if the application service is unable to reach an entire pool of pool members (critical). See pool alerts for information about how BIG-IP Next determines alert level.
Pool member alerts¶
The basis of all alerts comes from the ability for BIG-IP Next Central Manager to recognize a pool member as online or offline.
When BIG-IP Next identifies a pool member as offline or disabled, this triggers an alert. The alert level depends on whether the pool member checks are consistent.
The following are the different pool member alert levels, and the conditions that impact the pool member’s status.
| Status | Condition |
|---|---|
| Critical | The pool member is unreachable. |
| Warning | The pool member does not consistently respond when BIG-IP Next checks its status. |