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

Prevent instrumentation - act just like a bridge b/w Zabbix and JMX #187

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

Comments

@mabrarov
Copy link

Not an issue (I just failed to find place where I can ask about it):

Is there a way (configuration) to prevent any instrumentation of Java classes (byte code changes) and to use Zorka just as a bridge b/w Zabbix server and JMX?

What Zorka configuration options should I use to avoid instrumentation - for example, to avoid changes in JBOSS_MODULES_SYSTEM_PKGS when integrating Zorka into JBoss / WildFly (http://zorka.io/p/docs/install/appsrv/wildfly/)?

@jitlogic
Copy link
Owner

Adding spy = no should disable instrumentation but I haven't tested it for a long time :)

Note that lots of built in metrics (ZorkaStats/HTTP, ZorkaStats/SQL etc.) will stop working as they depend on instrumentation.

@mabrarov
Copy link
Author

mabrarov commented Oct 20, 2018

So does it mean that if I use:

spy = no

then I do not need to modify JBOSS_MODULES_SYSTEM_PKGS?

@mabrarov
Copy link
Author

@jitlogic

Note that lots of built in metrics (ZorkaStats/HTTP, ZorkaStats/SQL etc.) will stop working as they depend on instrumentation.

I understand but I need Zorka to play just as a bridge b/w Zabbix Server and JMX.

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

No branches or pull requests

2 participants