Repeating service=langflow in logs

[kartikgajjar]

Bug Description

Use of "service=langflow" with each debug line is unclear.

2026-06-10T18:55:32.868901Z [debug ] Starting Langflow v1.10.0... service=langflow
2026-06-10T18:55:32.869659Z [debug ] Initializing services service=langflow
2026-06-10T18:55:32.922162Z [debug ] Overriding service registration for auth_service service=langflow
2026-06-10T18:55:32.922422Z [debug ] Registered service class: auth_service -> AuthService service=langflow
2026-06-10T18:55:32.922937Z [debug ] Overriding service registration for authorization_service service=langflow
2026-06-10T18:55:32.923275Z [debug ] Registered service class: authorization_service -> LangflowAuthorizationService service=langflow
2026-06-10T18:55:32.923962Z [debug ] Skipping deployment adapter registration: wxo_deployments feature flag disabled service=langflow
2026-06-10T18:55:32.924193Z [debug ] Skipping deployment mapper registration: wxo_deployments feature flag disabled service=langflow
2026-06-10T18:55:32.924715Z [debug ] Create service ServiceType.CACHE_SERVICE service=langflow
2026-06-10T18:55:32.924989Z [debug ] Starting plugin discovery (config_dir: C:\Users\ekartka\AppData\Local\langflow\langflow\Cache)... service=langflow
2026-06-10T18:55:33.121745Z [debug ] Plugin discovery complete. Registered services: [<ServiceType.AUTH_SERVICE: 'auth_service'>, <ServiceType.AUTHORIZATION_SERVICE: 'authorization_service'>] service=langflow
2026-06-10T18:55:33.122241Z [debug ] Initializing database service=langflow
2026-06-10T18:55:33.123076Z [debug ] Create service ServiceType.DATABASE_SERVICE service=langflow
2026-06-10T18:55:33.135814Z [debug ] sqlite connection, setting pragmas: ['PRAGMA synchronous = NORMAL', 'PRAGMA journal_mode = WAL', 'PRAGMA busy_timeout = 30000'] service=langflow
2026-06-10T18:55:33.145663Z [debug ] Database and tables already exist service=langflow
2026-06-10T18:55:33.160894Z [debug ] Alembic initialized service=langflow
2026-06-10T18:55:34.105968Z [debug ] Database initialized service=langflow
2026-06-10T18:55:34.116655Z [debug ] AUTO_LOGIN is set to True. Creating default superuser with full initialization. service=langflow
2026-06-10T18:55:34.169373Z [debug ] Create service ServiceType.AUTH_SERVICE service=langflow
2026-06-10T18:55:34.169769Z [debug ] Creating service from class: auth_service -> AuthService service=langflow
2026-06-10T18:55:34.170058Z [debug ] Service created successfully: auth_service service=langflow
2026-06-10T18:55:34.195368Z [debug ] Successfully cleaned up old transactions service=langflow
2026-06-10T18:55:34.199539Z [debug ] Successfully cleaned up old vertex builds service=langflow
2026-06-10T18:55:34.201650Z [debug ] authz_audit_log cleanup removed 0 rows older than 90 days service=langflow
2026-06-10T18:55:34.203133Z [debug ] Services initialized in 1.33s service=langflow
2026-06-10T18:55:34.203830Z [debug ] Create service ServiceType.TELEMETRY_WRITER_SERVICE service=langflow
2026-06-10T18:55:34.211896Z [error ] Failed to start telemetry writer; transactions and vertex_build writes will use the legacy direct-write path: [WinError 11] An attempt was made to load a program with an incorrect format service=langflow
2026-06-10T18:55:34.213262Z [debug ] Setting up LLM caching service=langflow
2026-06-10T18:55:34.217379Z [debug ] No LLM cache set. service=langflow
2026-06-10T18:55:34.217806Z [debug ] LLM caching setup in 0.01s service=langflow
2026-06-10T18:55:34.218553Z [debug ] Copying profile pictures service=langflow
2026-06-10T18:55:34.219330Z [debug ] Create service ServiceType.STORAGE_SERVICE service=langflow
2026-06-10T18:55:34.219571Z [debug ] Create service ServiceType.SESSION_SERVICE service=langflow
2026-06-10T18:55:34.311971Z [debug ] Profile pictures copied in 0.09s service=langflow
2026-06-10T18:55:34.312441Z [debug ] Reconciling knowledge base rows from disk service=langflow
2026-06-10T18:55:34.331813Z [debug ] Knowledge base reconciliation completed in 0.02s (0 rows inserted) service=langflow
2026-06-10T18:55:34.332663Z [debug ] Create service ServiceType.TELEMETRY_SERVICE service=langflow
2026-06-10T18:55:34.627698Z [debug ] Loading bundles service=langflow
2026-06-10T18:55:34.628574Z [debug ] Bundles loaded in 0.00s service=langflow
2026-06-10T18:55:34.629124Z [debug ] Caching types service=langflow
2026-06-10T18:55:34.629850Z [debug ] Building components cache service=langflow
2026-06-10T18:55:34.677546Z [debug ] Loading components from built-in index service=langflow
2026-06-10T18:55:34.678466Z [debug ] Loaded 95 component categories from index service=langflow

Reproduction

uv run langflow run --dev --log-level debug

Expected behavior

Add "service=langflow" where required.

Who can help?

No response

Operating System

Windows 11

Langflow Version

1.10.0

Python Version

3.12

Screenshot

No response

Flow File

No response

[AntonioABLima]

Hi @kartikgajjar, thanks for the report!

I looked into this and can confirm the behavior. The service=langflow suffix is intentional — it comes from a structured-logging processor (structlog) that stamps a service field on every log record. This is by design for log aggregation: in multi-service deployments (e.g. Loki/Grafana), every line carries a service identifier so logs can be filtered and correlated.

That said, you're right that for a single-service / local run it's just repetitive noise — the value is always the same service=langflow on every line, and there's currently no clean way to turn it off (setting LANGFLOW_SERVICE_NAME="" only produces an empty service=, which is even worse).

So I agree this is worth improving. I'm opening an enhancement to suppress the service field in the pretty console renderer (or make it opt-in via an env var) while keeping it in the JSON / key-value outputs that aggregation pipelines actually rely on.

Thanks again for flagging it!

[AntonioABLima]

(LFP-427)