[Orca-users] Vertical marker in plots

[Thaddaus Rasmussen]

I can see how integrating with the data streams (by that you mean the RRDs
right?) would be difficult. Having a separate RRD to store the vrule
timestamps may be useful, but having the comments would be nice.

I am using Orca for monitoring several load test machines and I'm hoping to
put in a VRULE whenever I change/modify the load test for a specific client
PC.  I am hoping to use it as a way to annotate the graphs for easier
analysis. Theris one approach that I have been trying to investigate to get
this to work how I would like.

1.  Modifying the Orca::ImageFile::_update_graph_options subroutine to
accept arguments for pushing a VRULE option statement onto the @options
2.  Using a signal  to Orca (possibly adding to HUP) that will open a brief
user dialog to select a client from the list of available subgroups (These
are the client machines, if I am not mistaken, right?).  Then the dialog
would prompt for a comment string.  Then, by means of #1, the selected
subgroup will then have its @options array updated with the time the signal
occurred and the entered comment.

However, my Perl programming knowledge is limited and I am not sure if the
@options array is identical for all subgroups, or can it be distinct to each
subgroup?  Is there is feedback on a feasible approach?

Thanks,

Thad




On 8/18/06, Tankersley, Jon <jon.tankersley at eds.com> wrote:
>
>  I'd sent some 'hooks' for vrule into Orca directly to Blair.  The problem
> is the integration with the data streams.  Horizontal Rule was easy, and
> Blair adopted that.  VRules...are different.  They have to have EPOCH time
> stamps, etc.
>
> I've put some thought into it...
> I don't know if we could figure out a way to have an RRD of just data for
> vrule lines and then have Orca generate a vrule for every data point in the
> rrdtool plot interval.  The problem comes in with dealing with annotation of
> the vrules.  I don't think RRD's can have 'non-numeric' entities associated
> with EPOCH time.
> The other way would be to have some sort of 'include' file for the Orca
> run, but that didn't work all that well when I tried it.  I got inconsistent
> results.
>
>  ------------------------------
> *From:* orca-users-bounces+jon.tankersley=eds.com at orcaware.com [mailto:
> orca-users-bounces+jon.tankersley=eds.com at orcaware.com] *On Behalf Of *Thaddaus
> Rasmussen
> *Sent:* Friday, August 18, 2006 10:51 AM
> *To:* orca-users at orcaware.com
> *Subject:* Re: [Orca-users] Vertical marker in plots
>
> Hello,
>
> I wanted to bring this topic up again to see if anyone has created a
> solution for this challenge.
>
> I also have the desire to insert Vertical Markers within the graphs for
> similiar reasons.  From my reasearch of the RDDtool interface, this can be
> acomplished using the function:
>
> RDDs::graph option *VRULE**:**time**#**color*[*:**legend*].  However, I am
> having difficulty getting a seperate Perl script to use that option with the
> Orca RRDs files.  I am curious is there a way to inject the VRULE option
> into the Orca plots by say sending the Orca script a signal to do such??  Or
> is a seperate script the way to go about doing this?   If the latter it the
> better way, will there be any way of accessing the Orca variable used in the
> Orca::ImageFile module?
>
> Please forgive, I am new to Perl scripting as Orca has been my first
> endeavor in it.
>
> Thad Rasmussen
>
>
> Hi orca-users,
>
> I'm looking for a way of marking an event in time, by putting a vertical
>
> marker with a label in the plots, at a particular point in time.
>
> This is to mark intor the plots when a change in the environment
>
> happend, so it is eaysy to correlate the effect of the change in
> performance (if any) , to time of the change.
>
>
>
> --
> Jarle Bjørgeengen <
> jarle.bjorgeengen at usit.uio.no <http://www.orcaware.com/mailman/listinfo/orca-users>>
> Gruppe for basis systemdrift (BSD), SAPP, USIT
> University of Oslo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/orca-users/attachments/20060818/67533aea/attachment-0002.html>