Zabbix Web Scenario

htmlwebzabbix

One of my tasks with Zabbix is to monitor the many web applications that I support and gather accurate response times, emulating the user-experience. I have attempted to implement my scenarios based on the Zabbix Web Scenario section in the manual, but I can't manage to get Zabbix to login to the page.

In the Zabbix tutorial, they are using the namefield in the HTML to designate where to enter the data. Zabbix page example

On my web applications, this field is present for entering the user name and password, but not for the login button.
My page example

How can I get Zabbix to login to these pages without the name field being present in the HTML code?

Best Answer

Ok, I solved the problem. As per the comments, the button was not actually necessary to submit the content. However, the value of the name field was required for the username and password to submit properly.
Name fields
The trick was to create a login step, with the URL that is called when the form is submitted (in my example it is the action of the form). You need to put your post variables in this step as well, following redirects of course. Action
For example, using the above pictures:

URL: https://www.example.com/nu
Post (using macros in Zabbix): userName={user}&passWord={password}

Then, I created the login check step, which searched for a string that is on the landing page, and received a status code of 200.

Once this is working, you know that you have logged in successfully. Be sure that after all steps you want Zabbix to take, you have it log out.

Thanks for all the help in comments!

Related Solutions

Zabbix – trigger alerts from web scenario

The trigger expression {hosts1:web.test.fail[test.example.com].last()} will return a result of the latest test:

0 - OK. The web scenario test.example.com (all steps) was tested successfully;
1 - The first step of the web scenario test.example.com was failed (you have only one step of the scenario as you told);
UNKNOWN - The web host is unreachable.

If the trigger expression will return UNKNOWN state or value more than 0, the trigger will generate PROBLEM alert.

If you want to generate alert after three consecutive failed checks then rewrite the trigger expression as:

{hosts1:web.test.fail[test.example.com].sum(#3)}>0

This trigger will work with any step counts of your web scenario. It sends PROBLEM alert at first failed test and sends OK restore alert after three consecutive successful checks (180 secs after service was fully restored).

Zabbix Web Scenarios – How to Ignore First Failed Attempts

Solution/Workaround

I added tags on each trigger and I edited an e-mail actions by adding tag conditions.

For example:

First send an e-mail action: Can't ping the server.

ACTION tab
Conditions:
Tag value server equals icmpping

(rest unchanged)

Second send an e-mail action: Can't reach the website.

ACTION tab
Conditions:
Tag value server equals web

OPERATIONS tab
Default operation step duration: 3m
Operation details: Steps = 2-2; Step duration = 0