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
If you set export FTL_O11Y_LOG_LEVEL="debug" (could try other log levels too) before running ftl dev, you get some fairy rich otel logs in the terminal output:
Examples:
info:echo: Meter created Name: ftl_verb Version: SchemaURL:
Although these logs aren't human-readable, not to mention noisy (so we don't want them turned on by default), we could use the structured data we get out of here to build a new Console page that visualizes it all nicely. This would also improve the user experience of end users working on otel traces/metrics/logs. Currently, we have just otel-ui to debug traces, but not only does it not (yet) have metric/log support, but it also is only available to the FTL team, not end users of the SDK.
The text was updated successfully, but these errors were encountered:
(not urgent)
If you set
export FTL_O11Y_LOG_LEVEL="debug"
(could try other log levels too) before runningftl dev
, you get some fairy richotel
logs in the terminal output:Examples:
Although these logs aren't human-readable, not to mention noisy (so we don't want them turned on by default), we could use the structured data we get out of here to build a new Console page that visualizes it all nicely. This would also improve the user experience of end users working on otel traces/metrics/logs. Currently, we have
just otel-ui
to debug traces, but not only does it not (yet) have metric/log support, but it also is only available to the FTL team, not end users of the SDK.The text was updated successfully, but these errors were encountered: