'traces' 검색 결과

Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.

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

Designs and reviews production observability for mobile apps on every stack — Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers crash and error reporting with usable context, breadcrumbs, structured logs, traces and custom metrics, release and cohort segmentation, correlation with backend requests, alerting thresholds, sampling and cost, and what must never be collected. Use when production problems cannot be explained from the available data, when setting up crash reporting or telemetry, or when defining release health alerts.

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

Diagnoses build and runtime failures across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers pub/Dart, Gradle/AGP, Xcode/CocoaPods, Metro, KMP source sets and iOS frameworks, crashes and deep links. Use for failing builds, app launches, stack traces or /reis-mobile:debug.

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

Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.

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

Use when an agent, harness, gateway, MCP workflow, or multi-step automation claims completion and the available traces, checkpoints, approvals, tool calls, or deployment records must be judged without

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

Use when working with Chronosphere — chronosphere cloud-native observability platform for metrics, tracing, and alerting at scale. Covers PromQL-based metric queries, trace analysis, monitor management, dashboards, and control plane configuration. Use when querying Chronosphere metrics, investigating service performance, managing alerting rules, or analyzing distributed traces.

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

Turn a release or ship recap into a social pack: posts per platform where every claim traces to a facts file, clip cut-downs per aspect ratio cut with ffmpeg and checked with ffprobe, hand-off for publishing only after GO. Use for "social pack for the release", "posts and clips for this launch", "announce the release".

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

Pixel-based motion and UI change analysis from frame sequences or screenshots using computer vision and visual comparison. Use when `.transition` or visual effects are not observable via MotionEyes logs, when you only have screenshots/video, when you need regression diffs across builds, or when you need to summarize on-screen changes without instrumentation. Do not use when MotionEyes traces are available and you need precise timing/values; use `motioneyes-animation-debug` instead.

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

Attach review scores to recorded Whalesong traces and build comparison pairs — mark a session good/bad/regressed, then diff two runs deterministically. Use when evaluating agent changes, reviewing a run after the fact, or building a small eval set.

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

Capture and interpret iOS Simulator ETTrace profiles. Use when profiling launch or runtime latency, comparing traces, or finding CPU-heavy stacks.

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

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.

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

Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.

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

Use after the backend follows the model — derive E2E flow scripts from Lean golden traces, replay them against the Lean-backed dev screens and the real REST backend with Playwright, and compare observations. Also use to add a flow when a new command or screen appeared.

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

Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware payment tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence gathering.

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

Required reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons, etc.) and query analytics data (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces). Covers HogQL syntax differences from ClickHouse SQL, system table schemas (system.*), available functions, query examples, and the schema-discovery workflow.

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

Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.

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

Watch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically.

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

Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.

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

Set up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits `$ai_generation` and `$ai_evaluation` events with `$session_id` linkage to the trigger user's recording (the standard setup post the session-summary linkage PRs).

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

Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.

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

Read current Unity Console entries from a running Editor. Use during bug investigation after compile, tests, PlayMode, or dynamic code to inspect logs, warnings, errors, and stack traces.

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

Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.

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

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

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

Métricas, logs, traces, dashboards, alertas e SLO — Prometheus, Grafana, Loki, Tempo, Mimir, Zabbix, Alertmanager. Use quando o usuário disser "dashboard", "alerta", "métrica", "PromQL", "Grafana", "SLO", "golden signals", "não temos visibilidade", "monitoramento".

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