| UML2 Log Interactions [message #106280] |
Tue, 24 July 2007 11:03  |
Eclipse User |
|
|
|
Originally posted by: cvkmurthy.hotmail.com
Hi Experts,
I have two log files, client and server log which contains
transaction IDs. I defined transaction ID as an Extended Data Element. I
am using these transaction IDs to correlate the files. I defined a
filter which filters the log records based on a particular Transaction
ID. I did this by defining ExtendedDataValues like *<trans1>*. I am able
to see the log statements having this transaction ID in the Log View but
the UML2 Log Interactions does not show up the log interactions. What
could be the reason?
Regards,
Krishna
|
|
|
|
|
| Re: UML2 Log Interactions [message #107066 is a reply to message #106916] |
Wed, 01 August 2007 11:45  |
| Eclipse User |
|
|
|
Hi Krishna,
unfortunately your attachment has been removed and I cannot see the screen
shots. Can you reattach the screen shots as gif files? If I won't be able to
figure out from your screen shots the cause of your problem you may need to
send me your correlator, sample logs and a test case on how to reproduce
the problem.
Kind regards,
Alex Nan.
"Krishna" <cvkmurthy@hotmail.com> wrote in message
news:f8moil$2qr$1@build.eclipse.org...
> Hi Alex,
>
> I customized the LogCorrelator Engine provided as TPTP example to
> correlate the log files. Transaction ID is part of each statement in the
> log files. I created an ExtendedDataElement "TransactionID" and I am
> setting the value of this element with transaction ID read from the log
> files. When I apply "Show correlated log records only" I could see all
> the correlations. I defined a new filter which shows only the statements
> having the a particular transaction ID. Please see the attached
> document for the screeshots. In the log interactions view the logs are
> not correlated.
>
> Regards,
> Krishna
>
>
>
>
> Alex Nan wrote:
> > The log interactions view is using the same filtering mechanism and
filter
> > definition but with an additional flag "Show correlated log records
only" in
> > the filter definition. If this flag is specified in the filter
definition
> > the logic of applying the filter is the following: both correlation
source
> > and target events would need to satisfy the filter predicate in order to
be
> > included in the result set. So if you open just a log (not a
correlation!)
> > in the log interactions view and you have a filter defined that filters
out
> > uncorrelated events then you won't see any events in the view.
> > I need two questions answered from you in order to understand your
problem.
> > You are saying that you used the transaction ID to correlate the log
events,
> > did you create a correlator and registered it with the TPTP framework?
> > If so, are you viewing a correlation created with the above correlator
in
> > the log interactions diagram or just a log?
> > Kind regards,
> > Alex Nan.
> >
> > "Krishna" <cvkmurthy@hotmail.com> wrote in message
> > news:f854bj$f1o$1@build.eclipse.org...
> >> Hi Experts,
> >>
> >> I have two log files, client and server log which contains
> >> transaction IDs. I defined transaction ID as an Extended Data Element.
I
> >> am using these transaction IDs to correlate the files. I defined a
> >> filter which filters the log records based on a particular Transaction
> >> ID. I did this by defining ExtendedDataValues like *<trans1>*. I am
able
> >> to see the log statements having this transaction ID in the Log View
but
> >> the UML2 Log Interactions does not show up the log interactions. What
> >> could be the reason?
> >>
> >> Regards,
> >> Krishna
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.29566 seconds
Home