Skip to content
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

Feature request for Conntrack metrics #1204

Open
pppyx opened this issue Jan 9, 2025 · 0 comments
Open

Feature request for Conntrack metrics #1204

pppyx opened this issue Jan 9, 2025 · 0 comments

Comments

@pppyx
Copy link

pppyx commented Jan 9, 2025

Hi Retina team,
I'm from Cosmic networking team, we want to implement SNAT port auto-increase feature based on the real-time pod-level egress connections count, the gauge conntrack metrics that show "a pod is keeping(open&time-wait) how many egress tcp/ucp connections at 1 timepoint" is required.

I think the dimension we need is cluster, instance(node name), source namespace, source podname, egress destination ip, destination port, protocol(tcp/udp), value

Really appreciate if you can help us about this. Retina team have already helped us about the alert for SNAT port exhaustion issue, and if we can launch the SNAT auto-increase feature, we can address & auto-resolve the whole SNAT issue thoroughly! This has a huge impact on improving the current COSMIC user experience.

Thanks,
Yanxin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant