v1.37.0 #1391

mikecao · 2022-08-10T03:23:43Z

mikecao
Aug 10, 2022
Maintainer

Important

This release includes a new database migration. In this update we are making some changes to Events. Now instead of event_type and event_value columns, there is going to be a single renamed column, event_name. Having the two separate columns caused a lot of confusion regarding what to store in each field. There is now a new table called event_data which is used to store event related data. In the future you will be able to run reports against your events and event data.

Now to track events, you simply choose an event name, like button-click and optionally send some JSON data along with it.

umami.trackEvent('button-click', { userId: 123, buttonName: 'Newsletter signup' });

When you start the app for the first time, the database changes will be automatically applied. Your data however will not be automatically migrated because we can't determine what event_name you will want to use. Your old event table has been renamed to _event_old, which you can use to manually move data to the new table. If you've never used events, feel free to delete the _event_old table.

Features

New model for Events ☝️
New languages: Thai and Bengali! 🐯 🥳
Edit dashboard feature. You can now sort websites on the dashboard

UTM parameters section is now Query parameters. This now captures all the URL query parameters, not just UTM
Refactored handling of environment variables. Before, some environment variables had to be defined at built-time versus run-time, which caused a lot of issues for Docker users. With this change we can now access all environment variables at runtime. No need to rebuild the application or Docker image.

Fixes

Updated Docker build to work with COLLECT_API_ENDPOINT
Removed DISABLE_LOGIN check from middleware due to Vercel issues.
Fixed issue with Heroku deploy

Updates

Upgraded Next.js to 12.2.4
Upgraded Prisma to 4.1.1
Language translation updates.

A huge thanks to all the contributors on this release! @cywio @briancao @wangyang0210 @biqette @umarhadi @H0rn0chse

This discussion was created from the release v1.37.0.

MagicLike · 2022-08-10T11:44:53Z

MagicLike
Aug 10, 2022

When updating to v1.37, I get an error message, when loading the events. I looked in the db and there is no change of the colums as described.

1 reply

candidexmedia Aug 24, 2022

I have the same issue, unfortunately

brunoamaral · 2022-08-10T14:48:14Z

brunoamaral
Aug 10, 2022

Same here, with the following errors logged:

$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
Running update...
Error: P3008

The migration `01_init` is already recorded as applied in the database.

✗ Command failed: prisma migrate resolve --applied "01_init"
Error: P3008

The migration `01_init` is already recorded as applied in the database.


error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "check-db" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
Running update...
Error: P3008

The migration `01_init` is already recorded as applied in the database.

✗ Command failed: prisma migrate resolve --applied "01_init"
Error: P3008

The migration `01_init` is already recorded as applied in the database.


error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "check-db" exited with 1.
error Command failed with exit code 1.

4 replies

mikecao Aug 10, 2022
Maintainer Author

@brunoamaral A fix has been pushed to dev and master, can you try it again?

brunoamaral Aug 11, 2022

@mikecao I am running using docker, but if you tell me what steps to follow i will be happy to test on my side.

mikecao Aug 11, 2022
Maintainer Author

Looks like you have the same issue in #1393 and #1406. We will have a script out soon that should fix these issues.

brunoamaral Aug 12, 2022

Just pulled the latest docker image, ran it twice, and it seems to be working now.

/app $ yarn prisma migrate resolve --rolled-back "02_add_event_data"
yarn run v1.22.19
$ /app/node_modules/.bin/prisma migrate resolve --rolled-back 02_add_event_data
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "umami", schema "public" at "umamidb:5432"
Error: P3012

Migration `02_add_event_data` cannot be rolled back because it is not in a failed state.

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
/app $ yarn check-db
yarn run v1.22.19
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "umami", schema "public" at "umamidb:5432"

2 migrations found in prisma/migrations


Database schema is up to date!

✓ Database is up to date.
Done in 1.95s.

MostafaaRamadan · 2022-08-10T17:39:29Z

MostafaaRamadan
Aug 10, 2022

The event data is not showing in the UI, but I can confirm it has been saved into the database, is there any way to show the custom event data in UI?

2 replies

mikecao Aug 10, 2022
Maintainer Author

Not currently, that is a future feature.

QiotaTeam Sep 4, 2022

Hi @mikecao congrats for Umami app it's very easy to use and it's a great solution ! So also to get event_data from api GET /api/website/{id}/events it will be a future feature ? Thanks Alex

AliMickey · 2022-08-10T21:56:39Z

AliMickey
Aug 10, 2022

Thank you very much for the custom endpoint fix.

Realtime does not show anything for me.
I get a 500 Internal Server Error on /api/realtime/init

4 replies

mikecao Aug 11, 2022
Maintainer Author

Anything in your logs?

AliMickey Aug 11, 2022

PrismaClientKnownRequestError: Raw query failed. Code: `42703`. Message: `column "event_name" does not exist`
    at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/index.js:28658:13)
    at RequestHandler.request (/app/node_modules/@prisma/client/runtime/index.js:28640:12)
    at async consumer (/app/node_modules/@prisma/client/runtime/index.js:29618:18)
    at async Proxy._request (/app/node_modules/@prisma/client/runtime/index.js:29639:16)
    at async __WEBPACK_DEFAULT_EXPORT__ (/app/.next/server/pages/api/website/[id]/metrics.js:223:27)
    at async Object.apiResolver (/app/node_modules/next/dist/server/api-utils/node.js:184:9)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:381:9)
    at async Object.fn (/app/node_modules/next/dist/server/base-server.js:491:37)
    at async Router.execute (/app/node_modules/next/dist/server/router.js:213:36)
    at async NextNodeServer.run (/app/node_modules/next/dist/server/base-server.js:610:29) {
  code: 'P2010',
  clientVersion: '4.1.1',
  meta: { code: '42703', message: 'column "event_name" does not exist' }
}
PrismaClientKnownRequestError: The column `event.event_name` does not exist in the current database.
    at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/index.js:28658:13)
    at RequestHandler.request (/app/node_modules/@prisma/client/runtime/index.js:28640:12)
    at async consumer (/app/node_modules/@prisma/client/runtime/index.js:29618:18)
    at async PrismaClient._request (/app/node_modules/@prisma/client/runtime/index.js:29639:16)
    at async Promise.all (index 2)
    at async getRealtimeData (/app/.next/server/chunks/1573.js:760:43)
    at async __WEBPACK_DEFAULT_EXPORT__ (/app/.next/server/pages/api/realtime/init.js:143:22)
    at async Object.apiResolver (/app/node_modules/next/dist/server/api-utils/node.js:184:9)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:381:9)
    at async Object.fn (/app/node_modules/next/dist/server/base-server.js:491:37) {
  code: 'P2022',
  clientVersion: '4.1.1',
  meta: { column: 'event.event_name' }
}

mikecao Aug 11, 2022
Maintainer Author

Can you try manually running yarn check-db?

AliMickey Aug 12, 2022

/app $ yarn check-db
yarn run v1.22.19
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
✓ Database is up to date.
Done in 1.49s.

Restarted and tried browsing to realtime.

yarn run v1.22.19
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
✓ Database is up to date.
$ node scripts/update-tracker.js
Updated tracker endpoint: /api/mickit.
$ node server.js
Listening on port 3000
PrismaClientKnownRequestError: The column `event.event_name` does not exist in the current database.
    at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/index.js:28658:13)
    at RequestHandler.request (/app/node_modules/@prisma/client/runtime/index.js:28640:12)
    at async consumer (/app/node_modules/@prisma/client/runtime/index.js:29618:18)
    at async PrismaClient._request (/app/node_modules/@prisma/client/runtime/index.js:29639:16)
    at async Promise.all (index 2)
    at async getRealtimeData (/app/.next/server/chunks/1573.js:760:43)
    at async __WEBPACK_DEFAULT_EXPORT__ (/app/.next/server/pages/api/realtime/init.js:143:22)
    at async Object.apiResolver (/app/node_modules/next/dist/server/api-utils/node.js:184:9)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:381:9)
    at async Object.fn (/app/node_modules/next/dist/server/base-server.js:491:37) {
  code: 'P2022',
  clientVersion: '4.1.1',
  meta: { column: 'event.event_name' }
}

louis-l · 2022-08-11T06:48:39Z

louis-l
Aug 11, 2022

Thanks for the latest update.

Here is my build logs on Vercel:

[16:34:46.151] Cloning github.com/louis-l/umami (Branch: master, Commit: 2181ca4)
[16:34:46.688] Cloning completed: 536.309ms
[16:34:47.792] Looking up build cache...
[16:34:48.073] Build Cache not found
[16:34:48.293] Running "vercel build"
[16:34:48.771] Vercel CLI 27.4.0
[16:34:49.083] Installing dependencies...
[16:34:49.433] yarn install v1.22.17
[16:34:49.517] [1/4] Resolving packages...
[16:34:49.831] [2/4] Fetching packages...
[16:35:13.353] [3/4] Linking dependencies...
[16:35:13.357] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "konva@>=2.6".
[16:35:13.357] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "react-konva@^16.8.0  || ^17.0.0".
[16:35:13.357] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "react-native@>=0.58".
[16:35:13.357] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "@react-three/fiber@>=6.0".
[16:35:13.357] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "three@>=0.126".
[16:35:13.359] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "react-zdog@>=1.0".
[16:35:13.359] warning "react-spring > @react-spring/[email protected]" has unmet peer dependency "zdog@>=1.0".
[16:35:13.366] warning "eslint-config-next > @typescript-eslint/parser > @typescript-eslint/typescript-estree > [email protected]" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[16:35:29.238] [4/4] Building fresh packages...
[16:35:36.183] $ prisma generate || true
[16:35:37.817] prisma:warn The postinstall script automatically ran `prisma generate` and did not find your `prisma/schema.prisma`.
[16:35:37.817] If you have a Prisma schema file in a custom path, you will need to run
[16:35:37.817] `prisma generate --schema=./path/to/your/schema.prisma` to generate Prisma Client.
[16:35:37.818] If you do not have a Prisma schema file yet, you can ignore this message.
[16:35:37.818] 
[16:35:38.620] $ node -e "if (process.env.NODE_ENV !== 'production'){process.exit(1)} " || husky install
[16:35:38.771] husky - Git hooks installed
[16:35:38.775] Done in 49.35s.
[16:35:38.815] Detected Next.js version: 12.2.4
[16:35:38.817] Running "yarn run build"
[16:35:39.095] yarn run v1.22.17
[16:35:39.140] $ npm-run-all build-tracker build-geo build-db build-app
[16:35:39.595] $ rollup -c rollup.tracker.config.js
[16:35:39.798] �[36m
[16:35:39.799] �[1mtracker/index.js�[22m → �[1mpublic/umami.js�[22m...�[39m
[16:35:40.201] �[32mcreated �[1mpublic/umami.js�[22m in �[1m402ms�[22m�[39m
[16:35:40.583] $ node scripts/build-geo.js
[16:35:40.756] Saved geo database: /vercel/path0/node_modules/.geo/GeoLite2-Country.mmdb
[16:35:41.092] $ npm-run-all copy-db-files build-db-client
[16:35:41.455] $ node scripts/copy-db-files.js
[16:35:41.607] Database type detected: mysql
[16:35:41.618] Copied /vercel/path0/db/mysql to /vercel/path0/prisma
[16:35:41.840] $ prisma generate
[16:35:43.033] Prisma schema loaded from prisma/schema.prisma
[16:35:44.386] 
[16:35:44.386] ✔ Generated Prisma Client (4.1.1 | library) to ./node_modules/@prisma/client in 186ms
[16:35:44.386] You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
[16:35:44.386] ```
[16:35:44.386] import { PrismaClient } from '@prisma/client'
[16:35:44.386] const prisma = new PrismaClient()
[16:35:44.387] ```
[16:35:44.522] ┌─────────────────────────────────────────────────────────┐
[16:35:44.523] │  Update available 4.1.1 -> 4.2.1                        │
[16:35:44.523] │  Run the following to update                            │
[16:35:44.523] │    yarn add --dev prisma@latest                         │
[16:35:44.523] │    yarn add @prisma/client@latest                       │
[16:35:44.523] └─────────────────────────────────────────────────────────┘
[16:35:44.774] $ next build
[16:35:45.226] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[16:35:45.227] This information is used to shape Next.js' roadmap and prioritize features.
[16:35:45.227] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[16:35:45.227] https://nextjs.org/telemetry
[16:35:45.228] 
[16:35:45.325] info  - Skipping linting
[16:35:45.325] info  - Checking validity of types...
[16:35:45.439] info  - Creating an optimized production build...
[16:36:17.234] info  - Compiled successfully
[16:36:17.235] info  - Collecting page data...
[16:36:20.691] info  - Generating static pages (0/11)
[16:36:20.738] info  - Generating static pages (2/11)
[16:36:20.758] info  - Generating static pages (5/11)
[16:36:20.773] info  - Generating static pages (8/11)
[16:36:20.807] info  - Generating static pages (11/11)
[16:36:20.822] info  - Finalizing page optimization...
[16:36:20.826] 
[16:36:20.860] Page                                       Size     First Load JS
[16:36:20.860] ┌ ○ /                                      296 B           159 kB
[16:36:20.860] ├   /_app                                  0 B             159 kB
[16:36:20.860] ├ ○ /404                                   369 B           213 kB
[16:36:20.860] ├   └ css/ce16c43b6179ab29.css             1.98 kB
[16:36:20.861] ├ λ /api/account                           0 B             159 kB
[16:36:20.861] ├ λ /api/account/[id]                      0 B             159 kB
[16:36:20.861] ├ λ /api/account/password                  0 B             159 kB
[16:36:20.861] ├ λ /api/accounts                          0 B             159 kB
[16:36:20.861] ├ λ /api/auth/login                        0 B             159 kB
[16:36:20.861] ├ λ /api/auth/verify                       0 B             159 kB
[16:36:20.861] ├ λ /api/collect                           0 B             159 kB
[16:36:20.861] ├ λ /api/config                            0 B             159 kB
[16:36:20.861] ├ λ /api/realtime/init                     0 B             159 kB
[16:36:20.861] ├ λ /api/realtime/update                   0 B             159 kB
[16:36:20.861] ├ λ /api/scripts/telemetry                 0 B             159 kB
[16:36:20.861] ├ λ /api/share/[id]                        0 B             159 kB
[16:36:20.861] ├ λ /api/website                           0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]                      0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/active               0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/events               0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/metrics              0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/pageviews            0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/reset                0 B             159 kB
[16:36:20.862] ├ λ /api/website/[id]/stats                0 B             159 kB
[16:36:20.863] ├ λ /api/websites                          0 B             159 kB
[16:36:20.863] ├ λ /console/[[...id]]                     4.29 kB         351 kB
[16:36:20.863] ├   └ css/d334d2d6db22b87e.css             161 B
[16:36:20.863] ├ ○ /dashboard/[[...id]]                   36.5 kB         383 kB
[16:36:20.863] ├   └ css/6688a38b3e3354b3.css             489 B
[16:36:20.863] ├ λ /login                                 1.55 kB         225 kB
[16:36:20.864] ├   └ css/5c57a357791fbdf5.css             2.38 kB
[16:36:20.864] ├ ○ /logout                                336 B           159 kB
[16:36:20.864] ├ ○ /realtime                              7.35 kB         376 kB
[16:36:20.864] ├   └ css/2f45371959ed6b1f.css             3.64 kB
[16:36:20.864] ├ ○ /settings                              222 B           330 kB
[16:36:20.864] ├ ○ /settings/accounts                     264 B           330 kB
[16:36:20.864] ├ ○ /settings/profile                      263 B           330 kB
[16:36:20.864] ├ ○ /share/[...id]                         645 B           400 kB
[16:36:20.864] └ ○ /website/[...id]                       753 B           400 kB
[16:36:20.864] + First Load JS shared by all              159 kB
[16:36:20.864]   ├ chunks/framework-5f4595e5518b5600.js   42 kB
[16:36:20.864]   ├ chunks/main-f1f37299d5d02885.js        34.5 kB
[16:36:20.864]   ├ chunks/pages/_app-3f39117fa6aacd01.js  81.3 kB
[16:36:20.864]   ├ chunks/webpack-cb7634a8b6194820.js     884 B
[16:36:20.865]   └ css/2b825f07a02cea87.css               9.39 kB
[16:36:20.865] 
[16:36:20.865] ƒ Middleware                               19.8 kB
[16:36:20.865] 
[16:36:20.865] λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
[16:36:20.865] ○  (Static)  automatically rendered as static HTML (uses no initial props)
[16:36:20.865] 
[16:36:20.967] $ node scripts/postbuild.js
[16:36:21.557] Done in 42.47s.
[16:36:22.234] Traced Next.js server files in: 634.498ms
[16:36:33.808] Created all serverless functions in: 11.572s
[16:36:33.864] Collected static files (public/, static/, .next/static): 22.355ms
[16:36:35.755] Build Completed in /vercel/output [2m]
[16:37:06.191] Generated build outputs:
[16:37:06.192]  - Static files: 218
[16:37:06.192]  - Serverless Functions: 23
[16:37:06.192]  - Edge Functions: 1
[16:37:06.193] Serverless regions: Washington, D.C., USA
[16:37:06.193] Deployed outputs in 25s
[16:37:08.274] Build completed. Populating build cache...
[16:37:31.460] Uploading build cache [159.49 MB]...
[16:37:35.772] Build cache uploaded: 4.313s
[16:37:35.810] Done with "."

Cant see anything changed in the "event" table in database:

And now the "Realtime" page is broken (/api/realtime/init request gets 500 error)

5 replies

louis-l Aug 11, 2022

Do I need to manually run migration or anything like that? Or the migration will run automatically?

mikecao Aug 11, 2022
Maintainer Author

The migration should have run as part of the start script, but looks like it didn't. You can simply run yarn check-db against your database and it will do the migration.

marc-on-github · 2022-08-16T06:38:43Z

marc-on-github
Aug 16, 2022

When do you plan to update the typescript types? Thanks!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v1.37.0 #1391

{{title}}

Replies: 6 comments 16 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

v1.37.0 #1391

mikecao Aug 10, 2022 Maintainer

Important

Features

Fixes

Updates

Replies: 6 comments · 16 replies

mikecao Aug 10, 2022 Maintainer Author

mikecao Aug 11, 2022 Maintainer Author

mikecao Aug 10, 2022 Maintainer Author

mikecao Aug 11, 2022 Maintainer Author

mikecao Aug 11, 2022 Maintainer Author

mikecao Aug 11, 2022 Maintainer Author

mikecao
Aug 10, 2022
Maintainer

Replies: 6 comments 16 replies

mikecao Aug 10, 2022
Maintainer Author

mikecao Aug 11, 2022
Maintainer Author

mikecao Aug 10, 2022
Maintainer Author

mikecao Aug 11, 2022
Maintainer Author

mikecao Aug 11, 2022
Maintainer Author

mikecao Aug 11, 2022
Maintainer Author