Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs: add Monitor docs section (#79577)

Michael Ebyf9ac58f58608
diff --git a/docs/README.md b/docs/README.md
index 759195c2df6..d2ec8a744cd 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -48,7 +48,6 @@ Metabase's reference documentation.
- [Configuring the Metabase application database](./installation-and-operation/configuring-application-database.md)
- [Backing up Metabase](./installation-and-operation/backing-up-metabase-application-data.md)
- [Migrating to a production application database](./installation-and-operation/migrating-from-h2.md)
-- [Monitoring your Metabase](./installation-and-operation/monitoring-metabase.md)
- [Development instances](./installation-and-operation/development-instance.md)
- [Serialization](./installation-and-operation/serialization.md)
- [Remote sync](./installation-and-operation/remote-sync.md)
@@ -238,7 +237,6 @@ Metabase's reference documentation.
- [Webhooks](./configuring-metabase/webhooks.md)
- [Environment variables](./configuring-metabase/environment-variables.md)
- [Configuration file](./configuring-metabase/config-file.md)
-- [Metabase log configuration](./configuring-metabase/log-configuration.md)
- [Timezones](./configuring-metabase/timezones.md)
- [Languages and localization](./configuring-metabase/localization.md)
- [Appearance](./configuring-metabase/appearance.md)
@@ -246,11 +244,22 @@ Metabase's reference documentation.
- [Custom maps](./configuring-metabase/custom-maps.md)
- [Customizing the Metabase Jetty webserver](./configuring-metabase/customizing-jetty-webserver.md)
+### Monitor
+
+- [Monitor overview](./monitor/start.md)
+- [Dependency diagnostics](./monitor/dependency-diagnostics.md)
+- [Erroring questions](./monitor/erroring-questions.md)
+- [Alerts management](./monitor/alerts-management.md)
+- [Background tasks](./monitor/background-tasks.md)
+- [Scheduled jobs](./monitor/scheduled-jobs.md)
+- [Application logs](./monitor/application-logs.md)
+- [Model persistence log](./monitor/model-persistence-log.md)
+- [CLI analytics](./monitor/cli-analytics.md)
+
### Tools
- [Tools overview](./usage-and-performance-tools/start.md)
- [Usage analytics](./usage-and-performance-tools/usage-analytics.md)
-- [Admin tools](./usage-and-performance-tools/tools.md)
### Metabase Cloud
@@ -275,7 +284,7 @@ Metabase's reference documentation.
- [Troubleshooting guides](troubleshooting-guide/index.md)
- [Metabase forum](https://discourse.metabase.com/)
-- [Configuring logging](./configuring-metabase/log-configuration.md)
+- [Application logs](./monitor/application-logs.md)
### Tutorials and guides
diff --git a/docs/ai/usage-auditing.md b/docs/ai/usage-auditing.md
index f020c101e03..8c4329434fb 100644
--- a/docs/ai/usage-auditing.md
+++ b/docs/ai/usage-auditing.md
@@ -7,22 +7,22 @@ summary: "See token and message counts, chat logs, and more."
{% include plans-blockquote.html feature="AI usage auditing" %}
-_Admin > AI > Usage auditing_
+_Monitor > AI auditing_
Admins can get an overview of human-robot interactions across Metabase, from high-level stats like total token counts down to visibility into actual conversations. These interactions include the in-product Metabot chat sidebar, Metabot conversations in [Documents](../documents/start.md), [Slack chats](./metabot-slack.md), and [inline SQL editing](./metabot.md#inline-sql-editing).
The usage auditing section includes:
-- [Stats](#stats): aggregate charts across all Metabot activity.
+- [Usage stats](#usage-stats): aggregate charts across all Metabot activity.
- [Conversations](#conversations): a filterable list of every conversation, with a detail view for each.
You can also build your own questions on top of the [Usage Analytics views](#building-custom-reports) that back these reports.
-## Stats
+## Usage stats
-_Admin > AI > Usage auditing > Stats_
+_Monitor > Usage stats_
-The Stats page shows aggregate Metabot activity over a date range you choose, defaulting to the previous 30 days.
+The Usage stats page shows aggregate Metabot activity over a date range you choose, defaulting to the previous 30 days.
### Filters
@@ -56,11 +56,11 @@ You can drill through in the **By day**, **Groups with most ...**, **Users with
They often line up (a conversation that started in Slack is handled by the Slackbot profile), but they don't have to. A conversation started from the Metabot chat sidebar might be handled by the **Internal**, **NLQ**, or **SQL** profile depending on what the person asked.
-The Conversations admin page only shows **Profile**. Source is visible in the **Stats** charts and in the [Usage Analytics models](#building-custom-reports) used to build custom reports.
+The Conversations admin page only shows **Profile**. Source is visible in the **Usage stats** charts and in the [Usage Analytics models](#building-custom-reports) used to build custom reports.
### Sources
-Each conversation is tagged with a source, i.e. where in Metabase the conversation took place. The **By source** chart in [Stats](#stats) groups conversations by a human-readable `source_name`, and the [AI Usage Log](#building-custom-reports) model exposes both `source_name` and a raw `source` ID (e.g. `metabot_agent`, `oss-sql-gen`, `document_generate_content`) for custom reports. Conversations Metabase couldn't classify show up as `(empty)` on the chart.
+Each conversation is tagged with a source (where in Metabase the conversation took place). The **By source** chart in [Usage stats](#usage-stats) groups conversations by a human-readable `source_name`, and the [AI Usage Log](#building-custom-reports) model exposes both `source_name` and a raw `source` ID (like `metabot_agent`, `oss-sql-gen`, `document_generate_content`) for custom reports. Conversations Metabase couldn't classify show up as `(empty)` on the chart.
| Source name | Where it comes from |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
@@ -73,7 +73,7 @@ Each conversation is tagged with a source, i.e. where in Metabase the conversati
### Profiles
-A profile is the configuration Metabot uses for a conversation: which prompt, which tools, and what it's allowed to do. The Conversations admin page, the **By profile** chart in [Stats](#stats), and the **Metabot Conversations** model (see [Building custom reports](#building-custom-reports)) all show the human-readable profile name. The [AI Usage Log](#building-custom-reports) model exposes the raw `profile_id` instead (e.g. `internal`, `transforms_codegen`, `embedding_next`).
+A profile is the configuration Metabot uses for a conversation: which prompt, which tools, and what it's allowed to do. The Conversations admin page, the **By profile** chart in [Usage stats](#usage-stats), and the **Metabot Conversations** model (see [Building custom reports](#building-custom-reports)) all show the human-readable profile name. The [AI Usage Log](#building-custom-reports) model exposes the raw `profile_id` instead (e.g. `internal`, `transforms_codegen`, `embedding_next`).
| Profile | What it does |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
@@ -87,13 +87,13 @@ A profile is the configuration Metabot uses for a conversation: which prompt, wh
## Conversations
-_Admin > AI > Usage auditing > Conversations_
+_Monitor > Conversations_
The Conversations page lists every Metabot conversation Metabase has on file, newest first.
### Filters
-- **Date range**, **User**, **Group**, **Tenant**: same as the [Stats filters](#filters).
+- **Date range**, **User**, **Group**, **Tenant**: same as the [Usage stats filters](#filters).
### Columns
diff --git a/docs/configuring-metabase/environment-variables.md b/docs/configuring-metabase/environment-variables.md
index 5b024127284..dd5a75a8b20 100644
--- a/docs/configuring-metabase/environment-variables.md
+++ b/docs/configuring-metabase/environment-variables.md
@@ -3076,7 +3076,7 @@ Since: v51.3
If `true`, log a stack trace for any connections killed due to exceeding the timeout specified in [MB_DB_QUERY_TIMEOUT_MINUTES](#mb_db_query_timeout_minutes).
-In order to see the stack traces in the logs, you'll also need to update the com.mchange log level to "INFO" or higher via a custom log4j configuration. For configuring log levels, see [Metabase log configuration](./log-configuration.md).
+In order to see the stack traces in the logs, you'll also need to update the com.mchange log level to "INFO" or higher via a custom log4j configuration. For configuring log levels, see [Application logs](../monitor/application-logs.md).
### `MB_JETTY_ASYNC_RESPONSE_TIMEOUT`
diff --git a/docs/configuring-metabase/start.md b/docs/configuring-metabase/start.md
index 4fa6ac74273..3b4ce3156c1 100644
--- a/docs/configuring-metabase/start.md
+++ b/docs/configuring-metabase/start.md
@@ -34,7 +34,7 @@ Configure Metabase on launch via environment variables.
On self-hosted Pro and Enterprise plans, you can configure Metabase via a configuration file.
-## [Metabase logs configuration](./log-configuration.md)
+## [Application logs](../monitor/application-logs.md)
Tell Metabase what to log.
diff --git a/docs/data-modeling/model-persistence.md b/docs/data-modeling/model-persistence.md
index 9f3ce2f35f2..53a51f103b4 100644
--- a/docs/data-modeling/model-persistence.md
+++ b/docs/data-modeling/model-persistence.md
@@ -70,7 +70,7 @@ To refresh a model's results, go to the model and click on the three-dot menu (*
## View model persistence logs
-You can view the logs for model persistence by clicking on the **grid** icon in the upper right and selecting **Admin** > **Tools** > **Model caching logs**. See [Admin tools](../usage-and-performance-tools/tools.md).
+You can view the logs for model persistence in **Monitor** > **Model persistence log**. See [Model persistence log](../monitor/model-persistence-log.md).
## Difference between persisted models and caching
diff --git a/docs/data-studio/dependencies/graph.md b/docs/data-studio/dependencies/graph.md
index 66805fd3bdc..22bdc95bc87 100644
--- a/docs/data-studio/dependencies/graph.md
+++ b/docs/data-studio/dependencies/graph.md
@@ -80,6 +80,6 @@ You can use the dependency graph to replace query sources in bulk. See [Replace
## Further reading
- [Library](../library.md)
-- [Dependency diagnostics](./diagnostics.md)
+- [Dependency diagnostics](../../monitor/dependency-diagnostics.md)
- [Replace data sources](./replace-data-sources.md)
- [Schema viewer](../schema-viewer.md)
diff --git a/docs/data-studio/overview.md b/docs/data-studio/overview.md
index c42c845796b..28fa71321ab 100644
--- a/docs/data-studio/overview.md
+++ b/docs/data-studio/overview.md
@@ -22,10 +22,8 @@ Data Studio provides tools to shape and track your data so everyone can trust th
- **[Segments](./segments.md)**: Create saved filters on tables so people can use consistent definitions when building queries.
- **[Measures](./measures.md)**: Create saved aggregations on tables so people can use consistent calculations when building queries.
- **[Schema viewer](./schema-viewer.md)**\*: Visualize relationships between tables as an entity-relationship diagram (ERD).
-- **[Dependency graph](./dependencies/graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them.
+- **[Dependency graph](./dependencies/graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them. To find content with broken dependencies, see [Dependency diagnostics](../monitor/dependency-diagnostics.md).
- **[Replace data sources](./dependencies/replace-data-sources.md)**\*: Swap out a table or model across all content that uses it, in one operation.
-- **[Dependency diagnostics](./dependencies/diagnostics.md)**\*: See which items have broken dependencies, or that aren't used.
-
- **[Transforms](./transforms/transforms-overview.md)**: Wrangle your data in Metabase, write the query results back to your database, and reuse them in Metabase as sources for new queries.
- **[Glossary](../exploration-and-organization/data-model-reference.md#glossary)**: Define terms relevant to your business, both for people and agents trying to understand your data.
diff --git a/docs/installation-and-operation/alert-management.md b/docs/installation-and-operation/alert-management.md
deleted file mode 100644
index b536d006910..00000000000
--- a/docs/installation-and-operation/alert-management.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Alerts management
-summary: "See all alerts in your instance and manage them in bulk"
----
-
-# Alerts management
-
-_Admin > Tools > Alerts management_
-
-In the Alert management section, Admins can:
-
-- View and search all [question alerts](../questions/alerts.md) in their Metabase
-- Identify failed or orphaned alerts
-- Edit alerts, including changing the alert's owner
-- Delete alerts in bulk
-
-![Alert management](./images/alert-management.png)
-
-Currently, [dashboard subscriptions](../dashboards/subscriptions.md) are not included.
-
-## See all alerts
-
-To see all alerts active in your Metabase instance, go to **Admin > Tools > Alerts management**.
-
-You can:
-
-- Filter alerts by channel ([email](../configuring-metabase/email.md), [Slack](../configuring-metabase/slack.md), or [webhook](../configuring-metabase/webhooks.md)) or recipient.
-
-- See alerts that **failed** the last time they were ran.
-
- Failed alerts view include both alerts that were attempted but failed (for example, because of a query error) and alerts that were abandoned and never attempted (for example, because the instance was restarting at the moment when the alert was scheduled).
-
- To see the entire history of alert runs (not just the last attempt), go to **Admin > Tools > Tasks** instead.
-
-- See **ownerless** alerts - alerts whose owner has been deactivated
-
- This is helpful when you want to [mass-delete](#delete-alerts) alerts that are no longer relevant, or [change the owner](#change-alert-owners) to an active user.
-
-- See individual alert's properties and history.
-
-- [Delete alerts in bulk](#delete-alerts).
-
-- [Change alert owners in bulk](#change-alert-owners).
-
-If you want to get some analytics about your alerts (rather than manage them) - for example, you want to see how many alerts have failed per week, or which questions have the most number of alerts - use [Usage Analytics](../usage-and-performance-tools/usage-analytics.md) instead.
-
-## Change alert owners
-
-The owner of an alert has the power to edit or delete the alert. Usually, the person who created the alert is also the alert's owner.
-
-Admins can change owners of alerts. This is useful, for example, if the original alert owner left the company, and you need to give some else the power to manage the alert.
-
-To change the owner for one or more alerts:
-
-1. Go to **Admin > Tools > Alerts management**.
-2. Select the alerts whose owners you'd like to change.
-3. Click **Change owner** at the bottom of the screen.
-4. Assign a new owner.
-
-## Delete alerts
-
-![Bulk delete](./images/alerts-bult.png)
-
-You can delete multiple alerts at once.
-
-1. Go to **Admin > Tools > Alerts management**.
-2. Select the alerts whose owners you'd like to delete.
-3. Click **Delete** at the bottom of the screen.
-
-## Further reading
-
-- [Alerts](../questions/alerts.md)
-- [Usage analytics](../usage-and-performance-tools/usage-analytics.md)
-- [Setting up email](../configuring-metabase/email.md)
-- [Setting up Slack](../configuring-metabase/slack.md)
-- [Setting up webhooks](../configuring-metabase/webhooks.md)
-- [Managing people](../people-and-groups/managing.md)
diff --git a/docs/installation-and-operation/metabase-cli.md b/docs/installation-and-operation/metabase-cli.md
index 2ee03d597f5..be9577d6367 100644
--- a/docs/installation-and-operation/metabase-cli.md
+++ b/docs/installation-and-operation/metabase-cli.md
@@ -71,6 +71,7 @@ Pair the CLI with version control to build content with an agent in a developmen
## Further reading
+- [CLI analytics](../monitor/cli-analytics.md)
- [@metabase/cli on npm](https://www.npmjs.com/package/@metabase/cli)
- [Agent-driven development](../ai/file-based-development.md)
- [Agent skills](https://github.com/metabase/agent-skills)
diff --git a/docs/installation-and-operation/observability-with-prometheus.md b/docs/installation-and-operation/observability-with-prometheus.md
index 08627a07739..2558686d0b5 100644
--- a/docs/installation-and-operation/observability-with-prometheus.md
+++ b/docs/installation-and-operation/observability-with-prometheus.md
@@ -168,4 +168,4 @@ Metrics exported by Metabase include:
## Further reading
- [Running Metabase](../troubleshooting-guide/running.md)
-- [Monitoring Metabase](./monitoring-metabase.md)
+- [Profiling your Metabase](../troubleshooting-guide/profiling-metabase.md)
diff --git a/docs/installation-and-operation/start.md b/docs/installation-and-operation/start.md
index c8f975ad334..641846aff40 100644
--- a/docs/installation-and-operation/start.md
+++ b/docs/installation-and-operation/start.md
@@ -38,7 +38,7 @@ Export your questions, dashboards, and more as YAML files that you can check int
A command-line client that drives a Metabase instance over its API, on its own or through an AI agent.
-## [Monitoring your Metabase](./monitoring-metabase.md)
+## [Profiling your Metabase](../troubleshooting-guide/profiling-metabase.md)
Monitor your Metabase with JMX.
diff --git a/docs/monitor/alerts-management.md b/docs/monitor/alerts-management.md
new file mode 100644
index 00000000000..f2a9075adca
--- /dev/null
+++ b/docs/monitor/alerts-management.md
@@ -0,0 +1,67 @@
+---
+title: Alerts management
+summary: View and manage every alert in your Metabase, including failing and ownerless alerts.
+redirect_from:
+ - /docs/latest/installation-and-operation/alert-management
+---
+
+# Alerts management
+
+The Alerts management page lists every [alert](../questions/alerts.md) in your Metabase. Use this page to find and fix failing or ownerless alerts. Alerts management doesn't include [dashboard subscriptions](../dashboards/subscriptions.md).
+
+Alerts management is only available to admins.
+
+To open Alerts management:
+
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Alerts management**.
+
+The page has three tabs:
+
+- **All alerts**: Every alert in your Metabase.
+- **Failing**: Alerts whose last check or send attempt failed or was abandoned.
+- **Ownerless**: Alerts whose owner's account was deactivated. Metabase marks deactivated owners with a ghost icon.
+
+For each alert, Metabase shows the:
+
+- **ID**: The alert's unique identifier.
+- **Question**: The question that triggers the alert.
+- **Owner**: The person who created the alert.
+- **Channel**: Where the alert sends notifications (email, Slack, or webhook).
+- **Last checked**: The timestamp for when Metabase last ran the alert's question.
+- **Last send attempt**: The timestamp for when Metabase last tried to send the alert. Alerts that have never met their condition show **Never**.
+
+If a check or send attempt failed, Metabase displays an error icon next to the timestamp.
+
+To find a specific alert, search by question or owner. Click **Filter** to filter alerts by channel, last send attempt status, owner status, or email recipient.
+
+## Delete alerts or change owner
+
+To delete alerts or reassign them to a new owner:
+
+1. Select the checkbox next to each alert. To select all alerts, select the checkbox in the header row.
+2. In the action bar, click **Delete** or **Change owner**.
+3. If you click **Change owner**, select the new owner from the list.
+
+To deselect the alerts, click **Clear**.
+
+## Alert details
+
+To view more information about an alert, click on the alert's row to open the sidebar, which displays:
+
+- Error messages for failing alerts.
+- Link to the question that triggers the alert.
+- **Check history**: The status of the alert's recent checks.
+- **Send history**: The status of the alert's recent send attempts.
+
+Use the up and down arrows at the top of the sidebar to move between alerts in the list.
+
+To edit the alert, click the **pencil** icon at the top of the sidebar.
+
+## Further reading
+
+- [Usage analytics](../usage-and-performance-tools/usage-analytics.md)
+- [Dashboard subscriptions](../dashboards/subscriptions.md)
+- [Setting up email](../configuring-metabase/email.md)
+- [Setting up Slack](../configuring-metabase/slack.md)
+- [Setting up webhooks](../configuring-metabase/webhooks.md)
\ No newline at end of file
diff --git a/docs/configuring-metabase/log-configuration.md b/docs/monitor/application-logs.md
similarity index 82%
rename from docs/configuring-metabase/log-configuration.md
rename to docs/monitor/application-logs.md
index 09f5c2ad8c0..cc48dc134c1 100644
--- a/docs/configuring-metabase/log-configuration.md
+++ b/docs/monitor/application-logs.md
@@ -1,17 +1,18 @@
---
-title: Metabase logs
+title: Application logs
redirect_from:
- /docs/latest/operations-guide/log-configuration
+ - /docs/latest/configuring-metabase/log-configuration
summary: Configure how much information Metabase displays in its logs.
---
-# Metabase logs
+# Application logs
Metabase logs quite a bit of information by default. Metabase uses [Log4j 2](https://logging.apache.org/log4j/2.x/) under the hood, so you can configure how much information Metabase logs.
## View and download Metabase logs
-You can find Metabase logs in **Admin** > **Tools** > **Logs**. You can filter the logs by keywords (for example, "sync") and download them as a text file.
+You can find Metabase logs in **Monitor** > **Application logs**. You can filter the logs by keywords (for example, "sync") and download them as a text file.
If you're running self-hosted Metabase, you'll also be able to see the logs in the terminal.
@@ -19,17 +20,19 @@ If you're running self-hosted Metabase, you'll also be able to see the logs in t
See [How to read logs](../troubleshooting-guide/server-logs.md).
-## Configuring logging Level
+## Configuring logging level
Metabase uses [Log4j](https://logging.apache.org/log4j/2.x/) for logging configuration. Here is Metabase's [default logging configuration](https://github.com/metabase/metabase/blob/master/resources/log4j2.xml). Some troubleshooting tasks might require you to override this logging configuration (for example, to see more details about errors). See Log4j's docs for info on [log levels](https://logging.apache.org/log4j/2.x/manual/customloglevels.html).
-### Temporary override logging configuration
+### Temporarily override logging configuration
-_Admin > Tools > Logs_.
+_Monitor > Application logs_.
+
+Only admins can customize log levels.
To temporarily adjust the logging configuration:
-1. Go to **Admin** > **Tools** > **Logs**.
+1. Go to **Monitor** > **Application logs**.
2. Click on **Customize log levels** above the logs.
You can select from log-level presets for common troubleshooting tasks (for example, troubleshooting sync issues), or provide your own configuration as JSON. For example, here's an override configuration that increases logging for troubleshooting linked filters:
@@ -41,7 +44,7 @@ To temporarily adjust the logging configuration:
}
```
-The override from Admin settings will be temporary. You can select for how long the override should be in place (e.g., 60 minutes). When the override times out, the logging configuration will revert to the default logging configuration (or a custom configuration if you're using a [custom log file](#use-a-custom-log-configuration-file)).
+This override will be temporary. You can select for how long the override should be in place (e.g., 60 minutes). When the override times out, the logging configuration will revert to the default logging configuration (or a custom configuration if you're using a [custom log file](#use-a-custom-log-configuration-file)).
### Use a custom log configuration file
@@ -114,4 +117,4 @@ java --add-opens java.base/java.nio=ALL-UNNAMED -jar metabase.jar
### Turn off colorized logs
-By default, Metabase will use color when displaying logs (both in the Admin **Logs** and in the terminal). You can disable colorized logs using the [`MB_COLORIZE_LOGS` environment variable](../configuring-metabase/environment-variables.md#mb_colorize_logs).
+By default, Metabase will use color when displaying logs (both in **Monitor** > **Application logs** and in the terminal). You can disable colorized logs using the [`MB_COLORIZE_LOGS` environment variable](../configuring-metabase/environment-variables.md#mb_colorize_logs).
diff --git a/docs/monitor/background-tasks.md b/docs/monitor/background-tasks.md
new file mode 100644
index 00000000000..7b5f59c9779
--- /dev/null
+++ b/docs/monitor/background-tasks.md
@@ -0,0 +1,59 @@
+---
+title: Background tasks
+summary: See the status of the tasks and runs that Metabase performs in the background, like syncs, alerts, and notifications.
+---
+
+# Background tasks
+
+The Background tasks page lists the work Metabase performs in the background, including database syncs, alerts, and notifications. Use this page to check the status of tasks and to troubleshoot failures.
+
+To open Background tasks:
+
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Background tasks**.
+
+The Background tasks page has two tabs:
+
+- **Tasks**: The individual steps Metabase performs to complete a run.
+- **Runs**: Single operations, like database syncs or alert sends.
+
+## Tasks
+
+The Tasks tab lists the individual steps Metabase performs to complete a run. For each task, Metabase shows the:
+
+- **Task**: The type of task.
+- **DB Name**: The name of the database involved in the task.
+- **DB Engine**: The database engine.
+- **Started at**: The timestamp for when the task started.
+- **Ended at**: The timestamp for when the task finished.
+- **Duration (ms)**: The duration of the task in milliseconds.
+- **Status**: Whether the task succeeded, failed, or is still in progress.
+
+Use the **Filter by task** dropdown to view a single task type, and the **Filter by status** dropdown to view tasks with a specific status.
+
+### Task details
+
+Click a task to view more information about it, including the task's ID and a link to the run it belongs to.
+
+The Task details page displays the task's JSON details, which include the error message and stack trace for failed tasks. To save the JSON, click the **Download** button. To copy it, click the **Copy** icon.
+
+The Task details page also displays any logs the task captured.
+
+## Runs
+
+The Runs tab lists each operation Metabase performs. For each run, Metabase shows the:
+
+- **Run Type**: The type of run, like an alert or a sync.
+- **Entity**: The item the run involves, like a question for an alert or a database for a sync.
+- **Started at**: The timestamp for when the run started.
+- **Ended at**: The timestamp for when the run finished.
+- **Status**: Whether the run succeeded, failed, is still in progress, or was abandoned.
+- **Task Count**: The number of tasks in the run, including a breakdown of how many succeeded and failed.
+
+Use the **Filter by run type**, **Filter by started at**, **Filter by entity**, and **Filter by status** dropdowns to narrow the list.
+
+### Run details
+
+Click a run to view more information about it, including the run's ID, its entity type, and a link to the entity it involves.
+
+The Run details page also displays the run's tasks and their statuses. Click a task to view its [task details](#task-details).
diff --git a/docs/monitor/cli-analytics.md b/docs/monitor/cli-analytics.md
new file mode 100644
index 00000000000..4d880bbcc6a
--- /dev/null
+++ b/docs/monitor/cli-analytics.md
@@ -0,0 +1,85 @@
+---
+title: CLI analytics
+summary: See which operations the Metabase CLI runs, who runs them, and when each person last used the CLI.
+---
+
+# CLI analytics
+
+{% include plans-blockquote.html feature="CLI analytics" %}
+
+_Monitor > CLI analytics_
+
+The CLI analytics page shows how people use the [Metabase CLI](../installation-and-operation/metabase-cli.md) with your instance. Metabase records one row for every API call the CLI makes, so you can see whether anyone is using it, which operations they run, how often they run them, and when each person last used it.
+
+Admins and people in groups with [Monitoring access](../permissions/application.md#monitoring-access) can view CLI analytics. See [Permissions for Monitor](./start.md#permissions-for-monitor).
+
+The page has two tabs:
+
+- **Usage**: Charts that summarize CLI activity over the date range you pick.
+- **Calls**: One row per call, so you can look at individual requests.
+
+## Filters
+
+Both tabs share the same filters.
+
+- **Tenant**: Limit to a single [tenant](../embedding/tenants.md). Only shows up if tenants are enabled.
+- **Group**: Limit to a single [group](../people-and-groups/managing.md) (or **All groups**).
+- **User**: Limit to a single person (or **All users**).
+- **Date range**: The time window the page covers. Defaults to the last 30 days.
+
+## Usage
+
+The Usage tab summarizes the calls that match your filters:
+
+- **Calls by client over time**: A time series of call volume, split by client.
+- **Calls by client**: How many calls came from the Metabase CLI versus everything else. See [How Metabase identifies clients](#how-metabase-identifies-clients).
+- **Calls by operation**: Which operations get called most, like `GET /api/card/:id`.
+- **Calls by user**: Who makes the most calls.
+- **User activity**: A table of everyone who has used the CLI, including when they were last active. Use it to spot people who tried the CLI once and stopped, or credentials that are still running calls after someone has moved on.
+
+### Error charts only appear when calls have failed
+
+If any calls in your date range failed, Metabase adds an **Errors** section below the charts with:
+
+- **Calls by status over time**: Successful calls next to failed ones.
+- **Errors by operation**: Which operations fail most.
+
+If you're expecting errors and don't see the section, widen the date range.
+
+## Calls
+
+The Calls tab lists individual calls, newest first. For each call, Metabase shows:
+
+- **ID**: An identifier for the record, unique to each call.
+- **Created at**: When the call came in.
+- **Operation**: The HTTP method and API path, like `GET /api/card/:id`.
+- **Client**: **Metabase CLI** or **Other**.
+- **User**: Who made the call.
+- **Tenant**: The caller's [tenant](../embedding/tenants.md). Only shows up if tenants are enabled.
+- **IP address**: Where the call came from. Only shows up if you [turn on PII retention](#turn-on-pii-retention-to-see-ip-addresses-and-error-messages).
+- **Status**: `success` or `error`. Metabase counts any response of 400 or above as an error.
+- **Duration (ms)**: How long the call took, in milliseconds.
+- **Error message**: Why a failed call failed. Only shows up if you [turn on PII retention](#turn-on-pii-retention-to-see-ip-addresses-and-error-messages), and Metabase truncates long messages.
+
+You can sort by **Created at**, **Operation**, **Client**, **User**, **Status**, or **Duration (ms)**.
+
+## How Metabase identifies clients
+
+Metabase reads the `User-Agent` header the caller sends. A caller that identifies itself as `metabase-cli/<version>` shows up as **Metabase CLI**; everything else, including callers that send no user agent at all, shows up as **Other**.
+
+Clients report their own user agent, so treat the Client column as a usage signal, not a security control. Metabase never uses the client name to decide what a caller is allowed to do. Permissions are handled by the [permissions](../permissions/start.md) of the person who authenticated the CLI or [API key](../people-and-groups/api-keys.md) behind the call.
+
+## Turn on PII retention to see IP addresses and error messages
+
+The IP address and Error message columns stay empty unless you turn on [`MB_ANALYTICS_PII_RETENTION_ENABLED`](../configuring-metabase/environment-variables.md#mb_analytics_pii_retention_enabled), which controls whether Metabase stores personally identifiable information alongside its analytics. PII retention is off by default.
+
+## How long Metabase keeps CLI call data
+
+Once a day, Metabase deletes call records older than [`MB_AI_USAGE_MAX_RETENTION_DAYS`](../configuring-metabase/environment-variables.md#mb_ai_usage_max_retention_days). The same setting controls retention for [AI usage auditing](../ai/usage-auditing.md) data, so changing it affects both.
+
+## Further reading
+
+- [Metabase CLI](../installation-and-operation/metabase-cli.md)
+- [Agent API](../ai/agent-api.md)
+- [AI usage auditing](../ai/usage-auditing.md)
+- [Monitor overview](./start.md)
diff --git a/docs/data-studio/dependencies/diagnostics.md b/docs/monitor/dependency-diagnostics.md
similarity index 81%
rename from docs/data-studio/dependencies/diagnostics.md
rename to docs/monitor/dependency-diagnostics.md
index fd2aa0b9bda..e08a9524967 100644
--- a/docs/data-studio/dependencies/diagnostics.md
+++ b/docs/monitor/dependency-diagnostics.md
@@ -3,32 +3,34 @@ title: Dependency diagnostics
summary: Find broken content and unused items so you can fix problems and clean up safely.
redirect_from:
- /docs/latest/data-studio/dependency-diagnostics
+ - /docs/latest/data-studio/dependencies/diagnostics
---
# Dependency diagnostics
{% include plans-blockquote.html feature="Dependency diagnostics" %}
-Dependency diagnostics shows you content with broken dependencies, and content that isn't referenced by anything else.
+Dependency diagnostics shows you content with broken dependencies, and content that nothing else references.
To open Dependency diagnostics:
-1. Open [Data Studio](../overview.md).
-2. Click **Dependency diagnostics** in the left sidebar.
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Dependency diagnostics**.
Dependency diagnostics has two tabs: **Broken dependencies** and **Unreferenced entities**.
## Broken dependencies
-![Broken dependencies](../images/broken-dependencies.png)
+![Broken dependencies](./images/broken-dependencies.png)
-Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../../data-modeling/metadata-editing.md).
+Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../data-modeling/metadata-editing.md).
The broken dependencies table includes:
- Tables
-- [Questions](../../questions/introduction.md)
-- [Models](../../data-modeling/models.md)
+- [Questions](../questions/introduction.md)
+- [Models](../data-modeling/models.md)
+
For each item, the list shows:
@@ -46,7 +48,7 @@ Selecting an item opens a details panel with:
- The item's name, owner, and creation date
- A list of missing or invalid columns, with copy buttons to help fix references
- Downstream items that are broken because of this specific issue. You can filter this list by entity type
-- Quick links to open items or view them in the [dependency graph](./graph.md)
+- Quick links to open items or view them in the [dependency graph](../data-studio/dependencies/graph.md)
For tables created by transforms, the sidebar also shows a link to the source transform.
@@ -70,23 +72,23 @@ To fix this, either restore the expected column names in the SQL query or update
## Unreferenced entities
-![Unreferenced entities](../images/unreferenced-entities.png)
+![Unreferenced entities](./images/unreferenced-entities.png)
Unreferenced entities shows items that aren't used by any other non-archived content. Use this view to clean up unused content, especially reusable items like measures, metrics, and snippets. Start by checking why an item was created, when it was last edited, and whether it was meant to be reused.
-An unreferenced item isn't broken and isn't automatically safe to delete. It simply means nothing else depends on it. Check [Usage analytics](../../usage-and-performance-tools/usage-analytics.md) for view activity before you archive or delete an item.
+An unreferenced item isn't broken and isn't automatically safe to delete. It simply means nothing else depends on it. Check [Usage analytics](../usage-and-performance-tools/usage-analytics.md) for view activity before you archive or delete an item.
The Unreferenced entities list is limited to what you can access, so an item can show up as unreferenced even if something you can't see depends on it.
Unreferenced entities includes:
- Tables
-- [Questions](../../questions/introduction.md)
-- [Models](../../data-modeling/models.md)
-- [Metrics](../../data-modeling/metrics.md)
+- [Questions](../questions/introduction.md)
+- [Models](../data-modeling/models.md)
+- [Metrics](../data-modeling/metrics.md)
- Segments
- Measures
-- [Snippets](../../questions/native-editor/snippets.md)
+- [Snippets](../questions/native-editor/snippets.md)
For each item, the list shows:
@@ -99,6 +101,6 @@ Selecting an item opens a details panel with:
- Who created the item and when
- When it was last edited
-- Links to open the item or view it in the [dependency graph](./graph.md)
+- Links to open the item or view it in the [dependency graph](../data-studio/dependencies/graph.md)
For tables, the sidebar also shows owners, descriptions, and links to open the schema or database. For tables created by transforms, the sidebar shows a link to the source transform.
diff --git a/docs/monitor/erroring-questions.md b/docs/monitor/erroring-questions.md
new file mode 100644
index 00000000000..dfabdeef849
--- /dev/null
+++ b/docs/monitor/erroring-questions.md
@@ -0,0 +1,28 @@
+---
+title: Erroring questions
+summary: See which questions returned errors when last run, and rerun them as you troubleshoot.
+redirect_from:
+ - /docs/latest/enterprise-guide/tools
+ - /docs/latest/usage-and-performance-tools/tools
+---
+
+# Erroring questions
+
+{% include plans-blockquote.html feature="Erroring questions" %}
+
+The Erroring questions page lists the questions that returned an error the last time they ran.
+
+To open Erroring questions:
+
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Erroring questions**.
+
+For each question, Metabase shows the:
+
+- Error message
+- Database that returned the error
+- Collection that contains the question
+
+You can search by question, error, database, or collection.
+
+To check whether you've fixed an error, select one or more questions and rerun them.
\ No newline at end of file
diff --git a/docs/data-studio/images/broken-dependencies.png b/docs/monitor/images/broken-dependencies.png
similarity index 100%
rename from docs/data-studio/images/broken-dependencies.png
rename to docs/monitor/images/broken-dependencies.png
diff --git a/docs/data-studio/images/unreferenced-entities.png b/docs/monitor/images/unreferenced-entities.png
similarity index 100%
rename from docs/data-studio/images/unreferenced-entities.png
rename to docs/monitor/images/unreferenced-entities.png
diff --git a/docs/monitor/model-persistence-log.md b/docs/monitor/model-persistence-log.md
new file mode 100644
index 00000000000..17db76dd931
--- /dev/null
+++ b/docs/monitor/model-persistence-log.md
@@ -0,0 +1,25 @@
+---
+title: Model persistence log
+summary: View the status of persisted models and refresh their cached results.
+---
+
+# Model persistence log
+
+The Model persistence log lists your [persisted models](../data-modeling/model-persistence.md) and the status of their refreshes.
+
+To open the Model persistence log:
+
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Model persistence log**.
+
+For each persisted model, Metabase shows the:
+
+- **Model**: The [model](../data-modeling/models.md) being persisted
+- **Collection**: The collection that contains the model
+- **Status**: The status of the last refresh
+- **Last run at**: When the model's results were last refreshed
+- **Created by**: Who created the persisted model
+
+Click a model's name to open the model, or its collection to open the collection.
+
+To rerun a model's query and update its results, click the **refresh** icon at the end of the model's row.
diff --git a/docs/monitor/scheduled-jobs.md b/docs/monitor/scheduled-jobs.md
new file mode 100644
index 00000000000..ffe97bafa2d
--- /dev/null
+++ b/docs/monitor/scheduled-jobs.md
@@ -0,0 +1,35 @@
+---
+title: Scheduled jobs
+summary: View the recurring jobs Metabase runs automatically, and the triggers that determine when each job fires.
+---
+
+# Scheduled jobs
+
+The Scheduled jobs page lists the recurring work Metabase performs on a schedule, like cache refreshes, model persistence refreshes, and health checks. To manage these jobs, Metabase uses the [Quartz scheduler](https://www.quartz-scheduler.org/).
+
+While [Background tasks](./background-tasks.md) shows the work Metabase performed, Scheduled jobs shows the schedules themselves, including which jobs exist and when they'll fire next.
+
+To open Scheduled jobs:
+
+1. Open [Monitor](./start.md).
+2. In the left sidebar, click **Scheduled jobs**.
+
+At the top of the page, Metabase displays information about the scheduler itself, including how long it's been running, the number of jobs executed, and its thread pool size.
+
+For each job, Metabase shows the:
+
+- **Key**: The job's unique identifier.
+- **Class**: The code that the job runs.
+- **Description**: What the job does. Not all jobs include a description.
+
+## Triggers
+
+Click a job to view its triggers. A trigger is a schedule that determines when the job fires.
+
+For each trigger, Metabase shows the:
+
+- **Key**: The trigger's unique identifier.
+- **State**: The trigger's current state.
+- **Priority**: The trigger's priority when multiple jobs fire at once.
+- **Last Fired**: The timestamp for when the trigger last fired.
+- **Next Fire Time**: The timestamp for when the trigger will fire next.
diff --git a/docs/monitor/start.md b/docs/monitor/start.md
new file mode 100644
index 00000000000..e3a996a43cb
--- /dev/null
+++ b/docs/monitor/start.md
@@ -0,0 +1,55 @@
+---
+title: Monitor
+summary: Monitor contains Metabase's troubleshooting and observability tools, so you can find and fix problems with your content and your Metabase.
+---
+
+# Monitor
+
+Monitor contains Metabase's troubleshooting and observability tools. Use it to find and fix problems with your content, like broken dependencies and failing questions. You can also check on the work Metabase performs in the background, like syncs and alerts.
+
+To open Monitor:
+
+1. Click the **grid** icon in the upper right.
+2. Select **Monitor**.
+
+## What's in Monitor
+
+Monitor contains three sections:
+
+- [Content management](#content-management)
+- [Logs and activity](#logs-and-activity)
+- [AI auditing](#ai-auditing)
+
+### Content management
+
+- **[Dependency diagnostics](./dependency-diagnostics.md)**\*: Find content with broken dependencies, and content that nothing else references.
+- **[Erroring questions](./erroring-questions.md)**\*: See questions that returned an error the last time they ran.
+- **[Alerts management](./alerts-management.md)**: View and manage every alert in your Metabase, including failing and ownerless alerts.
+
+\* Available on [Pro and Enterprise plans](https://www.metabase.com/pricing/). On other plans, these tabs show an upgrade page.
+
+### Logs and activity
+
+- **[Background tasks](./background-tasks.md)**: See the status of the tasks and runs Metabase performs in the background, including syncs, alerts, and notifications.
+- **[Scheduled jobs](./scheduled-jobs.md)**: View the recurring work Metabase performs on a schedule, like cache refreshes, model persistence refreshes, and health checks.
+- **[Application logs](./application-logs.md)**: View Metabase's logs, and configure how much information Metabase logs.
+- **[Model persistence log](./model-persistence-log.md)**: View the status of persisted models and refresh their cached results.
+
+### AI auditing
+
+The AI auditing tabs are only available on [Pro and Enterprise plans](https://www.metabase.com/pricing/).
+
+- **[Usage stats](../ai/usage-auditing.md#usage-stats)**: See AI feature usage, including tokens and messages.
+- **[Conversations](../ai/usage-auditing.md#conversations)**: Review people's conversations with Metabot.
+- **MCP analytics**: See usage of the [Metabase MCP server](../ai/mcp.md).
+- **[CLI analytics](./cli-analytics.md)**: See which operations the [Metabase CLI](../installation-and-operation/metabase-cli.md) runs against your Metabase.
+
+## Permissions for Monitor
+
+Who can see each Monitor page depends on their group:
+
+- **Admin group** can view every page.
+- **[Data Analysts](../people-and-groups/managing.md#data-analysts) group** can view Dependency diagnostics.\*
+- **Groups with [Monitoring access](../permissions/application.md#monitoring-access)** can view every page except Dependency diagnostics and Alerts management.\*
+
+\* On OSS, only admins can view Monitor. The Data Analysts group and the Monitoring access permission are only available on [Pro and Enterprise plans](https://www.metabase.com/pricing/).
diff --git a/docs/permissions/application.md b/docs/permissions/application.md
index cb323534ca8..36e5d4088ea 100644
--- a/docs/permissions/application.md
+++ b/docs/permissions/application.md
@@ -30,11 +30,22 @@ Settings access defines which groups can view and edit the settings under the Ad
## Monitoring access
-Monitoring access sets permissions for the following:
-
-- [Tools](../usage-and-performance-tools/tools.md)
+People in groups with Monitoring access can view:
+
+- [Monitor](../monitor/start.md), including:
+ - [Erroring questions](../monitor/erroring-questions.md)
+ - [Background tasks](../monitor/background-tasks.md)
+ - [Scheduled jobs](../monitor/scheduled-jobs.md)
+ - [Application logs](../monitor/application-logs.md) (read-only)
+ - [Model persistence log](../monitor/model-persistence-log.md)
+- The **Help** tab in Admin
- [Troubleshooting](../troubleshooting-guide/index.md)
+The following Monitor pages aren't included in Monitoring access:
+
+- [Dependency diagnostics](../monitor/dependency-diagnostics.md): Available to admins and people in the [Data Analysts](../people-and-groups/managing.md#data-analysts) group
+- [Alerts management](../monitor/alerts-management.md): Available to admins only
+
## Subscriptions and alerts
This setting determines who can create:
diff --git a/docs/questions/alerts.md b/docs/questions/alerts.md
index 92e6ef9acfc..a95a45db2e8 100644
--- a/docs/questions/alerts.md
+++ b/docs/questions/alerts.md
@@ -116,7 +116,7 @@ Admins:
- Admins can add or remove recipients on any alert, even ones that they didn't create themselves.
- Admins can bulk manage alerts per person from the [People menu in Admin settings](../people-and-groups/managing.md#unsubscribe-from-all-subscriptions-and-alerts).
-- Admins can bulk manage all alerts in the instance in [Admin > Tools > Alert management](../installation-and-operation/alert-management.md).
+- Admins can bulk manage all alerts in the instance in [Monitor > Alerts management](../monitor/alerts-management.md).
Metabase will email you when:
diff --git a/docs/installation-and-operation/images/AddRemoteHost.png b/docs/troubleshooting-guide/images/AddRemoteHost.png
similarity index 100%
rename from docs/installation-and-operation/images/AddRemoteHost.png
rename to docs/troubleshooting-guide/images/AddRemoteHost.png
diff --git a/docs/installation-and-operation/images/ClickAddJMXHost.png b/docs/troubleshooting-guide/images/ClickAddJMXHost.png
similarity index 100%
rename from docs/installation-and-operation/images/ClickAddJMXHost.png
rename to docs/troubleshooting-guide/images/ClickAddJMXHost.png
diff --git a/docs/installation-and-operation/images/EnterJMXPort.png b/docs/troubleshooting-guide/images/EnterJMXPort.png
similarity index 100%
rename from docs/installation-and-operation/images/EnterJMXPort.png
rename to docs/troubleshooting-guide/images/EnterJMXPort.png
diff --git a/docs/installation-and-operation/images/HeapDump.png b/docs/troubleshooting-guide/images/HeapDump.png
similarity index 100%
rename from docs/installation-and-operation/images/HeapDump.png
rename to docs/troubleshooting-guide/images/HeapDump.png
diff --git a/docs/installation-and-operation/images/LocalProcessVisualVM.png b/docs/troubleshooting-guide/images/LocalProcessVisualVM.png
similarity index 100%
rename from docs/installation-and-operation/images/LocalProcessVisualVM.png
rename to docs/troubleshooting-guide/images/LocalProcessVisualVM.png
diff --git a/docs/installation-and-operation/images/OpenRemoteInstance.png b/docs/troubleshooting-guide/images/OpenRemoteInstance.png
similarity index 100%
rename from docs/installation-and-operation/images/OpenRemoteInstance.png
rename to docs/troubleshooting-guide/images/OpenRemoteInstance.png
diff --git a/docs/installation-and-operation/images/SetRemoteHostName.png b/docs/troubleshooting-guide/images/SetRemoteHostName.png
similarity index 100%
rename from docs/installation-and-operation/images/SetRemoteHostName.png
rename to docs/troubleshooting-guide/images/SetRemoteHostName.png
diff --git a/docs/installation-and-operation/images/ThreadDump.png b/docs/troubleshooting-guide/images/ThreadDump.png
similarity index 100%
rename from docs/installation-and-operation/images/ThreadDump.png
rename to docs/troubleshooting-guide/images/ThreadDump.png
diff --git a/docs/troubleshooting-guide/index.md b/docs/troubleshooting-guide/index.md
index 0aec880f62f..6ed069fecf3 100644
--- a/docs/troubleshooting-guide/index.md
+++ b/docs/troubleshooting-guide/index.md
@@ -10,6 +10,7 @@ Problems, their causes, how to detect them, and how to fix them.
- [Download diagnostic info](./diagnostic-info.md)
- [Create a HAR file](./create-har-file.md)
+- [Profiling your Metabase](./profiling-metabase.md)
## Installation
diff --git a/docs/installation-and-operation/monitoring-metabase.md b/docs/troubleshooting-guide/profiling-metabase.md
similarity index 95%
rename from docs/installation-and-operation/monitoring-metabase.md
rename to docs/troubleshooting-guide/profiling-metabase.md
index b940e22fda0..f8af72073ef 100644
--- a/docs/installation-and-operation/monitoring-metabase.md
+++ b/docs/troubleshooting-guide/profiling-metabase.md
@@ -1,11 +1,12 @@
---
-title: Monitoring your Metabase
+title: Profiling your Metabase
redirect_from:
- /docs/latest/operations-guide/jmx-monitoring
- /docs/latest/operations-guide/enable-jmx
+ - /docs/latest/installation-and-operation/monitoring-metabase
---
-# Monitoring Your Metabase
+# Profiling your Metabase
Diagnosing performance-related issues can be a challenge. Luckily, the JVM ships with tools that can help diagnose many common issues. Enabling JMX and using a tool like VisualVM can help diagnose issues related to running out of memory, a stalled Metabase, or slow response times.
@@ -88,5 +89,5 @@ Another useful picture of a running Metabase system is a Thread Dump. In cases w
## Further reading
-- [Running Metabase](../troubleshooting-guide/running.md)
-- [Observability with Prometheus](./observability-with-prometheus.md)
+- [Running Metabase](./running.md)
+- [Observability with Prometheus](../installation-and-operation/observability-with-prometheus.md)
diff --git a/docs/troubleshooting-guide/running.md b/docs/troubleshooting-guide/running.md
index 19ec49a0309..1584f7c5550 100644
--- a/docs/troubleshooting-guide/running.md
+++ b/docs/troubleshooting-guide/running.md
@@ -45,7 +45,7 @@ If you're seeing this "Out of memory" (OOM) error, you'll need to [allocate more
You can use tools to view how Metabase uses the memory available to it over time. Check out:
- [Observability with Prometheus](../installation-and-operation/observability-with-prometheus.md)
-- [Monitoring your Metabase](../installation-and-operation/monitoring-metabase.md)
+- [Profiling your Metabase](./profiling-metabase.md)
The specific Prometheus metric you need to check is jvm_memory_bytes_used{area="heap"}
diff --git a/docs/troubleshooting-guide/server-logs.md b/docs/troubleshooting-guide/server-logs.md
index 65048778daf..a39b4fa4a9d 100644
--- a/docs/troubleshooting-guide/server-logs.md
+++ b/docs/troubleshooting-guide/server-logs.md
@@ -27,5 +27,5 @@ Let's unpack the log:
- **Queries in flight:** `Queries in flight: 0 (0 queued)`. The number of active and queued queries across all database sources connected to Metabase. We recommend checking the **Database info** below for troubleshooting issues with the database related to the request.
- **Database info**:`h2 DB 4 connections: 0/1 (0 threads blocked)`. Shows database type, database ID, connections active/pool (and queue). This info is specific to the database related to the request (in this case a `POST` request), and not to the overall queries in flight.
-[log-level]: ../configuring-metabase/log-configuration.md
+[log-level]: ../monitor/application-logs.md
[scale]: https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale
diff --git a/docs/usage-and-performance-tools/start.md b/docs/usage-and-performance-tools/start.md
index 343c5c5d556..ac81324daec 100644
--- a/docs/usage-and-performance-tools/start.md
+++ b/docs/usage-and-performance-tools/start.md
@@ -12,6 +12,6 @@ Administration tools for managing your Metabase.
See how people are using your Metabase.
-## [Admin tools](./tools.md)
+## [Monitor](../monitor/start.md)
-View question error and model caching logs.
+View erroring questions, logs, and other troubleshooting tools.
diff --git a/docs/usage-and-performance-tools/tools.md b/docs/usage-and-performance-tools/tools.md
deleted file mode 100644
index 0de22dac1ea..00000000000
--- a/docs/usage-and-performance-tools/tools.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Admin tools
-redirect_from:
- - /docs/latest/enterprise-guide/tools
----
-
-# Admin tools
-
-The Admin **Tools** tab contains features for troubleshooting. To get to the Admin tools sections, go to the top right of the screen and click the **grid** icon > **Admin** > **Tools**.
-
-## Question error logs
-
-{% include plans-blockquote.html feature="Question error logs" %}
-
-Metabase will list the questions that returned errors when last run, including the:
-
-- Error message,
-- Database that returned the error,
-- Collection that houses the question that errored.
-
-You can select and rerun multiple questions at a time while you troubleshoot to see whether you've resolved their errors.
-
-## Model caching logs
-
-Here you can view the:
-
-- [Models](../data-modeling/models.md) being persisted
-- The status of the last model query refresh
-- When the model was last refreshed
-- And who created the persisted model
-
-You can also click the refresh icon to rerun the model's query to update its results.
diff --git a/src/metabase/cmd/resources/other-env-vars.md b/src/metabase/cmd/resources/other-env-vars.md
index 277510696db..087134f2772 100644
--- a/src/metabase/cmd/resources/other-env-vars.md
+++ b/src/metabase/cmd/resources/other-env-vars.md
@@ -268,7 +268,7 @@ Since: v51.3
If `true`, log a stack trace for any connections killed due to exceeding the timeout specified in [MB_DB_QUERY_TIMEOUT_MINUTES](#mb_db_query_timeout_minutes).
-In order to see the stack traces in the logs, you'll also need to update the com.mchange log level to "INFO" or higher via a custom log4j configuration. For configuring log levels, see [Metabase log configuration](./log-configuration.md).
+In order to see the stack traces in the logs, you'll also need to update the com.mchange log level to "INFO" or higher via a custom log4j configuration. For configuring log levels, see [Application logs](../monitor/application-logs.md).
### `MB_JETTY_ASYNC_RESPONSE_TIMEOUT`
diff --git a/src/metabase/metabot/settings.clj b/src/metabase/metabot/settings.clj
index 0403012893e..7011a39df36 100644
--- a/src/metabase/metabot/settings.clj
+++ b/src/metabase/metabot/settings.clj
@@ -431,6 +431,7 @@
- `ai_usage_log`
- `metabot_conversation`
- `metabot_message`
+- `agent_api_call_log`
Once a day, Metabase deletes rows older than this threshold. The minimum value is 30 days (Metabase will treat entered values of 1 to 29 the same as 30).
-If set to 0, Metabase will keep all rows.")
+If set to 0, Metabase will keep all rows. If you don't set this variable, Metabase keeps rows for 180 days.")