I believe we need to add support for one or more of these metadata properties in the OpenRouter node:
-
session_id(recommended by OpenRouter, up to 128 characters) -
thread_id(LangSmith convention) -
conversation_id(LangSmith convention)
Optional Enhancement
Allow users to define custom metadata key-value pairs for app-specific dimensions (e.g., customer_type, transaction_type, product_code) to enable richer analysis in observability platforms.
My use case:
OpenRouter now supports broadcasting traces to external observability platforms (LangSmith, Langfuse, Datadog, Arize, S3, webhooks). However, without session/thread identifiers in metadata, these platforms cannot group related traces into conversations—making error analysis and debugging across multi-turn interactions impossible.
I’m using OpenRouter with external observability to debug agent workflows. Without session tracking, I get isolated traces with no way to see the full conversation context when errors occur.
Any resources to support this?
https://openrouter.ai/docs/guides/features/broadcast/overview
Are you willing to work on this?
Available to consult on requirements and test implementations.