Overview empty but events are tracked

[se7entynine]

Describe the Bug

Hey,

I am feeding events through an traefik plugin, but I noticed that the events are populated but the overview isnt showing any of them. What could cause this behaviour?
Events tab:

Overview tab:

docker-compose.yml

services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    container_name: umami
    ports:
      - "3000:3000"
    environment:
      DATABASE_URL: postgresql://REDACTED:REDACTED@db:5432/umami
      DATABASE_TYPE: postgresql
      APP_SECRET: "REDACTED"
    depends_on:
      db:
        condition: service_healthy
    init: true
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "curl http://localhost:3000/api/heartbeat"]
      interval: 5s
      timeout: 5s
      retries: 5
  db:
    image: postgres:15-alpine
    container_name: umami-db
    environment:
      POSTGRES_DB: REDACTED
      POSTGRES_USER: REDACTED
      POSTGRES_PASSWORD: REDACTED
    volumes:
      - ./umami-db-data:/var/lib/postgresql/data
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5

Database

PostgreSQL

Relevant log output

DB:

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-04-03 09:07:56.084 UTC [1] LOG:  starting PostgreSQL 15.12 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit
2025-04-03 09:07:56.084 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-03 09:07:56.084 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-03 09:07:56.087 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-03 09:07:56.090 UTC [28] LOG:  database system was shut down at 2025-04-03 09:07:55 UTC
2025-04-03 09:07:56.096 UTC [1] LOG:  database system is ready to accept connections
2025-04-03 09:12:56.174 UTC [26] LOG:  checkpoint starting: time
2025-04-03 09:13:06.968 UTC [26] LOG:  checkpoint complete: wrote 110 buffers (0.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=10.745 s, sync=0.023 s, total=10.795 s; sync files=19, longest=0.014 s, average=0.002 s; distance=707 kB, estimate=707 kB
2025-04-03 09:17:57.059 UTC [26] LOG:  checkpoint starting: time
2025-04-03 09:18:07.521 UTC [26] LOG:  checkpoint complete: wrote 105 buffers (0.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=10.431 s, sync=0.008 s, total=10.462 s; sync files=17, longest=0.003 s, average=0.001 s; distance=709 kB, estimate=709 kB
2025-04-03 09:22:57.621 UTC [26] LOG:  checkpoint starting: time
2025-04-03 09:23:11.309 UTC [26] LOG:  checkpoint complete: wrote 137 buffers (0.8%); 0 WAL file(s) added, 0 removed, 1 recycled; write=13.640 s, sync=0.018 s, total=13.688 s; sync files=22, longest=0.007 s, average=0.001 s; distance=844 kB, estimate=844 kB

Umami:
yarn run v1.22.22
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database version check successful.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "umami", schema "public" at "db:5432"

7 migrations found in prisma/migrations


No pending migrations to apply.

✓ Database is up to date.
$ node scripts/update-tracker.js
$ node server.js
   ▲ Next.js 15.0.4
   - Local:        http://localhost:3000
   - Network:      http://0.0.0.0:3000

 ✓ Starting...
 ✓ Ready in 69ms

Which Umami version are you using? (if relevant)

2.17.0

Which browser are you using? (if relevant)

Edge, Firefox

How are you deploying your application? (if relevant)

Docker