The AAD status UI

StackState Self-hosted v5.0.x
This page describes StackState version 5.0.


The AAD status UI provides details on the technical state of the AAD. It can be used to retrieve information about scheduling progress, possible errors, the ML models selected and job statistics.

When to use the AAD status UI

Common questions that can be answered in the AAD status UI:
Is the AAD Kubernetes service running? If the status UI is accessible: The service is running. If the status UI is not available: Either the service is not running, or the Ingress has not been configured (See the install section).
Can the AAD Kubernetes service reach StackState? Check the status UI sections Top errors and Last stream polling results. Errors here usually indicate connection problems.
Has the AAD Kubernetes service selected metric streams for anomaly detection? The status UI section Anomaly Detection Summary shows the total time of all registered streams, if no streams are selected it will be zero.
Is the AAD Kubernetes service detecting anomalies? The status UI section Top Anomalous Streams shows the streams with the highest number of anomalies. No streams in this section means that no anomalies have been detected. The status UI section Anomaly Detection Summary shows other relevant metrics, such as total time of all registered streams, total checked time and total time of all anomalies detected.
Is the AAD Kubernetes service scheduling streams? The status UI tab Job Progress shows a ranked list of streams with scheduling progress, including the last time each stream was scheduled.

Access the status UI


To access the status UI by proxy, run kubectl proxy:
kubectl proxy
The UI will be accessible at the URL:


For more permanent accessibility, the status UI can also be exposed using ingress configuration. The example below shows how to configure an nginx-ingress controller.
# status UI ingress (the configuration below is example for nginx ingress controller)
enabled: true
hostname: <domain name> # e.g.
port: 8090 # status page will be available on
annotations: <domain name> # e.g. nginx nginx
- host: <domain name> # e.g.
Setting up the controller itself is beyond the scope of this document. More information about how to set up Ingress can be found at: