The dashboard shows the types and the number of registered actors in the "Actors" tab for dapr applications running in self-hosted mode.
Actual Behavior
The "Actors" tab always shows "No registered actors". The issue only appears in version 0.11.0 of the dashboard in self-hosted mode. Everything works as expected in kubernetes mode or in self-hosted mode with the dashboard version 0.10.0, so I am guessing it is a regression from 0.10.0 to 0.11.0.
The metadata api seems to be unreachable from the dashboard, and all calls to http://localhost:8080/api/metadata/All/dapr-app always fail with ERR_EMPTY_RESPONSE. It might have been this commit that introduced the issue to the metadata api.
Steps to Reproduce the Problem
Install dapr-cli and run dapr init to install the latest runtime and dashboard versions locally.
Run any dapr application that registers actors.
Run the dashboard with dapr dashboard.
Navigate to http://localhost:8080 and to the details page of the running dapr app.
Expected Behavior
The dashboard shows the types and the number of registered actors in the "Actors" tab for dapr applications running in self-hosted mode.
Actual Behavior
The "Actors" tab always shows "No registered actors". The issue only appears in version 0.11.0 of the dashboard in self-hosted mode. Everything works as expected in kubernetes mode or in self-hosted mode with the dashboard version 0.10.0, so I am guessing it is a regression from 0.10.0 to 0.11.0.
The metadata api seems to be unreachable from the dashboard, and all calls to
http://localhost:8080/api/metadata/All/dapr-app
always fail withERR_EMPTY_RESPONSE
. It might have been this commit that introduced the issue to the metadata api.Steps to Reproduce the Problem
dapr-cli
and rundapr init
to install the latest runtime and dashboard versions locally.dapr dashboard
.http://localhost:8080
and to the details page of the running dapr app.Actors
tab nearSummary
.No registered actors
.Release Note
RELEASE NOTE: FIX Bug in dashboard.