Skip to content

Documentation Update: 0.6.13 #286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sg-doc-holiday wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Documentation Update: 0.6.13 #286

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
add364a
reporting-analytics: update tables.mdx
sg-doc-holiday[bot] Jan 7, 2026
3f232af
reporting-analytics: update tables.mdx
sg-doc-holiday[bot] Jan 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions reporting-analytics/tables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ OpenOps tables are fully integrated with OpenOps workflow capabilities: there ar
Tables help you perform multiple tasks, such as:
* Map **cloud resources to owners** based on tags and business units. This is an essential stage for workflows that include [human-in-the-loop](/workflow-management/human-in-the-loop/) steps. For every resource that provides cost-saving opportunities requiring human intervention, the workflow needs a way to determine who to send an approval request to.
* Log **opportunities and anomalies** in a central location, with options to approve, dismiss, mark as false positive, or snooze.
* Compile a list of unused or idle **resources to delete**.
* Compile a list of unused or idle **resources to delete**, such as Idle EBS volumes.
* Generate **spend reports** broken down by business unit, owner, or cloud service.

## Preconfigured tables
Expand All @@ -28,16 +28,17 @@ OpenOps comes with multiple [workflow templates](/workflow-management/workflow-t

This means that when you decide to create a workflow based on a template, you don't need to create the tables that your workflow uses: they're already available. If you’re using workflows from templates, make sure not to modify the structure of preconfigured tables to avoid breaking the workflows.

Let's take a look at two tables that come preconfigured and are used in many workflow templates: **Opportunities** and **Tag-owner mapping**.
Let's take a look at preconfigured tables that are used in many workflow templates, such as **Opportunities**, **Tag-owner mapping**, and **Business units**.

### Opportunities

The preconfigured **Opportunities** table is used in multiple workflow templates to track realized and unrealized savings and to provide visibility into why savings have not yet been achieved.

By default, this table has 20 fields (columns): **ID**, **Status**, **Owner**, **Estimated savings USD per month**, **Snoozed until**, **Workflow**, **Resource ID**, **Follow-up task**, **Account**, **Region**, **Service**, **Opportunity source**, **External opportunity ID**, **Opportunity type**, **Resolution notes**, **Opportunity details**, **Complexity**, **Risk**, **Creation time**, and **Last modified time**.

Here's a sample of the **Opportunities** table in an active OpenOps installation:
In each OpenOps project, the **Opportunities** table is automatically created in that project's OpenOps Tables database.

Here's a sample of the **Opportunities** table in an active OpenOps installation:
![Sample Opportunities table](/images/tables-opportunity.png)

### Tag-owner mapping
Expand All @@ -46,6 +47,10 @@ The preconfigured **Tag-owner mapping** table is used in workflow templates to r

This table has three fields: **Owner tag value**, **Owner email**, and **BU**. The latter connects it to another preconfigured table, **Business units**, which stores more details about each business unit.

### Business units

The preconfigured **Business units** table stores information about business units used in your workflows. By default, this table includes fields such as **BU name**, **BU code**, and **Notes**.

### Example of usage in a workflow template

To better understand how the two tables described above are used in real-life workflows, here's what the **Idle RDS Instances in Staging, Terraform Remediation** workflow template does with them:
Expand Down