find_exceptions_in_file
Identify ERROR-level traces linked to a specific source file in Langfuse. Filter exceptions by file name substring to debug Java application issues.
Instructions
Returns ERROR-level traces whose metadata contains the given file name as a substring.
Both conditions must be true for a trace to appear in the result: (1) the trace level is ERROR, and (2) the trace metadata JSON contains the fileName string anywhere inside it.
Use this to isolate errors originating from a specific source file. fileName is required. Both time range parameters are optional — omit them to search across the full project history.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fileName | Yes | Substring to match against trace metadata, typically a source file name such as OrderService.java. Required — the call will be rejected if this is missing or blank. | |
| fromTimestamp | Yes | Start of time range in ISO-8601 format, e.g. 2025-06-01T00:00:00Z. Omit to search from the beginning of the project. | |
| toTimestamp | Yes | End of time range in ISO-8601 format, e.g. 2025-06-30T23:59:59Z. Omit to search up to the current time. |