Skip to main content

Composer Insights

Composer Insights actions list proprietary Insights recipes and their findings from a flow, so you can act on open issues without checking the Insights dashboard each time. For example, a weekly flow can list recipes that still have active cost findings, keep only those above a savings threshold, and pass the affected resources to the Terraform PR agent to open pull requests.

These actions run on a Cloud Intelligence node.

Before you begin​

Composer must be enabled for the accounts you query.

Required permissions​

  • Your DoiT account needs the Insights Manager permission.

Find an action​

You can list Composer recipes and findings from a flow by adding a Cloud Intelligence action node and selecting the List recipes or List recipe findings action.

  1. When adding a node, from Actions, select Cloud Intelligence. The Find Cloud Intelligence actions pane is displayed.

  2. Search for the ComposerApi service.

    Composer API actions

  3. Select the List recipes or List recipe findings action.

  4. Configure the action. You can reference values from previous nodes in the fields using the + button; see Node parameters.

    • List recipes returns a paginated list of Composer recipes. You can filter by cloud provider, severity, pillar, and whether the recipe currently has active results, and you can sort the page (for example by severity or active result count).

    • List recipe findings returns the individual findings for one recipe. Pass the recipe ID from a previous List recipes step. You can filter by account, region, resource name, and status (active, snoozed, resolved, or all). If you omit status, the action typically returns active findings only.

Example: List, filter, and get findings​

This example lists Composer recipes that currently have active results, keeps only those whose potential savings are above a threshold, then lists the findings for each remaining recipe.

  1. List recipes, optionally limited to recipes that currently have active results.

  2. Add a Filter node if you want a narrower set — for example, recipes whose potential savings are above a threshold.

  3. List recipe findings for each remaining recipe ID, keeping active findings.

Test​

Select Test to test the node.

See also​

Last updated on