Beta

Reports

Every report qloudpulse draws from your AWS accounts and your Kubernetes clusters, grouped as on your start page. Every plan has all of them. Each has a page of its own here, with what it shows, the questions it answers, what it reads and what to do with the result, and each one also says, under the (i) in its top corner, where its figures come from and what they leave out.

Overview

  • Executive summary

    What AWS costs, what could be saved and what needs attention, on one page: the run rate as a month, the savings still open and those made, what AWS Health has open or coming up, and what fails the infrastructure rules. Each figure links to the report with the detail.

Cost now

The run rate: what your running resources cost in real time, refreshed every hour, at AWS list price, without waiting a day for the bill.

  • AWS run-rate cost

    What AWS costs an hour now, by account, service and environment. Compared with an hour, 8 hours, 24 hours or 7 days ago, with what went up and what went down, and a flow from account to service to resource.

  • AWS run rate by account

    Each account's hourly cost and how it moves, its share of the whole, and the services and resources inside the accounts you pick.

  • AWS run rate by service

    Which services drive the hourly cost, which accounts each one runs in, and the resources behind it.

  • AWS cost, bill and analysis

    One line for what AWS cost an hour: the bill for every day it holds whole, the run rate after that, so the latest hours are never empty.

  • Kubernetes cost pilot

    What each namespace and workload costs on your Kubernetes clusters, in AWS and on your own servers, and a month at this rate, by namespace and by cluster.

  • Kubernetes cost per namespace pilot

    What each namespace costs, and the CPU and memory its pods requested and used, over the last 12 hours.

The bill

What AWS charged, read from the billing export you connect. It arrives about a day late and can still change until the month closes.

  • AWS cost from the bill

    The settled bill per day, with discounts and the Savings Plan, the month projected from it, and the cost by service and by line item type.

  • AWS cost per day, bill and analysis

    What AWS cost per day: the bill for each day it holds whole, the run rate after that.

  • Run rate vs bill

    How far the run rate is from what the bill charged, per day, by service and by resource, so you know how far to trust the hourly figure.

  • Run rate vs bill, per hour

    What each hour's run rate said against what the bill charged for that hour, by account, service and resource.

  • Projected month vs AWS forecast

    What AWS says this month will cost against qloudpulse's own projection, the gap between them over time, and AWS's range for each account.

  • Every cloud's bill

    Your Azure, Google Cloud and Oracle Cloud bills beside AWS's, day by day, uploaded as FOCUS files, in the currency each was billed in.

What to change

  • AWS savings recommendations

    Changes that would cut the bill, priced per month, largest first, and what the changes made so far save. Each says what to do and what to watch out for, and where one command does it, gives you the command. You run it: qloudpulse changes nothing.

  • AWS waste

    Money paid for what is not used, sorted by how easily it goes: unused, overprovisioned or stranded, by category and by service.

  • AWS infrastructure findings

    Unattached volumes, idle Elastic IPs and versions past support, by rule and by account, with the resources that fail.

  • AWS resources

    Every resource the inventory found, with its cost, by type and by its Environment and Team tags.

  • Other providers

    What your AWS setup could cost at Azure, at DigitalOcean or on a cluster of your own, like for like. An estimate, and it says so.

Security

  • Internet exposure

    What anyone on the internet can reach: open ports, load balancers, public buckets, and snapshots and images shared with everyone. A map from the internet to each resource, by port and by kind. These are your infrastructure's settings, not a scan of what runs inside it.

Health

  • AWS Health

    AWS's open issues, upcoming scheduled changes and notifications for every account, in one list, with what closed recently.

Sustainability

  • Carbon emissions

    What your AWS usage emits, month by month, by service, region, account and scope, as AWS's own Sustainability service estimates it, market-based and location-based, with the newest months estimated from your spend and marked as such.

Allocation and chargeback

Your AWS cost by your own tags, such as Team or CostCenter, with the costs your teams share split across them, read from the billing export you connect.

  • Cost allocation

    What each team, cost centre or project cost in a month, by your own tags, with its share of the costs your teams share, such as a shared network, a support plan or the untagged cost: the showback statement, one line per team, ready to download for finance.

  • Chargeback

    Each team's share of a month's AWS bill, its own cost and its share of the shared cost, and a statement finance can book, frozen once it is produced.

Network

From samples of the VPC flow logs in the VPCs you choose. AWS charges for the samples, in your own account.

In every report

  • Split and filter. Break the figures down by account, environment, service and resource, and pick the part you care about. The link holds the view, so a colleague sees what you see.
  • Back in time. Look back 14 days, 2 months, 90 days or 13 months, and step the whole page to any hour or day of it. A collection run that failed shows as a gap, never as a zero.
  • Take it with you. Download the page as a PDF, and its tables as CSV.
  • Straight to AWS. A ↗ beside a resource opens it in the AWS console, in the account that holds it.
  • Your own. Copy any report and change it, or build one from the same blocks, with no code. How, in the docs.

Missing a report you need? Ask for it with Suggest a feature in the product, or write to support@qloudpulse.com: what gets built next is decided by what you ask for.