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

[Infra UI] Services overview page #26167

Closed
skh opened this issue Nov 26, 2018 · 8 comments
Closed

[Infra UI] Services overview page #26167

skh opened this issue Nov 26, 2018 · 8 comments
Labels
Feature:Metrics UI Metrics UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services

Comments

@skh
Copy link
Contributor

skh commented Nov 26, 2018

Add a page to show an overview of services. It should contain

  • query bar
  • datetime range picker
  • list of services reporting data, within the given datetime range and with the given filter query applied, if any
@skh skh added the Feature:Metrics UI Metrics UI feature label Nov 26, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/infrastructure-ui

@skh skh self-assigned this Nov 26, 2018
@makwarth
Copy link

makwarth commented Jan 2, 2019

@skh we should discuss design of this feature, and how it (hopefully) fits with the proposed layout changes in #27916

@makwarth
Copy link

Had a chat with @skh about this feature.

  • The primary purpose of this feature is service discovery.
  • It likely makes sense to have "Services" as a top level feature. (New tab here)
  • As a first iteration, showing a full list of services running on the infrastructure with respective links to Kibana dashboards might be sufficient. (No metrics)
  • The services list should have basic filtering via the query bar (host name, container name, service name, etc.)
  • We'll need to check if the dashboards exists before linking off. Hopefully it's possible to pass filter params as part of the link. Need to investigate.

Thoughts @ruflin @exekias @roncohen ?

@ruflin
Copy link
Contributor

ruflin commented Jan 11, 2019

Overall LGTM. +1 on a new tab.

Agree that links to dashboards are sufficient to get started. What I would like to add here is the link can be edited. There will be services which don't have a dashboard yet and the user can link his own or even added more dashboards for a specific service.

@exekias
Copy link
Contributor

exekias commented Jan 11, 2019

Thanks @makwarth, that sounds good to me

@makwarth
Copy link

@ruflin @exekias Thanks for the input. I'm wondering if we should pause for a bit and wait for users to request a service discovery feature. Do you have input on the importance of this feature? I don't think I've seen explicit requests for it, so I want to make sure we fully understand the problem we're trying so solve here before diving into implementation of a new top level feature. Thoughts?

@ruflin
Copy link
Contributor

ruflin commented Jan 14, 2019

I personally think we should at least build the foundation, meaning the links to the dashboards. Right now it's tricky to find the right links from the Infra UI to each single dashboard for each service. We put quite a bit of effort in all the modules and having this service tab with links to the dashboards will make them much more accessible and visible.

@skh skh removed their assignment Jan 22, 2019
@alvarolobato alvarolobato added the Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services label Jan 29, 2019
@makwarth
Copy link

We discussed this feature today and decided the following approach: #31405
This feature will enable users to do service discovery and view metrics of nodes with certain services. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Metrics UI Metrics UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Projects
None yet
Development

No branches or pull requests

6 participants