plainblack.com
Username Password
search
Bookmark and Share
View All Tickets
wremonitor doesn't say which site generated an error  (#4097)
Issue

when the wremonitor sends out this error message

A workflow activity has a priority that is too high.
localhost

It does not indicate which site is having the problem.

Susan B

Solution Summary
Comments
koen
0
9/9/2008 4:49 pm

on the #WebGUI irc channel Haargh suggested this patch for wremonitor.pl in line 105:

if(my @sites = grep { $workflowsPerSite->{$_} >= $maxWorkflowsPerSite } keys %$workflowsPerSite ) {
sendEmail(qq|There are too many workflows running on these sites: | . join(', ', @sites));
}

That would only list all sites that have more then the maxWorkflows number of workflows.

And he also mentioned: "one thing to keep in mind is that the messages are currently kept short so they can be sent via sms".

Perhaps the above is the fix for this bug, but I cannot test that so I think it would be unwise for me to implement that right now. And then again, the list of sites could potentially also make the message long.

Perhaps this is more of an RFE than a bug?

Koen de Jonge - ProcoliX
http://www.procolix.com
Hosting - WebGUI - Virtualization

susanb
0
9/9/2008 5:15 pm
How about a separate message for each site that exceeds the threshold.  
That way message length would still be small, but necessary  
information for possibly acting on and resolving the problem would be  
included. When it tells me localhost is having a problem and I have 10  
sites on that server (which I can only determine from the From  
address) I spend much more time trying to find the misbehaving  
workflow than I should have to.

--Susan (Not a programmer, so will not/cannot evaluate code snippet)


On Sep 9, 2008, at 2:49 PM,    
wrote:

>
> koen has posted to one of your subscriptions
> http://www.plainblack.com/bugs/tracker/wremonitor-doesnt-say-which-site-generated-an-error/1
> on the #WebGUI irc channel Haargh suggested this patch for  
> wremonitor.pl in line 105:
>
> if(my @sites = grep { $workflowsPerSite->{$_} >=  
> $maxWorkflowsPerSite } keys %$workflowsPerSite ) {
> sendEmail(qq|There are too many workflows running on these sites:  
> | . join(', ', @sites));
> }
>
> That would only list all sites that have more then the maxWorkflows  
> number of workflows.
>
> And he also mentioned: "one thing to keep in mind is that the  
> messages are currently kept short so they can be sent via sms".
>
> Perhaps the above is the fix for this bug, but I cannot test that so  
> I think it would be unwise for me to implement that right now. And  
> then again, the list of sites could potentially also make the  
> message long.
>
> Perhaps this is more of an RFE than a bug?
>
> Koen de Jonge - ProcoliX
> http://www.procolix.com
> Hosting - WebGUI - Virtualization
>
>
>
> Unsubscribe
>
>
>
> --
>
> Plain Black, makers of WebGUI
> http://plainblack.com

koen
0
9/10/2008 1:42 am

[quote]How about a separate message for each site that exceeds the threshold.[/quote]

I think that an RFE for having separate messages for SMS and for E-mail is the right way to go.

[quote]I spend much more time trying to find the misbehaving  
workflow than I should have to.[/quote]

An RFE for a (commandline) tool that shows you what spectre is doing on which sites that gives you a full outline is probably the solution for this.

After a good night sleep I think that this bug isn't a bug. The e-mail is used to notify you that 'something might be wrong, go have a look' and that is all it's designed to do. It is deliberately short so it can be sent as an SMS too.

I would say the only bug is that it's not clearly documented that this is its use.

Koen de Jonge - ProcoliX
http://www.procolix.com
Hosting - WebGUI - Virtualization

Graham
0
9/10/2008 10:15 am

There are various ways this could be reported that would keep the message short yet provide more information.  It could include the site with the most workflows, how many workflows it has, and how many other sites are over the limit.

The hostname it includes in the message is the default Apache hostname as configured in the wre.conf file.  If you have it set to a site that exists on the server, it makes it easy to know what server you are dealing with.

koen, is there some information that spectre.pl --status doesn't provide that is needed?  Improvements to that would be an RFE, but it seems like it already gives the information needed.

JT
0
9/10/2008 11:33 am

Fixed in 0.8.5

Details
Ticket Status Closed  
Rating0.0 
Submitted Bysbaur 
Date Submitted2008-08-29 
Assigned To unassigned  
Date Assigned2010-07-31 
Assigned By 
Severity Cosmetic (misspelling, formatting problems)  
What's the bug in? WRE  
WebGUI / WRE Version 0.8.3  
URLbugs/tracker/wremonitor-doesnt-say-which-site-generated-an-error
Keywords
Ticket History
© 2010 Plain Black Corporation | All Rights Reserved