LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

I am releasing this library here, so people can download the latest copy of it, and this provides a good place to provide feedback as well.

This asset was introduced in Session 15, but this seems a better place for ongoing discussions, and newer releases.

I don't think it is far enough along to warrant going into the prototype library yet, and it is special purpose enough that it might always be in a different library, but here it is.

Please feel free to post on this thread for uses you have found with it, success stories, issues, or post any updates to it.

Incidentally, there are a couple of bugs regarding inFlow visualizers and library inheritance that make this a bit more usable once 4.5.3 is released.

Cheers
Rich
Attachments:
LAE Profiling.brg

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Kirk Purches

I love this Library! But I can't figure out how to turn on the brd log file generation.

The logs were already there in my environment, but only for brx's that are launched via cron jobs with nohup shell scripts; the brd log files are in:

/mda/log/brain_####/controller/brd/graph.date.log.brd
(where #### is the port number)

But, how do I enable getting these brd log files generated ad-hoc from the brg's that I run on my destop BRE against a server farm or my local machine? Is there a property setting somewhere I need to enable?

Please advise.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Kirk, I'm glad you are loving it! Unfortunately, right now, the only way to get the brdlogs is from the external controller running with the command line. I have just posted PR 3721 (feel free to update with your thoughts), that requests the ability to capture brdlogs when using the external controller from BRE. That shouldn't be that difficult; having a brdlog when using the internal controller will be unlikely, however.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

So I have updated this a bit, and it now can be used with statsfiles. For those that don't know, the LAE can generate stats on EVERY node that is executed on a server, with a setting: ls.brain.server.logFileStats. If this is set to a file, the LAE will write to that file, one line per node execution. I have updated the Porfolio Analyzer to take either brdlogs or this stats file (it has two inputs, use either one, but if you use both, it only uses the brdlog input.

There are still some issues, in that there is no concept of a "run" in this area, so I just labeled each graph as it's own run, regardless of how often it has been run (I don't see start/end graph events). I think this probably really needs to be split into a graph that is designed for the stats, and another that is designed for the log, with some overlap in common areas. But for now, this is something that should still be useful. If you take the statsfile and filter it out for a window, you can start to see visiblity into the schedule for that window...and if you look at certain graphs, you can see the nodes and what is going right or not. So still useful.

Good luck, and let me know what you think.
Cheers
Rich
Attachments:
LAE Profiling.brg