Open hexedpackets opened 5 years ago
⚠ This issue has been automatically marked as stale because it has not been updated for at least two months. If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open. This issue will automatically be closed in ten days if no further activity occurs. Thank you for all your contributions.
Currently resource identifiers (RI's) are not filterable in visualization frontends like grafana. Since RI's are not indexed in elasticsearch, the filtering will have to happen after the metrics are fetched from bigtable (need to actually verify this with how the row-key is constructed). There is a UX workflow that needs to be thought out, on how a user takes an RI like podname and adds a filter for that since suggestions won't auto-populate anything.
This is needed to make troubleshooting problematic kubernetes pods easier and actually understandable. When you have 100's of pods its impossible to tell what is going on.
When talking various squads the use case for this is as follows. Alerts are typically a max/avg within a given region. When an alert fires often the on-call person will change the aggregation from region -> instance. That instance is then usually added to a filter.