'alert' 검색 결과

Set up and troubleshoot the WizTelemetry Notification extension for KubeSphere. Configure delivery channels such as email and Slack, route alerts by labels, silence notifications for scheduled periods, and search notification history to investigate delivery problems.

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

• Configuring email or Slack alert delivery
• Routing alerts by severity or namespace
• Silencing notifications during maintenance

Investigate an alert or suspicious identifier using logs and source code. Assess attack success, measure affected data and users, test the suspected flaw locally, and produce a response plan for human review and execution.

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

• Investigating a security alert
• Measuring affected records and customers
• Checking a suspected flaw with a local proof of concept

Turns one-shot external recon into a continuous monitoring program. Covers the scheduled re-scan-and-diff loop (baseline snapshot -> interval sleep -> re-scan -> asset/finding delta -> threshold-gated webhook alert), the scan-to-scan diff engine (new/removed/changed assets by a tracked-attribute table, new/resolved findings by a stable cross-scan fingerprint), adversary CTI / chatter monitoring across six public feeds (ransomwatch, ransomware.live, HackerNews Algolia search, Reddit security-subreddit RSS, GitHub Gist code-search, public Telegram channel scraping) with a source-kind-aware severity engine (leak-site/forum/telegram/paste tiers, CRITICAL through INFO), literal/glob/regex watchlist pattern matching, full-corpus capture with retroactive rescan on new watchlist entries, infrastructure-tracking-over-time discipline (certificate-transparency, passive-DNS, port/service, and typosquat re-enumeration cadence, and what a genuine 'perimeter drift' event looks like in the diff output), a five-state finding-lifecycle state machine (open/triaged/risk_accepted/resolved/false_positive) with per-severity SLA and fingerprint-based cross-scan dedup and auto-resolve/reopen rules, the alert-fatigue trap where a lifecycle-unaware rule re-fires on an already-accepted finding, a durable retry/backoff alert-outbox pattern ('queued is not delivered'), and copy-paste bash-cron plus PowerShell-Scheduled-Task recipes for a re-scan+diff loop with the Slack-compatible webhook payload shape. Passive OSINT and analysis only -- no new active-intrusion technique. Use when setting up ongoing monitoring for a retainer or MSSP engagement, tuning alert thresholds to avoid fatigue, triaging a finding's lifecycle status, investigating adversary chatter about a brand, building a 'what changed on the perimeter since last week' report, or deciding whether a persisting finding should re-alert.

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

Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.

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

Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.

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

Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst tiering, and shift handoffs. Use when the user mentions 'SOC,' 'security operations,' 'SOC analyst,' 'alert triage workflow,' 'runbook,' 'escalation,' 'on-call,' 'SOC tiering,' 'tier 1 / tier 2,' 'MTTD,' 'MTTR,' 'alert fatigue,' 'alert tuning,' 'shift handoff,' 'SOAR,' or wants to design or improve a security operations team.

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

Use when the repository keeps its alerting in code, or a person asks for alerts outside TaskTrooper - PrometheusRule YAML, a Cloud Monitoring alert policy in Terraform, a Datadog monitor, each routed to TaskTrooper's alert ingest URL so it opens an incident here

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

Analyze production Agentforce agent behavior using session traces and Data Cloud, and manage Agent Health Monitoring (AHM) alerts. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries; creates, lists, updates, or deletes an AHM data alert on an agent metric (escalation rate, deflection, etc.); asks why an alert is not firing or wants to check whether alerts have fired (notification counts, or the per-alert Incidents view). DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use agentforce-test); uses sf agent preview for local development iteration; deploys or publishes agents.

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

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski rule of five, Veber, Oprea, CNS, lead-like, rule of three), structural alert catalogs (PAINS a/b/c, NIBR screening-deck severity, Brenk, BMS, Glaxo, Dundee, ChEMBL common alerts), ZINC-15 percentile complexity metrics (Bertz, SAscore, QED, Whitlock, Barone), chemical-group detection, Lilly demerits, and the medchem query language (MATCHRULE, HASALERT, HASPROP, HASGROUP) for filtering a library at scale. Also trigger on medchem, `import medchem as mc`, RuleFilters, NIBRFilters, CommonAlertsFilters, NamedCatalogs, QueryFilter, PAINS filtering, or structural alerts.

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

OpenClaw의 GitHub Secret Scanning 경고를 조사하고 비밀 정보를 가립니다. 댓글 삭제와 재작성, 작성자 알림, 경고 처리를 진행합니다.

• 인증 정보가 유출된 위치를 조사합니다
• Issue와 PR 본문의 비밀 정보를 가립니다
• 비밀 정보가 있는 댓글을 삭제하고 재작성합니다

영상과 음성을 VideoDB에 가져와 발화나 화면 내용으로 장면을 찾고 클립을 만듭니다. 자막과 음성 추가, 화면 비율 변환, 라이브 영상 알림 설정도 지원합니다.

• 발화나 화면 내용으로 장면 검색 및 클립 제작
• 자막·배경 음악·더빙 추가
• 영상 해상도와 화면 비율 변경

전자 의무기록에 임상 의사결정 지원을 구현합니다. 약물 상호작용, 용량 검증, 임상 점수 계산과 경고 심각도별 화면 동작 및 누락 검증 테스트를 다룹니다.

• 약물 상호작용과 알레르기 확인 구현
• 환자 정보에 따른 용량 검증
• NEWS2 등 임상 점수 구현

Create and tune Falco rules to detect possible container escapes, where a container gains access to its host. Define detection conditions, alert priorities, and output fields, then refine exceptions to reduce false positives.

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

• Writing rules for suspicious host filesystem access
• Investigating noisy container escape alerts
• Reusing detection conditions through macros and lists

Deploy decoy credentials, documents, and URLs with Canarytokens to detect suspicious access. Guides token generation, placement, alert testing, and inventory tracking, with email or webhook notifications when someone interacts with a planted token.

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

• Add intrusion alerts to shared folders
• Detect use of decoy cloud credentials
• Monitor decoy documents for signs of data theft

Set up decoy files on endpoints and shared folders to detect possible ransomware activity. Monitor modifications, deletions, and renaming with file monitoring tools, connect events to alerts, and test whether the detection and response process works.

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

• Adding ransomware warning files to shared folders
• Supplementing endpoint protection with decoy file monitoring
• Testing alerts triggered by decoy file changes

Set up decoy credentials, storage, and secrets across AWS, Azure, and GCP to detect suspicious access. Connect audit logs to security alerts, verify detection, and document permissions, resource inventories, and maintenance plans.

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

• Detecting use of leaked cloud credentials
• Monitoring suspicious access to decoy storage and secrets
• Extending on-premises deception coverage to cloud environments

Create automated workflows that add threat intelligence to suspicious IP addresses, domains, URLs, and file hashes. Combine findings from multiple services into consistent alert context and confidence scores to support analysts reviewing security alerts.

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

• Adding threat context to security alerts
• Processing indicators from phishing email submissions
• Standardizing bulk indicator lookups from threat feeds

Design a product metrics dashboard with clearly defined measures, data sources, charts, targets, and alert thresholds. The skill produces a Markdown specification that also covers dashboard layout, review schedules, and responsibilities for responding to alerts.

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

• Defining product KPIs and their calculation rules
• Reviewing whether existing metrics support decisions
• Planning dashboard charts and layout

Configure GKE logging, metrics collection, dashboards, and alerts with Cloud Logging, Cloud Monitoring, and managed Prometheus. Diagnose missing measurements, collection failures, permission errors, and alert rule problems to identify appropriate configuration changes.

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

• Setting up GKE logging and metrics collection
• Investigating missing Prometheus metrics
• Planning dashboards and alerts for cluster health

Monitor daily AWS spending by service and account, compare it with historical baselines, and send Slack alerts with cost differences and likely causes. Known planned increases are excluded, and cloud resources remain unchanged.

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

• Detecting unusual increases in daily AWS spending
• Investigating cost spikes by service and account
• Excluding planned or seasonal spending increases

Track machine learning experiments with Trackio by recording training measurements, viewing live dashboards, and flagging diagnostic events. Retrieve metrics and alerts through command-line queries, with JSON output for automated monitoring and experiment review.

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

• Recording training loss and accuracy
• Flagging loss spikes or stalled training
• Monitoring cloud training through a Space dashboard

Hunt for signs of compromise in web and application logs without an initial alert. Establish normal activity, record investigative hypotheses, check source code, and reproduce issues locally before producing incident records and a report.

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

• Hunting for compromise without an initial alert
• Tracing related activity across application logs
• Distinguishing attack attempts from successful exploitation

Set up alerting rules, configure on-call rotations, and manage incident response workflows. Integrate with PagerDuty, Opsgenie, or Grafana OnCall for alert routing and escalation. Use when implementing alerting strategies and on-call management for production systems.

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

Define monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON- entries with monitoring rules and alert configurations.

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