'alerting' 검색 결과

Anomaly Detection Specialist IA — Expert en détection d'anomalies (statistique, ML, séries temporelles, alerting temps réel)

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

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

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

Complete observability & reliability engineering system. Use when designing monitoring, implementing structured logging, setting up distributed tracing, building alerting systems, creating SLO/SLI frameworks, running incident response, conducting post-mortems, or auditing system reliability. Covers all three pillars (logs/metrics/traces), alert design, dashboard architecture, on-call operations, chaos engineering, and cost optimization.

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

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

Assess an application against OWASP Top 10:2025 risk categories using Strix. Get findings backed by working exploit examples, organized by category, with clear explanations of what was tested and what remains unassessed.

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

• Assessing an app against OWASP Top 10:2025
• Testing access controls across users and tenants
• Organizing proven vulnerabilities by risk category

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

Configure Fail2ban to detect port scans, repeated SSH login attempts, and suspicious web requests from server logs. Create custom detection patterns, automatically block source IP addresses, and set up notifications and longer bans for repeat offenders.

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

• Automatically blocking port scans against public servers
• Defending SSH against repeated login attempts
• Detecting suspicious paths in Nginx access logs

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

Build a recurring vulnerability scanning process with Nessus, Qualys, or OpenVAS. Prioritize findings using asset importance and known exploitation, then organize remediation deadlines, monitoring dashboards, and automatic tickets for urgent issues.

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

• Establish recurring infrastructure vulnerability scans
• Prioritize fixes using asset importance and exploitation data
• Track remediation deadlines and overdue findings

Build automated pipelines that collect threat indicators, such as malicious IP addresses and file hashes, from multiple feeds. Standardize formats, remove duplicates, assess confidence, and distribute indicators to security monitoring systems for matching and alerts.

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

• Automating threat feed ingestion
• Standardizing and deduplicating threat indicators
• Distributing indicators to multiple monitoring systems

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

Review incoming sales inquiries, classify their fit and urgency, and draft replies in the owner's voice using available meeting times. Notify the team about urgent prospects, record activity, and hold every customer reply for approval.

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

• Drafting a reply to an unanswered inquiry
• Sorting overnight inquiries for morning review
• Alerting the team to urgent prospects

Design service monitoring dashboards and improve existing alert configurations. Generate Grafana dashboard files and documentation, analyze noisy or duplicate alerts and coverage gaps, and outline how metrics, logs, and request traces fit together.

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

• Designing monitoring for a new service
• Reducing noisy and duplicate alerts
• Creating Grafana dashboards for different roles

Evaluate whether Google SecOps rules detect threats described in articles or supplied text. Generate simulated attack logs, identify coverage gaps, summarize matching rules, and create rules for uncovered threats, with user approval before adding them.

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

• Evaluate detection coverage for threats described in a blog
• Test existing rules with simulated attack logs
• Review matching rules and their alerting status

Design service monitoring with Prometheus, write PromQL queries to analyze metrics, and build Grafana dashboards. Configure actionable alerts and manage metric labels so monitoring stays useful as the volume of collected data grows.

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

• Monitor service latency, traffic, and errors
• Review PromQL queries and precomputed metrics
• Group related alerts and filter brief spikes

Set up application monitoring with structured logs, performance metrics, and traces that follow requests across services. Build dashboards and alerts, run load tests, investigate CPU and memory bottlenecks, and estimate future infrastructure capacity.

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

• Set up application dashboards and alerts
• Investigate production issues using logs, metrics, and traces
• Run load tests before traffic increases

Set up Apollo.io monitoring and observability. Use when implementing logging, metrics, tracing, and alerting for Apollo integrations. Trigger with phrases like "apollo monitoring", "apollo metrics", "apollo observability", "apollo logging", "apollo alerts".

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

Set up observability for Claude API integrations with metrics, logging, and alerting for latency, cost, errors, and token usage. Trigger with phrases like "anthropic monitoring", "claude observability", "anthropic metrics", "track claude usage", "claude dashboard".

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

Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.

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

Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.

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

Set up metrics, dashboards, distributed tracing, log aggregation, and alerting. Use when implementing observability or improving visibility into application and infrastructure health.

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

Set up and send technical status notifications through WeCom (Enterprise WeChat) webhooks. Use this skill whenever the user needs to send notifications, alerts, backup completion reports, or status updates via WeCom; when they mention 企业微信, 企微机器人, webhook, or alerting; or when a message needs to be clear, unambiguous, and technically precise rather than vague or condescending.

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

Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace schema, metric definitions with owners and alert thresholds, sampling and retention policy, and a privacy note for logged content.

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