We're excited to share some recent updates we made in August to DoiT's product portfolio. If you prefer watching a video over reading, check out our five-minute summary below.

Or if reading is more your thing, we've got you covered with a short summary of each update below the video.

Let's begin!

Update #1: Set default report configuration

Previously when building cost and usage Reports in the DoiT Console, by default your report would be configured to look at the last 7 days of consumption at a daily interval. But if you're like me and prefer to look further back in time — say over the last 3 months — or wanted to examine costs at a larger interval (ex. monthly), you'd always have to re-configure your Report.

Now, by setting a default report configuration, you won't need to repeatedly re-configure your reports.

Update #2: Infrastructure availability and uptime for your cloud services

The "Cloud incidents" page is where we display any known issues for the cloud services you use. "Known issues" are events — outages, impaired services, etc. — that impact the performance or availability of the cloud services we use.

It's useful for when you're experiencing an issue with your application and want to verify whether it's an issue on your side that you can fix (or open a ticket with DoiT to investigate). In most cases, if the issue stems from the cloud provider, there's not much you can do but wait for them to fix the issue and monitor the progress.

With our latest update, your Cloud Incidents page now displays a chart showing your infrastructure availability and uptime over time for any cloud service you use and regions you operate in.

Update #3: No-code cloud billing analysis via Zapier

Last month we released our Zapier integration, and with this month's product updates we're building on that with a brand new "Action" for analyzing your cloud billing in response to a trigger.

For instance, you may want to analyze your expenses for a particular cloud service (such as "AWS Lambda") when you find out a new team or cost center in your organization has begun using it. For this situation (and more), we released a "Query Cloud Analytics" action in Zapier!

This allows you to execute an instant analysis of your cloud billing records without the need for coding.

Watch our product release notes video (jump to the clip at the 2:06 mark] for a live example of how this works!

Update #4: Improved support ticket flow to improve P1 and P2 ticket resolution times

In case you're unfamiliar with DoiT, in addition to building products that help you manage, optimize, and control your cloud spend, we also offer zero-cost access to 180+ Senior Cloud Architects globally for any infrastructure-related issues or questions you may have.

When opening a ticket, it's important for us to collect all of the necessary information upfront to minimize any back-and-forth and help you resolve your issues fast (see our real-time support stats).

To improve this, we added prompts for several AWS and Google Cloud services when you open a P1 or P2 ticket, requesting additional information in an effort to solve your most challenging issues faster. This asks for the core set of information needed to begin debugging or researching a problem.

In initial tests, this has worked wonders. Using CloudSQL as an example, the median ticket resolution time was reduced by 12X after these prompts were introduced.

Update #5: Give unallocated costs a custom name

When performing cost allocation using Attribution Groups, any costs which aren't captured by the Attributions in your group are automatically placed in the "Unallocated" bucket.

However some customers prefer to refer to unallocated costs by a different name and have it reflected in their reports as such. Now you can edit the name of that bucket to whatever you'd like.