LAE

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

Originally posted by: Azad Thalor

What is the use of Logistics tab in Lavastorm nodes? And what does LogLevel in Logistics tab signify?

Thanks and regards,
Azad Thalor
India

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

Originally posted by: DanRosenblatt

Hi Azad- You'll see three options on the Logistics tab for most nodes: Enabled, Mandatory, and LogLevel.

The Enabled parameters determine whether or not a node should be executed. In the Node Editor, the Enabled parameter can be set to true, false, default, or other. Other is used to enter a Boolean expression to be evaluated. Default uses the value of Enabled at the next highest level (composite or graph). Nodes with Enabled set to false will be displayed in the graph underneath a black "no" symbol.

The Mandatory parameters determine whether or not a node should generate an error if it is on a bypass, and will be bypassed. In the Node Editor, the Mandatory parameter can be set to true, false, default, or other. Other is used to enter a Boolean expression to be evaluated for this parameter's value. Default uses the value of Mandatory at the next highest level (composite or graph).

Set the level at which messages are logged. The lower the level, the more information will be recorded in the log file. If no LogLevel parameter is specified, the default is taken from the property "ls.brain.node.java.logLevel", specified in the config files. The values are 0 (DEBUG), 1 (INFO), 2 (WARN) and 3 (ERROR). The use of 4 (FATAL) is deprecated and is now equivalent to 3 (an ERROR). Note that an issue affecting LogLevel functionality is resolved in LAE versions 5.0 and 4.6.2.

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

Originally posted by: Tim Meagher

Just a note:
The Logistics tab will contain the three parameters mentioned above but on different nodes can also contain other parameters that govern the execution infrastructure used for the nodes.
For instance in the Java node various JVM and compilation parameters will be in the Logistics tab.
In the Python node it also contains a python compilation parameter (whether the code is on the server or within the node directly).

Also:

			
				Note that an issue affecting LogLevel functionality is resolved in LAE versions 5.0 and 4.6.2.
			

The issues referenced here do not affect the LogLevel specified within the nodes themselves - rather the issues which are/will be resolved in LAE 5.0 and LAE 4.6.2 are related to the LAE server and command line controller's log levels.

Regards,
Tim.

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

Originally posted by: Azad Thalor

Thanks Dan and Tim.

One more point, we check error log by pressing (Control and Right click). Is there any log file generated and saved in the system which we can see later on?

Thanks for your Help.

Best regards,
Azad Thalor,
India

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

Originally posted by: Tim Meagher

Hi,

There are logs for the server - on a desktop install, you will find in your Lavastorm tmp direcory under <tmpDir>/log/server/server.<port>.log.
On a desktop install, the tmp directory defaults to c:\brainscratch, and the port defaults to 7721.

Regarding node logs - yes, each node will generate it's own node log.
These will persist until the status of the node is cleared.
You can find the location of the node log by going into the node editor and looking at the Status tab.
In the "Log Files" section of the status tab, the file will be referenced as the "Error Log File".

Note - these log files are only maintained for concrete instance nodes, not for a composite node.
If a node has completed execution, and you go to the Status tab and do not see any log files referenced, it is likely the node you are looking at is a composite node.
In order to find the logs for the individual nodes that are part of the composite node you will need to drill into the composite node.
If the composite node has it's DefaultAction parameter set to Edit, and is appearing as a single node, you can drill into the composite node using Right click->Open.

Also note that so long as you don't clear the status of the nodes, you can choose File->Export BRS for a graph.
This will export the graph run status - which includes the information about all of the node's execution states, and links to the log files for all nodes which have run.
This will not contain the actual node logs themselves, so you still need to make sure that you don't clear the node status if you want to see the logs later on.
However, assuming you don't clear the status you can then open the graph later and choose File->Import BRS to load up the previously saved status - then you will have the ability to view the node logs again in BRE.

Final note: The best way to view these logs is probably through the Log Viewer, using CTRL + Shift + Right click, or via right clicking on the node, and selecting "View Error Log".
This provides more information than the CTRL + Right click (text only) view of the log, and also provides options to filter out log entries that you are not interested in, or filter by log level, timestamp, etc.
However, both the text-only view (via CTRL + Right click) and the Log Viewer view (via CTRL + Shift + Right click) of the logs are simply different ways of rendering the underlying log file.
The log file itself is stored in an XML format - which - if you don't use either of these options is not quite as easy to understand.

Regards,
Tim.