1772328969274173 172.20.0.14 2026-03-01 01:36:09.271 UTC [39] supabase_auth_admin@postgres FATAL: the database system is starting up
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:09.271 UTC [39] supabase_auth_admin@postgres FATAL: the database system is starting up",
"id": "d5b688de-bf12-471b-9b61-1130556e134a",
"metadata": {
"host": "db-default",
"parsed": {
"error_severity": "FATAL",
"timestamp": "2026-03-01T01:36:09.274173289Z"
}
},
"project": "default",
"timestamp": 1772328969274173
}
1772328969298008 172.20.0.14 2026-03-01 01:36:09.297 UTC [41] supabase_auth_admin@postgres FATAL: the database system is starting up
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:09.297 UTC [41] supabase_auth_admin@postgres FATAL: the database system is starting up",
"id": "aeda5ccc-5f8c-4901-8edd-883e69ef05ac",
"metadata": {
"host": "db-default",
"parsed": {
"error_severity": "FATAL",
"timestamp": "2026-03-01T01:36:09.298008365Z"
}
},
"project": "default",
"timestamp": 1772328969298008
}
1772328969969853 172.20.0.14 2026-03-01 01:36:09.960 UTC [43] supabase_auth_admin@postgres FATAL: the database system is not accepting connections
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:09.960 UTC [43] supabase_auth_admin@postgres FATAL: the database system is not accepting connections",
"id": "c04d5b51-4a2c-4f3f-814f-825851f44f1a",
"metadata": {
"host": "db-default",
"parsed": {
"error_severity": "FATAL",
"timestamp": "2026-03-01T01:36:09.969853868Z"
}
},
"project": "default",
"timestamp": 1772328969969853
}
1772328969969915 172.20.0.14 2026-03-01 01:36:09.960 UTC [43] supabase_auth_admin@postgres DETAIL: Hot standby mode is disabled.
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:09.960 UTC [43] supabase_auth_admin@postgres DETAIL: Hot standby mode is disabled.",
"id": "f8240e2f-1fff-4aac-aee8-e50c48da4f1d",
"project": "default",
"timestamp": 1772328969969915
}
1772328970019601 172.20.0.14 2026-03-01 01:36:10.019 UTC [45] supabase_auth_admin@postgres FATAL: the database system is not accepting connections
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:10.019 UTC [45] supabase_auth_admin@postgres FATAL: the database system is not accepting connections",
"id": "c7b3c686-0bf1-409c-8a5f-612b99a0334e",
"metadata": {
"host": "db-default",
"parsed": {
"error_severity": "FATAL",
"timestamp": "2026-03-01T01:36:10.019601164Z"
}
},
"project": "default",
"timestamp": 1772328970019601
}
1772328970019640 172.20.0.14 2026-03-01 01:36:10.019 UTC [45] supabase_auth_admin@postgres DETAIL: Hot standby mode is disabled.
event body
{
"appname": "supabase-db",
"event_message": "172.20.0.14 2026-03-01 01:36:10.019 UTC [45] supabase_auth_admin@postgres DETAIL: Hot standby mode is disabled.",
"id": "cd8544a8-c3f2-415e-b79f-075e4b5acc00",
"project": "default",
"timestamp": 1772328970019640
}
random(tips): Search a date range (e.g. `t:2020-03-{01..05}T00:00:00`).
Send Logs to this Source
Source ID
You'll need this source ID for some integrations or libraries.
86cbc65f-53eb-4387-9e6b-6609a8adac54
If you're hosted on Vercel setup our Vercel integration!
Set your Github webhook to this Logflare endpoint and we'll ingest Github webhooks for you. This endpoint drops all keys ending in _url so it keeps your Github payloads in check.
Watch log files on a server with this Fluent Bit output config.
[INPUT]
Name tail
Path /var/log/syslog
[OUTPUT]
Name http
Match *
tls On
Host api.logflare.app
Port 443
URI /logs/json?api_key=ouzYyAJblHNv&source=86cbc65f-53eb-4387-9e6b-6609a8adac54
Format json
Retry_Limit 5
json_date_format iso8601
json_date_key timestamp
Generic Webhook
Use the generic JSON ingest endpoint to generate log events from an external webhook.
e.g. you can set a Github webhook to send events to: