> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/optimize-cost-savings-and-recommendations/deep-insights/azure-monitor.md).

# Azure Monitor

Azure Monitor shows the cost of your Log Analytics workspaces: what each workspace ingests, how long it keeps data, and what it costs to query, alert on and export.

Go to **Optimize → Deep Insights → Monitor** (under Azure).

### Workspaces list

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2Fcv4k6WNW506NlSdqCAYm%2Fimage.png?alt=media&amp;token=69fe9ad8-a095-4ef0-b26f-aceb9fe917a5" alt=""><figcaption></figcaption></figure>

### Workspace details

Open a workspace to see its details. Four cards show **Last 30 Days Cost**, **Previous Month Cost**, **Avg Daily Ingestion** and **Inbound Sinks**.

#### Resource Details

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FsPZAYM5n7MdK3MTz3BoF%2Fimage.png?alt=media&amp;token=dba3e770-e544-4995-9a8e-e03345914262" alt=""><figcaption></figcaption></figure>

| Section              | What it shows                                                                                                                                                                                          |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Resource Information | Subscription, resource group, region, pricing tier, workspace ID, daily cap, default retention, total retained data, and whether archive retention is enabled                                          |
| Tables by Plan       | The workspace's tables grouped by table plan, such as Analytics, with table count, daily ingestion and price per GB                                                                                    |
| Connected Sources    | What sends data to the workspace or uses it: data collection rules (DCRs), diagnostic settings, AKS clusters (Container Insights), VM Insights agents, linked App Insights components, and alert rules |
| Azure Tags           | Tags on the workspace                                                                                                                                                                                  |

#### Cost & Usage Overview

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FDvvBCX1eGlaTTwAhEJNH%2Fimage.png?alt=media&amp;token=ebbd3b66-8449-420b-83d2-ef759b88d2c7" alt=""><figcaption></figcaption></figure>

Each row shows the component's **Plan**, **Cost** and **Volume**.

| Component                        | What it covers                                                           |
| -------------------------------- | ------------------------------------------------------------------------ |
| Data Ingestion (by Table × Plan) | Ingestion cost for each table, such as SigninLogs                        |
| Data Retention (Interactive)     | Cost of keeping data in interactive retention beyond the included period |
| Archive Data Retention           | Cost of data kept in archive                                             |
| Query Costs                      | Cost of queries that are billed                                          |
| Alert Rules                      | Alert rules that use the workspace                                       |
| Data Export                      | Data export rules and their cost                                         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onelens.cloud/optimize-cost-savings-and-recommendations/deep-insights/azure-monitor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
