Skip to content
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

Task manager UI #40029

Closed
bmcconaghy opened this issue Jul 1, 2019 · 5 comments
Closed

Task manager UI #40029

bmcconaghy opened this issue Jul 1, 2019 · 5 comments
Labels
Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@bmcconaghy
Copy link
Contributor

Implement task manager UI.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services

@alexfrancoeur
Copy link

The ES-UI team is building out a tasks UI (https://github.com/elastic/elasticsearch-team/issues/227) and after some discussion on slack, the general consensus (without design input) is that we should have a single UI for both Elasticsearch and Kibana tasks. At the moment, they are targeting the same release as us for this UI. @alisonelizabeth is leading this effort. Does it make sense to touch base and align our efforts sooner than later? I'd also like to get some design input on this decision.

@peterschretlen
Copy link
Contributor

Aside from the name these strike me as pretty different concepts.

Task management in elasticsearch is about in-progress work on a cluster. https://www.elastic.co/guide/en/elasticsearch/reference/current/tasks.html
It makes me think of task manager on windows / activity monitor on Mac / top on linux
It's like a snapshot in time of in-progress work, a lot of which is transient.

Task management is Kibana is more about scheduled work or periodic work. It's like a cron job manager or task scheduler. Most of the tasks won't be active at a given time. They may have concepts like a task history or audit log. A kibana task could end up creating one or more elasticsearch tasks.

It may make sense to co-locate them in the UI for people trying to centrally manage resources, but I'd expect they'd need very different UI.

@alexfrancoeur
Copy link

+1, I agree they are very different but as discussed in slack we'll need to think through the UI/UX for all of the task related "things" (slow queries, ES tasks, reporting, ml jobs, kibana tasks, etc.). Worst case scenario, this is a quick discussion and we decide to continue on with two separate UI's. For anyone following, I'll update this issue with notes after the discussion.

@ymao1
Copy link
Contributor

ymao1 commented Mar 18, 2021

Closing this old issue. Will re-open when we come closer to implementation.

@ymao1 ymao1 closed this as completed Mar 18, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

6 participants