Accessing AIDA

You can access AIDA user interface from different entry points.

In AIDA, each user is granted access to the same scheduling objects (such as jobs, job streams, and so on..) as they are in the Dynamic Workload Console. As a result, in AIDA, each user can view only KPIs and alerts related to these scheduling objects. Dynamic Workload Console administrators are also AIDA administrators and can work with all KPIs, manage special days, customize prediction tuning parameters, and pause alerts.

Dynamic Workload Console users can access AIDA from any of the following entry points:

From the Workload Dashboard of the Dynamic Workload Console
When anomalies in a KPI trend generate an alert, the alert is notified by AIDA through the Anomaly Widget on the Workload Dashboard.

For instructions about how to customize the Workload Dashboard with AIDA Anomaly Widget, see the topic Creating a customized dashboard for monitoring in the Dynamic Workload Console User's Guide.

The Anomaly Widget on the Workload Dashboard indicates the number of Anomaly Alerts that have been generated in the last 24 hours. To analyze the alerts, run the following steps:
  1. Click on the Anomaly Widget. A panel opens containing the list of the latest Anomaly Alerts. For each alert, the following information is displayed:
    • Alert severity
    • Alert description
    • A link to AIDA UI where you can find detailed alert information to quickly identify the root cause of the issue.
  2. Follow the link for the alert that you want to analyze. For details, see Analyzing an alert instance.
  3. Click the View all alerts button to view the full list of alerts.
Note:
When accessing AIDA UI from the Dynamic Workload Console, the connection authentication is based on the public key of the WebSphere Application Server Liberty SSL certificates, which is the default public key set during AIDA deployment. If you use custom certificates for the Dynamic Workload Console, you must change AIDA default public key accordingly. Properly customize the parameter:
  • DWC_PUBLIC_KEY in the common.env file, during AIDA deployment with Docker.
  • aida-nginx.waConsoleCertSecretName in the values.yaml file, during AIDA deployment with Kubernetes.
If AIDA is already installed, after changing the parameter run the command:

docker -compose up -d --build

For AIDA Docker installation only, to manage access to AIDA you can optionally use Keycloak.

Users defined with Keycloak are tipically AIDA administrators and can access AIDA from the following entry points:
From a direct login
AIDA administrators can directly login to AIDA user interface by using a dedicated userid and password. For details about defining users with Keycloak, see Configuring security.

AIDA user interface can be accessed at the link

https://aida-ip:aida-port/

where aida-host and aida-port are the values specified during AIDA deployment.

By following the link provided in the alert email notification
By following the link provided in the notification email, administrators can access the alert instance page in AIDA UI and run an anomaly analysis. For details, see Analyzing an alert instance.