skills.rest
golemcloud
golemcloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

investigating-executor-performance

Run worker-executor tests with OTLP tracing and analyze trace data in Jaeger.

1.5k|207|Updated Nov 24, 2023
Search Tags:#performance#debugging#tracing#jaeger#executor#otel
One-click install
npx skills add https://github.com/golemcloud/golem --skill investigating-executor-performance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigating-executor-performance
Source: https://github.com/golemcloud/golem/tree/main/.agents/skills/investigating-executor-performance
Command: npx skills add https://github.com/golemcloud/golem --skill investigating-executor-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose slow tests and understand the performance characteristics of worker-executor interactions by enabling distributed tracing and analyzing the resulting trace data.

Core Features & Use Cases

  • Enable OTLP Tracing: Run tests with OpenTelemetry tracing configured to send data to Jaeger.
  • Analyze Traces: Use Jaeger UI and API to inspect span durations, operation distributions, and identify errors or bottlenecks.
  • Use Case: When tests are consistently running slower than expected, use this skill to pinpoint which specific executor calls or operations are taking the most time.

Quick Start

Start the monitoring stack and then run the worker-executor tests with OTLP tracing enabled.

Frequently Asked Questions about investigating-executor-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug slow worker-executor performance issues?▼

Debug slow worker-executor performance by running executor tests with OTLP tracing enabled and analyzing span durations in Jaeger to pinpoint bottlenecks in call flows.

What's the best way to trace executor call flows and profile span durations?▼

Trace executor call flows and profile span durations by enabling OpenTelemetry during test execution, sending telemetry data to Jaeger, and inspecting operation distributions via the Jaeger API.

How do I set up OTLP tracing for executor tests?▼

Set up OTLP tracing for executor tests by starting the monitoring stack with Docker Compose, configuring specific environment variables for OTLP, and running the tests to emit trace data.

Do I need Docker to analyze executor traces in Jaeger?▼

Yes, analyzing executor traces in Jaeger requires Docker and Docker Compose to deploy the monitoring stack and receive the OTLP telemetry data generated during test execution.

Why are my executor tests running slower than expected?▼

Executor tests run slow due to bottlenecks in specific calls; use this tracing approach to inspect span durations in Jaeger and identify which operations consume the most time.

Can I use Jaeger UI to identify errors in worker-executor interactions?▼

Yes, the Jaeger UI inspects span durations and operation distributions from worker-executor interactions, allowing you to identify errors and pinpoint performance bottlenecks.

Related Skills

Explore More Software Engineering Skills→
cwijayasundaracwijayasundara
3

deploy

Generate Docker Compose stacks, Dockerfiles, environment variables, and bootstrap scripts.

Community
Advanced
VictoriaMetricsVictoriaMetrics
45

victoriatraces-query

Query VictoriaTraces Jaeger-compatible HTTP API via curl for traces and dependencies.

Official
Intermediate
aRustyDevaRustyDev
1

distributed-tracing

Trace requests across microservices using OpenTelemetry with Jaeger and Tempo.

Community
Advanced
IndustrialIndustrial

distributed-tracing

Implement distributed tracing across microservices with Jaeger and Tempo.

Community
Advanced