'logs' 검색 결과

Investigate AWS production incidents using reusable CloudWatch log queries and metric calculations. Narrow affected resources, compare alarms with deployment events, and reconstruct a timeline to identify changes that may explain the symptoms.

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

• Investigate error spikes, slow responses, and memory exhaustion
• Compare alarm transitions with recent deployments
• Narrow an incident to affected services and resources

Analyze proxy, DNS, and firewall traffic logs to uncover unapproved SaaS and cloud services. Group usage by domain, compare it with approved applications, and produce a report with traffic volumes, user counts, risk scores, and remediation recommendations.

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

• Finding unapproved SaaS and cloud services
• Measuring traffic volumes and users by service
• Prioritizing services by potential data leakage risk

Investigate Active Directory authentication logs with Splunk and KQL queries to find signs of Golden Ticket attacks, which use forged Kerberos authentication tickets. Examine encryption mismatches, missing ticket requests, unusual lifetimes, and account inconsistencies.

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

• Hunting for forged tickets after credential theft
• Investigating encryption mismatches in authentication logs
• Checking for persistent access after incident response

Examine Windows endpoint logs for attempts to avoid security detection, including log clearing, altered file timestamps, injected code, and disabled protection. Correlate events to investigate suspicious behavior and develop detection rules with context for legitimate activity.

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

• Investigating cleared logs and altered file timestamps
• Checking suspected attempts to disable security tools
• Finding abuse of legitimate Windows utilities

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

Analyze Windows event logs in Splunk to investigate suspicious logins, privilege changes, persistence, and movement between computers. Build detection searches and organize endpoint activity into timelines, with findings linked to MITRE ATT&CK attack techniques.

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

• Investigating suspicious Windows logins
• Building detection searches in Splunk
• Creating incident timelines

Investigate Office 365 account compromise by reviewing audit logs, email forwarding rules, mailbox permissions, and application access grants. Produce a JSON report with risk scores and a timeline showing suspicious activity and affected mailboxes.

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

• Investigating suspicious email forwarding
• Reviewing mailbox delegation changes
• Checking suspicious application access grants

Test Qwen Code through realistic keyboard interactions in tmux, a terminal session tool. Capture readable screen snapshots at each step and produce a report documenting dialogs, commands, outcomes, and observed side effects.

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

• Testing authentication dialogs and keyboard navigation
• Checking slash command interactions
• Reviewing intermediate screens for regressions

Design systems where multiple AI agents share work, generate tool schemas that define tool inputs for Anthropic and OpenAI, and analyze execution logs. Outputs include role assignments, communication diagrams, and recommendations for addressing cost, latency, and failures.

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

• Designing agent roles for research automation
• Choosing how multiple agents coordinate work
• Generating and validating tool schemas

Turn development tickets, product requirements, or internal changelogs into release notes users can understand. Organize updates into features, improvements, and fixes, explain their benefits, and highlight changes that require users to take action.

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

• Creating release notes from development tickets
• Turning internal changelogs into user announcements
• Explaining updates that require user action

Retrieve and analyze Screenpipe recording engine and desktop app logs to investigate errors or events at a specific time. Get timestamped findings, recurring error patterns, possible causes, suggested fixes, and indications of service status.

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

• Investigate recording failures
• Check audio and transcription errors
• Trace events at a specific time

Turn plain-language requests into Cloud Logging queries for Google Cloud. Generate service-specific filters to find errors, investigate issues, or review audit logs using LQL, the language used to search these logs.

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

• Finding recent error logs
• Filtering logs for a specific Google Cloud service
• Investigating who changed or accessed a resource

Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.

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

• Launch gator to review and monitor a specific pull request
• Inspect sandbox status and runtime logs
• Restart a stalled or outdated gator agent

Run builds, tests, and other long commands in the background while continuing other work. Explains how to read new log output, check completion, send input, and stop processes using the available platform controls.

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

• Running long builds or tests in the background
• Monitoring development servers and streaming logs
• Taking over an automatically backgrounded command

Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll. Use when: the shim picks the wrong runtime, fails to load any runtime, shows unexpected .NET 3.5 Feature-on-Demand (FOD) dialogs, unexpectedly does NOT show FOD dialogs, loads both v2 and v4 into the same process causing failures, or any time someone is wondering "what is happening with .NET Framework activation?"

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

Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API. Triggers: "azure-monitor-ingestion", "LogsIngestionClient", "custom logs", "DCR", "data collection rule", "Log Analytics".

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

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".

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

Infer orthologous genes and gene families across species using OrthoFinder3 (HOG-based phylogenetic orthology), SonicParanoid2, Broccoli, ProteinOrtho, OMA / FastOMA hierarchical orthologous groups, eggNOG-mapper, JustOrthologs, and TOGA whole-genome-alignment orthology. Use when building single-copy ortholog sets for phylogenomics, classifying co-orthologs and in/out-paralogs after gene duplication, propagating functional annotation via orthology with awareness of the ortholog conjecture, distinguishing speciation from duplication via gene-tree species-tree reconciliation, computing Quest-for-Orthologs benchmark performance, or running synteny-aware ortholog detection in WGD-affected lineages.

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

Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll. Use when: the shim picks the wrong runtime, fails to load any runtime, shows unexpected .NET 3.5 Feature-on-Demand (FOD) dialogs, unexpectedly does NOT show FOD dialogs, loads both v2 and v4 into the same process causing failures, or any time someone is wondering "what is happening with .NET Framework activation?"

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

Design, audit, or implement application structured logging architecture from repository evidence. Use when a user asks whether or where to add logs, how to choose or migrate a logger, how to standardize events/fields/levels/redaction, how to add HTTP access or panic logs, or why production logs cannot answer an incident question. Do not use merely to tail platform logs or to design a full metrics, tracing, SLO, and incident-management program.

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

Infer orthologous genes and gene families across species using OrthoFinder3 (HOG-based phylogenetic orthology), SonicParanoid2, Broccoli, ProteinOrtho, OMA / FastOMA hierarchical orthologous groups, eggNOG-mapper, JustOrthologs, and TOGA whole-genome-alignment orthology. Use when building single-copy ortholog sets for phylogenomics, classifying co-orthologs and in/out-paralogs after gene duplication, propagating functional annotation via orthology with awareness of the ortholog conjecture, distinguishing speciation from duplication via gene-tree species-tree reconciliation, computing Quest-for-Orthologs benchmark performance, or running synteny-aware ortholog detection in WGD-affected lineages.

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

Internal — for Boundless team members only. Query AWS CloudWatch logs for Boundless services (provers, slasher, distributor, order stream, order generator, indexer, signal) on prod/staging environments. Use when the user asks to look at service logs, debug service behavior from log output, search logs for a request ID, or investigate errors using CloudWatch. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

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

Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.

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

Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.

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