Skip to main content
In the Sources page of your UI, the “Logs” tab provides a centralized view of any errors that occurred during the data ingestion process: logs Errors typically occur when there is a schema mismatch:
  • Field Type Mismatch: The data type of a field does not match the expected type (e.g., a String instead of Integer)
  • Missing Required Fields: A required field is absent in the data being ingested
  • Unexpected Fields: The data contains fields that are not defined in the schema

​
Example

For example, we can take this sample dataset of customer information: 
{"name": "John Doe", "age": 36, "email": "[email protected]"}
{"name": "Jane Smith", "age": 59, "email": "[email protected]"}
{"name": "Emily Johnson", "age": 56, "email": "[email protected]"}
{"name": "Michael Brown", "age": 52, "email": "[email protected]"}
{"name": "Sarah Davis", "age": 27, "email": "[email protected]"}
...
{"name": "Harper Baker", "age": 50, "email": "[email protected]"}
{"name": "Noah Nelson", "age": 19, "email": "[email protected]"}
{"name": "Ella Carter", "age": 47, "email": "[email protected]"}
{"name": "William Perez", "age": "thirty", "email": "[email protected]"}
With the following schema: 
name: String
age: Integer
email: String
Note that the final data entry has “thirty” for age, which expects an Integer. On the “Logs” tab, we can see detailed information about the ingestion error that occurred: timestamp (Datetime): The exact date and time when the error occurred

data format options

error (String): The type of the error encountered error col We can see here that the error occurred at row 30 specifically for the age value. data (String): The specific data payload that caused the error data col