'traces' 검색 결과

Inspect existing LLM application records in Arize to investigate errors, slow operations, or behavior changes. Export traces, which group related operations, or individual operations and conversation sessions as JSON using the ax command-line tool.

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

• Investigate errors in an LLM application
• Review the inputs and outputs of a conversation
• Find slow operations in recorded traces

Configure OpenTelemetry to send AI application traces, records of execution steps, to Confident AI. Reuse existing exporters, choose the regional endpoint, and add AI-specific attributes without requiring the deepeval Python package.

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

• Send existing AI application traces to Confident AI
• Configure tracing for a non-Python AI application
• Choose the US or EU endpoint for an API key

Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.

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

• Checking a local Mastra project before release
• Testing Studio and server deployments in the cloud
• Running targeted checks for agents or traces

Investigate errors, crashes, and unexpected behavior by reproducing failures, tracing execution, and comparing logs. Tests one explanation at a time, then provides a verified fix, supporting evidence, and tests or safeguards to prevent recurrence.

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

• Investigate error messages and execution traces
• Find the cause of an application crash
• Compare logs to locate a failure

Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.

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

Collect, normalize, and structure execution traces from instrumented programs (strace, ltrace) into JSON format for downstream analysis. Use when working with system call traces, library call traces, or execution logs that need to be analyzed for debugging, test case reproduction, or verification. Supports parsing strace/ltrace output, filtering noise, extracting debug information, and preparing traces for bug analysis or reproduction workflows.

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

Honeycomb의 처리 기록으로 Paperclip 실행, 화면 표시, CI의 지연을 조사합니다. 오래 걸리는 구간을 정리하고 계측 설정과 누락된 계측 추가도 다룹니다.

• 에이전트 실행 전후의 지연 조사하기
• 작업 페이지 표시 지연 조사하기
• 전체 CI를 지연시키는 작업 찾기

Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.

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

• Investigating an agent failure
• Checking tool selection and execution order
• Investigating memory storage and recall

Capture Unreal Engine traces, export timing and counter data to CSV, and summarize expensive operations. Manage ongoing recordings, browse stored traces, and open Unreal Insights for visual inspection on Windows.

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

• Record Unreal Engine startup performance
• Find expensive operations in timing summaries
• Export counter values to CSV

Turn graded execution traces and production logs into model training examples and preferred-versus-rejected response pairs. Select useful records, remove sensitive information, exclude evaluation examples, and preserve links to the original runs.

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

• Convert high-scoring successful runs into training examples
• Use expert-corrected failures as training examples
• Pair passing and failing responses to the same task

Reconstruct Windows folder browsing activity from Shellbag registry records using SBECmd and ShellBags Explorer. Investigate traces of deleted directories, disconnected USB drives, and network shares while accounting for limits in what the records and timestamps show.

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

• Reconstructing a user's folder browsing history
• Investigating browsing traces on disconnected USB drives
• Checking access traces for deleted folders

Use Phoenix to record execution traces, detailed records of an AI application's operations, and investigate problems. Evaluate answers on datasets, compare prompts and models, and set up monitoring through a self-hosted server.

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

• Investigate AI application problems using execution traces
• Evaluate answer quality across a test dataset
• Compare prompts and models through experiments

Investigate slow or failing requests in Google Cloud using Cloud Trace. Filter traces by duration or error status, inspect spans representing individual operations, and retrieve related Cloud Logging entries to investigate bottlenecks and exceptions.

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

• Find requests exceeding a latency threshold
• Inspect operation hierarchies within a trace
• Investigate failures using related application logs

Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.

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

• Investigating an agent failure
• Checking tool selection and execution order
• Investigating memory storage and recall

Use Phoenix to record execution traces, detailed records of an AI application's operations, and investigate problems. Evaluate answers on datasets, compare prompts and models, and set up monitoring through a self-hosted server.

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

• Investigate AI application problems using execution traces
• Evaluate answer quality across a test dataset
• Compare prompts and models through experiments

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

Profile app launches and individual user flows in iOS Simulator with ETTrace. Collect traces with readable function names, identify CPU-heavy call stacks, and compare performance changes when recording conditions are consistent.

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

• Investigating slow app launches
• Finding CPU-heavy work during a specific interaction
• Comparing performance before and after a change

Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.

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

Use when you have captured session evidence — session-retro / session- observatory-live traces in .planning/patterns/, tool logs, correction records — and want to induce a reusable skill from it. Segments the traces into candidate skill units (an LLM judgment, not a deterministic parse) and decomposes each candidate into a four-part structured spec: workflow structure, execution semantics, and runtime attachments (verification, safety, rollback, state). It emits a spec object, NOT a finished SKILL.md, and hands that spec to skill-forge. It sits between skill-integration (upstream frequency detector) and skill-forge (downstream author). Backed by Agent-Trace-to-Skill Induction (arxiv 2606.06893v1). Triggers on inducing a skill from captured traces, turning a repeated pattern into a skill spec, and preparing evidence for skill-forge.

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

Evolve SKILL.md files from agent execution traces using a three-stage pipeline: trajectory collection from observed runs, parallel multi-agent patch proposal for error and success analysis, and conflict-free consolidation of overlapping edits via prevalence-weighting. Based on the Trace2Skill methodology.

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

VictoriaTraces provider for obz. Covers trace search, trace retrieval by ID, and extension commands for service and operation discovery via the Jaeger-compatible HTTP API. This skill should be used when the user mentions "VictoriaTraces", "obz trace -p vt", or needs to search distributed traces from a VT backend.

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

ABSOLUTE MUST to debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/<id> or /ai-observability/sessions/<id>), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against `events.properties.$ai_input` / `$ai_output_choices` returns empty — message content lives only on the dedicated `posthog.ai_events` table.

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

Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP. Use when the user asks about service traces, slow HTTP/database spans, error spans, trace IDs, or span attributes — not AI observability traces or product logs. Uses posthog:query-apm-spans, posthog:apm-trace-get, posthog:apm-services-list, posthog:apm-attributes-list, and posthog:apm-attribute-values-list.

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

Compile your local stellar-build usage traces into sharper skills. Use when the user says "optimize my skills", "optimize-skills", "improve my skills from usage", "learn from my traces", "stellar-loop optimize", or wants the learning loop to refine installed skills based on how they've actually been used. DSPy-style prompt optimization over the local trace store at ~/.stellar-build/traces — fully local, reversible.

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