This is especially useful once timeouts are configured for the service mesh: after a link is torn down, today there's no way to see that it ever existed.
The Sessions page only reports currently open, Ingress connections.
With this issue I propose to create two new pages: Ingress and Egress, where we can see all past connections and filter them by time range.
Service-to-service edges aren't needed to be tracked since given a defined service mesh their creation is expected, known, and deterministic.
Alternatively, instead of having them in separate pages, Ingress and Egress can be in included in the existing Sessions page where we can filter by "only active" (default), "only ingress", "only egress", "time range".
This is especially useful once timeouts are configured for the service mesh: after a link is torn down, today there's no way to see that it ever existed.
The
Sessionspage only reports currently open, Ingress connections.With this issue I propose to create two new pages:
IngressandEgress, where we can see all past connections and filter them by time range.Service-to-service edges aren't needed to be tracked since given a defined service mesh their creation is expected, known, and deterministic.
Alternatively, instead of having them in separate pages,
IngressandEgresscan be in included in the existingSessionspage where we can filter by "only active" (default), "only ingress", "only egress", "time range".