> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics.md). # Tool Usage Metrics The tool usage metrics marts are meant to provide users with more information about LTI tools that send Caliper events to the *event\_store.expanded* table. These marts include data such as the time of the earliest and latest Caliper event for the tool and the number of Caliper events for the tool. The marts can be used for monitoring, as they track instances of low activity for a tool that may indicate an outage. ## Data Marts * [Tool Usage Metrics](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics/tool-usage-metrics.md) * [Tool Usage Metrics Archive ](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics/tool-usage-metrics-archive.md) * [Tool Low Events](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics/tool-low-events.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, and the optional `goal` query parameter: ``` GET https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.