Yann Simon

> Our usecase is to follow company-wide log formats so that log lines are indexed properly. Being able to select and naming fields would be nice (as outlined in [#3226...

## Example 1 ### What we get from the router: ``` { "timestamp": "2023-03-22T16:18:38.164112Z", "level": "INFO", "fields": { "message": "bla bla." }, "target": "apollo_router::executable" } ``` ### Transform into: ```...

If it helps, this how to we manipulate the logs currently: https://github.com/apollographql/router/issues/1651#issuecomment-1493830314

Issue with this PR: ``` Doc-tests axum-macros test axum-macros/src/lib.rs - debug_middleware (line 634) has been running for over 60 seconds ``` Edit: fixed by https://github.com/tokio-rs/axum/pull/2725/commits/8257e1f35b1b47880d07a9bb6dd3545e725b930f, the same way it's done...

For info, it seems that https://maelstrom-software.com/ embraces the idea of one container per test. I had no opportunity to try it out yet.

I've played a bit with systemd-nspawn, but I could not manage starting it with a normal user (not root)

> > I've played a bit with systemd-nspawn, but I could not manage starting it with a normal user (not root) > > I think you would need to enable...

We could also check how https://maelstrom-software.com/ is doing it.

Fix https://github.com/jetstack/elasticsearch-pet/issues/3

I'll try to take time today to address the comments. Thx all for the feedback!