'logging' 검색 결과

Build detections for fileless attacks on Windows using process activity, script logs, and endpoint monitoring. Investigate suspicious PowerShell, code injected into running processes, WMI persistence, and registry-based execution with logging guidance and detection query examples.

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

• Building detections for suspicious PowerShell activity
• Hunting for code injection into running processes
• Monitoring WMI persistence and registry-based execution

Create detection rules and investigation queries from API access logs to flag repeated identifier probing and unusual authorization responses. Helps investigate attempts to access other users’ data and review logging and rate limits.

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

• Investigating suspected unauthorized API data access
• Creating detection rules for repeated identifier probing
• Reviewing API logging and rate limits

Investigate interruptions affecting GPU and TPU workloads on GKE using maintenance labels, monitoring queries, logs, and node scheduling restrictions. The skill helps determine whether host maintenance caused a disruption and recommends workload protection measures when maintenance is confirmed or expected.

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

• Investigating unexpected GPU or TPU workload interruptions
• Checking upcoming host maintenance on GKE nodes
• Tracking maintenance interruptions with PromQL

Configure Google Cloud logs across multiple projects, either by storing them centrally or querying them together where they already reside. The skill guides routing, access permissions, and log views, and helps diagnose missing logs and permission failures.

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

• Collect logs from multiple projects in one central bucket
• Query distributed logs without copying their data
• Set log access boundaries by project or log type

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.

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

Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.

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

Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".

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

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".

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

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

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

Implements structured usage logging and audit trails for cost and session tracking. Use when adding audit trails, usage analytics, or cost tracking to a skill.

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

Implements data lineage tracking for privacy compliance including origin tracking, transformation logging, access auditing, deletion verification, and cross-system lineage graphs. Covers source-to-sink mapping, GDPR Art. 30 RoPA integration, automated lineage discovery, and breach impact scoping. Keywords: data lineage, data provenance, data flow mapping, transformation logging, deletion verification.

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

Structured logging with proper levels, context, PII handling, centralized aggregation. Use for application logging, log management integration, distributed tracing, or encountering log bloat, PII exposure, missing context errors.

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

Expert at making systems observable and debuggable. Covers structured logging, metrics collection, distributed tracing, error tracking, and alerting. Knows how to find the needle in the haystack when production breaks at 3 AM. Use when "observability, logging, metrics, tracing, monitoring, error tracking, Sentry, Datadog, OpenTelemetry, debugging production, observability, logging, metrics, tracing, monitoring, sentry, prometheus, opentelemetry" mentioned.

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

Expert guide for structured logging (Pino, Winston), error tracking (Sentry), log aggregation (Axiom, Datadog), request correlation, and GDPR-compliant log management / Panduan ahli untuk logging terstruktur (Pino, Winston), pelacakan error (Sentry), agregasi log, korelasi request, dan manajemen log sesuai GDPR.

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

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

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

Maintain AuthCrunch logging skip rules, the reusable logging directive parser, immutable Zap filters, root server logger wiring, and TLS log-output tests. Excludes host-specific access-log configuration and changes to authentication decisions.

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

Applies best practices for logging (zerolog/zap), project structure (cmd/internal/pkg), middleware registration order, and environment configuration in Go Fiber v2/v3 applications.

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

Hunts malicious PowerShell using script-block (EID 4104) and module logging: scoring encoded commands, download cradles, AMSI/logging bypass, and in-memory execution, then decoding payloads for triage. Activates for requests to hunt malicious PowerShell, analyze script-block logs, or detect encoded command abuse.

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

Configures GKE observability, including Cloud Logging, Cloud Monitoring, and managed Prometheus. Use when configuring GKE monitoring, setting up GKE logging, or configuring Prometheus metrics collection. Don't use to configure local application logging frameworks or external APMs outside GKE.

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

Configure single-project Google Cloud Logging: regional log buckets, log sinks, log views, restricting or hiding sensitive logs in the default view (_Default) filter, IAM permissions for views (Logs View Accessor, IAM conditions), logs-based metrics, log exclusions, and sampling. Don't use for cross-project logging or multi-project setups.

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

Generates Logging Query Language (LQL) queries for Google Cloud Logging from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google Cloud service. Don't use this skill to query other databases, such as SQL or Cloud Spanner.

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

Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.

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

Use when working with Gcp Cloud Logging — google Cloud Logging log analysis, log-based metrics, sink management, exclusion filters, and log routing configuration via gcloud CLI.

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

Enforces consistent structured logging with request correlation IDs, standardized log schema, middleware integration, and best practices. Use for "structured logging", "log standardization", "request tracing", or "log correlation".

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