Feat logs

[Threated]

Is this fine for logging?
It creates newline delimited json where each entry has the following schema:

{
  "id": "the uuid of the task",
  "query": "b64 encoded query",
  "user_email": "someone@test.com",
  "results": ["mainz"], // Subset of sites which responded before timeout with a Successful result
  "sites": ["frankfurt", "mainz"], // Only proxy name of the site
  "ts": 17109385271000 // Unix timestamp of when the task was created
}

[torbrenner]

i think that is a good base for logging. One information is missing, the user which executed the search, but this will involve lens also sending more information to spot. I have a prototypical implementation for sending that information in lens project-manager-connection branch maybe we could look at it together if that can work for logging.

[Threated]

If that information is included in the first post request it should be trivial to add.

[torbrenner]

Yes, thats right. I think the main issue is getting that data into the first post requests. Currently the ui and backend don't have anything todo with the authentication, as the oauth2-proxy in front of them is handling authentication, but i think it should be possible to make it requestable or add it to the request.