[ZBX-6581] host not printed out in web monitoring error messages Created: 2013 May 08  Updated: 2017 May 30  Resolved: 2013 May 31

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 2.1.0

Type: Incident report Priority: Minor
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: logging, webmonitoring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

templated web monitoring was implemented for 2.2, but error messages were not changed to identify host - it is now really hard to find which scenario is causing the messages. all messages should include host name, but a couple of examples :

774:20130508:100927.390 web scenario step "Local web scenario:" error: error doing curl_easy_perform: URL using bad/illegal format or missing URL
774:20130508:100927.408 web scenario step "b:b" error: error doing curl_easy_perform: Couldn't resolve host name



 Comments   
Comment by Aleksej Ivanov (Inactive) [ 2013 May 14 ]

Available in developement branch svn://svn.zabbix.com/branches/dev/ZBX-6581

Comment by dimir [ 2013 May 23 ]

How about (first example - scenario fail, second - step fail):

  • cannot process web scenario "My scenario" on host "Zabbix server": URL using bad/illegal format or missing URL
  • cannot process step "Second page" of web scenario "My scenario" on host "Zabbix server": Couldn't resolve host name

?

Comment by dimir [ 2013 May 23 ]

The error message will be generated in the log file for every processing of the scenario. Is that OK or this message better appear only the first time?

<richlv> i believe that's how it is done currently, too, right ?
if so, i'd probably leave it that way. it spams the logfile, but doing otherwise would make it much harder to spot issues

dimir Ye, that's current behavior, leaving it as it is then.

Comment by dimir [ 2013 May 24 ]

Successfully tested. Improved the web monitoring messages a lot. Please review the changes in r35832.

sasha TESTED please review my changes in r35982.

dimir Great, please review my small fix in r35990.

Comment by dimir [ 2013 May 31 ]

Fixed in pre-2.1.0 r35995 .

Comment by richlv [ 2013 May 31 ]

(1) whatsnew

so the new messages look like this :

cannot process step "b" of web scenario "b" on host "screenhost": Couldn't resolve host name
cannot process step "" of web scenario "Local web scenario" on host "Web server 1": URL using bad/illegal format or missing URL
cannot process step "statuscode" of web scenario "statuscode test" on host "A Test host": Couldn't connect to server

added at https://www.zabbix.com/documentation/2.2/manual/introduction/whatsnew220#improved_error_logging
RESOLVED

dimir Wait, how did you get that empty step?

<richlv> mnoovk sebagraq

dimir I beg your pardon?!?!?!!?!!?!!!/!?!?!?1//1!?11//1/1?1??!?!??

dimir So, it looks like at this point it's not possible to have a step with empty name but it was possible before. So you might end up with message nr. 2 above.

As for docs, looks great, thanks! CLOSED

Generated at Thu Apr 25 22:53:23 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.