I'm having an issue with Zabbix web monitoring. I am monitoring our SSO service and have configured 8 web scenarios (one for each of our authsources).
The scenarios are all identical except for the variables used. For some reason one of them fails on the required pattern missing, I couldn't replicate it manually and I've narrowed it down to the username variable.
In the scenario that fails the username variable is {user} => user_name
When the variable contains an underscore the scenario fails at step 2 of 4.
If I remove the underscore in the variable to be {user} => username
Then it will correctly fail at step 3 of 4 (as the user without an underscore doesn't exist).
The simple solution is to create another user on our back-end without an underscore, then all steps finish correctly - but this isn't always possible as we don't always have control over the user accounts we are given.
Is this a bug or have I missed some documentation somewhere that I should be escaping underscore characters?
Attached images of complete scenario and steps 1 to 3.
The scenarios are all identical except for the variables used. For some reason one of them fails on the required pattern missing, I couldn't replicate it manually and I've narrowed it down to the username variable.
In the scenario that fails the username variable is {user} => user_name
When the variable contains an underscore the scenario fails at step 2 of 4.
If I remove the underscore in the variable to be {user} => username
Then it will correctly fail at step 3 of 4 (as the user without an underscore doesn't exist).
The simple solution is to create another user on our back-end without an underscore, then all steps finish correctly - but this isn't always possible as we don't always have control over the user accounts we are given.
Is this a bug or have I missed some documentation somewhere that I should be escaping underscore characters?
Attached images of complete scenario and steps 1 to 3.
Attached Files
Comment