Слияние кода завершено, страница обновится автоматически
| title |
|---|
Usage analytics |
{% include plans-blockquote.html feature="Usage analytics" %}
The Usage analytics collection is a special collection that contains view-only questions, dashboards, and models that help you understand how people are using your Metabase.
You can find the Usage analytics collection under collections in the left navigation sidebar. You can also create custom reports.
These resources are useful for:
Metabase creates some default user accounts that you might see in your usage analytics, like
internal@metabase.com. See Default accounts.
You can find the Usage analytics collection under collections in the navigation sidebar. By default, only admins can see the Usage analytics collection, but admins can grant other groups view access to it. You can manage permissions for the collection in Admin settings > Permissions > Collections.
There are only two access types for the Usage analytics collection: View and No access. Even admins can't curate Usage analytics.
Additionally, this Usage analytics collection has a default sub-collection called "Custom reports" which you can use to save duplicated/modified questions, dashboards, and models. This sub-collection inherits the same permissions, but it's not view-only; admins have curate access by default, and can grant other groups view access.
If you're upgrading from a version older than 48, people in groups with monitoring access will also get access to the Usage analytics collection. But after that initial grandfathering in, the monitoring access privilege is unrelated to the Usage analytics collection; you'll need to specifically grant groups access to the Usage analytics collection.
Only people in groups with view access to the Usage analytics collection will see this Usage insights option.
To view usage analytics for a question, dashboard, or model:
Metabase will take you to the relevant usage dashboard and plug in the item's ID.
By default, Metabase will keep the data about activity, views, and query execution for 720 days. Twice a day, Metabase will delete rows older than this threshold. You can change this limit by adjusting the environment variable MB_AUDIT_MAX_RETENTION_DAYS.
Metabase Open Source edition, which is also used on the Metabase Cloud Starter plan, doesn't collect Activity and View data. If you upgrade from the Open Source/Starter to a Pro or Enterprise plan, you'll only see View and Activity data in Usage Analytics starting from the time when you upgraded.
You can duplicate any of the questions, dashboards and models in the Usage analytics collection and tweak them to your liking, but you'll need to save them to a different collection.
While you can save custom questions, models, and dashboards wherever you like (except for the Usage analytics collection), we recommend that you save your custom Usage analytics reports in the conveniently named "Custom reports" sub-collection. That way these items inherit the same permissions as the parent Usage analytics collection.
There is one thing to know about the Custom reports collection: its metadata resets whenever Metabase restarts. While you are able to temporarily rename the Custom reports collection, or give it a description or an Official badge, Metabase will drop this collection's metadata when it restarts. But rest assured that Metabase will preserve any questions, models, events, or dashboards that you add to the Custom reports collection.
The Usage analytics collection includes a set of read-only dashboards.
General information about people viewing and creating dashboards, questions, subscriptions, and alerts. Cards include:
View the most relevant content in your Metabase. Cards include:
See what someone's been up to in your Metabase. Cards include:
Information about dashboards, questions, models, and tables. Cards include:
Views, performance, activity, and other data for a particular question. Cards include:
Question, dashboard and database performance. Cards include:
If you're using MySQL or MariaDB as your application database, the Performance overview dashboard won't display results for the cards displaying the 50th and 90th percentile query running times, because MySQL and MariaDB don't support the Percentile aggregation. We recommend using PostgreSQL as your application database.
Dashboards and questions that you could consider archiving. Cards include:
The Usage analytics collection includes a bunch of useful models based on Metabase's application database.
Each row of this model describes one event of a particular topic. Fields include:
The topics include:
Tracks views cards (which includes models), dashboards, and tables. Fields include:
Information about all queries Metabase ran across all dashboards. Fields include:
Query sources include:
All alerts, both active and archived.
Questions, dashboards, models, events, and collections.
Entity types include:
Everyone in your Metabase, including deactivated accounts. Fields include:
Which subscriptions are active, who created them, who's subscribed to them, when they're sent, and more.
Each row is a dashboard card: either a question card or a text card. Fields include:
Information about your connected data sources. Fields include:
List of all tables across all connected data sources. Fields include:
All fields from all connected data sources. Fields include:
Describes the last 14 days of Metabase internal processes tasks.
Вы можете оставить комментарий после Вход в систему
Неприемлемый контент может быть отображен здесь и не будет показан на странице. Вы можете проверить и изменить его с помощью соответствующей функции редактирования.
Если вы подтверждаете, что содержание не содержит непристойной лексики/перенаправления на рекламу/насилия/вульгарной порнографии/нарушений/пиратства/ложного/незначительного или незаконного контента, связанного с национальными законами и предписаниями, вы можете нажать «Отправить» для подачи апелляции, и мы обработаем ее как можно скорее.
Опубликовать ( 0 )