You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking about convenient centralized logging for NiceGUI, including LLM requests, and I've come across the OpenTelemetry standard.
To summarize, since NiceGUI is built on FastAPI, it seems that most telemetry systems can work almost automatically with NiceGUI. However, there's an important issue with settings related to Unicorn, the --reload option, and the number of workers. Unfortunately, I couldn't find a GitHub OpenTelemetry issue about this, but it's mentioned in the documentation of many systems working with this format.
As someone who learned about OpenTelemetry only about 72 hours ago, I'm not the best person to write a technically correct solution. But as a "user," I can say that when I saw on hyperDX how all user actions can be linked together without much effort from the developer, it seemed like an essential feature for any project.
For LLM projects, this might be even more necessary. You can see how it looks in projects like langfuse and OpenLLMetry.
I mentioned several projects to avoid promoting any specific one. They all use the same standard, and their integration process looks very similar.
Since I want NiceGUI to succeed and grow, I think mentioning the possibility of integrating with OpenTelemetry and providing examples in of how to do it in documentation would help future users.
Currently, OpenTelemetry isn't mentioned in any NiceGUI discussions. So I thought this discussion might help users consider this standard for their current and future projects. Maybe someone here is already an expert in this area and can share their experience on how to do it best.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone,
I've been thinking about convenient centralized logging for NiceGUI, including LLM requests, and I've come across the OpenTelemetry standard.
To summarize, since NiceGUI is built on FastAPI, it seems that most telemetry systems can work almost automatically with NiceGUI. However, there's an important issue with settings related to Unicorn, the --reload option, and the number of workers. Unfortunately, I couldn't find a GitHub OpenTelemetry issue about this, but it's mentioned in the documentation of many systems working with this format.
For example, you can find information here:
https://signoz.io/blog/opentelemetry-fastapi/
And more detailed workarounds here:
https://uptrace.dev/get/opentelemetry-python.html#application-servers
As someone who learned about OpenTelemetry only about 72 hours ago, I'm not the best person to write a technically correct solution. But as a "user," I can say that when I saw on hyperDX how all user actions can be linked together without much effort from the developer, it seemed like an essential feature for any project.
For LLM projects, this might be even more necessary. You can see how it looks in projects like langfuse and OpenLLMetry.
I mentioned several projects to avoid promoting any specific one. They all use the same standard, and their integration process looks very similar.
Since I want NiceGUI to succeed and grow, I think mentioning the possibility of integrating with OpenTelemetry and providing examples in of how to do it in documentation would help future users.
Currently, OpenTelemetry isn't mentioned in any NiceGUI discussions. So I thought this discussion might help users consider this standard for their current and future projects. Maybe someone here is already an expert in this area and can share their experience on how to do it best.
Beta Was this translation helpful? Give feedback.
All reactions