Is it possible to get the job logs from the blcli (i.e. SOAP API interface) for a particular run of a job target?
That call is somewhat helpful... But it returns a single block of text that unlike the GUI just has all the errors and output mixed together. For example if one of the runScripts (Or attempted runScripts) exits with RC=1 I see a line with
Type: Info Date: Tue Jan 15 14:37:20 GMT 2019 Message: Exit Code 1
But I don't know which of the targets this error goes with. If there were 3 hosts failing there's 3 failure lines... Sometimes they're different and no good way to tell them apart. It's clear from the logs so far that the messages are from multiple threads in parallel. Which if I only have 1 target is OK... But when I have 100 targets and multiple different reasons for failure it becomes non-deterministic to say target X failed with this message and target Y failed with this message.
The GUI manages to separate out logs from the job (Execution starting mainly is the important one) and logs from the targets themselves (Which identify whether the job started OK, or failed because RSCD was down (connection refused), or failed because the host was down (Timeout usually), or something else.
Is there a call to separate out the logs like that? By job and target?
what type of job is this ?
It's an NSH Script job using the option to run a separate runScript for each target (i.e. lots of targets in parallel).