> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/infrastructure-as-code-management/platform/workspaces/insights.md).
# Workspace Insights
Review drift and cost optimization insights for a workspace and trigger the IaCM Remediation Agent to generate a pull request with the proposed fix.
{% hint style="warning" %}
**BETA**
The Insights tab is currently **pending release**. Contact [Harness Support](mailto:support@harness.io) to request access.
{% endhint %}
Workspace resources drift from your configuration, and cloud spend accumulates in ways that are hard to track down resource by resource. The **Insights** tab consolidates both types of finding in one place: resources that have drifted from your OpenTofu or Terraform configuration, and cost optimization opportunities sourced from Cloud Cost Management. From each insight, you can trigger the [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) to generate a pull request with the proposed fix.
***
## What you will learn from this topic
* How to open the Insights tab and read its summary cards.
* The difference between open and applied insights.
* How drift insights and cost optimization insights appear.
* Which cloud providers and resource types are supported for cost recommendations.
* How to start the remediation flow with the **Apply with agent** button.
***
## Open the Insights tab
Navigate to your workspace and select the **Insights** tab. The tab opens on the **Open** insights, with a count of open and applied insights shown at the top.
* **Open:** Insights that have been detected and not yet acted on.
* **Applied:** Insights for which the remediation pipeline has run and generated a pull request. Applied means a fix has been proposed, not that your infrastructure has already changed. The pull request still needs to be reviewed, merged, and the workspace provisioned before any infrastructure changes take effect.
***
## Insight summary cards
The cards at the top of the tab change depending on whether you are viewing open or applied insights.
**Open insights:**
* **All Insights:** The total number of insights detected for the workspace.
* **Optimization opportunity:** The estimated monthly savings across all cost recommendations, with the number of recommendations that contribute to it.
* **Resources drifted:** The number of resources that have drifted from your configuration.
**Applied insights:**
* **All Insights:** The total number of applied insights.
* **Savings realized:** The estimated monthly savings across all applied cost recommendations, with the number of recommendations that have had a pull request generated. This reflects proposed savings, not savings already realized in your infrastructure.
* **Drifts reconciled:** The number of drift insights for which a remediation pull request has been generated.
***
## Insight details
Each row in the insights list represents one finding. The columns describe the resource and the recommended fix.
**Open insights columns:**
* **Resource Name:** The affected resource. For cloud resources this typically includes the account, resource ID, and resource type.
* **Recommended Action/Resource:** The suggested fix (for example, **Rightsize** or **MigrateToGraviton**) and the resource type.
* **Saving Opportunity:** The estimated monthly savings and the percentage reduction for a cost recommendation. This is empty for drift insights.
* **Monthly Spend:** The current monthly spend for the resource, when cost data is available.
**Applied insights columns:**
* **Resource Name:** The affected resource.
* **Recommended Action/Resource:** The action that was applied.
* **Applied:** The date the remediation pipeline ran and the user who triggered it.
* **Monthly Savings:** The estimated monthly savings from the applied recommendation.
* **Status:** Whether the pipeline completed successfully (**SUCCESS**) or failed (**FAILED**). A failed row also shows a **Pipeline failed. Try to apply again** prompt.
### Drift insights
When a resource drifts from your OpenTofu or Terraform configuration, it appears as a **Drift detected** row with a **Drift reconciliation** recommended action. Click **Apply with agent** to start the remediation flow. Go to [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) for the full workflow.
Go to [Drift detection](/infrastructure-as-code-management/platform/iacm-pipelines/operations-overview.md) to understand how Harness IaCM detects drift.
### Cost optimization insights
When Cloud Cost Management Integration is enabled for your workspace, the Insights tab also surfaces cost optimization recommendations sourced from Harness CCM. Each row shows the recommended action (for example, Rightsize or Shutdown), the estimated saving opportunity, and the current monthly spend. Click **View details in CCM** to open the full recommendation in the Cloud Cost Management module.
Click **Apply with agent** to act on a cost recommendation. Go to [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) for the full remediation workflow.
#### Supported recommendations
CCM cost recommendations are available for AWS and Azure resources. GCP recommendations are not supported at this time.
**AWS**
| Resource type | Recommendation | Description |
| ----------------------- | ------------------- | --------------------------------------------------------------------------------------- |
| EC2 Instance | Rightsize | Change the instance type to one that better matches actual CPU and memory utilization. |
| EC2 Instance | Migrate to Graviton | Move the instance to an AWS Graviton processor-based type for better price-performance. |
| EBS Volume | Delete | Remove an unattached or unused EBS volume to eliminate unnecessary storage costs. |
| EC2 Auto Scaling Group | Migrate to Graviton | Update the launch configuration to use Graviton-based instance types across the group. |
| RDS DB Instance | Rightsize | Change the DB instance class to one that better matches actual database workload. |
| RDS DB Instance Storage | Rightsize | Reduce allocated storage to match actual usage and lower storage costs. |
**Azure**
| Resource type | Recommendation | Description |
| --------------- | -------------- | ---------------------------------------------------------------------------------- |
| Virtual Machine | Rightsize | Change the VM size to one that better matches actual CPU and memory utilization. |
| Virtual Machine | Shutdown | Stop an idle or unused VM to eliminate compute costs while retaining the resource. |
| AKS Node Pool | Rightsize | Change the node VM size to one that better matches actual workload requirements. |
***
## Applied insights
Select the **Applied** tab to review insights that have been remediated. The Applied view shows the same resources as the Open view but with additional columns tracking the outcome.
Each row shows:
* The date and user who triggered the remediation pipeline.
* The estimated monthly savings from the applied recommendation.
* A **SUCCESS** or **FAILED** status badge.
* Links to **Execution details** and the **PR** that was created.
If the pipeline failed, the row shows **Pipeline failed. Try to apply again**. Click **Apply with agent** again to re-run the remediation pipeline for that resource.
***
## Troubleshooting
No cost optimization insights appear on the Insights tab
Verify that Cloud Cost Management Integration is enabled in the workspace **Configuration** tab. CCM Integration syncs approximately every 12 hours, so recommendations may not appear immediately after enabling the toggle. Confirm that the Harness CCM module is active on your account and that the workspace manages resources on AWS or Azure. GCP recommendations are not supported at this time.
The Apply with agent button is missing from an insight
The IaCM Remediation Agent is a beta feature that requires enablement. Contact Harness Support to request access, and confirm a default remediation pipeline is configured for the project in the IaCM Defaults. Go to [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) for setup details.
An applied insight shows a FAILED status
The row shows **Pipeline failed. Try to apply again**. Click **Execution details** to open the pipeline run and review the step logs. After resolving the issue, click **Apply with agent** again to re-run remediation for that resource.
***
## Next steps
The Insights tab gives you a single view of what needs attention in a workspace.
* Go to [IaCM Remediation Agent](/infrastructure-as-code-management/platform/workspaces/remediation-agent.md) to remediate drift and cost recommendations with the agent.
* Go to [Drift detection](/infrastructure-as-code-management/platform/iacm-pipelines/operations-overview.md) to configure drift detection.
* Go to [Cost estimation](/infrastructure-as-code-management/platform/workspaces/cost-estimation.md) to connect Cloud Cost Management to your workspace.
{% @harness-feedback/feedback %}