refactor: move budget alert and cost analysis to its own tutorial

Signed-off-by: Nilushan Costa <nilushan@wso2.com>

Author: nilushancosta

docs/tutorials/component-alerts-and-incidents.mdx

@@ -413,9 +413,10 @@ Apply this step to create alert-rule trait instances for:
 - `cart` component (metric-based alert)
   - Trigger: memory usage of the cart component exceeds 70% for 2 minutes
   - Trait instance name: `cartservice-high-memory-alert`
-- `redis` component (budget-based alert)
-  - Trigger: Cost of the redis component exceeds USD 2 in 5 minutes
-  - Trait instance name: `redis-budget-alert`
+
+:::tip
+To configure a **budget-based** alert (and have the **FinOps Agent** generate an AI cost analysis report when it fires), see [Configure Budget Alert and Perform Cost Analysis using FinOps Agent](./configure-budget-alert-and-cost-analysis.mdx).
+:::
 
 Attach the alert-rule traits to existing components by appending them to spec.traits if the field already exists,
 or creating the array if it does not:
@@ -544,46 +545,6 @@ else
   ]'
 fi
 
-# redis component: budget-based alert
-if kubectl get component redis -n default \
-     -o jsonpath='{.spec.traits[*].instanceName}' 2>/dev/null \
-     | tr ' ' '\n' | grep -qx "redis-budget-alert"; then
-  echo "Trait 'redis-budget-alert' already exists on component 'redis', skipping."
-else
-  kubectl patch component redis -n default --type=json -p='[
-    {
-      "op": "add",
-      "path": "/spec/traits/-",
-      "value": {
-        "name": "observability-alert-rule",
-        "kind": "ClusterTrait",
-        "instanceName": "redis-budget-alert",
-        "parameters": {
-          "description": "Alert when redis cost for 5mins exceeds USD 2",
-          "severity": "warning",
-          "source": { "type": "budget" },
-          "condition": { "window": "5m", "interval": "1m", "operator": "gt", "threshold": 2 }
-        }
-      }
-    }
-  ]' 2>/dev/null || kubectl patch component redis -n default --type=json -p='[
-    {
-      "op": "add",
-      "path": "/spec/traits",
-      "value": [{
-        "name": "observability-alert-rule",
-        "kind": "ClusterTrait",
-        "instanceName": "redis-budget-alert",
-        "parameters": {
-          "description": "Alert when redis cost for 5mins exceeds USD 2",
-          "severity": "warning",
-          "source": { "type": "budget" },
-          "condition": { "window": "5m", "interval": "1m", "operator": "gt", "threshold": 2 }
-        }
-      }]
-    }
-  ]'
-fi
 ```
 
 #### Notification Channels Are Configured Per Environment
@@ -605,7 +566,6 @@ This step creates `ReleaseBinding`s that:
   - `frontend` component: overrides `PRODUCT_CATALOG_SERVICE_ADDR` to an invalid endpoint
   - `recommendation` component: reduces CPU requests/limits to make high CPU easier to hit
   - `cart` component: reduces memory requests/limits to make high memory easier to hit
-  - `redis` component: inflates CPU and memory requests/limits so the projected cost crosses the budget threshold in a short period of time
 - Configure alert behavior for the `development` environment via `traitEnvironmentConfigs`:
   - Enable/disable alert rules
   - Select notification channels
@@ -693,42 +653,11 @@ spec:
         memory: "150Mi"
   # Note: traitEnvironmentConfigs is omitted here.
   # Defaults: alert enabled, incident creation disabled, no AI RCA, uses environment's default notification channel
-
----
-# ReleaseBinding for redis component with oversized resource requests/limits to trigger a budget alert
-apiVersion: openchoreo.dev/v1alpha1
-kind: ReleaseBinding
-metadata:
-  name: redis-development
-  namespace: default
-spec:
-  owner:
-    projectName: gcp-microservice-demo
-    componentName: redis
-  environment: development
-  componentTypeEnvironmentConfigs:
-    resources:
-      requests:
-        cpu: "500m"
-        memory: "400Mi"
-      limits:
-        cpu: "1000m"
-        memory: "1000Mi"
-  traitEnvironmentConfigs:
-    redis-budget-alert:
-      enabled: true
-      actions:
-        notifications:
-          channels:
-            - "webhook-notification-channel-development"
-        incident:
-          enabled: true
-          triggerAiCostAnalysis: true
 EOF
 ```
 
 :::note
-`actions.incident.triggerAiRca: true` and `actions.incident.triggerAiCostAnalysis: true` both require `actions.incident.enabled: true`. `triggerAiCostAnalysis` is only valid for alerts with `source.type: budget`.
+`actions.incident.triggerAiRca: true` requires `actions.incident.enabled: true`.
 :::
 
 ### Step 6: Trigger Alerts
@@ -772,14 +701,6 @@ Also you can acknowledge and resolve incidents via the Backstage portal when the
 
 If you have properly configured the [SRE Agent](../ai/sre-agent.mdx), you can verify AI root cause analysis by checking the RCA reports in the Backstage portal when an incident is created.
 
-### Step 9: Verify Budget Alert and AI Cost Analysis
-
-Within a few minutes of applying the redis `ReleaseBinding`, the `redis-budget-alert` should fire because the inflated CPU/memory requests push the cost above the threshold.
-
-- Confirm alert delivery to the configured webhook notification channel.
-- Confirm that an incident was created for the budget alert
-- If the FinOps Agent is configured, an **AI cost analysis** report is generated for the incident — view it in the Backstage portal alongside the incident. The cost analysis report provides a cost optimization recommendation and lets you apply the recommendation automatically.
-
 ## Summary
 
 You attached OpenChoreo **observability alert rules** to existing components (as `observability-alert-rule` traits), configured **email** and **webhook** notification channels per environment, and enabled **incident creation** (plus AI root cause analysis) via `ReleaseBinding` `traitEnvironmentConfigs`.
@@ -789,6 +710,7 @@ Then you triggered the alerts using controlled misconfigurations, and verified a
 ## Next Steps
 
 - Configure and tune the [SRE Agent](../ai/sre-agent.mdx) for your observability/AI requirements.
+- Follow [Configure Budget Alert and Perform Cost Analysis using FinOps Agent](./configure-budget-alert-and-cost-analysis.mdx) to set up budget alerts and AI cost analysis.
 - Explore how to view and manage alerts/incidents via the Observer API (Backstage portal and OpenChoreo MCP server).
 - Customize webhook formatting using `payloadTemplate` for downstream systems (for example, Slack-compatible payloads).
 - Refer to [Observability Alerting](../platform-engineer-guide/observability-alerting.mdx) for how alerting architecture works in OpenChoreo.