diff --git a/content/tutorials/en/cost-review-guide.mdx b/content/tutorials/en/cost-review-guide.mdx new file mode 100644 index 000000000..bbccedab4 --- /dev/null +++ b/content/tutorials/en/cost-review-guide.mdx @@ -0,0 +1,92 @@ +--- +title: How to Review Your SleakOps Costs +sidebar_label: Cost Review Guide +sidebar_position: 48 +description: A practical walkthrough of the SleakOps Cost Explorer, Kubecost, and Cost Allocation Tags — how to read what you're already spending before deciding what to optimize. +tags: + - billing + - cost-analysis + - kubecost + - monitoring +--- + +import Zoom from "react-medium-image-zoom"; +import "react-medium-image-zoom/dist/styles.css"; +import { FiExternalLink } from "react-icons/fi"; + +Learn how to read your AWS spend inside SleakOps — where to look, how to drill down to the resource that's driving a cost, and what to check first when a number looks off. + +## Why Review Your Costs Regularly + +AWS spend changes as your infrastructure changes: a new environment, an autoscaled workload, a nodepool running more On-Demand nodes than expected. Checking the Cost Explorer on a regular cadence — weekly or at least once a month — lets you catch that drift while it's still a small number, instead of finding out at the end of the month. + +This guide covers **reading and interpreting** what you're already spending. If you're looking for ways to actively cut costs, see [AWS Cost Optimization Strategies](/tutorial/optimize-aws-costs) and the [Cost Optimization Strategies](/tutorial/nodepool-strategies#cost-optimization-strategies) section of the Nodepool Strategies guide. + +--- + +## The Cost Explorer (`/billing`) + +The Cost Explorer is the main place to review spend across every AWS account connected to your company. + +**Getting there** — any of these: +- Click **Go to Cost Explorer** on the cost card in the main Dashboard. +- Open the detail view of a **Cluster**, **Project**, or **Dependency** and click its **Cost Explorer** button — this opens the Cost Explorer pre-filtered to that specific resource. + +{/* TODO: screenshot - Cost Explorer dashboard, account cards + drill-down chart */} + +**Account cards** — one per AWS account (production, development, management), each showing: +- Current month cost. +- Forecast month cost (projected total for the current month based on spend so far). +- Variation versus the previous month. + +**Filters:** + +| Filter | Options | +|---|---| +| **Date range** | Last 7 days, Last 30 days, Last 90 days, This month, Last month, Last quarter, or a custom range | +| **Group by** | day, week, month | +| **Resource type** | Cluster, Environment, NodePool, Addon, ProjectEnv, Dependency | + +**Drill-down** — click a bar in the chart to go one level deeper: account → resource type → individual resource (a specific cluster, dependency, or project environment). Click **View Resources** to open the full, paginated list of resources behind the current selection, with name, date, cost, account, and resource type. + +**Exporting** — use **Export CSV** to download the resource list, or **Export PDF** to download a summary that includes the chart. + +--- + +## Going Deeper at the Cluster Level with Kubecost + +The Cost Explorer's Resource type filters stop at the SleakOps object level (cluster, project environment, dependency, etc.). To break costs down further — by Kubernetes namespace, pod, deployment, or node — install the [Kubecost](/docs/cluster/addons/kubecost) addon on the cluster. + +Once **Resource type** is set to **Cluster** and a cluster is selected, the Cost Explorer shows a Kubecost tag: +- If Kubecost is installed, the tag opens its dashboard, filtered to that cluster's cost details. +- If it isn't installed yet, the tag links to the addon installation form. + +Kubecost's own dashboard is where you'll find the `idle` cost metric — capacity you're paying for but not using — and per-namespace, per-node, and storage cost breakdowns. See the [Kubecost documentation](/docs/cluster/addons/kubecost) for how to read that dashboard. + +--- + +## Where Your Costs Come From + +The Cost Explorer tells you *how much* and *where*; these pages explain *why* a resource costs what it costs: + +- **Nodepool strategy** (Spot vs. On-Demand vs. Reserved, ARM vs. AMD) — see [Node Pools](/docs/cluster/nodepools) and the [Nodepool Strategies](/tutorial/nodepool-strategies) tutorial. +- **Workload sizing** (CPU/Memory requests, autoscaling limits) — a workload's requests are the floor of what it reserves, and drive most of its Kubecost `idle` cost when they're set higher than actual usage. See [Web Service](/docs/project/workload/webservice) configuration. +- **Cluster uptime** — if a cluster doesn't need to run 24/7, a [scheduled shutdown](/docs/cluster/shutdown-cluster) stops charging for that time window. + +--- + +## If You Don't See a Cost Breakdown + +The per-resource breakdown in the Cost Explorer depends on **Cost Allocation Tags** being active in the AWS account. SleakOps enables these automatically during onboarding, but AWS can take a few days to propagate them, and in some accounts the activation needs a manual nudge. + +If they aren't active yet, the Cost Explorer for that account only shows the account's total daily cost, with no resource-level split. If that's the case: + +1. Check for a notification titled **"CostAllocationTags are not active in your AWS root account"** — it links directly to the AWS Cost Management console. +2. Follow the link and activate the tags listed there (`Model`, `Name`, `Cluster`, `ClusterId`, `Environment`, `Dependency`). +3. The breakdown becomes available once AWS finishes propagating the tags — this isn't instant, so expect a short delay. + +--- + +## Next Step: Reducing What You Spend + +Once you know where your spend is going, [AWS Cost Optimization Strategies](/tutorial/optimize-aws-costs) and the [Nodepool Strategies](/tutorial/nodepool-strategies) tutorial walk through concrete ways to bring it down — Spot instances, right-sizing, Graviton, storage lifecycle policies, and more. diff --git a/content/tutorials/en/nodepool-strategies.mdx b/content/tutorials/en/nodepool-strategies.mdx index f9e6c8023..6ea7e6749 100644 --- a/content/tutorials/en/nodepool-strategies.mdx +++ b/content/tutorials/en/nodepool-strategies.mdx @@ -41,6 +41,8 @@ Each Project Environment is assigned to one nodepool. The assignment can be chan ## Cost Optimization Strategies +Not sure yet where your spend is actually going? Start with the [Cost Review Guide](/tutorial/cost-review-guide) to read your current costs before applying any of these strategies. + ### 1. Spot with On-Demand Fallback The most effective way to reduce compute costs is to run workloads on **Spot instances** while keeping **On-Demand as an automatic fallback**. In SleakOps, configure this by selecting both `Spot` and `On-Demand` as Node Types when creating or editing a nodepool. The system prioritizes them in this order: **Reserved → Spot → On-Demand**. diff --git a/content/tutorials/en/optimize-aws-costs.mdx b/content/tutorials/en/optimize-aws-costs.mdx index c2c7226c2..1774b6f88 100644 --- a/content/tutorials/en/optimize-aws-costs.mdx +++ b/content/tutorials/en/optimize-aws-costs.mdx @@ -15,6 +15,8 @@ import { FiExternalLink } from "react-icons/fi"; Practical techniques to reduce AWS costs without sacrificing reliability — covering compute, storage, CDN, and right-sizing strategies. +Haven't looked at where your spend is actually going yet? Start with the [Cost Review Guide](/tutorial/cost-review-guide) to read your Cost Explorer and Kubecost dashboards first. + ## 1. Spot Instances with Auto Scaling — Cut EC2 Costs Significantly Running all workloads on On-Demand EC2 instances is expensive. Moving stateless or fault-tolerant workloads to **Spot Instances** backed by an **Auto Scaling Group (ASG)** with On-Demand fallback can cut those costs substantially. diff --git a/content/tutorials/es/cost-review-guide.mdx b/content/tutorials/es/cost-review-guide.mdx new file mode 100644 index 000000000..02c60b263 --- /dev/null +++ b/content/tutorials/es/cost-review-guide.mdx @@ -0,0 +1,92 @@ +--- +title: Cómo revisar tus costos en SleakOps +sidebar_label: Guía de revisión de costos +sidebar_position: 48 +description: Un recorrido práctico por el Cost Explorer de SleakOps, Kubecost y las Cost Allocation Tags — cómo leer lo que ya estás gastando antes de decidir qué optimizar. +tags: + - billing + - cost-analysis + - kubecost + - monitoring +--- + +import Zoom from "react-medium-image-zoom"; +import "react-medium-image-zoom/dist/styles.css"; +import { FiExternalLink } from "react-icons/fi"; + +Aprendé a leer tu gasto en AWS dentro de SleakOps — dónde mirar, cómo llegar al recurso puntual que está generando un costo, y qué revisar primero cuando un número no cierra. + +## Por qué revisar tus costos regularmente + +El gasto en AWS cambia a medida que cambia tu infraestructura: un ambiente nuevo, un workload que escaló, un nodepool corriendo más nodos On-Demand de lo esperado. Revisar el Cost Explorer con una frecuencia regular — semanal o al menos una vez al mes — te permite detectar esa variación cuando todavía es un número chico, en lugar de encontrarla a fin de mes. + +Esta guía cubre **cómo leer e interpretar** lo que ya estás gastando. Si buscás formas de reducir costos activamente, mirá [Estrategias de optimización de costos en AWS](/tutorial/optimize-aws-costs) y la sección [Estrategias de optimización de costos](/tutorial/nodepool-strategies#estrategias-de-optimización-de-costos) de la guía de Estrategias de Nodepools. + +--- + +## El Cost Explorer (`/billing`) + +El Cost Explorer es el lugar central para revisar el gasto en todas las cuentas de AWS conectadas a tu empresa. + +**Cómo llegar** — cualquiera de estas opciones: +- Hacé clic en **Go to Cost Explorer** en la tarjeta de costo del Dashboard principal. +- Abrí el detalle de un **Cluster**, **Project** o **Dependency** y hacé clic en su botón **Cost Explorer** — esto abre el Cost Explorer ya filtrado a ese recurso puntual. + +{/* TODO: screenshot - Dashboard del Cost Explorer, tarjetas de cuenta + gráfico con drill-down */} + +**Tarjetas de cuenta** — una por cada cuenta de AWS (production, development, management), cada una mostrando: +- Costo del mes actual. +- Forecast del mes (proyección del total del mes según lo gastado hasta el momento). +- Variación respecto al mes anterior. + +**Filtros:** + +| Filtro | Opciones | +|---|---| +| **Rango de fechas** | Last 7 days, Last 30 days, Last 90 days, This month, Last month, Last quarter, o un rango personalizado | +| **Agrupar por** | día, semana, mes | +| **Tipo de recurso** | Cluster, Environment, NodePool, Addon, ProjectEnv, Dependency | + +**Drill-down** — hacé clic en una barra del gráfico para bajar un nivel: cuenta → tipo de recurso → recurso individual (un cluster, dependencia o ambiente de proyecto puntual). Hacé clic en **View Resources** para abrir el listado completo y paginado de recursos detrás de la selección actual, con nombre, fecha, costo, cuenta y tipo de recurso. + +**Exportar** — usá **Export CSV** para descargar el listado de recursos, o **Export PDF** para descargar un resumen que incluye el gráfico. + +--- + +## Bajando a nivel Kubernetes con Kubecost + +Los filtros de "Tipo de recurso" del Cost Explorer llegan hasta el nivel de objeto de SleakOps (cluster, ambiente de proyecto, dependencia, etc.). Para desglosar costos más allá de eso — por namespace, pod, deployment o nodo de Kubernetes — instalá el addon [Kubecost](/docs/cluster/addons/kubecost) en el cluster. + +Cuando el **Tipo de recurso** está en **Cluster** y hay un cluster seleccionado, el Cost Explorer muestra un tag de Kubecost: +- Si Kubecost ya está instalado, el tag abre su dashboard, filtrado a los detalles de costo de ese cluster. +- Si todavía no está instalado, el tag lleva al formulario de instalación del addon. + +El dashboard propio de Kubecost es donde vas a encontrar la métrica de costo `idle` — capacidad que estás pagando pero no usando — y el desglose de costos por namespace, por nodo y de storage. Mirá la [documentación de Kubecost](/docs/cluster/addons/kubecost) para saber cómo leer ese dashboard. + +--- + +## De dónde vienen tus costos + +El Cost Explorer te dice *cuánto* y *dónde*; estas páginas explican *por qué* un recurso cuesta lo que cuesta: + +- **Estrategia de nodepool** (Spot vs. On-Demand vs. Reserved, ARM vs. AMD) — mirá [Node Pools](/docs/cluster/nodepools) y el tutorial de [Estrategias de Nodepools](/tutorial/nodepool-strategies). +- **Sizing del workload** (CPU/Memory requests, límites de autoscaling) — los requests de un workload son el piso de lo que reserva, y son los que más impactan el costo `idle` en Kubecost cuando quedan configurados por encima del uso real. Mirá la configuración de [Web Service](/docs/project/workload/webservice). +- **Uptime del cluster** — si un cluster no necesita correr 24/7, un [apagado programado](/docs/cluster/shutdown-cluster) deja de generar costo durante esa ventana horaria. + +--- + +## Si no ves un desglose de costos + +El desglose por recurso del Cost Explorer depende de que las **Cost Allocation Tags** estén activas en la cuenta de AWS. SleakOps las activa automáticamente durante el onboarding, pero AWS puede tardar unos días en propagarlas, y en algunas cuentas la activación necesita un empujón manual. + +Si todavía no están activas, el Cost Explorer para esa cuenta solo va a mostrar el costo total diario de la cuenta, sin desglose por recurso. Si te pasa esto: + +1. Buscá una notificación titulada **"CostAllocationTags are not active in your AWS root account"** — lleva directo a la consola de AWS Cost Management. +2. Segui ese link y activá los tags que aparecen ahí (`Model`, `Name`, `Cluster`, `ClusterId`, `Environment`, `Dependency`). +3. El desglose queda disponible una vez que AWS termina de propagar los tags — no es instantáneo, esperá un rato. + +--- + +## Siguiente paso: reducir lo que gastás + +Una vez que sabés a dónde va tu gasto, [Estrategias de optimización de costos en AWS](/tutorial/optimize-aws-costs) y el tutorial de [Estrategias de Nodepools](/tutorial/nodepool-strategies) recorren formas concretas de bajarlo — instancias Spot, right-sizing, Graviton, políticas de ciclo de vida de storage, y más. diff --git a/content/tutorials/es/nodepool-strategies.mdx b/content/tutorials/es/nodepool-strategies.mdx index dd6dfdef2..df0302fa7 100644 --- a/content/tutorials/es/nodepool-strategies.mdx +++ b/content/tutorials/es/nodepool-strategies.mdx @@ -41,6 +41,8 @@ Cada Project Environment se asigna a un nodepool. El cambio de asignación es po ## Estrategias de Optimización de Costos +¿Todavía no sabés bien a dónde va tu gasto? Empezá por la [Guía de revisión de costos](/tutorial/cost-review-guide) para leer tus costos actuales antes de aplicar estas estrategias. + ### 1. Spot con Fallback On-Demand La forma más efectiva de reducir costos de cómputo es correr workloads en **instancias Spot** manteniendo **On-Demand como fallback automático**. En SleakOps, configurá esto seleccionando tanto `Spot` como `On-Demand` como Node Types al crear o editar un nodepool. El sistema los prioriza en este orden: **Reserved → Spot → On-Demand**. diff --git a/content/tutorials/es/optimize-aws-costs.mdx b/content/tutorials/es/optimize-aws-costs.mdx index fb38b453a..8849e73c9 100644 --- a/content/tutorials/es/optimize-aws-costs.mdx +++ b/content/tutorials/es/optimize-aws-costs.mdx @@ -15,6 +15,8 @@ import { FiExternalLink } from "react-icons/fi"; Técnicas prácticas para reducir costos en AWS sin sacrificar confiabilidad — cubriendo cómputo, almacenamiento, CDN y estrategias de right-sizing. +¿Todavía no revisaste a dónde va tu gasto? Empezá por la [Guía de revisión de costos](/tutorial/cost-review-guide) para leer tus dashboards de Cost Explorer y Kubecost primero. + ## 1. Spot Instances con Auto Scaling — Reducir Costos EC2 Significativamente Correr todos los workloads en instancias EC2 On-Demand es caro. Mover workloads sin estado o tolerantes a fallos a **Spot Instances** respaldadas por un **Auto Scaling Group (ASG)** con fallback a On-Demand puede reducir esos costos sustancialmente. diff --git a/src/data/tutorials-generated.json b/src/data/tutorials-generated.json index 0cf44ba6d..a08ef036a 100644 --- a/src/data/tutorials-generated.json +++ b/src/data/tutorials-generated.json @@ -535,6 +535,19 @@ ], "image": "/img/tutorials/nodepool-strategies/nodepool-strategies.png", "sidebar_position": 47 + }, + { + "id": "cost-review-guide", + "title": "How to Review Your SleakOps Costs", + "description": "A practical walkthrough of the SleakOps Cost Explorer, Kubecost, and Cost Allocation Tags — how to read what you're already spending before deciding what to optimize.", + "tags": [ + "billing", + "cost-analysis", + "kubecost", + "monitoring" + ], + "image": null, + "sidebar_position": 48 } ], "es": [ @@ -1073,6 +1086,19 @@ ], "image": "/img/tutorials/nodepool-strategies/nodepool-strategies.png", "sidebar_position": 47 + }, + { + "id": "cost-review-guide", + "title": "Cómo revisar tus costos en SleakOps", + "description": "Un recorrido práctico por el Cost Explorer de SleakOps, Kubecost y las Cost Allocation Tags — cómo leer lo que ya estás gastando antes de decidir qué optimizar.", + "tags": [ + "billing", + "cost-analysis", + "kubecost", + "monitoring" + ], + "image": null, + "sidebar_position": 48 } ] } \ No newline at end of file