v3.0.0

[mikecao]

We are excited to announce the release of Umami v3! This release comes with a new interface, lots of new features and enhancements and lays the groundwork for the future of the application. Read more about it on our blog post.

New features and improvements

Updated UI

We've updated the UI to be more user friendly and help you see all your data at a glance. With the new navigation bar you can quickly see all your website content and even easily switch between websites with the embedded dropdown.

Additionally, all the previous reports have been separated out into individual pages for easier access.

Improved filters

Filters are now applied universally everywhere in the application via the query string. That means you can copy the URL to share with your team and it will remember what filters were applied.

We've also enhanced the filter form so that you can add and edit multiple filters at once.

Segments and cohorts

Segments are a set of filters that you can save to use for later. For example, you can create a segment called Windows users from the United States, and apply it to your data via the filter form.

A cohort is a group of users who share a common event or experience during a specific time period, and are then tracked over time. For example, you can create a cohort called Users who signed up in November. You can then analyze retention or behavior over time. Just like segments, cohorts can be applied as a filter parameter.

Links and pixels

Umami v3 introduces two additional elements you can use for tracking, links and pixels. Links are simply short URLs that redirect to another URL. You can use links to measure how often users are clicking on certain links or as download links to a file to see how many downloads
it received.

Pixels are invisible images your can embed elsewhere to measure traffic. For example, on external websites where you can't install a website tracker but can post images. You can also embed pixels into your emails to measure open rates, for example in a monthly newsletter to members.

Both links and pixels have their own stats pages just like websites.

New admin page

There is a new dedicated admin page for admin users. You can view and make changes to all the users, websites and teams in the system.

Coming soon

One feature that unfortunately didn't make it into this release was Boards. With boards, you would be able to create your own dashboards and components to display your data however you like. We're still hard at work on it and it will be available in the next release.

Breaking changes

Umami v3 no longer supports MySQL as a database option, only PostgreSQL. If you want to migrate your data over we've written a guide to help you migrate.

Updates

• Next v15.5.3
• Prisma v6.18.0

Thanks

@mdotme @mcnaveen @kronthto @malwarepad @nickcmaynard @andreynering @matiasfacello @halkeye @fauzora @0xflotus @badmike @fnwbr @markkuhar

---

This discussion was created from the release v3.0.0.

[Matthijz98]

Is there no page anymore where I can quickly see all websites stats for an account?
I liked that view, specially on mobile.

Also, as someone with 10+ accounts, the switching to the new UI takes more time/clicks.
Would it be an idea to show all sites for all different accounts in the dropdown in the top left and then grouped by the account?

[s-theo]

I also need this convenient feature to quickly view statistics for all websites; it shouldn't be removed.

[lucasfcunha]

I suspect it might be related to this?

Coming soon
One feature that unfortunately didn't make it into this release was Boards. With boards, you would be able to create your own dashboards and components to display your data however you like. We're still hard at work on it and it will be available in the next release.

That is also the first thing that I noticed, my "homepage" for Umami was always the /dashboard endpoint that would show quick stats for all my websites.

[mikecao]

The new boards feature will replace the old dashboard. The problem was the old dashboard was fine if you had a couple websites, but was unusable for people with many websites.

[mishatashev123-jpg]

Спасибо

[monolithseo]

Perfect - I emailed support about this exact thing. Glad to hear consideration for lots of websites is being taken into account 🙏

In the meantime, I found this - which works with v3: https://github.com/songtianlun/umami-dashboard

[Matthijz98]

Small UI bug in Firefox when adding a new goal

[refringe]

Is there an issue or a PR that I can read that goes into detail about why MySQL was dropped?

[mikecao]

A couple reasons:

1. Usage was significantly below PostgreSQL (only 2% of users used MySQL)
2. MySQL performance was worse than PostgreSQL.
3. Supporting multiple databases greatly increased development and testing time.

[MichaelBelgium]

How would u know mysql was used less? Mysql has been around for ages and is most used and u can do lot more than postgres

This is really a bummer

[TreyWW]

How would u know mysql was used less?

Most likely the image downloads. There's a separate image for Postgres and MySQL.

I don't think in the scope of this project there's anything than MySQL can do that Postgres can't.

The only downside I see is that for people that already have MySQL infra, they have to now run Postgres aswell.

[michelmelo]

So I didn't use images to test the platform; if you use images, they usually go to the first option. Now, on real servers it might be different. You could do a poll and see the difference between one option and another.

[gerardnll]

Beware. There are breaking changes in the API that are not listed.

[goshku]

after updating :)

[PatrickD1985]

Not sure what I am doing wrong with the new postgresql docker image.
After updating postgresql to 18.0 locally (as the version Plesk has by default well ... it's old ), i used a mysql dump of the database as instructed and then used pgloader to convert that mysql db to postgresql.

I then fired up a new docker image using
docker pull docker.umami.is/umami-software/umami:postgresql-latest
and with the postgresql databaseurl.

But what ever I do it keeps returning;

 ------------------------------------------------------

[email protected] start-docker /app
npm-run-all check-db update-tracker start-server

[email protected] check-db /app
node scripts/check-db.js

✓ DATABASE_URL is defined.
✓ Database connection successful.
✗
Invalid prisma.$queryRaw() invocation:

 ELIFECYCLE  Command failed with exit code 1.
ERROR: "check-db" exited with 1.
 ELIFECYCLE  Command failed with exit code 1. 
 ------------------------------------------------------
 
 And I have no idea as to why, can anyone give me some pointers perhaps?

[halkeye]

Right that's the umami side, but can you connect to the db with a client. You can use psql inside a postgres container. Or some other db client directly on your computer.

I guess also how are you running postgres

[PatrickD1985]

Yeah I was able to connect to the postgresql db as I used pgloader to migrste the mysql database.
SO let me try that.

`# /usr/pgsql-18/bin/psql -h localhost -p 5432 -d XXXXX -U postgres
psql (18.0)
Type "help" for help.

umamidbpostgres=# select version() as version
umamidbpostgres-# \dt
List of tables
Schema | Name | Type | Owner
---------+--------------------+-------+----------
umamidb | _prisma_migrations | table | postgres
umamidb | event_data | table | postgres
umamidb | report | table | postgres
umamidb | revenue | table | postgres
umamidb | segment | table | postgres
umamidb | session | table | postgres
umamidb | session_data | table | postgres
umamidb | team | table | postgres
umamidb | team_user | table | postgres
umamidb | user | table | postgres
umamidb | website | table | postgres
umamidb | website_event | table | postgres
(12 rows)

umamidbpostgres=# SELECT version();
version

PostgreSQL 18.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-28), 64-bit
(1 row)
`

So yeah you tell me ;)

[halkeye]

I was hoping it was something like it wasn't started yet or something
postgres 18 is pretty new
you could try again (without worrying about the db dump, just to test) postgres 15 like is in the docker compose file - https://github.com/umami-software/umami/blob/master/docker-compose.yml#L22

[PatrickD1985]

Hehehe ok I might try that the issue first was I started with postgresql 10 (as the one with plesk was old) had to do some tricks for 18... but well wonder if 15 would change anything. As it does not get to the database version is an issue statement.

[PatrickD1985]

In short after fiddling around with a lot I got it working BUT and the but is big here; It understood my imported user data, my website but nothing about events/sessions etc.

Some more info;
As noted I used pgloader, which seemed to do the conversion fine. But what it does not do correctly is set the schema of the tables for the Postgresql database. So they where listed under the schema umamidb while my docker umami was looking in the public schema. So after fixing that commandline with a bunch of alter table statement, hey it at least let me login.

Various errors regarding UUIDs etc popped up.

But the whole migrating from mysql to psql is not something that is very clear or easy to do.
The normal instruction listed here https://umami.is/docs/guides/migrate-mysql-postgresql for running the dump; simply results in a lot of invalid commands for me, same goes for when doing it directly with the docker command.

I think the migration process should be more clear before people of all sort/walks can make this step.
I for one will be staying on 2.19.0 with in my case MariaDB untill it all becomes more clear as how to deal with it all.

Love you guys for sure, but this simply does not seem wordlwide production ready ... and I dont mean that in a bad way. I mean that there are so many possible hosting setups, with quirks, that currently simply dont work with how it is today.

Will be keeping an eye out and try this a bit later down the road.

[mishatashev123-jpg]

й

[Matthijz98]

After using the new ui a bit more i have some more feedback.
There are plenty of things that take extra clicks to view.

I use the events a lot. And viewing the event properties.
Maybe this is also fixed with the boards later.
But I think I should be able to click a event and see the properties.

[Villi0naire]

Hello,

I recently upgraded my Umami instance from version 2.19.0 to 3.0.

Since the upgrade, I've noticed a significant and noticeable drop in the unique visitor count reported on my dashboard. While there may have been a slight decrease in actual traffic, the reported difference is much larger than expected.

I am concerned that this drastic change might be due to an alteration in the visitor tracking/counting algorithm between the two major versions.

Could you please confirm if there were any fundamental changes in how unique visitors (or sessions) are aggregated or identified in version 3.0 compared to 2.19.0?

Any information regarding changes in the following would be helpful:

The logic for generating the session UUID.

The criteria for distinguishing a unique visitor.

The implementation of bot/crawler filtering.

Thank you for your time and help!

[dinohajric]

After upgrading from 2.19 to 3.0 there is a significant CPU usage. From average 26 on 2.19 to constant max 100 now on 3.0.
I have upgraded our cloud instance but not helping.

It happens when I login to the platform

[issam-seghir]

@mikecaothe i didn't like the new dark mode in v3 the old dark mode it's a lot better

[mikaello]

No longer v prefix for versions in published docker images?

Previously the version number in all docker image tags where prefixed with v. E.g., postgresql-v2, "postgresql-v2.9.0",, but as of v3, the v is removed:

  "3",
  "3.0",
  "3.0.0",
  "postgresql-3",
  "postgresql-3.0",
  "postgresql-3.0.0",

See all tags with:

$ curl -sH "Authorization: Bearer $(curl https://ghcr.io/token?scope=repository:umami-software/umami:pull 2>/dev/null | jq -r .token)" https://ghcr.io/v2/umami-software/umami/tags/list?n=10000 | jq .tags

Is this intended? It seems OK to me, but we didn't get an update to this image because we have a regex for Renovate that has a v in it, so we need to change that if this will be the new pattern.

[mikaello]

I notice v3.0.1 is published without v as prefix as well: https://github.com/umami-software/umami/pkgs/container/umami/581143940?tag=3.0.1 , so I guess this is the new pattern ✅