-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Support Jolokia agent in proxy mode #4421
Comments
I wonder how come the proxy mode is not supported? Any idea on what exactly we're missing? Or is one of the limitations listed there affecting us? |
The reason I think it is not going to work in proxy mode is that proxy mode requires the url, username and password passed. And that is not possible in our config at the moment:
|
@whale-shark Looking at this issue I saw that you did a commit referencing this issue. Does the commit you made work? If yes, any chance to contribute it back? |
@whale-shark Awesome. Left some comments on the PR. Are you using this code on your end in production / testing? Did you compile your own beat? |
@ruflin Thank you for checking. I built it locally on my CentOS. The bundled test did not work well from the beginning, so I could not do it. |
Any binary to test it? |
@balamacab For a binary you would have to check out #6475 and run |
@ruflin Can this issue be closed? The docs were updated with this commit. Since the options are now documented, users will expect this to be supported. Not clear to me from this exchange whether we can say that's the case. |
Yes, proxy mode should now be supported. @jsoriano Please correct me if that is not the case. |
Currently, we do not support the Jolokia agent when it is run in proxy mode. There are users out there with IT restrictions and not able to get approvals for installing a direct agent so supporting the proxy mode will be helpful for these situations.
The text was updated successfully, but these errors were encountered: