Insight details

To learn more about a specific insight and take actions, navigate to its details page.

View insight details

To view the details of a DoiT-proprietary insight, select its name from the Insights table under the Insights view. (You can also open the insight details page when viewing a resource.)

The details page displays insight metadata and a table of affected resources.

If you apply an allocation filter on the Insights view before opening an insight, the detail page is automatically scoped to your selection (including affected resources, tab counts, and cost savings metrics). This scoped view is preserved in the URL, so you can bookmark or share a link to it.

Note

For cost insights, if one or more connected Composer accounts are not yet set up for billing, a warning icon appears on the Account coverage chip in the page header. Hover over the warning icon to see more information.

Metadata

In addition to the insight's pillar, cloud provider, and insight name, the insight details also show the following metadata:

• Source: The system that generates the insight. This field always displays DoiT for DoiT-proprietary insights.

• Severity: The risk level of the insight based on its potential impact.

• Complexity: The estimated effort to resolve the issue and an estimated fix time in minutes when available.

• Potential savings: The estimated yearly cost savings across all active (non-snoozed, non-resolved) resources, converted to your organization's currency. This field is hidden when the insight is dismissed, when results are still loading, or when there are no active savings. See Cost insight financial metrics.

• Potential cost avoidance: The estimated annualized savings from actions that prevent future cost increases. See Cost insight financial metrics.

• Freed commitments: The annualized value of commitment coverage that would be freed when you act. See Cost insight financial metrics.

• Avoidable commitments: The annualized value of commitments that could be downsized or not renewed based on current usage. See Cost insight financial metrics.

Hover any metric label for a brief definition. A dash (—) means savings for that metric could not be calculated. See Dashes and $0 and Tooltips.

The four cost metrics above are hidden when no connected Composer accounts have billing data available.

When an allocation scope is active, the cost metrics reflect only the resources in the selected allocations.

Affected resources

The resource table lists all resources affected by the insight, including resources from inactive or disconnected accounts, deleted resources, and resources that haven't been scanned yet. You can sort the table by selecting a column header, filter resources by property, or select the tabs to list resources by status:

• Active: Resources with an active issue detected by the insight.

• Resolved: Resources where the issue has been resolved. Resources from inactive accounts and deleted resources also appear under this tab, displayed with a Deleted status.

• Snoozed: Resources that have been temporarily snoozed.

• All: All resources regardless of status.

The resource table includes the following fields:

• Resource name: The name of the affected resource. Select the name to open the resource details panel.

• Status: The current status of the resource (Active, Resolved, Snoozed, or Deleted). Resources that have been deleted or belong to inactive accounts display a Deleted status.

• Affected resource type: The type of cloud resource.

• Region: The cloud region where the resource is deployed.

• Detected at: The date and time when the issue was first detected.

• Resolved at: The date and time when the issue was resolved, if applicable.

• Deleted at: The date and time when the resource was deleted, if applicable. A dash (—) appears for resources that have not been deleted.

• Account: The cloud account that owns the resource.

• Tags: The number of tags associated with the resource.

• Cost savings: The estimated yearly savings for this resource, displayed in your organization's currency. See Cost insight financial metrics.

• Cost avoidance: The estimated yearly avoidable costs for this resource, displayed in your organization's currency. Select the column header to sort by this value. See Cost insight financial metrics.

• Freed commitments: The yearly freed commitment value for this resource, displayed in your organization's currency. Select the column header to sort by this value. See Cost insight financial metrics.

• Avoidable commitments: The yearly avoidable commitment value for this resource, displayed in your organization's currency. Select the column header to sort by this value. See Cost insight financial metrics.

The four cost columns above are hidden when no connected Composer accounts have billing data available.

When a resource shows a positive savings value, hover the value for an explanation of how that figure was calculated for that resource. A dash (—) means savings could not be calculated for that resource. See Tooltips.

If you have applied an allocation filter, only resources that belong to the selected allocations appear in the table. If an error occurs while loading the resources, select Retry.

Note

Resources from inactive or disconnected accounts, and deleted resources whose issue was not resolved before deletion are read-only. Their row actions and selection checkboxes are disabled because these resources can't be acted upon (for example, snoozed or assigned to a thread).

Remediation details

When remediation information is available for an insight, additional details appear below the resources table. These sections provide guidance on how to manually address the issue identified by the insight.

The following sections may appear depending on the data available for each insight:

• Manual Remediation: Step-by-step instructions for resolving the issue manually.

• Impacts to Consider During Remediation: An explanation of potential side effects or consequences that may result from applying the remediation steps.

• Important points to note: Additional considerations to keep in mind when remediating the issue.

• Reference: A link to external documentation with more information about the issue or remediation approach. The link opens in a new browser tab.

Each section only appears when the corresponding information is available for the insight. Not all insights include remediation details.

Remediation history

Remediation history is available as part of the Terraform PR agent feature. It appears after at least one remediation run has been triggered for the insight.

See Work with remediations for more information.

Take action

On the insight details page, you can take actions on the insight itself or on the resources related to it.

Note

To create threads, your DoiT plan must include Threads, your Jira or Linear integration must be connected to the platform, and you must have the Thread Manager permission.

Insight

For the insight, select Take action in the upper-right corner:

• Dismiss this Insight: Opens a dialog where you need to specify a reason and optionally add a comment to dismiss the current insight.

• Enable this Insight: Re-enables a previously dismissed insight.

• Ask an expert: Opens an expert inquiry pre-filled with details from this insight.

• Open in Composer: Opens the corresponding Composer recipe so you can adjust the recipe's rules and parameters.

• Create thread: Creates a thread to track work on this insight in Jira or Linear. If no integration is connected, you'll be prompted to connect your integration.

• Share: Share the insight to a Slack channel, a Microsoft Teams channel, or by email. The tabs you see depend on your access: the Teams tab appears only if you have the Manage Settings permission and your plan includes Microsoft Teams. If Slack isn't set up for your organization, the dialog opens on the next available tab.

  • On the Slack tab, select a channel, optionally add a note (up to 500 characters), and select Post.

  • On the Teams tab, select a channel, optionally add a note (up to 500 characters), and select Post.

  • On the Email tab, enter up to 10 recipient email addresses, optionally add a note (up to 500 characters), and select Send. Recipients must be members of your organization.

  You can also select Copy link to copy the insight URL to your clipboard.

• Remediate with Terraform PR agent: Starts a Terraform PR agent remediation run for all of the insight's active resources. See Work with remediations for details.

Resource

For a resource, select the kebab menu (⋮) at the rightmost end of the resource row:

• Snooze resource: Snoozes the resource for the current insight. You need to specify the snooze duration and provide a reason. This action does not affect other resources related to the insight, nor other insights related to this resource.

  Tip

  You can snooze a resource either from the insight details page or from the Insights tab in the Recipe builder.

  Alternatively, select multiple resources using the checkboxes, select Actions next to the filter bar, and then select Snooze resources to snooze the chosen resources.

• Ask an expert: Opens an expert inquiry pre-filled with the insight name, a link to the insight, and the name of the resource. The form also pre-fills severity as General Guidance, the cloud account of the resource, and a suggested cloud product based on the affected resource type. The cloud platform is also pre-selected when available.

• Create thread: Creates a thread for the insight from the resource row.

When the Terraform PR agent feature is enabled, you can also select multiple active resources, select Actions, then select Remediate selected resources to start a remediation run for the chosen resources. See Work with remediations for details.

Linked threads

Linked threads displays any threads that have been created for the insight. When threads exist, the count of linked threads is displayed.

For each linked thread you can view details such as the thread name, status, and the connected ITSM tool (Jira or Linear). You can also manage threads using the options in each thread's kebab menu (⋮).

If no threads have been created yet, you can select Create thread to create the first thread.