Emiliano Suñé

Related: https://github.com/hyperledger/aries-cloudagent-python/issues/2668

> Is this for traction or aca-py? It sounds like the issue is with log messages that are logged by aca-py, but does aca-py know the tennant_id? This is for...

It would be easier to have ACA-Py log the tenant id rather than having to maintain a service with the mapping to reconcile the logs - if I understand correctly...

> Could the logging in ACA-Py be extended to allow a plugin, like traction's innkeeper plugin, to specify (inject) the identifier it wants to use for a tenant's logs rather...

> > I’m certainly not suggesting we need any manual intervention. I misread the comment then, I thought you meant we keep "status-quo" for logs to be served by the...

This *might* possibly be covered under [tracing](https://github.com/hyperledger/aries-cloudagent-python/blob/main/demo/AgentTracing.md)

> Where did we get on per tenant logging? Is that complete? I think so... #2550 . I need to pick up where we left and re-review what we have...

Is this something we could tackle next, based on the `anoncreds-rs` work and having non-indy images now? @swcurran @WadeBarnes @andrewwhitehead

> The issue is with the BBS Signatures dependency. The work needed to do that is (at a high level) documented in this issue — [hyperledger/aries-bbssignatures-rs#8](https://github.com/hyperledger/aries-bbssignatures-rs/issues/8). I was going to...

Adding that this seems to also (obviously) affect devcontainers when running on an arm64 platform such as MacOS - they fail to build and start with `ursa-bbs-signatures` being the trigger...