Logflare | Cloudflare, Vercel & Elixir Logging

~/logs/postgres.logs

1752022186963938 event body

{
  "appname": "supabase-db",
  "event_message": null,
  "id": "d95c41b3-34b6-4831-b021-ec65431bdf72",
  "project": "default",
  "timestamp": 1752022186963938
}

1752022186985846 PostgreSQL Database directory appears to contain a database; Skipping initialization event body

{
  "appname": "supabase-db",
  "event_message": "PostgreSQL Database directory appears to contain a database; Skipping initialization",
  "id": "d407faef-8388-4b87-a980-31a2efbf478e",
  "project": "default",
  "timestamp": 1752022186985846
}

1752022186986072 event body

{
  "appname": "supabase-db",
  "event_message": null,
  "id": "d4366444-3316-47d3-907a-97af47802423",
  "project": "default",
  "timestamp": 1752022186986072
}

1752022187767438 172.18.0.14 2025-07-09 00:49:47.719 UTC [38] supabase_admin@postgres FATAL: the database system is starting up event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.14 2025-07-09 00:49:47.719 UTC [38] supabase_admin@postgres FATAL:  the database system is starting up",
  "id": "9a095cca-a989-48e0-9795-8fd75c77c44e",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:47.767438290Z"
    }
  },
  "project": "default",
  "timestamp": 1752022187767438
}

1752022188243547 172.18.0.11 2025-07-09 00:49:48.236 UTC [40] supabase_auth_admin@postgres FATAL: the database system is starting up event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.11 2025-07-09 00:49:48.236 UTC [40] supabase_auth_admin@postgres FATAL:  the database system is starting up",
  "id": "57554ace-6040-4370-acf9-9234cbd0bc8e",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:48.243547288Z"
    }
  },
  "project": "default",
  "timestamp": 1752022188243547
}

1752022188262304 172.18.0.11 2025-07-09 00:49:48.261 UTC [42] supabase_auth_admin@postgres FATAL: the database system is starting up event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.11 2025-07-09 00:49:48.261 UTC [42] supabase_auth_admin@postgres FATAL:  the database system is starting up",
  "id": "4b055a01-f481-49bb-96bc-440d3b2dddb4",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:48.262304842Z"
    }
  },
  "project": "default",
  "timestamp": 1752022188262304
}

1752022189369059 172.18.0.3 2025-07-09 00:49:49.346 UTC [43] authenticator@postgres FATAL: the database system is not accepting connections event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.346 UTC [43] authenticator@postgres FATAL:  the database system is not accepting connections",
  "id": "2ee6cd47-04f3-4112-b537-7cd7874703cc",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:49.369059143Z"
    }
  },
  "project": "default",
  "timestamp": 1752022189369059
}

1752022189369081 172.18.0.3 2025-07-09 00:49:49.346 UTC [43] authenticator@postgres DETAIL: Hot standby mode is disabled. event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.346 UTC [43] authenticator@postgres DETAIL:  Hot standby mode is disabled.",
  "id": "b03b2f5f-2830-4193-8c4d-47e9d604a130",
  "project": "default",
  "timestamp": 1752022189369081
}

1752022189481237 172.18.0.3 2025-07-09 00:49:49.419 UTC [44] authenticator@postgres FATAL: the database system is not accepting connections event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.419 UTC [44] authenticator@postgres FATAL:  the database system is not accepting connections",
  "id": "d0e5b833-2b03-4227-89f4-bd010ef75a9e",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:49.481237678Z"
    }
  },
  "project": "default",
  "timestamp": 1752022189481237
}

1752022189481264 172.18.0.3 2025-07-09 00:49:49.419 UTC [44] authenticator@postgres DETAIL: Hot standby mode is disabled. event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.419 UTC [44] authenticator@postgres DETAIL:  Hot standby mode is disabled.",
  "id": "4196ff30-09b1-4792-aa5c-a97d915accb5",
  "project": "default",
  "timestamp": 1752022189481264
}

1752022189481268 172.18.0.3 2025-07-09 00:49:49.454 UTC [45] authenticator@postgres FATAL: the database system is not accepting connections event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.454 UTC [45] authenticator@postgres FATAL:  the database system is not accepting connections",
  "id": "8a442f99-3c9c-4029-ae1b-91098cf4749e",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:49.481268429Z"
    }
  },
  "project": "default",
  "timestamp": 1752022189481268
}

1752022189481271 172.18.0.3 2025-07-09 00:49:49.454 UTC [45] authenticator@postgres DETAIL: Hot standby mode is disabled. event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.454 UTC [45] authenticator@postgres DETAIL:  Hot standby mode is disabled.",
  "id": "8747ebb0-5d39-46f5-b4a3-d2f67322445b",
  "project": "default",
  "timestamp": 1752022189481271
}

1752022189481274 172.18.0.3 2025-07-09 00:49:49.465 UTC [46] authenticator@postgres FATAL: the database system is not accepting connections event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.465 UTC [46] authenticator@postgres FATAL:  the database system is not accepting connections",
  "id": "66ab67df-9f85-406d-83d4-8b730db2a0e7",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:49.481274266Z"
    }
  },
  "project": "default",
  "timestamp": 1752022189481274
}

1752022189481277 172.18.0.3 2025-07-09 00:49:49.465 UTC [46] authenticator@postgres DETAIL: Hot standby mode is disabled. event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.465 UTC [46] authenticator@postgres DETAIL:  Hot standby mode is disabled.",
  "id": "96035f92-3d6d-4332-9e85-51a02a82f127",
  "project": "default",
  "timestamp": 1752022189481277
}

1752022189519044 172.18.0.3 2025-07-09 00:49:49.503 UTC [47] authenticator@postgres FATAL: the database system is not accepting connections event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.503 UTC [47] authenticator@postgres FATAL:  the database system is not accepting connections",
  "id": "6a6ae891-34db-49d8-bcea-537f0d118691",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-07-09T00:49:49.519044331Z"
    }
  },
  "project": "default",
  "timestamp": 1752022189519044
}

1752022189519054 172.18.0.3 2025-07-09 00:49:49.503 UTC [47] authenticator@postgres DETAIL: Hot standby mode is disabled. event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.3 2025-07-09 00:49:49.503 UTC [47] authenticator@postgres DETAIL:  Hot standby mode is disabled.",
  "id": "64cc4e66-3d3a-4561-a082-c2bdbda92777",
  "project": "default",
  "timestamp": 1752022189519054
}

1756181537709772 172.18.0.1 2025-08-26 04:12:17.709 UTC [2595757] postgres@postgres FATAL: password authentication failed for user "postgres" event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.1 2025-08-26 04:12:17.709 UTC [2595757] postgres@postgres FATAL:  password authentication failed for user \"postgres\"",
  "id": "cc2c6bd7-6b9d-4bd2-9ff9-b8bea296955c",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-08-26T04:12:17.709772462Z"
    }
  },
  "project": "default",
  "timestamp": 1756181537709772
}

1756181537712467 172.18.0.1 2025-08-26 04:12:17.709 UTC [2595757] postgres@postgres DETAIL: Connection matched pg_hba.conf line 89: "host all all 172.16.0.0/12 scram-sha-256" event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.1 2025-08-26 04:12:17.709 UTC [2595757] postgres@postgres DETAIL:  Connection matched pg_hba.conf line 89: \"host  all  all  172.16.0.0/12  scram-sha-256\"",
  "id": "c70a901c-dfb7-45b2-9724-4470674b262f",
  "project": "default",
  "timestamp": 1756181537712467
}

1756181566486491 172.18.0.1 2025-08-26 04:12:46.486 UTC [2595837] postgres@postgres FATAL: password authentication failed for user "postgres" event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.1 2025-08-26 04:12:46.486 UTC [2595837] postgres@postgres FATAL:  password authentication failed for user \"postgres\"",
  "id": "56a7c0e4-7018-4c82-b34e-3454594606a3",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-08-26T04:12:46.486491336Z"
    }
  },
  "project": "default",
  "timestamp": 1756181566486491
}

1756181566486548 172.18.0.1 2025-08-26 04:12:46.486 UTC [2595837] postgres@postgres DETAIL: Connection matched pg_hba.conf line 89: "host all all 172.16.0.0/12 scram-sha-256" event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.1 2025-08-26 04:12:46.486 UTC [2595837] postgres@postgres DETAIL:  Connection matched pg_hba.conf line 89: \"host  all  all  172.16.0.0/12  scram-sha-256\"",
  "id": "33c16009-1fd7-45f4-9420-88c35d4648d9",
  "project": "default",
  "timestamp": 1756181566486548
}

1762751167315607 172.18.0.14 2025-11-10 05:06:07.315 UTC [3174149] supabase_admin@postgres FATAL: connection to client lost event body

{
  "appname": "supabase-db",
  "event_message": "172.18.0.14 2025-11-10 05:06:07.315 UTC [3174149] supabase_admin@postgres FATAL:  connection to client lost",
  "id": "50a878d4-009d-420c-9e3d-3c98e19df7ea",
  "metadata": {
    "host": "db-default",
    "parsed": {
      "error_severity": "FATAL",
      "timestamp": "2025-11-10T05:06:07.315607057Z"
    }
  },
  "project": "default",
  "timestamp": 1762751167315607
}

random(tips): Search a date range (e.g. `t:2020-03-{01..05}T00:00:00`).

Source ID

You'll need this source ID for some integrations or libraries.

2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf

If you're hosted on Vercel setup our Vercel integration!

Install the Vercel integration

Gigalixir

Install the Gigalixir command line tool, and navigate to your project directory.

          
    gigalixir drains:add "http://localhost:4000/logs/logplex?api_key=WZDrPh6ElGST&source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf"

Cloudflare App

Already on Cloudflare? Install the Cloudflare app and start sending logs now.

Heroku

Add our log drain with a simple command.

          
    heroku drains:add "http://localhost:4000/logs/logplex?api_key=WZDrPh6ElGST&source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf"

Elixir Logger

Using Elixir? Use our Logger backend to send your structured logs.

Setup the Logger backend

Elixir Agent

Watch log files on a server with our Elixir agent.

Install the agent

Javascript

Use our official Pino transport to send log events from your Javascript project.

Setup the Pino transport

Github Webhook

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.

        
http://localhost:4000/logs/github?api_key=WZDrPh6ElGST&source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf

Github Action

Use our Github Action (thanks @gr2m) to easily log events coming from your repositories.

Setup the Github Action

Fluent Bit

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=WZDrPh6ElGST&source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf
        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:

          
http://localhost:4000/logs/json?api_key=WZDrPh6ElGST&source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf

Or send generic JSON events yourself.

          
    curl -X "POST" "http://localhost:4000/logs/json?source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf" \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'X-API-KEY: WZDrPh6ElGST' \
         -d $'[
      {
        "yellow": true,
        "tags": [
          "popular, tropical, organic"
        ],
        "store": {
          "state": "AZ",
          "city": "Phoenix",
          "zip": 85016,
          "address": "123 W Main St"
        },
        "type": "fruit",
        "name": "banana",
        "qty": 12
      }
    ]'

Custom API Request

Send logs via an HTTP request. This request body payload lets you send over a human readable event message in the message field.

          
    curl -X "POST" "http://localhost:4000/logs?source=2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf" \
    -H 'Content-Type: application/json' \
    -H 'X-API-KEY: WZDrPh6ElGST' \
    -d $'{
      "event_message": "This is another log message.",
      "metadata": {
        "ip_address": "100.100.100.100",
        "request_method": "POST",
        "custom_user_data": {
          "vip": true,
          "id": 38,
          "login_count": 154,
          "company": "Apple",
          "address": {
            "zip": "11111",
            "st": "NY",
            "street": "123 W Main St",
            "city": "New York"
          }
        },
        "datacenter": "aws",
        "request_headers": {
          "connection": "close",
          "user_agent": "chrome"
        }
      }
    }'

Custom Cloudflare Worker

Customize the Cloudflare worker using the template below.

          
    const makeid = length => {
        let text = ""
        const possible = "ABCDEFGHIJKLMNPQRSTUVWXYZ0123456789"
        for (let i = 0; i < length; i += 1) {
            text += possible.charAt(Math.floor(Math.random() * possible.length))
        }
        return text
    }

    const buildMetadataFromHeaders = headers => {
        const responseMetadata = {}
        Array.from(headers).forEach(([key, value]) => {
            responseMetadata[key.replace(/-/g, "_")] = value
        })
        return responseMetadata
    }

    const WORKER_ID = makeid(6)

    async function handleRequest(event) {
        const {
            request
        } = event;
        const rMeth = request.method
        const rUrl = request.url
        const uAgent = request.headers.get("user-agent")
        const rHost = request.headers.get("host")
        const cfRay = request.headers.get("cf-ray")
        const cIP = request.headers.get("cf-connecting-ip")
        const rCf = request.cf

        const requestMetadata = buildMetadataFromHeaders(request.headers)

        const sourceKey = "2ee36ec8-1f1a-4534-b1f6-f2828aefc9bf"
        const apiKey = "WZDrPh6ElGST"

        const t1 = Date.now()
        const response = await fetch(request)
        const originTimeMs = Date.now() - t1

        const statusCode = response.status

        const responseMetadata = buildMetadataFromHeaders(response.headers)

        const logEntry = `${rMeth} | ${statusCode} | ${cIP} | ${cfRay} | ${rUrl} | ${uAgent}`

        const logflareEventBody = {
            source: sourceKey,
            log_entry: logEntry,
            metadata: {
                response: {
                    headers: responseMetadata,
                    origin_time: originTimeMs,
                    status_code: response.status,
                },
                request: {
                    url: rUrl,
                    method: rMeth,
                    headers: requestMetadata,
                    cf: rCf,
                },
                logflare_worker: {
                    worker_id: WORKER_ID,
                },
            },
        }

        const init = {
            method: "POST",
            headers: {
                "X-API-KEY": apiKey,
                "Content-Type": "application/json",
                "User-Agent": `Cloudflare Worker via ${rHost}`
            },
            body: JSON.stringify(logflareEventBody),
        }

        event.waitUntil(fetch("http://localhost:4000/logs", init))

        return response
    }

    addEventListener("fetch", event => {
        event.passThroughOnException()

        event.respondWith(handleRequest(event))
    })