-
Notifications
You must be signed in to change notification settings - Fork 31
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
Return value is True even if value is not actually sent #5
Comments
I don't really want to parse plain text in order to get this information, unless there is a good use-case where this is required. |
The use case is clear, the information is sent however the host/key did not exist, therefore sending the value failed, although the actual connection was successful (which is why 'response' is 'success'). I know that was a quick and dirty way to solve it, I also think the response should be properly parsed and then evaluated. Just didn't have the time to do it, but I'll get to it and let you know, if you still believe it's something you would allow to be implemented. Thanks |
If you could make a small patch to implement this, that would be great. |
|
Hey,
The function for sending data only evaluates if the response from the Zabbix server was valid or not:
if resp.get('response') != 'success':
There are cases where the response is successful though actually sending the value failed:
Maybe you could add another condition for the evaluation, something as simple as:
if resp.get('response') != 'success' or resp.get('info').find('failed: 1') != -1:
Thanks
The text was updated successfully, but these errors were encountered: