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

feat: forward accept/drop metrics #229

Open
WDaan opened this issue Mar 6, 2024 · 2 comments
Open

feat: forward accept/drop metrics #229

WDaan opened this issue Mar 6, 2024 · 2 comments
Labels
enhancement New feature or request feature request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@WDaan
Copy link

WDaan commented Mar 6, 2024

What would you like to be added:

I'd be nice if instead of just logging events like this, they also would tracked as a metric like cilium does.

Why is this needed:
This would allow for easy debugging/monitoring. Currently you could still do it by building dashboards on top of the log messages, but doing this through metrics would be a more ergonomic approach.

@WDaan WDaan added the enhancement New feature or request label Mar 6, 2024
@jayanthvn jayanthvn added good first issue Good for newcomers help wanted Extra attention is needed labels Jun 11, 2024
@shukla2009
Copy link

Its quite important feature specially in case of debugging

@shaunofneuron
Copy link

I'm in the process of moving away from kube-iptables-tailer and currently have no alternative for getting kubernetes events when traffic is being blocked by a network policy. It would be great to have metrics, it would be even better to have k8s events with context like pod/service (not just dest ip/src ip from event logs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants