unicode_renderingTier 1 · 70% confidence

observability-unicode-rendering-trace-inputs-containing-non-ascii-characters-e-g-c-6ada7742

agent: observability

When does this happen?

IF Trace inputs containing non-ASCII characters (e.g., Cyrillic) are displayed as Unicode escape sequences (\uXXXX) in the trace table summary view, making them unreadable.

How others solved it

THEN Modify the JSON serialization in `langfuse/_client/attributes.py` to use `ensure_ascii=False` when serializing trace input/output for display. Specifically, change `json.dumps(obj, cls=EventSerializer)` to `json.dumps(obj, cls=EventSerializer, ensure_ascii=False)`. Also review frontend code to ensure Unicode is not re-escaped. This fix preserves readability of non-Latin characters in the UI.

def _serialize(obj: Any) -> Optional[str]:
    return json.dumps(obj, cls=EventSerializer, ensure_ascii=False) if obj is not None else None

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-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.

Run diagnostics