Feature Request: Option to add a separator between invocations for local server option #243
Open
Description
Hi, my application does extensive logging to console/output and it is extremely hard to follow separate invocations/executions because there is no way to separate requests when running lambda-local using the HTTP server option. Although I have my own spacing once each invocation starts, if there was a way to optionally add a separator between each invocation that would make it better for readability and to search for and/or parse individual request IDs more easily.
CURRENT:
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>PROPOSED (with optional dashed line - or any other custom separator)
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>
--------------------------------------------------------------------------
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>
--------------------------------------------------------------------------
info: START RequestId: <<GUID>>
...
info: END - Result:
info: <<response>>Thanks in advance for any consideration.
Metadata
Assignees
Labels
No labels