Create Custom Dashboards for AI PODs

Ensure that you have configured AppDynamics to collect data from the AI components. See Configure AI Components to Collect MetricsNo Content found for /db/organizations/splunk/repositories/appdsaas-26_6_0/content/documents/AppDynamics/c_configure_ai_components_to_collect_metrics.dita.
To create the custom dashboards and view the associated metrics, do the following:
  1. Download the custom_dashboard_script_ai_pods file.

    The custom dashboard script generates ready-to-import AppDynamics dashboard JSON files from a set of templates. You supply your environment's node names and the custom metric path prefixes. The script substitutes them into the templates and writes the rendered files. The zip file contains the following resources:

    File/ Directory Description

    templates

    Contains the following json templates to create the dashboard files:

    • appd_ai_pod_overview.json

    • appd_intersight_dashboard.json

    • appd_nexus_dashboard.json

    • appd_dcgm_gpu.json

    • appd_nim_llm.json

    • appd_tokenomics.json

    • appd_storage_dashboard.json

    • appd_vectordb.json

    • appd_redhat_openshift.json

    • appd_ai_pod_hosts.json

    dashboards

    Contains the output json files that are generated after running the main.py script.

    main.py

    Python script to create the dashboards.

    readme.md

    Description of the solution.
  2. Run the following command to create the dashboard that you want:
    CODE 
    ```bash
cd custom-dashboard-script
python3 main.py
```
    The script prompts for parameters specific to the dashboard you are creating, then generates the JSON file and saves it to the dashboards directory.
  3. Based on your selected dashboard, specify the following dashboard parameters:
    Parameter Description Default Values
    dashboard_name

    The dashboard name to be displayed on Dashboard & Reports in the Controller UI.

    Example:

    temp-dashboard-ai-pod-overview
    worker_node_names

    Comma-separated worker hostnames for multi-node widgets.

    The first name is also used automatically for single-node-scoped widgets.

    No default value. Enter the node names from your environment.
    cluster_node_name

    The Cluster-agent node hostname for cluster-scoped widgets.

    No default value. Enter the node names from your environment.
    intersight_metric_prefix

    The metric path prefix for Intersight widgets.

    		 Custom Metrics\|Intersight
    nexus_metric_prefix

    The metric path prefix for Nexus widgets.

    		 Custom Metrics\|Network\|Nexus
    gpu_metric_prefix

    The metric path prefix for GPU widgets.

    		 Custom Metrics\|AI Pod\|GPUs
    nim_metric_prefix

    The metric path prefix for NIM widgets.

    		 Custom Metrics\|NIM\|LLMs
    storage_metric_prefix

    The metric path prefix for Pure Storage widgets.

    		 Custom Metrics\|Storage
    vectordb_metric_prefix

    The metric path prefix for Vector DB widgets.

    		 Custom Metrics\|Vector DB
    Note: All widgets are configured to use the Server & Infrastructure Monitoring application. If your environment requires a different application, update the SAMPLE_APPLICATION_NAME variable in main.py.
  4. Import the dashboard in the Controller UI. See Import Custom DashboardsNo Content found for /db/organizations/splunk/repositories/appdsaas-26_6_0/content/documents/AppDynamics/t_import_custom_dashboards.dita.
  5. After importing, verify that each widget is successfully resolving live custom metrics:
    1. Distinguish between zero-value and missing paths: A path that reports zero should be handled differently than one that is missing.
    2. Validate metric path families: Ensure they align with the exporter YAML contract for each component.