Troubleshoot App Dashboard

Last published : Sep 21, 2026
After you add an application in the App Dashboard, the dashboard immediately displays the app basic configuration details. The application analytics details such as app score, key metrics, and issues start to populate within a few minutes (approximately 10 to 15 minutes). For more information, see Applications.
You must ensure that there is no issue with metrics data flow (AppFlow collector or Analytics profile) from the NetScaler instance. You can get more information on AppFlow collector and analytics profile in this document.
This document describes the troubleshooting steps that you need to perform when:
  • You click an application, the analytics for the selected application do not display the required data even after the mentioned duration (10–15 minutes).
  • The CS or LB application is always indicating Gray color (Not Applicable status) in App Dashboard.
Note
The troubleshooting procedures mentioned in this document are only applicable to Content Switching and Load Balancing virtual servers.
Related information

Troubleshooting scenario

Troubleshooting scenario

Application is licensed

You must ensure if the application is licensed. Navigate to Settings > Licensing & Analytics Configuration and verify if the application is licensed under Virtual Server License Summary. If the application is not licensed, see the following:

Metrics collector is enabled

You must ensure if Metrics Collector is enabled in the NetScaler instance.
For NetScaler version 13.0 or later, Metrics Collector is enabled by default, after the ADC instance is successfully added in ADM. To ensure if metrics collector is enabled:
  1. Navigate to Infrastructure > Instances. Under Instances, select the type of instance (for example, NetScaler VPX).
  2. Select the NetScaler instance.
    1. From the Select Action list, select Metrics Collector.
      Metrics-collector
  3. On the Configure Metrics Collector settings page, ensure if Enable option is selected. If not, select the Enable option and click OK.
After you enable metrics collector and if you are still not able to view the data, validate:

NetScaler instance earlier builds

In NetScaler:
  1. Run the following command to ensure if the collector is UP and running at Port 5563:
    sh appflow collector af_collector_rest_<adm_receiver_ip>
    AppFlow
  2. If no collector is available, do an instance manual polling in NetScaler® ADM.
    1. Navigate to Infrastructure > Network Function > Poll Now
    2. Select the instance and click Start Polling.
      Polling
      If polling fails, remove the ADC instance from ADM and then add the ADC instance again. When you add the ADC instance, the collector gets added on ADC.
If the collector indicates Down status:
  1. Ensure if SNIP is configured.
    SNIP
    If SNIP is not configured, you must configure SNIP. For more information, see Configuring SNIP.
  2. Ensure that if ADC instance is reachable to ADM.
    You can validate by doing a ping test. Run ping -S <SNIP> <adm_receiver_ip>
    Ping test

NetScaler instance later builds

In NetScaler ADM, ensure that the metrics collector service is available:
  1. Navigate to Infrastructure > Network Function > Load Balancing > Services.
  2. On the search bar, filter by Instance: (IP address) and Name: ADM.
  3. Ensure if adm_metric_collector_svc_<adm_receiver ip> is available. The IP address can be either the ADM management IP or the agent IP.
    Ensure that this service is in UP status and running at Port 5563.
    Metrics collector service
If you still cannot view the data, ensure that the collector service is bound to time series analytics profile in NetScaler.
  1. Log on to NetScaler
  2. Run the following command:
    sh analytics profile ns_analytics_time_series_profile
    Time series
If the collector indicates Down status:
  1. Ensure if SNIP is configured.
    SNIP
    If SNIP is not configured, you must configure SNIP. For more information, see Configuring SNIP.
  2. Ensure that if ADC instance is reachable to ADM.
    You can validate by doing a ping test. Run ping -S <SNIP> <adm_receiver_ip>
    Ping test
  3. Ensure that the traffic connectivity through telnet is able to connect the service.
    Telnet
    If telnet is able to connect the service, then a firewall exists and is blocking the metric data flow. You must resolve the firewall block issue.
If no collector service is bound to time series analytics profile in NetScaler, the Collector is displayed as blank.
No collector service
You must do an instance manual polling in NetScaler ADM.
  1. Navigate to Infrastructure > Network Function > Poll Now
  2. Select the instance and click Start Polling.
    Polling
    If polling fails, add the collector service directly at NetScaler instance using the following commands:
    add service adm_metric_collector_svc_<adm_receiver_ip> <adm_receiver_ip> HTTP 5563
    unset analyticsprofile ns_analytics_time_series_profile -collectors
    set analytics profile ns_analytics_time_series_profile -collectors adm_metric_collector_svc_<adm_receiver_ip> -metrics enabled -events enabled
    The analytics time series profile is updated.
    Update collector service
If the issue still persists even after performing all the mentioned troubleshooting steps, contact NetScaler support.