Is anyone using Metabase or similar to understand analytical dimensions of activity within Twenty?
Hey All, I'm in the beginning stages of getting deeper into the activity and use of what's happening from those on our team using of twenty. Has anyone started to use tools like metabase/tableau/Grafana/Superset to see how your users are using twenty?
15 Replies
I think I have an idea how to do it
Since in logs there are no information whether someone did something with record, the other way to know which user did something with object/record is by directly fetching data from database
I've been thinking about this too. I'm leaning towards clickhouse and metabase as the tool to build some analytics around our user activity. it's really difficult to know what your team is up to and how they're using the CRM. I'm probably going to start working on this over the coming weeks.
So probably the easiest way is to:
- connect Grafana with database like explained here in documentation
- set correct interval (I suggest 5-15 min if there are many users, 1 hour if less)
- run the query
select * from <workspace>."auditLog";Or do you need to know how specific user uses Twenty?
I was hoping to see on a per user basis in terms of activity. Or a collection of users as a team/group.
This Grafana setup would be nice though. Easy setup and configurable routines.
It's a matter of time and trials till I find the query
yeah, I was hoping to lace together another system so the columnar structure of clickhouse was appealing.
I was just going to set up some data-pipe routines on n8n into clickhouse and the attach metabase.
I was about to suggest using webhooks and n8n for aggregating them but I'm not so sure about that
I considered that, but I wasn't sure how reliable the APIs are and how often they change, cursors, etc..
Webhooks don't change that much (or at least I'm not aware of)
I'm still a little skittish from when the core team introduced the unannounced "app secret" change. It did break the hooks.
I figure a pipe routine in columnar would be pretty safe, and from that standpoint it doesn't really matter if schemas change.
I'm not really married to anything and open to other ideas too.
I just want some visibility for our team and hopefully that will help others here too.
Found it
select * from <workspace>."auditLog" as auditLog inner join <workspace>."workspaceMember" as member on auditLog."workspaceMemberId" = member.id;
If you want to limit data, then instead of select * you have to provide all columns one by one (additionally, you can replace the names of columns with as keyword like I did earlier)
I understand you, the releases notes are something worth changing as they're fine with how they are but they could be better since they are quite short and don't show everything done in sprint/since last version and rarely someone takes a look at releases in Github where are mentioned all merged pull requests (kind of hassle to check every single pull request and, hopefully, linked pull request but oh well)I totally get it. Releases are moving quick it's hard to update everyone on everything. That's what the community is for.
I think it's possible to change that
I understand how annoying it is to found out "bug" which turns out to be a breaking change as I reported few of those "bugs" 😆
Totally forgot, if you need to change the query, feel free to ask
No, the query above is a great start. I was just inspecting the result and sorting by the and . Thanks