View Source BroadwayDashboard (BroadwayDashboard v0.4.0)
BroadwayDashboard
is a tool to analyze Broadway
pipelines. It provides some insights about performance and errors for
your running pipelines.
It works as an additional page for the Phoenix LiveDashboard
.
You can inspect pipelines on remote nodes that are not running BroadwayDashboard
too.
See Distribution for details.
integration-with-phoenix-livedashboard
Integration with Phoenix LiveDashboard
You can add this page to your Phoenix LiveDashboard by adding as a page in
the live_dashboard
macro at your router file.
live_dashboard "/dashboard",
additional_pages: [
broadway: {BroadwayDashboard, pipelines: [MyBroadway]}
]
The :pipelines
option accept pipeline names (the :name
option of your Broadway).
By omitting the :pipelines
option, BroadwayDashboard
will try to autodiscover your pipelines.
live_dashboard "/dashboard",
additional_pages: [
broadway: BroadwayDashboard
]
Once configured, you will be able to access the BroadwayDashboard
at /dashboard/broadway
.
using-from-the-command-line-with-plds
Using from the command line with PLDS
It's possible to use Broadway Dashboard without having to install it on your application. PLDS stands for Phoenix LiveDashboard Standalone and it's a CLI version of Phoenix LiveDashboard with some tools pre-installed. One of those tools is Broadway Dashboard.
To install PLDS on your machine, you can run:
$ mix escript.install hex plds
Then connect to your running node with:
$ plds server --connect mynode --open
For more information about the usage, please check the PLDS documentation.
distribution
Distribution
Phoenix LiveDashboard works with distribution out of the box, and it's not different with Broadway Dashboard! You can inspect your pipelines that are running on connected nodes.
You can also inspect pipelines from nodes that are not running the same system of
your dashboard. This is possible because we "copy" the essential parts of this
tool to the remote node when it's not running BroadwayDashboard
. We stop the tracking
once the node that started it is disconnected.