Looking at the 7.6 design, I'm realizing that I'm really missing the URL column in the list. Esp. when id/name are not configured as is the case on one of our test clusters (SS below). @katrin-freihofner @drewpost WDYT about bringing it back in some form for the non-expanded table?
I realize that this would ordinarily be considered a feature, and not fit into the post-FF category, but I'm genuinely worried about UX in 7.6 without that field in cases like the SS below. In this case users must expand a row to see what the actual thing is being monitored. Now, it is true that the user should set the id/name for the monitor, but I'm wondering if that's not as prevalent as we'd like in the real world (I wish we had telemetry around that, and we will soon-ish hopefully).
One thought is that we could sneak the URL in below the name/id field in some compact form. Thoughts?
Looking at the 7.6 design, I'm realizing that I'm really missing the URL column in the list. Esp. when id/name are not configured as is the case on one of our test clusters (SS below). @katrin-freihofner @drewpost WDYT about bringing it back in some form for the non-expanded table?
I realize that this would ordinarily be considered a feature, and not fit into the post-FF category, but I'm genuinely worried about UX in 7.6 without that field in cases like the SS below. In this case users must expand a row to see what the actual thing is being monitored. Now, it is true that the user should set the id/name for the monitor, but I'm wondering if that's not as prevalent as we'd like in the real world (I wish we had telemetry around that, and we will soon-ish hopefully).
One thought is that we could sneak the URL in below the name/id field in some compact form. Thoughts?