Is your feature request related to a problem? Please describe.
The design of LinguFlow App is based on a DAG (Directed Acyclic Graph) for information flow. In the DAG, if a block encounters an error during execution (e.g., an SQL block receives an error from the database), the block will return the error, and the entire DAG execution will be terminated.
After the DAG execution is terminated, completed block information is still sent to LangFuse (a Tracing Tool).
In LangFuse, it is challenging to quickly distinguish between DAG errors and successful block returns because all traces are currently set to the same level 'default'.
Describe the solution you'd like
Implement a more nuanced tracing level logic, such as:
- Any complete DAG execution is labeled as 'normal', regardless of whether the execution result meets expectations.
- When an error occurs during block execution, the tracing level is labeled as 'error'."
Additional context
It is expected to have a logical way to use LangFuse Tracing Levels
Is your feature request related to a problem? Please describe.
The design of LinguFlow App is based on a DAG (Directed Acyclic Graph) for information flow. In the DAG, if a block encounters an error during execution (e.g., an SQL block receives an error from the database), the block will return the error, and the entire DAG execution will be terminated.
After the DAG execution is terminated, completed block information is still sent to LangFuse (a Tracing Tool).
In LangFuse, it is challenging to quickly distinguish between DAG errors and successful block returns because all traces are currently set to the same level 'default'.
Describe the solution you'd like
Implement a more nuanced tracing level logic, such as:
Additional context
It is expected to have a logical way to use LangFuse Tracing Levels