[FR] Optionaly support open-telemetry for backend troubleshooting

[aegypius]

Is your feature request related to a problem? Please describe.

While setting up my instance, I struggled to make OIDC working and the few logs I found was not quite descriptive to be able to found the issue.

Describe the solution you'd like

Supporting open-telemetry would allow to capture a stacktrace and details without sending the details to the client.

Additional context

No response

Could you implement it?

Yes - I am able to do it

Implementation plan (optional)

Well, I did implement it here (with crush to be totally honest) : https://github.com/aegypius/trip/tree/feature/setup-opentelemetry
It probably need some polish but I manager to get my instance working !

[itskovacs]

Hi 👋,

I aim to keep TRIP as minimalist as possible for maintainability and because that's my POV on softwares.

Topic being enhancing logging, I'd rather extend the built-in logger (that is not used) with a debug option and add more logs in the output than introduce an external library with its own backend 👍

[aegypius]

Hi !

I understand your point of view even if I don't think Open-Telemetry (otel) and logging serve the same purpose. You log what you expect to happen and you use otel when something unexpected happen.

Nevermind, I proposed it because it's in the spirit of Open Source and as a fellow BZH developper ;)

[itskovacs]

Still highlighting two real issues: logging which is really absent, and the topic of optional telemetry, disabled by default, for usage and performance 🤝