'alert' 검색 결과

Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

OpenStack monitoring operations skill for deploying, configuring, and operating the cloud health monitoring stack. Covers Prometheus metric collection and scrape targets, Grafana dashboard provisioning and visualization, Alertmanager notification channels and routing, alerting rules for service health and resource exhaustion, service endpoint health checks, log aggregation strategies, SLA tracking with availability and response time percentiles, and capacity trend analysis from historical metrics. Use when deploying monitoring via Kolla-Ansible, configuring alert thresholds, troubleshooting blank dashboards, tuning noisy alerts, or analyzing cloud performance trends.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with a Grafana instance — search and read dashboards, run datasource queries (Prometheus, Loki, PostgreSQL, etc.), inspect alert rules and silences, post annotations, and manage folders. Use this whenever the user mentions a Grafana dashboard, panel, or alert; pastes a Grafana URL; asks "what does this dashboard show", "query this metric in Grafana", "is this alert firing", "silence this alert", or wants to create/export a dashboard — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guidance for security alert triage in Google SecOps. Use when investigating and triaging security alerts, determining false positives vs. true positives, assessing entity risk, adjusting alert severity or priority, and closing or escalating alerts and cases. Don't use for deep multi-hop incident investigations across host timelines (use secops-investigate), proactive threat hunting or retroactive IoC sweeps (use secops-hunt), or authoring new detection rules (use secops-detection-engineering).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures best-practice, high-signal alerting policies for Google Cloud Run resources (services, jobs, and worker pools) based on seasoned SRE practices. Use when analyzing, recommending, writing, or deploying Terraform PromQL alerting policies to monitor Cloud Run error rates (4xx/5xx), request latency, container instance saturation (warning/critical), container CPU/memory utilization and allocation, billable instance time, job execution status, and worker pool queue backlog. Don't use for GKE workloads (use gke-alert-configuration) or Compute Engine VMs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing, reviewing, or troubleshooting Salesforce email templates, email alerts, and declarative notification design. Triggers: 'Lightning Email Template', 'email alert', 'merge field', 'org-wide email', 'too many emails', 'mass email limit'. NOT for migrating Classic templates to Lightning — use admin/classic-email-template-migration. NOT for sending email from Apex — use apex/apex-outbound-email-patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operational guide for the NV oOS Dependabot alert triage-and-remediation loop: querying open alerts via gh api, separating stale from genuinely vulnerable lockfile entries (default-branch forensics), deciding between safe in-major override bumps, scoped overrides, or deferred major migrations (npm pack signature diffing), regenerating the 13-lockfile tree, dismissing alerts with the right reason, GitHub issue housekeeping, and triaging the known CI failure modes. Use when asked to fix dependabot alerts, close out dependabot issues, bump vulnerable npm packages, or resume a dependabot session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

気象庁の火山情報(噴火速報・噴火警報/噴火警戒レベル・火山の状況に関する解説情報)を公開JSONから取得する。火山、噴火、噴火警戒レベル、噴火速報の確認に対応。APIキー・ログイン不要。地震・津波はbosai-alert、気象警報はbosai-alertを使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates SLO-based alerts and operational dashboards with key charts, alert thresholds, and runbook links. Use for "alerting", "dashboards", "SLO", or "monitoring".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

상품, 항공권, 숙박 시설 등의 가격과 재고를 주기적으로 확인합니다. 세금과 수수료를 포함한 총액 및 환불 조건을 대조해 조건 충족 시 중복을 줄여 알립니다.

• 상품이 목표 가격까지 내리는지 감시
• 예산 내 항공권 확인
• 환불 가능한 호텔 객실의 빈방 확인

Add logs, metrics, traces that follow requests across services, and actionable alerts to production features. This skill guides signal design, request identification, response instructions, and checks that the collected data can explain failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add monitoring signals to a new production feature
• Connect logs across services and background jobs
• Review alerts and their response instructions

Create a one-page service operations guide in HTML. It organizes service details, alerts and first responses, dashboard links, procedures with copyable commands, an on-call schedule, and an incident checklist so teams can find operational instructions together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an operations guide for a service
• Documenting first responses to alerts
• Organizing deployment and rollback procedures

Create HTML slides for a hospital board or regulators, explaining patient-data risks, safeguards, responsibilities, and required approvals. The skill uses a fixed presentation template with speaker notes to organize evidence and support a clear decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Briefing a hospital board on patient-data risks
• Explaining data controls and responsibilities to regulators
• Preparing slides for a data-governance approval

Customize what claude-mem remembers by defining note categories and reusable tags through a guided conversation. Install and activate the configuration, verify it appears in startup context, and optionally set up Telegram alerts for selected notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tailor memory categories to work or study
• Define what to record and what to skip
• Receive Telegram alerts for selected notes

Check current airport delays and cancellations worldwide, including delay types, severity, average delay minutes, and the share of flights affected. Use airport-level alerts to understand disruption before a trip or review conditions across a region.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking airport disruption before departure
• Reviewing airports with severe delays
• Checking delayed-flight shares and cancellation counts

Define service reliability measurements and targets, then turn them into Prometheus monitoring rules and alerts. Calculate error budgets, the amount of failure allowed, and outline Grafana dashboards for tracking reliability and deciding when to prioritize fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting availability and response time targets
• Calculating and tracking error budgets
• Creating alerts for rapid error budget consumption

Configure Prometheus to collect and store operational metrics from infrastructure and applications. Covers collection schedules, alert rules, automatic discovery of monitored services, and troubleshooting checks to help establish and maintain monitoring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up infrastructure and application monitoring
• Configuring metric collection intervals and retention
• Designing alert rules

Investigate signs of Mimikatz credential theft using command lines, access to Windows authentication memory, file indicators, and known modules in memory. Correlate endpoint and security logs to assess suspicious alerts, document evidence, and recommend response actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating alerts about Windows authentication memory access
• Hunting for signs of credential theft
• Assessing compromise scope during incident response

Deploy decoy files and monitor changes, renames, and deletions for early signs of ransomware. This skill guides Python monitoring, email, Slack, and syslog alerts, plus simulated file operations to verify that the detection and notification pipeline works.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitoring shared drives and NAS for suspicious file changes
• Adding decoy file monitoring alongside endpoint protection
• Testing incident response with decoy file triggers

Monitor public Certificate Transparency logs, which record TLS certificates, to spot unexpected issuance and discover subdomains. Use crt.sh data to maintain a certificate inventory, check domain findings against DNS, and configure alerts for suspicious activity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitoring owned domains for unexpected certificate issuance
• Discovering subdomains and checking their DNS records
• Investigating certificates for look-alike domains

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining reliability targets for a new service
• Calculating allowed downtime and alert thresholds
• Reviewing existing reliability definitions