[ZBX-1181] Incorrect WEB data processing in case of a failed scenario step Created: 2009 Nov 03 Updated: 2017 May 30 Resolved: 2010 Dec 22 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | None |
| Affects Version/s: | 1.8.4rc2 |
| Fix Version/s: | 1.8.4 |
| Type: | Incident report | Priority: | Major |
| Reporter: | Alexei Vladishev | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
1.7.1 |
||
| Issue Links: |
|
||||
| Description |
|
If a WEB step fails (cannot match page or incorrect response code), we save speed and response time as 0. It is incorrect. We must save correct data and also display correct data for the step in Monitoring->WEB, and also have them correct in history. Now zeroes are displayed there for the failed step. Another small improvement, when we edit scenario details, please reset next check time, so the WEB scenario will be executed immediately. |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2010 Dec 17 ] |
|
To be fixed under this issue: if one of cURL functions fails for some reason, then HTTP poller goes into a (possibly infinite) CPU-intensive loop. |
| Comment by Aleksandrs Saveljevs [ 2010 Dec 20 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-1181. |
| Comment by Aleksandrs Saveljevs [ 2010 Dec 20 ] |
|
Field "nextcheck" will not be reset when updating a Web scenario. |
| Comment by Aleksandrs Saveljevs [ 2010 Dec 22 ] |
|
Merged into pre-1.8.4 in r16325. |
| Comment by Aleksandrs Saveljevs [ 2010 Dec 22 ] |
|
If the server was compiled without cURL, then a corresponding message will now be visible in the frontend. |