Custom Metadata Field as Dimension in Dashboard Widgets #7577
-
|
Hi! I am trying to create a widget for a custom dashboard. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 16 replies
-
|
Hi @tjs-coding! I'm Dosu and I’m helping the langfuse team. The documentation does say you can use custom metadata as a dimension in widgets, but currently, the frontend only exposes a fixed set of fields as dimension options for each widget type—custom metadata fields are not dynamically listed or selectable. This isn't controlled by a feature flag or permission; it's just not implemented yet in the UI or backend to enumerate arbitrary metadata fields as dimensions [docs]. As a workaround, if you want to group or filter by custom metadata, make sure you attach it directly to the trace (not just observations or experiment runs). For example, you can write your metadata into a trace-level tag or metadata key, which are supported as dimensions and filters [discussion]. If you need this feature, it would require product changes to support dynamic metadata fields as dimensions in the widget configuration. If you’re on a much older or customized deployment, let me know your version—otherwise, this is a current product limitation. To reply, just mention @dosu. Docs are dead. Just use Dosu. |
Beta Was this translation helpful? Give feedback.
-
|
I’m very sorry. This is a roadmap item that made it to the docs too early (initially this was part of the scope and then we cut it as there was some complexity in using metadata at scale in dashboards). Will update the docs right now. |
Beta Was this translation helpful? Give feedback.
-
|
Is the road map item for custom metadata as a dimension in widgets was deployed and available for users ?? |
Beta Was this translation helpful? Give feedback.
-
|
When will this be available? We need the metadata to be displayed as dimensions. |
Beta Was this translation helpful? Give feedback.

I’m very sorry. This is a roadmap item that made it to the docs too early (initially this was part of the scope and then we cut it as there was some complexity in using metadata at scale in dashboards). Will update the docs right now.