> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/run-the-platform/tenants/tenant-monitoring.md). # Monitoring Tenants This page discusses the use of dashboards and subscriptions to oversee tenants. Dashboards provide a lot of helpful information about tenants. Subscriptions allow for sending reports and on-demand alerts based upon various events. ## The *All-Tenants Dashboard* (summary info) The *All-Tenants Dashboard* provides an overview of tenants with links to drill down to more detailed information. **To access the *****All-Tenants Dashboard*****:** Click **Tenants** on the top menu and select **Dashboard** **-OR-** click the Tenants card on the Main Dashboard Page. ### Counts/Status Indicators In the top left of the *All-Tenants Dashboard*, counts and status indicators will show the number of tenants powered on/total number of tenants; and the number of tenant nodes powered on/total number of tenant nodes. These count boxes are clickable to access the list of tenants or list of tenant nodes, respectively. ### Usage Usage sections provide a **quick view** of the **top usage** among your tenants, across **CPU, RAM, Storage, and Network**. Each list entry here is also a **link** to the individual tenant Dashboard to quickly access more detailed information about the particular tenant. ## Individual Tenant Dashboards Each tenant has its own dashboard to show configuration and summary information for the individual tenant, with each card on the dashboard providing a link to increased detail. **To access a particular tenant's dashboard:** 1. From the *All-Tenants Dashboard*, click **Tenants**. 2. **Double-click** on the **desired tenant** in the list. ### Understanding Storage Used/Provisioned/Allocated * **Provisioned** - the amount of (post-deduplication) storage that has been specified as available to the tenant. A tenant's provisioned storage is not a hard limit. However, log alerts are triggered based on this threshold; monitor the *All-Tenants Dashboard* and Logs for warnings and alerts. * **Used** - reflects the tenant's actual consumed storage, after deduplication. * **Allocated** - identifies the top amount of storage that would be utilized should all the tenant's disk devices be filled to capacity. The amount of allocated storage can often show a much larger number than used or provisioned because device files are thin provisioned; the amount of storage allocated to a VM drive/NAS volume is not consumed by the vSAN until actually used, e.g. a 4TB VM drive that only contains 200GB of data has 4TB allocated, but only uses 200GB (minus any deduplication) of vSAN space {% hint style="info" %} **Tenant Storage and Deduplication** Tenant storage numbers only consider deduplication within the tenant's own stored data. Cross-tenant deduplication is not factored in. {% endhint %} {% hint style="success" %} Subscriptions (covered below) are a good tool to use for monitoring tenant storage; you can get dashboard reports on a regular basis and notifications based on storage thresholds. {% endhint %} ### Usage Statistics CPU, RAM, and Storage usage for the tenant is provided in graph form in **5-minute intervals**. Statistic listings for the current **5-second "heartbeat"** are displayed under the graph. History links allow you to see beyond the current 5-minute interval and gather usage information for specific periods. Historical statistical information is saved at **5-minute** intervals, **corresponding to standard 95th percentile standards for billing**. **To see more granular detail on graphs:** Click and drag a subset of the graph to see more detail for that selected timeframe. Double-click to back out to the original detail level. ### Logs The most recent log entries will show on the dashboard screen. Errors are highlighted in red for easy recognition. Click the **--View More--** link at the bottom to view further back in the logs. ## Subscriptions Subscriptions can provide both scheduled reports and on-demand alerts when errors, warnings, or specified changes occur, or if configured thresholds are reached. Subscription emails are sent to the defined email address(es) of the user(s). The Subscription engine allows you to customize how and when you receive reports and notifications. The following examples demonstrate tenant-related Subscriptions that can help in ongoing monitoring of the health and usage of tenants. ### I. Example configuration - receive alerts for any status errors or warnings related to tenants: ![tenantssubscription-alert](/files/zXMOQlWNP1mvADYaPWCl) ### II. Example configuration - 7:15 am daily report of the All-Tenants Dashboard (overview information): ![tenantssubscription-report](/files/mBRulvKGPOQycPqGks6l) ### III. Example configuration - weekly report (to the Administrators Group) showing summary information for a specific tenant: ![singletenantsubscription-report](/files/dkR3d466OXNjmsfeBdkV) There are many options available when creating subscriptions. For more information see: [**Subscriptions-Overview**](/run-the-platform/system-administration/subscriptions-overview.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vergeos-demo.com/run-the-platform/tenants/tenant-monitoring.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.