With the final formalization of the data-tier concepts into Elasticsearch with this issue, I think there is value in also formalizing this concept into the Monitoring app of Kibana.
The primary use case in question here, is adding views over the "disk available" section of the overview component. Overall a cluster might still have 50% of its disk available, however all of the hot nodes might actually be approaching capacity. Enabling this high level view to break this down by data tier types would enable ops teams to get a better understanding of their cluster quicker.
Secondary use cases might also include being able to break down the other views of the app by data tier as well.
With the final formalization of the data-tier concepts into Elasticsearch with this issue, I think there is value in also formalizing this concept into the Monitoring app of Kibana.
The primary use case in question here, is adding views over the "disk available" section of the overview component. Overall a cluster might still have 50% of its disk available, however all of the hot nodes might actually be approaching capacity. Enabling this high level view to break this down by data tier types would enable ops teams to get a better understanding of their cluster quicker.
Secondary use cases might also include being able to break down the other views of the app by data tier as well.