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

TLS support #186

Open
mabrarov opened this issue Mar 23, 2018 · 2 comments
Open

TLS support #186

mabrarov opened this issue Mar 23, 2018 · 2 comments
Assignees

Comments

@mabrarov
Copy link

Not an issue but feature request:
It would be very helpful if Zorka could support TLS - both certificate based TLS and TLS PSK, in both passive and active modes. This would make Zorka complete equivalent to Zabbix Java gateway in terms of supported features.

@jitlogic
Copy link
Owner

I still remember about this :) I have to backport some TLS library that does not interfere with built in JVM cryptography/SSL/TLS implementation, possibly BouncyCastle.

@mabrarov
Copy link
Author

mabrarov commented Oct 20, 2018

does not interfere with built in JVM cryptography/SSL/TLS implementation

That's the reason I started thinking that native JVM agent (bridge to JMX with Zabbix Agent interface implemented as native JVM agent) could be a better choice:

  1. no need to care about interfering with Java libraries (standard or 3rd-party), additionally this fact gives freedom in terms of available solutions for cryptography (though there is a chance that static linking will be required)
  2. doesn't use JVM heap so won't be (much) impacted by high memory consumption of Java application (at least is able to report about that before JMX will be down)
  3. doesn't impact GC ("C++ doesn't produce garbage" joke), i.e. smaller footprint for the monitored Java application

I know (have some experience with) Dyntrace uses (provides) native JVM agent for monitoring of Java applications.

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

3 participants