# Cost Reporting ## Overview Cost Reporting in OneLens is your command center for understanding and managing cloud spend. It gives you the clarity to see where your money is going, why it’s being spent, and how you can optimize it. With these reports, you can: * Break down your costs exactly the way you want—by service, region, account, resource, or tags. * Track spending trends over time and spot unusual changes before they become problems. * Align cloud costs with your business objectives and cost centers. * Share clear, actionable insights with your team or stakeholders. * Cost Reporting provides unified visibility across all connected cloud providers - AWS, Azure, GCP, and OCI - in one place. ## Your Cost Reporting Tools ### [**Cost Atlas**](/observe-visibility-and-insights/cost-reporting/cost-atlas.md) Quickly drill into your spending from any angle. Group and filter costs to isolate specific drivers -whether it’s a single resource, a particular region, or an entire service. ### **Persona-Wise Reports** See reports built around your role. Whether you’re driving technical efficiency, financial control, or product delivery, you get the most relevant insights without wading through unnecessary data. ### [**Dashboards**](/observe-visibility-and-insights/cost-reporting/dashboards.md) Track the metrics that matter most to you, all in one view. Dashboards give you real-time visibility by aggregating multi-cloud costs, trends, and savings progress. ### **Cost Allocation Report** Easily assign costs to the right teams, projects, or cost centers. This gives you transparency, supports chargeback or showback, and keeps everyone accountable for their part of the spend. --- # Agent Instructions: 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: ``` GET https://docs.onelens.cloud/observe-visibility-and-insights/cost-reporting.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.