Logflare converting object to array of objects on ingestion.
Not sure if this is the right place, I'm having a tough time figuring this out and there is no documentation on this.
curl --location 'https://api.logflare.app/logs?source=xxx' \
--header 'Content-Type: application/json; charset=utf-8' \
--header 'X-API-KEY: xxx' \
--data '{
"event_message": "demo123",
"message": "This is the main event message",
"metadata": {"some": "log event"},
"timestamp": "2025-07-29T05:23:58.582Z",
"attributes":{
"name": "demo",
"number": "hellssd"
}
When I send some curl like this to logflare, for some reason, it converts things like metadata to array of objects. It saves as Repeatable records and big query ignored the log because the schema is different. How can I enforce the object structure? I have tried locking the schema and all but to nothing worked.
curl --location 'https://api.logflare.app/logs?source=xxx' \
--header 'Content-Type: application/json; charset=utf-8' \
--header 'X-API-KEY: xxx' \
--data '{
"event_message": "demo123",
"message": "This is the main event message",
"metadata": {"some": "log event"},
"timestamp": "2025-07-29T05:23:58.582Z",
"attributes":{
"name": "demo",
"number": "hellssd"
}
When I send some curl like this to logflare, for some reason, it converts things like metadata to array of objects. It saves as Repeatable records and big query ignored the log because the schema is different. How can I enforce the object structure? I have tried locking the schema and all but to nothing worked.
