Cost Reports and Exports — Every View, and a CSV That Matches the Screen

Reporting is where discovery, billing import and metric collection stop being plumbing and become a number someone can act on. ZopNight exposes that as a set of report endpoints the interface reads, plus exports for the moments when a spreadsheet is genuinely the right tool.

The reports that exist

Close to thirty report endpoints sit under an organisation, and they are worth listing because “cost reporting” otherwise means nothing in particular:

• Summary, metrics and trends: the headline totals and their movement over a window.
• Per-resource costs: spend attributed down to the individual resource, not just the service.
• Provider summary: the split across the clouds and data platforms you have connected.
• Kubernetes breakdowns: cost by cluster, by workload, and a cluster-level report, because a node bill tells you nothing about which team caused it.
• Resource metrics and activity: the utilisation series behind a recommendation.
• Snapshots: a point-in-time record, so a later question about last month has an answer.
• Anomalies: spend that departed from its own pattern.
• Schedule success: whether the schedules you set actually ran.
• Unit economics: cost divided by a business number you supply.
• Team and tag showback: spend and trends per team and per tag key and value, down to the resources behind each.
• Cost breakdown and history: the flow of spend across dimensions, and its history over time.
• AI seat licences: per-seat effectiveness for AI assistant licences.

Exports run in the background, not in your browser

An export of any real size cannot be a synchronous request; the connection dies long before the query does. Three exports are available: the cost report and the audit log, which produce CSV, and the recommendations export, which produces an Excel workbook. All three follow the same shape.

The request returns immediately. A background worker builds the file, writes it to cloud storage under a timestamped path, generates a signed URL, and emails you the link. Concurrent exports are bounded by a semaphore so a room full of people clicking Export at month end cannot exhaust the service. The download arrives with a filename carrying the date it was produced.

The detail that makes an export trustworthy

The CSV is converted into your organisation’s display currency using the same exchange-rate lookup the interface performs.

That sounds like a small thing and is not. An export that quietly ships USD while the screen shows EUR produces two numbers for the same month, and the resulting conversation is about which system is broken rather than about the bill. Resolving the rate the same way in both paths means the spreadsheet and the dashboard agree by construction.

Audit-log exports carry the filters you applied (HTTP method, resource type, success or failure, user, free-text search, and the origin of the change), so what lands in the file is what you were looking at, not the whole log.

What this does not produce

Cost-report and audit-log exports are CSV, which Excel and Google Sheets both open directly. The recommendations export is the exception: an .xlsx workbook with an Executive Summary sheet and a Recommendation Details sheet. Exports are also on demand rather than scheduled. You ask for a file and it is emailed to you, rather than one arriving every Monday.