[kepler-dev] question about logging and monitoring

ian.brown@hsbcib.com ian.brown at hsbcib.com
Tue Sep 11 07:47:44 PDT 2007

Hi, I have quite a large model that runs in real time using the Discrete
Event Director and which buys / sells currency on various foreign
exchanges. At the moment, I monitor this by means of a number of Timed
Scopes, monitors and displays attached as sinks at various 'interesting'
parts of the model. This is okay for a small scale implementation but will
not scale - eventually we may be running up to 100 models simulataneously!
What I think is required is for the individual models to log relevant
information as they run. A separate (and probably remote) application can
then selectively monitor those log signals. My thought at the moment is to
use log4j (because that's what Kepler seems to use). I'm thinking that I
can develop an actor that is a log4j sink (i.e. it is a sink that just
writes the input data to a specified log4j destination). Then, we can
develop something to watch the log output in real time on another machine.
My question is whether this is a good idea. Does anyone have any experience
in doing anything like this and in such case is there any experience that
you can offer?



HSBC Bank plc may be solicited in the course of its placement efforts for a
new issue, by investment clients of the firm for whom the Bank as a firm
already provides other services. It may equally decide to allocate to its
own proprietary book or with an associate of HSBC Group. This represents a
potential conflict of interest. HSBC Bank plc has internal arrangements
designed to ensure that the firm would give unbiased and full advice to the
corporate finance client about the valuation and pricing of the offering as
well as internal systems, controls and procedures to identify and manage
conflicts of interest.

HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority.


This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.

More information about the Kepler-dev mailing list