'traces' 검색 결과

Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.

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

코드, 변경 이력, 재현 절차로 오류와 예상 밖 동작의 원인을 조사합니다. 가설 검증 후 최소한으로 수정하고 회귀 테스트와 증거를 담은 보고서까지 남깁니다.

• 오류와 스택 추적의 원인 조사
• 최근 변경으로 생긴 버그 추적
• 수정 검증과 회귀 테스트 기록

Caveman Cloud의 비용, 응답 시간, 오류를 읽기 전용으로 조사합니다. 집계와 개별 실행 기록을 대조해 지출 내역과 개선 여지를 근거와 함께 정리합니다.

• LLM 비용을 높이는 처리 파악
• 응답 지연과 오류 조사
• 실측 비용과 검증된 절감액 정리

Investigate memory dumps, disk records, and captured network traffic while preserving evidence. The skill guides timeline reconstruction and examination of system traces to identify suspicious activity and produce findings that others can review.

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

• Preserve evidence before starting an incident investigation
• Inspect processes and connections in memory dumps
• Build timelines from event logs and execution traces

Set up distributed tracing with Jaeger and Tempo to follow requests across services. Examine delays, service dependencies, and error propagation, with guidance on sampling, linking logs to traces, and troubleshooting missing trace data.

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

• Investigating slow requests across services
• Understanding service dependencies
• Tracing how errors spread

Prepare an evaluation framework before fine-tuning a language model. Build labeled examples, checks for each failure type, and a base-model benchmark, while calibrating model-based judges against human labels to support comparisons after training.

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

• Build an evaluation set from agent traces
• Create separate checks for each failure type
• Calibrate an LLM judge against human labels

Investigate LLM application failures with Phoenix CLI by reviewing execution records, recording observations, and grouping mistakes into counted categories. Inspect datasets and experiments to identify which failure types deserve evaluation tests first.

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

• Investigating failures in LLM applications
• Grouping observed mistakes into failure categories
• Choosing which evaluation tests to build first

Create shareable links that open specific Arize resources, including traces, datasets, and evaluators. Use IDs from logs or exported data, with suitable time ranges, to direct teammates to the relevant view.

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

• Share a trace with teammates
• Open an Arize view from IDs in logs
• Link directly to a dataset or evaluator

Improve LLM prompts using Arize production traces, evaluation results, and human feedback. Extract current instructions, identify recurring failures, revise the prompt, and compare experiments to measure changes in output quality and catch regressions.

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

• Improve a prompt using failed production traces
• Fix responses that use the wrong output format
• Review unsupported answers in retrieval-based responses

Add Arize AX tracing to an LLM application, recording how model calls and tool executions connect. Inspect the existing code, select suitable integrations, add instrumentation, and verify that the application runs and traces reach Arize.

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

• Setting up tracing for an LLM application
• Recording tool inputs and outputs in an agent
• Adding Arize export to an existing OpenTelemetry setup

Diagnose problems in OMC or Claude Code sessions using logs, execution traces, saved state, and focused reproduction. Receive a clear account of the failure, a supported cause hypothesis, and the smallest next corrective action.

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

• Diagnosing a broken Claude Code workflow
• Investigating unexpected hook or agent behavior
• Narrowing down causes of failing tests or commands

Analyze LLM serving traces to identify GPU time usage, opportunities to run operations concurrently, and known patterns for combining operations. Produce three consistent tables from saved traces or live captures on supported servers.

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

• Identify GPU operations that dominate inference time
• Compare input processing and token generation
• Trace GPU operations back to Python code

Measure denoising latency in SGLang diffusion models and identify slow operations with profiler traces. Compare performance and output quality on the same GPUs, check existing optimizations, and gather evidence before starting low-level kernel work.

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

• Measuring diffusion denoising latency
• Ranking slow operations from profiler traces
• Checking whether existing optimizations address a bottleneck

Map attacker behaviors and indicators of compromise, or traces of an intrusion, to MITRE ATT&CK techniques. Build coverage heatmaps, compare threat groups, and identify monitoring gaps to guide detection improvements and threat intelligence reporting.

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

• Mapping attacker behaviors and intrusion traces to ATT&CK techniques
• Visualizing detection coverage with ATT&CK Navigator
• Identifying attack techniques missing from monitoring

Analyze Windows Amcache records to investigate applications, deleted executable traces, and drivers. Extract file details, compare SHA-1 hashes with malware databases, and combine records into a timeline to support incident investigations.

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

• Investigating traces of deleted executables
• Checking software installed during an incident
• Comparing file hashes with malware databases

Analyze Windows Registry files to uncover user activity, installed software, USB connections, and automatic startup entries. Organize these traces into investigation summaries and timelines to help examine suspicious activity and possible malware persistence.

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

• Investigating suspicious automatic startup entries
• Reconstructing user activity around an incident
• Checking USB device connection traces

Parse Windows Prefetch files, which store traces of program execution, to extract run counts, timestamps, and referenced files. Build execution timelines and compare findings with other forensic evidence when investigating suspicious software or tool usage.

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

• Checking whether a suspicious program ran
• Building a timeline of investigative tool findings
• Investigating compression and file transfer tool usage

Examine Windows shortcuts and Jump Lists, records of recently used files, to reconstruct user activity. Extract paths, timestamps, and device details with LECmd and JLECmd, including traces that remain after target files are deleted.

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

• Reconstructing file access and program execution timelines
• Investigating access to files that have been deleted
• Examining traces of removable media use

Investigate production issues by searching Datadog logs, querying metrics, and following request traces across services. Compare error counts across time periods, inspect surrounding logs, and manage dashboards through a command-line tool.

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

• Investigating errors in production
• Comparing error counts across time periods
• Following request traces across services

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

Automate a real browser from the terminal to navigate pages, fill forms, extract data, and investigate interface problems. Use page snapshots to identify controls, and capture screenshots or traces, records of browser activity, for review.

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

• Automate form filling and submission
• Extract information from web pages
• Investigate UI flows with screenshots and traces

Build AI features for Dart and Flutter applications with the Genkit Dart SDK. Provides code and documentation for conversational agents, reusable processing flows, prompt files, model integrations, interactive interfaces, and debugging through recorded execution traces.

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

• Adding a conversational AI agent to a Flutter app
• Building AI processing flows in Dart
• Managing prompts in separate files

Build AI applications in Python with Genkit, including conversational agents, generation workflows, streaming responses, and tool use. The skill also guides setup and debugging through traces, recorded details of model inputs, outputs, and actions.

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

• Build a chatbot that keeps conversation history
• Implement streaming responses and tool calls
• Investigate Genkit import and API errors

Add DeepEval tracing to Python AI applications so execution steps appear in Confident AI. Choose a supported integration or manual @observe instrumentation, then capture inputs, outputs, step types, tags, and metadata.

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

• Trace execution steps in a Python AI application
• Select tracing integrations for an existing framework
• Add manual tracing with @observe