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

Mechanism for Auditing Network Access Not Isolated by Hystrix #116

Closed
benjchristensen opened this issue Feb 27, 2013 · 1 comment
Closed

Comments

@benjchristensen
Copy link
Contributor

Explore options for tracking when network access is done with Hystrix isolating it (such as within a thread isolated HystrixCommand).

If a reasonable solution can be done generically implement a contrib module.

The intent is:

  • find unknown vulnerabilities
  • track "drift" over time as transitive dependencies pull in code that performs network access
  • track metrics and optionally provide alerts
  • allow failing a canary build if unexpected network access occurs
  • alert in production if unexpected network access starts (such as if a property is flipped to turn on a feature)
@ghost ghost assigned benjchristensen Feb 27, 2013
abersnaze pushed a commit to abersnaze/Hystrix that referenced this issue Nov 7, 2013
Netflix#116

- Java agent for instrumenting blocking and non-blocking IO and notifying of these events to a registered listener.
- Hystrix.getCurrentThreadExecutingCommand to allow querying if currently inside a command
abersnaze pushed a commit to abersnaze/Hystrix that referenced this issue Nov 7, 2013
This is a tweak to: Netflix#116

It should only start/stop on immediate sides of executeCommand() being invoked.
@karthikitzmi
Copy link

karthikitzmi commented Nov 21, 2016

HystrixNetworkAuditorEventListener#handleNetworkEvent() isn't invoked when encountered with "java/net/ConnectException". Its not invoked with few other Simple Network exceptions. Here is the link for one of them.

http://stackoverflow.com/questions/40643621/hystrixnetworkauditoreventlistener-is-not-invoked-upon-failure-in-connecting-to

Is there anything that could be done. Not sure if it's the new issue . Any info on this issue would be helpful.

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

No branches or pull requests

2 participants