Wrapping/Parsing of logs from API

[mguidon]

With the integration into the rocket I see different types of logs:

• Autoscaler

  The on demand computational cluster is not ready 'est. remaining time: 03:59'
  The on demand computational cluster is not ready 'est. remaining time: 03:54'

• comp sidecar

  [sidecar] Starting task for simcore/services/comp/isolve-8-0-0-gpu:2.2.0 on ip-10-0-0-53-dask_stack_dask-sidecar...
  [sidecar] Pulling simcore/services/comp/isolve-8-0-0-gpu:2.2.0: {'status': 'Pulling from simcore/services/comp/isolve-8-0-0-gpu', 'id': '2.2.0'}...
  [sidecar] Pulling simcore/services/comp/isolve-8-0-0-gpu:2.2.0: {'status': 'Pulling fs layer', 'progressDetail': {}, 'id': 'd5fd17ec1767'}...

• entrypoint of solver

  INFO: [entrypoint.sh]  Entrypoint for stage production ...
  INFO: [entrypoint.sh]  User    :uid=0(root) gid=0(root) groups=0(root)
  INFO: [entrypoint.sh]  Workdir :/home/smu
  INFO: [entrypoint.sh]  setting correct user id/group id...

• solver

  iSolve X, Version 8.0.0 (14056), 64Bit Linux
  Running MPI version 3.1 on 1 process.
  Simulation 'EM' started on 2023-Dec-05 08:14:23

• comp sidecar

  [sidecar] Compressing 'isolve-8-0-0-gpu_2.2.0.logs' to 'logs.zip'...
  [sidecar] Compression of 'isolve-8-0-0-gpu_2.2.0.logs' to 'logs.zip' complete.
  [sidecar] Uploading 'logs.zip' to 's3://sim4life-simcore/b9cbbbbd-2705-433c-a25c-dbadaae032ca/37793e09-2861-528e-84f6-60543ce963d1/logs.zip'...

  The API spits them out as

  {
  "errors": [
  {
    "loc": [
      "string",
      0
    ],
    "msg": "string",
    "type": "string"
  }
  ]
  }

  Maybe we could add a origin key to distinguish where they come from? (not for the entrypoint of course)

[pcrespov]

Actually loc (as location) is to point where the error is coming within a tree structure using a dotted name as parent.chid. It comes from pydantic validation error but we could use the first entry for the service. For instance loc=sidecar