Chronograf: As a user I can see a host list view configuration page

Created on 12 Dec 2016  路  11Comments  路  Source: influxdata/chronograf

The idea here is to allow the user to select the tags that populate the table as well as to attach apps to dashboards

stale design feature request epihost_page

Most helpful comment

All 11 comments

See also #2025

See also #1790

Here's my first pass at a design for this.

User can create "Host Groups" which appear as vertical tabs with a table inside. Create & Update of groups is accessed via the + Create Group or Settings buttons
manage-hosts--table-v0

Create & Update overlay
manage-hosts--overlay-v0

Not sure the details of how the user will narrow scope on the group and a column. I'm guessing it will be kind of like a query so I have a text field for now. There is probably a more elegant way to handle this. Perhaps once the main filter for the group is set, then the column options appear. In each row of the options the user can select a tag or something using a dropdown instead of a text field

Initial questions:

  • What would the default screen look like with no configurations?
  • Could someone create groups that match to an App?
  • Could someone create a group from a specified list of things (hosts, apps, ids, containers)
  • Why does the user need to specify the column type?
  • How would the user re-arrange the columns?
  • What does the filter syntax look like? Is this builder just creating a giant query behind the scenes?
  • What timeframe does this cover?
  • We want to be careful about the use of "host" here. It could be physical or virtual or container id. Could be long running or short lived.

I'll provide feedback from a consumer and Enterprise level, on just the items that need attention. I'll share this from a disaster recovery standpoint, rebuilding a system, etc. Often times, depending on how your system model is architected, you will get a different hostname with each hardware. If I rip and replace after a hurricane or earthquake, obviously, I am not going to have the same hardware. If my DB is in AWS or the likes of, easy to maintain that data structure, however, a delete command seems very simple.

By the way, I arrived at this item because of previous posts about deleting stale hosts. I assume this is the place for that issue, but Ill provide feedback that I hope will give some direction. :)

Initial questions:

Could someone create groups that match to an App?
Yes, what if I only want a mayor or public official to see certain data, in this region, or in his county? I don't need them seeing the entire State data.

Could someone create a group from a specified list of things (hosts, apps, ids, containers) Yes, see above. However, if you're in the world of Docker or Kube, or AWS, we would use tags. All should be available as a string or query to complete such.

We want to be careful about the use of "host" here. It could be physical or virtual or container id. Could be long running or short lived.
Neither should matter, you are correct. I may only need a system while I am building a new infrastructure or certain components. When I walk away, I wouldn't leave that artifact. VM or physical.

manage-hosts--v2.pdf

Here's the latest iteration of the design

Aiming for a flow in which a user can create template variables during the table creation process, which can then be sent along to a dashboard. This should be it fairly smooth to have a pairing between an overview table and a dashboard view

To-Do:

  • [x] Empty State design
  • [x] Add time range and autorefresh to page header
  • [ ] What happens to the table columns if a user changes the filter in Table Settings?

Moved this issue into "In Progress" since it pertains to design, assuming we will break it up into smaller stories during IPM

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed because it has not had recent activity. Feel free to reopen if this issue is still important to you. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings