Splitting up HTTP into separate individual tests - best practice?

(2nd try correcting from-address)

Wouldn't using the 'httpstatus'-test solve the problem of separate status columns and alerting? P probably i didn't get the hardcase correctly but the following example gives 2 columns (h_app1 and 2) and allows separate alerting. In addition xymon " feeds" the data to the http- column - so all checks are aggregated there.

hosts.cfg:
1.2.3.4    appsrv.example.com     #
httpstatus=h_app1;http://appsrv.example.com:80/;200;3..|4..|5..|999
httpstatus=h_app2;http://appsrv.example.com:81/;200;3..|4..|5..|999

alerts.cfg:
SERVICE=h_app1
        MAIL user-5d4c7ac01393@xymon.invalid

SERVICE=h_app2
        MAIL user-37188eade3bf@xymon.invalid

Thomas

user-ce4a2c883f75@xymon.invalid schrieb:

On Thu, 8 Nov 2012 22:23:28 -0500, Betsy Schwartz
<user-c61747246f66@xymon.invalid> wrote:

I have a high-visibility request to change all of our server http
tests so that they appear as separate tests per URL,  with the ability
to alert separately, sign out separately, etc.
As most of our web servers are application servers in one form or
another, the various URL's test very different functionality.

I have been thinking about making this configurable, so you could do

  http=App1;http://myserver/App1 http=App2;http://myserver/App2

and have "App1" and "App2" appears as separate columns.


Haven't done any code yet, though, since this would happen "automagically"
with the new network tester I have underway for Xymon 5.0. So putting it
into 4.x would be somewhat of a wasted effort.

But I have the same issue myself, so perhaps I should look at how much
effort it would take.


Regards,
Henrik