-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
subctl should be able to report historical connection information #795
Comments
@maayanf24 would be interested in working on this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
So it can be used to run `subctl gather` inside a pod to collect data from metrics. Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
So it can be used to run `subctl gather` inside a pod to collect data from metrics. Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
So it can be used to run `subctl gather` inside a pod to collect data from metrics. Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
So it can be used to run `subctl gather` inside a pod to collect data from metrics. Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
So it can be used to run `subctl gather` inside a pod to collect data from metrics. Refer submariner-io/subctl/issues/795 Signed-off-by: Maayan Friedman <[email protected]>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
What would you like to be added:
A feature in
subctl gather
(or a specific sub-command) to report historical connection information. This might require storing that information somewhere new, but it should be available from Prometheus as a start (on setups running Prometheus of course).Why is this needed:
This helps identify connectivity issues: how frequently connections are broken, for how long...
The text was updated successfully, but these errors were encountered: