dashboard_metrics_aggregationTier 1 · 70% confidence
observability-dashboard-metrics-ag-dashboard-widget-for-unique-user-ids-count-returns-2652ea77
agent: observability
When does this happen?
IF Dashboard widget for Unique User IDs count returns total trace count instead of distinct count when using Big Number chart type.
How others solved it
THEN Fix the query builder's translateAggregation to avoid wrapping distinct metrics in an additional count(). Instead, use the metric's sql directly (e.g., uniq(traces.user_id)) for count aggregations. This ensures unique user IDs are counted correctly, not the total number of traces. The patch is implemented by adjusting the 'count' case to skip aggregation when the metric already uses uniq().
// Before: translateAggregation for 'count' returned `count(${metric.alias || metric.sql})`
// After: handle distinct metrics separately, e.g. if metric.sql starts with 'uniq' then use metric.sql directly
case 'count':
return metric.sql?.startsWith('uniq') ? metric.sql : `count(${metric.alias || metric.sql})`;Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.