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

# Telemetry

In Finout, **telemetry** refers to the **data points you want to bring into the platform** to improve insights, monitoring, and cost management. Finout imports telemetry **daily**, and you can use it for things like **unit economics**, **shared cost breakdowns**, and **telemetry-based widgets**<br>

The Telemetry managment tab enables you to view and manage how telemetry data is used across Finout, providing a centralized view of all ingested telemetry. From here, you can track which telemetry is active, see its source, and quickly find specific telemetry using free-text search. This makes it easier to control which data points are used in unit economics, shared cost breakdowns, and telemetry-based widgets, ensuring your insights are accurate, relevant, and easy to maintain.

<figure><img src="https://3858159242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWqjB2puKXPDR7L86FX2e%2Fuploads%2FKNBUkHEw5i4GBMxdVs9h%2Fimage.png?alt=media&amp;token=89c5b1e7-d80f-4042-9498-1d6c9b59c6fd" alt=""><figcaption></figcaption></figure>

1. **Telemetry Status**: Choose to filter by active (default status) or inactive (result of deactivation).
2. **Telemetry Source**: Choose to filter by the source of the telemetry.
3. **Telemetry Search**: Free-text search of the telemetry table.
4. **Deactivate Telemetry**: Deactivating telemetry pauses data ingestion, but prior data remains available.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong>: This is only available for Admins.</p></div>

   1. Navigate to **Settings** > **Cost Centers**.
   2. Click ![](https://3858159242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWqjB2puKXPDR7L86FX2e%2Fuploads%2F2TS42AWLee4r5A6Lh9zW%2Fimage.png?alt=media\&token=a7a03f10-1b56-4b86-9954-73725460f5b1) and then click **Deactivate Cost Center**.<br>

      <div align="left"><figure><img src="https://3858159242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWqjB2puKXPDR7L86FX2e%2Fuploads%2FNVCo26F5wqd3QRZuzmhO%2Fimage.png?alt=media&amp;token=ae4b6e1a-30b6-48f9-899d-124cf79b6792" alt=""><figcaption></figcaption></figure></div>
   3. Click **Deactivate**.\
      The cost center is deactivated. It stays in the cost center management page as *Inactive*.
5. **Telemetry Table**: A table displaying all the telemetry that you have in Finout, with all their data.
6. **Add Telemetry** (Alpha): Add one of the following telemetry sources:
   * MegaBill View (Alpha) - Transform internal cost and usage data into telemetry.
   * S3 (Coming Soon) - Integrate telemetry data from an S3 bucket.
   * Datadog (Coming Soon) - Set up metrics from Datadog.


---

# 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.finout.io/settings/telemetry.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.
