type: error post: description: |

Log (plain text or html)

___

Parameters in the POST body schema

<> <> <>
NameTypeDescriptionExampleDefault
``jobschedulerId``required, stringJobScheduler Master IDscheduler
``mime``optional, string,
enum[PLAIN,HTML]
The log can have a HTML representation where the HTML content is a colored version consider the log levelfor the browser where CSS is required.
      pre.log                         {font-family:"Lucida Console",monospace;font-size:12px;line-height:1.1em;margin-left:2px;padding-left:0}
      .log_error                      {color:red;}
      .log_warn                       {color:tomato;}
      .log_info                       {color:black;}
      .log_stderr                     {color:red;}
      .log_debug                      {color:darkgreen;}
      .log_debug2                     {color:#408040;}
      .log_debug3                     {color:#808080;}
      .log_debug4                     {color:#8080FF;}
      .log_debug5                     {color:#8080FF;}
      .log_debug6                     {color:#8080FF;}
      .log_debug7                     {color:#8080FF;}
      .log_debug8                     {color:#8080FF;}
      .log_debug9                     {color:#a0a0a0;}
    
PLAIN
``filename``optional, stringname of a temp. file from ./<><>/info
This file will be responsed if exists
sos-download-5961566003164029224.tmp
body: application/json: schema: <> example: <> responses: 200: description: Content of log. It depends on the if size if it is offered as download with the Content-Disposition header headers: Content-Disposition: type: string required: false example: attachment;filename=xxx.<>.log Content-Type: type: string required: true default: text/plain body: application/octet-stream: text/plain: #description: <> #body: # application/json: # schema: logContent # example: <> 420: body: application/json: 440: body: application/json: