Dify adapter

Chart: ams-helm-dify-adapter

This worker bridges Dify (and often Langfuse) activity into the AMS observability path. It is not a replacement for the Dify UI.

When you need it

• You run Dify so users can create and operate agents.
• You want those runs visible inside AMS telemetry (OTEL → observability stack).
• Langfuse is in play as the place Dify (or your pipeline) sends detailed trace data that the adapter consumes.

Read Dify, Langfuse, and LibreChat for the usability picture.

Prerequisites

• Observability installed
• Reachability to Dify and/or Langfuse APIs from the cluster
• API tokens stored as secrets

Helm outline

helm upgrade --install ams-dify-adapter ./ams-helm-dify-adapter \
  --namespace dify-adapter \
  --create-namespace \
  -f providers/azure/release/values.yaml

Configure upstream URLs, credentials, and OTEL export settings in release values.

Verify

• Adapter pods Ready
• No crash loops when talking to Langfuse/Dify
• New telemetry appears in your observability backends after generating traffic in Dify