Documentation Error

[Ben Clewett]

That's right, from A to C.  Yes this will be a straight connecting line.

I understand your feeling on this being miss-guided.  But I see this 
information as a record of the latency of the plugin, not a check on 
whether there is a response.  That is better taken care of by returning 
  WARNING or CRITICAL from plugin exit code.

In PerfParse I am toying with leaving a gap in the graph where a value 
is expected but not forthcomming, if the user selects some option. 
However this is difficult as the user may have changed the timeing of 
the plugin and the gap may be an expected response :)

Either way, I would prefure to have no value, than to try and code a 
response for an infinite value.

Unless the people who designed the plugin performance protocol want to 
give us some valid extensions for coding an infinite value, or coding a 
NULL value.  Something like:

| latency=INFms

or

| latency=NULLms

But this is a better question for another news group, to which I'll make 
a posting now :)

Regards, Ben.








Andreas Ericsson wrote:
> Ben Clewett wrote:
> 
>> Andreas,
>>
>> I cannot talk with respect to other parsers.  But for our PerfParse 
>> project it would be better to report no data for this example.  The 
>> gap will then be ignored during data analysis, which will join the 
>> previous good value to the next good value parsed.
>>
> 
> So... the graph would go from point A to point C without ever popping by 
> point B? Won't that be sort of misguiding, since it in most cases will 
> create a more or less straight line.
> 



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click