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

Zabbix can't recieve data when using agent encryption #19

Open
j91321 opened this issue Apr 25, 2019 · 3 comments
Open

Zabbix can't recieve data when using agent encryption #19

j91321 opened this issue Apr 25, 2019 · 3 comments

Comments

@j91321
Copy link

j91321 commented Apr 25, 2019

I'm using zabbix-agent-extention-elasticsearch 20180831.32_7cbc5d1 and I noticed that Zabbix will not receive most of the items when only encrypted communication is allowed from host.

As a workaround allow No encryption from host together with PSK or Certificate.

Not sure if this is a problem in the newer versions too, feel free to close this issue if it is already fixed. Just wanted to save somebody time debugging the issue, because it's not really mentioned anywhere.

@tears-of-noobs
Copy link
Contributor

@j91321 Hi. Do you talk about communication between the extension and elasticsearch node through HTTPS?

@tears-of-noobs
Copy link
Contributor

@j91321 Seems I've understood what you mean. You talk about - https://www.zabbix.com/documentation/4.2/manual/encryption. It's a pity but now we don't support any of the encryption features. The zabbix-sender functionality of the extension implemented in https://github.com/adubkov/go-zabbix and there is only one solution - to make a PR with encryption support to the library.

@j91321
Copy link
Author

j91321 commented Apr 26, 2019

@tears-of-noobs Yes that's what I mean. If I'll have time I'll look into it, but I doubt my go skills are good enough. Anyway think it would be worth adding this to the readme, in case anybody else encounters this problem.

For me the workaround of allowing no encryption from host for extension and PSK for agent is good enough and acceptable solution. This way only the data collected by the extension goes unencrypted.

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