> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/object-storage-stook/analytics/metrics.md). # Metrics [Stook Analytics](/products/object-storage-stook/analytics.md) metrics provide quantitative insight into how your [Stook Object Storage](/products/object-storage-stook/stook-cloud-object-storage.md) buckets are accessed and used over time. Metrics are calculated from request-level data generated by [Stook API](/api-documentation/object-storage-stook.md) operations. They are aggregated based on the selected filters and time range in [Stook Analytics](/products/object-storage-stook/analytics.md). ## Requests **Requests** represents the total number of API requests processed by Stook Object Storage. This metric includes all supported Stook API operations, such as object retrieval, upload, listing, and deletion. **Use this metric to:** * Monitor overall activity levels * Detect sudden traffic increases or drops * Compare usage across buckets or endpoints ## Bytes **Bytes** represents the total amount of data transferred as part of Stook API requests. This metric includes data transferred both to and from [Stook Object Storage](/products/object-storage-stook/stook-cloud-object-storage.md). **Use this metric to:** * Measure data transfer volume * Analyze bandwidth consumption * Correlate traffic volume with storage usage ## Throughput **Throughput** represents the rate at which data is transferred over time. It is calculated as the amount of data transferred per second within the selected time interval. **Use this metric to:** * Evaluate data transfer efficiency * Identify performance bottlenecks * Analyze sustained versus burst traffic patterns ## IO Rate **IO Rate** represents the number of requests processed per second. This metric reflects how frequently applications interact with Stook buckets. **Use this metric to:** * Analyze request intensity * Identify high-frequency access patterns * Monitor load characteristics per bucket ## Average Response Time **Average Response Time** represents the average time required to process a request. It is calculated across all requests within the selected scope and time range. **Use this metric to:** * Monitor request latency * Detect performance degradation * Validate application responsiveness ## Success Rate **Success Rate** represents the percentage of requests completed successfully. Successful requests are typically identified by [`2xx` HTTP status codes](/getting-started/concepts/http-response-codes.md). **Use this metric to:** * Measure service reliability * Track operational stability * Validate access and configuration correctness ## Failure Rate **Failure Rate** represents the percentage of requests that resulted in an error. This includes both client-side ([`4xx`](/getting-started/concepts/http-response-codes.md)) and server-side ([`5xx`](/getting-started/concepts/http-response-codes.md)) responses. **Use this metric to:** * Detect access or permission issues * Identify malformed or invalid requests * Monitor error trends over time ## 4xx Ratio **4xx Ratio** represents the proportion of client-side errors. These errors usually indicate issues such as invalid requests, authentication failures, or missing resources. **Use this metric to:** * Identify application-level issues * Detect incorrect request patterns * Review access control configuration ## 5xx Ratio **5xx Ratio** represents the proportion of server-side errors. These errors may indicate temporary service issues or internal processing failures. **Use this metric to:** * Monitor platform stability * Identify systemic issues * Support troubleshooting and incident analysis ## Total Stored Data **Total Stored Data** represents the total size of data currently stored across the selected Stook Buckets. This metric reflects storage usage rather than request activity. **Use this metric to:** * Track storage growth over time * Monitor capacity usage * Support planning and cost-related decisions ## Metric Availability and Limits {% hint style="info" %} * Metrics are aggregated based on the selected time range and applied filters. * Each analytics query supports a maximum **90-day time range**. * Historical analytics data is retained for **up to 6 months**. * Queries outside the retention period may return partial or empty results. * FTP uploads are not included in [Stook Analytics](/products/object-storage-stook/analytics.md). {% endhint %} ### Related topics * [Stook Analytics](/products/object-storage-stook/analytics.md) (dashboard, filters, raw logs) * [Stook Analytics API Reference](/api-documentation/analytics/stook-analytics.md) (pull the same metrics via API) * [Stook API Reference](/api-documentation/object-storage-stook.md) (bucket operations, credentials, settings) * [Getting Started with Stook](/products/object-storage-stook/getting-started-with-stook.md) (create buckets, credentials, FTP) * [Manage Access Keys](/products/object-storage-stook/manage-access-keys.md) (rotate keys, tighten access) * [Connect Stook Bucket to CDN](/products/object-storage-stook/connect-stook-bucket-to-cdn.md) (serve objects via CDN) * [HTTP Response Codes](/getting-started/concepts/http-response-codes.md) (what 2xx/4xx/5xx mean) --- # 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://clients.medianova.com/products/object-storage-stook/analytics/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.