Analytics in Postgres

[normanrz]

• Adds tracking of analytics events in our own postgres database
• Adds the POST /api/analytics/ingest route to accept events from other wk instances, just like the current event-relay does

Steps to test:

• fetch("/api/analytics/ingest", {method:"POST", headers:{"content-type": "application/json"}, body: JSON.stringify({"events":[{"event_type":"open_annotation","user_id":"123456789012345678901234","time":"1706510609682","user_properties":{"organization_id":"123456789012345678901234","is_organization_admin":false,"is_superuser":false,"webknossos_uri":"https://webknossos.org"},"event_properties":{"annotation_id":"123456789012345678901234","annotation_owner_multiuser_id":"123456789012345678901234","annotation_dataset_id":"123456789012345678901234"},"session_id":1706510609681}], "api_key": "dingdong"})}) (also try with other webknossos_uri and api_key)
• Click around in wk and check the postgres database

TODOs:

• Add migration

---

(Please delete unneeded items, merge only when none are left open)

• Updated changelog
• Updated migration guide if applicable

[fm3]

Looking good. I’ll test some once the CI is green

[fm3]

I tested some locally and saving the events of the own instance works.

Did you also test the ingesting? Do you have steps to test for that? Ah, I see them now. Will do some more tests now!

I did see some Unsuccessful WS request to https://events-relay.webknossos.org/events (ID: 0).Status: 500. in the logging. Did something change there?

I also added some comments on the code.

Also, reminder for the migration guide

[fm3]

Testing the ingest worked with the fetch you provided. It also worked with wrong api keys and wrong uris, though. I couldn’t immediately spot the error in the code. Can you reproduce this? If so, maybe you can debug why it is not strictly checked.

[normanrz]

It also worked with wrong api keys and wrong uris

URIs that are not in the list are not protected. For these, you can send events with any key.