Enterprise-only observability layer that emits OpenTelemetry traces, metrics, and logs for workflow executions, LLM calls, message processing, and node runs. Key components: - core/telemetry: CE-safe gateway and event facade (no-ops when EE disabled) - enterprise/telemetry: full trace/metric/log pipeline with OTLP exporter - extensions/ext_enterprise_telemetry: Flask extension for lifecycle management - tasks/enterprise_telemetry_task: Celery task for async metric dispatch Wiring changes: - app_factory: register ext_enterprise_telemetry extension - ext_celery: conditionally import enterprise_telemetry_task - configs/enterprise: add EnterpriseTelemetryConfig with OTLP settings - ops_trace_manager: add enterprise telemetry hooks with lazy imports - trace_entity: add new trace types (WorkflowNode, PromptGeneration, DraftNode) - ext_otel: improve gRPC TLS auto-detection and optional auth headers All enterprise imports are guarded behind ENTERPRISE_ENABLED + ENTERPRISE_TELEMETRY_ENABLED feature flags with graceful fallbacks. |
||
|---|---|---|
| .. | ||
| .idea | ||
| .vscode | ||
| commands | ||
| configs | ||
| constants | ||
| context | ||
| contexts | ||
| controllers | ||
| core | ||
| dify_graph | ||
| docker | ||
| enterprise/telemetry | ||
| enums | ||
| events | ||
| extensions | ||
| factories | ||
| fields | ||
| libs | ||
| migrations | ||
| models | ||
| repositories | ||
| schedule | ||
| services | ||
| tasks | ||
| templates | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .importlinter | ||
| .ruff.toml | ||
| AGENTS.md | ||
| Dockerfile | ||
| README.md | ||
| app.py | ||
| app_factory.py | ||
| celery_entrypoint.py | ||
| cnt_base.sh | ||
| dify_app.py | ||
| gunicorn.conf.py | ||
| pyproject.toml | ||
| pyrefly-local-excludes.txt | ||
| pyrightconfig.json | ||
| pytest.ini | ||
| uv.lock | ||
README.md
Dify Backend API
Setup and Run
[!IMPORTANT]
In the v1.3.0 release,
poetryhas been replaced withuvas the package manager for Dify API backend service.
uv and pnpm are required to run the setup and development commands below.
Using scripts (recommended)
The scripts resolve paths relative to their location, so you can run them from anywhere.
-
Run setup (copies env files and installs dependencies).
./dev/setup -
Review
api/.env,web/.env.local, anddocker/middleware.envvalues (see theSECRET_KEYnote below). -
Start middleware (PostgreSQL/Redis/Weaviate).
./dev/start-docker-compose -
Start backend (runs migrations first).
./dev/start-api -
Start Dify web service.
./dev/start-web -
Set up your application by visiting
http://localhost:3000. -
Start the worker service (async and scheduler tasks, runs from
api)../dev/start-worker -
Optional: start Celery Beat (scheduled tasks).
./dev/start-beat
Environment notes
[!IMPORTANT]
When the frontend and backend run on different subdomains, set COOKIE_DOMAIN to the site’s top-level domain (e.g.,
example.com). The frontend and backend must be under the same top-level domain in order to share authentication cookies.
-
Generate a
SECRET_KEYin the.envfile.bash for Linux
sed -i "/^SECRET_KEY=/c\\SECRET_KEY=$(openssl rand -base64 42)" .envbash for Mac
secret_key=$(openssl rand -base64 42) sed -i '' "/^SECRET_KEY=/c\\ SECRET_KEY=${secret_key}" .env
Testing
-
Install dependencies for both the backend and the test environment
cd api uv sync --group dev -
Run the tests locally with mocked system environment variables in
tool.pytest_envsection inpyproject.toml, more can check Claude.mdcd api uv run pytest # Run all tests uv run pytest tests/unit_tests/ # Unit tests only uv run pytest tests/integration_tests/ # Integration tests # Code quality ./dev/reformat # Run all formatters and linters uv run ruff check --fix ./ # Fix linting issues uv run ruff format ./ # Format code uv run basedpyright . # Type checking