NeatlogsNeatlogs
Core Concepts

Workflow Name

How to use workflow_name to organize traces in the Neatlogs dashboard.

workflow_name is the top-level label for your application in the Neatlogs dashboard. All traces produced by a process share the same workflow name, and the dashboard lets you filter, compare, and group traces by it.

Setting a Workflow Name

Pass it to neatlogs.init():

neatlogs.init(
    api_key=os.environ["NEATLOGS_API_KEY"],
    endpoint=os.environ["NEATLOGS_ENDPOINT"],
    workflow_name="customer-support",
)

If you omit workflow_name, the SDK derives one from the current script filename (e.g., main.pymain).

Naming Guidance

Use a name that reflects the application or feature area — not the environment or version (those belong in tags):

GoodAvoid
"customer-support""customer-support-prod-v2"
"research-agent""research-agent-2024"
"rag-api""my-app"
"email-writer""test"

One Workflow Per Feature Area

Give each distinct agent application or feature its own workflow name. If your codebase runs multiple different pipelines, consider separate workflow_name values — or separate init() calls in separate processes — so traces are grouped meaningfully in the dashboard.