> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/features/visibility.md).

# Visibility

Learn how to break down, filter, compare, and forecast your cloud spend in Visibility.

In Visibility, you can see the cost data from your cloud accounts in one place: where your spend goes, how it changes, and where it is heading. Visibility has three tabs:

* **Explore** shows your spend over a date range. See [Explore costs](/docs/features/visibility/explore-costs.md).
* **Compare** shows two date ranges side by side. See [Compare costs](/docs/features/visibility/compare-costs.md).
* **Forecast** shows your projected spend. See [Forecast costs](/docs/features/visibility/forecast-costs.md).

To open Visibility, select **Analyze** in the top navigation, then select **Explore**, **Compare**, or **Forecast**.

{% hint style="info" %}
**Visibility is not limited to cloud spend.** If you have connected a Cost Loop, use the **Cost loops** control at the top right to add its spend to the page. The loops you select appear alongside your cloud account, on the same chart and in the same table. See [Cost Loops](/docs/features/cost-loops.md).
{% endhint %}

## Splitting Your Costs

Split your spend by a dimension to see the cost of each of its values, such as each service or each region. Use splits to find the largest parts of your spend. For example, split by Service and then by Region to see the cost of each service in each region.

Splits apply to Explore and Compare. To add a split, click **Add split**, then select a dimension. You can add up to five splits.

With more than one split, each chart series is one combination of values, such as `Amazon Elastic Compute Cloud - us-east-1`. The table below the chart acts like a pivot table showing one column for each split.

<figure><img src="https://1793025303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeLw7hj1pxE38VmG1sYVW%2Fuploads%2FhVLHSwaxwq7o6jYqbJfv%2Fvisibility-splits.gif?alt=media&amp;token=fbb75857-7873-4c51-a3eb-b80e24db238b" alt="Adding a Region split and then a Pricing Term split in Explore. The chart legend and the table update to show each combination of service, region, and pricing term."><figcaption></figcaption></figure>

## Filtering Your Costs

Use filters to keep only the costs you care about. You can filter by any dimension, including one that you do not split by. For example, filter to one service and split by Region to see where that service runs.

1. Click **Filters** at the top right.
2. Select a dimension, then select the values to keep.

When you select more than one value for a dimension, Visibility includes cost that matches any of those values. When you filter on more than one dimension, Visibility includes only cost that matches every filter.

<figure><img src="https://1793025303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeLw7hj1pxE38VmG1sYVW%2Fuploads%2FEDNekJJGYsQjbCZndCMQ%2Fvisibility-filters.gif?alt=media&amp;token=eaadb00d-f26b-4cf0-be08-a21f4727dc9b" alt="Opening the Filters drawer in Explore, selecting Pricing Term, and selecting Standard. A Pricing Term: Standard filter pill appears above the chart."><figcaption></figcaption></figure>

## Dimensions You Can Split and Filter By

Visibility uses the same dimensions as [Streams](/docs/features/coststreams.md), for both splits and filters. These are the most commonly used dimensions:

| Dimension      | What it is                                                                                      |
| -------------- | ----------------------------------------------------------------------------------------------- |
| Service        | The cloud service, such as Amazon Elastic Compute Cloud.                                        |
| Linked Account | The account in your org that the cost belongs to.                                               |
| Region         | The cloud region where the cost occurred.                                                       |
| Usage Type     | The specific usage that you were billed for.                                                    |
| Pricing Term   | How the usage was priced, such as Committed for usage that a commitment covers, or Standard.    |
| Charge Type    | The kind of charge, such as usage or a fee.                                                     |
| Instance Type  | The instance type of the resource.                                                              |
| Tags           | The tags on your resources. Each tag key is its own dimension. Select the key, then its values. |

There is much more to slice and dice by. The split menu and the **Filters** drawer have more dimensions, grouped by product, configuration, location, billing, and commitments. If your account has cost categories, they are available too.

## Keeping Tabs in Sync

With **Sync** on, your settings stay the same as you move between tabs. Sync is on by default. Its switch is at the top of the **Filters** drawer.

* **From Explore, or the Compare base state.** Your date range, granularity, splits, and filters carry over to the other tabs.
* **From Forecast.** Your granularity and filters carry over to Explore and Compare.

Turn Sync off to set up each tab separately.


---

# 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.north.cloud/docs/features/visibility.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.
