They can be created using Metabase’s SQL or Report Wizard tools and applied directly to, say, Koha LMS’s existing SQL reports. Using Metabase, reports can be presented graphically, dashboarded, scheduled and distributed. I'm not sure I understand what that means.Metabase is a business intelligence and analytics system for PTFS Europe’s library applications (eg, Koha LMS). Would you mind elaborating a bit more when you say in the Github issue that the "Temporary workaround is to use custom destination type URL." ? T16:30:47+02:00 INFO Question's average execution duration is 2.8 s using 'magic' TTL of 28.0 s ? T16:30:47+02:00 DEBUG GET /api/table/61/query_metadata 200 2.5 ms (8 DB calls) App DB connections: 0/15 Jetty threads: 5/50 (3 idle, 0 queued) (130 total active threads) Queries in flight: 6 (0 queued)
This looks like the exact same issue I am having, as reproduced below from the Metabase logs: T16:30:47+02:00 WARN GET /api/dashboard/17 403 8.9 ms (13 DB calls) Hi indeed! Well spotted - I didn't see that Github issue so thanks for pointing that out. I would be surprised if that were the problem, but it might still be relevant mentioning. I am also still using the default H2 database for the dashboard data, but am in the process of switching to a separate Postgres instance for that this week. "java.vm.name": "OpenJDK 64-Bit Server VM",Īdditionally, I am querying PostgreSQL 12.2 (Ubuntu 12.2-4).
I would really appreciate any help / guidance you can provide me, and I am more than happy to provide any other screenshots / info that you need to help me debug this. I could try to re-arrange some of the collections / dashboard to perhaps organize them in such a way that these automatic requests / re-routes are no longer an issue, but that would be less than ideal, and I would more importantly like to understand what is going on that is causing this behavior to begin with. This all leads me to believe that there is some weird glitch going on underneath the hood that I simply do not understand. Plus, even if that were the case, my understanding from the Metabase documentation is that if a dashboard has things that are coming from other collections that a user does not have access to, then the dashboard should still load, but just hide the specific elements on the screen that they don't have access to. Being an open source tool, it’s a great MVP and, for many organizations, it’s a great tool to build on top of and really make your own on account of its open. For those who are unfamiliar, Metabase is an open-source business intelligence tool with both a query builder and a native query option. hyperlinks, questions accidentally coming from other collections), but I confirmed that no such linkage / association exists. Metabase is the best open-source BI tool. However, the bigger issue that is puzzling me is why? Why is the mere act of clicking on a permitted dashboard (which is dashboard 5, for reference) sending a request to 2 other unrelated dashboards, which are in collections that the user does not (and should not) have access to? At this point I triple-checked the dashboard to see if there are any traces of anything pointing to those other 2 dashboards (e.g. HOWEVER, for some reason (explained in more detail below), I get a "Sorry, you don’t have permission to see that." error screen when clicking on the actual dashboard - even though the user has access to all the underlying charts / questions and data.Īt this point, I tried digging a bit deeper into where exactly these requests are being made, though I am not an expert in web-dev / networking so I could only get so far, and perhaps I am missing something simple here. It is worth noting that the questions in this collection are querying from 2 different materialized views (also in different schemas), but I made sure that this group has access to both of them.Īs expected, when I log in as that user, they can only view that collection, and inside that collection, they can view all the individual questions (able to view the charts and play around with them, regardless of which of the 2 materialized views the data is coming from). This troubleshooting guide has you covered if you’ve connected your database to Metabase, set up groups for new people, and granted data permissions and collection permissions to those groups, but. So what I did was create a test user in our Metabase application that is in the Company group, which only has access to this specific collection, as well as access to the underlying materialized views that these questions are querying from. v0.43 / Troubleshooting Guide / Permissions Fixing permissions issues.