Units of Work

If you're here, you probably want to:

  • Forecast and plan the growth of your costs with your business.

  • invest in features intelligently

  • Map costs to teams, features and customers (i.e.: customer profitability

  • Increase profits / improve margins

We need something to map to your cloud costs called Unit of Work (UOW). UOW is typically customer and product activity that drives cost.

We produce a marginal cost for these UOW, map back to customers and customer groupings to get your customer profitability. Examples of UOW that may be good proxies for customer profitability are:

  • Cost per 1M Messages

  • Cost per API Call

  • Cost per Booking

  • Cost per Report

Getting UOW data into Taloflow

Taloflow pulls the Billing info and the System State (including tagging information) automatically via an IAM role (takes 5 minutes to set up). How you send us External events and UOW has a few avenues. You can use our hooks, or you can integrate us via your normal SDKs or deployment code.

Integration Methods

Here’s a further description of the ways you can send us External events and UOW:

Method

Description

CSV File via website

You can manually post a CSV file to our S3 buckets, which we will read. We provide a web portal that makes this easy to upload. This works well if you are sending data weekly, monthly, or data periodically.

AWS Event Bus

You can post an event with the body containing a “detail” field with the fields described in the table below in JSON. This works great if you are generating your UOW metrics directly from your AWS process and your developers can implement the simple scripts necessary to make a PutEvent request to CloudWatch.

AWS SQS

We offer an SQS entry point into the profitability system if that’s more convenient for you. The body of the message is the JSON of the table below.

AWS SNS or Email (max 120 chars per email)

We can accept an email that you generate from your notification system. The body of the email contains a comma separated line of text labeled: UOW:. We recommend this for low volume UOW feeds.

API Post (max 5mb per post)

We provide you with a web interface where you can make direct post to the UOW. This means that you can make an HTTP request with the JSON/JsonArray from the table below in the body of the request.

Specialized 3rd party integrations

In the event that you would like us to take a feed directly from a 3rd party application (for example Salesforce), let us know. We can receive data this way depending on the source of the 3rd party application.

Field

Detail

Requirement

client_id

Your Client ID.

Required

cp_id

The AWS ID.

Required

categories

A comma separated array of categorical variables that can be used to pass a service code, client cluster code, etc.

Optional

If you pass multiple UOWs for the same time period then the categories should be mutually exclusive within the time period. We add up all entries to create totals for the periods.

region

A region code.

Optional

unit_name

Name of the UOW.

Required

unit_time

Timestamp for the UOW.

Required

unit_interval

One of our interval costs that provides context for the type of UOW you are passing.

Required

unit_value

Numeric (float) of unit value.

Required

Examples:

  • Count

  • WeightedCount