-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EctoJob UI #47
Comments
Awesome @joshuataylor ! I’m wondering if the Notifications for UI should be a little different to ones used for workers. Worker notifications only include the queue name. UI notifications payload could include the queue name, job ID, operation (insert/update/delete) and job status. This would allow the UI to show visibility of all queues without having to configure them explicitly. |
Makes sense! I'll make a new branch for ecto_job that'll play around with these concepts, then however it's decided we can just refactor the code that updates the pubsub with this. The way I've done it is setup a Genserver with ecto_job_ui that listens with Postgrex, then sends Phoenix Pubsub so that every client connected (though there shouldn't be many for a tool like this) doesn't use pg_notify. |
I have just added mysql support. Mysql do not provide such pubsub feature, so jobs are polled regularly from DB. |
How about embedding the UI within the Phoenix Live Dashboard? Metrics could be exposed via telemetry and shown on the existing LiveDashboard metrics page. |
Following from the proof-of-concept in #46 this issue is to track the integration between ecto_job and a separate EctoJob UI from @AaronCowan.
The text was updated successfully, but these errors were encountered: