11건 · 관련도순
Define service reliability targets, choose measurements that reflect user experience, and calculate error budgets—the failures a target allows. Generate alert thresholds and review existing definitions for unrealistic targets, unclear metrics, and missing response policies.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Track production session spending over time by grouping costs into configurable time windows. Compare the latest window with earlier spending averages, display the increase, and optionally return a failure exit code when it exceeds a chosen percentage.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan R&D budgets with direct and indirect costs, track spending and how long funds will last, and check whether milestones remain affordable. Prepare accounting review routes for development costs, with explicit assumptions and a named finance owner.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and validate Terraform alerts for GKE using PromQL, a monitoring query language. Cover response times, errors, traffic, memory usage, and cluster health, with checks for alert timing, duplicate signals, and metric ingestion costs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research budgeting and funding operations — study budget construction, cost per participant and per insight, burn against milestones, and portfolio prioritisation by decision value. Use when costing, tracking, or ranking research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforce structured JSON logging, OpenTelemetry distributed tracing, and RED metrics across backend services. Use when adding request correlation, setting up tracing spans, defining SLO burn-rate alerts, or instrumenting middleware.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Don't die. Runway calculation, default alive vs. default dead, when to raise vs. cut, zero-based budgeting for startups. The math that keeps companies alive long enough to win. Burn rate is not just accounting - it's strategic leverage. Companies with runway have options. Companies without runway have desperation. Use when "burn rate, runway, default alive, default dead, how much money, when to raise, cutting costs, layoffs, cash management, should we hire, running out of money, bridge round, extend runway, ramen profitable, finance, runway, cash, burn, survival, fundraising, startup" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements OpenTelemetry logs/metrics/traces, SLI/SLO gates, burn-rate alerts, and APM integrations. Use when adding or validating observability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature velocity against system reliability through error budgets, migrating from arbitrary uptime goals to data-driven metrics, or implementing Site Reliability Engineering practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using Multi-Window Multi-Burn-Rate SLO alerts, memory saturation, and cluster health such as CrashLoopBackOff and Node NotReady conditions. Don't use for non-GKE compute runtimes such as standalone Compute Engine VMs or standalone Cloud Run services without GKE.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up application observability with Prometheus, Grafana, Datadog, or CloudWatch — instrument metrics endpoints, configure Golden Signal dashboards, define alert rules with burn-rate SLOs, and add structured logging
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.