Skip to content
This repository has been archived by the owner on Mar 26, 2018. It is now read-only.

Expose blocked connection stats as Prometheus metrics #7

Closed
awh opened this issue Sep 20, 2016 · 1 comment
Closed

Expose blocked connection stats as Prometheus metrics #7

awh opened this issue Sep 20, 2016 · 1 comment
Assignees
@awh
Labels
kind/feature
Milestone
1.8.0

Comments

@awh
Copy link
Contributor

awh commented Sep 20, 2016 •
edited
Loading

To enable diagnosis of programming/deployment errors and attacks, a summary of rejected traffic should be recorded for reporting and alerting purposes. This should take the form of a single 'blocked connections' metric with 'protocol' and 'destination port' labels.
@awh
Copy link
Contributor Author

awh commented Sep 28, 2016

NFLOG might be useful here.

@awh awh modified the milestone: 1.8.0 Oct 7, 2016
@awh awh changed the title Record connection attempts blocked by policy Expose blocked connection stats as Prometheus metrics Oct 7, 2016
@awh awh mentioned this issue Oct 12, 2016
Closed
@awh awh self-assigned this Oct 12, 2016
This was referenced Oct 14, 2016
Closed
Merged
Merged
@jml jml mentioned this issue Oct 17, 2016
Closed
@awh awh mentioned this issue Oct 19, 2016
Closed
@brb brb closed this as completed in #23 Oct 19, 2016
brb referenced this issue Oct 19, 2016
@brb
Merge pull request #23 from weaveworks/issues/7-blocked-connection-me…
026e057 
…trics

Expose blocked connection metrics
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@awh awh

Labels
kind/feature
Projects
None yet
Milestone
1.8.0
Development

No branches or pull requests
1 participant
@awh