One-click install
npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-php
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-php
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/otel-php
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-php

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you correctly add or repair OpenTelemetry SDK setup and instrumentation in a confirmed PHP codebase so traces, metrics, and logs flow reliably and follow OTel best practices.

Core Features & Use Cases

  • PHP OTel instrumentation guidance for real deployments: Covers SDK setup, traces, metrics, logs, and resource attributes for Laravel, Symfony, Slim, and plain PHP.
  • Auto-instrumentation and dependency correctness: Ensures the required ext-opentelemetry C extension and the right framework auto-packages are installed and enabled.
  • Production-safe mutation workflow: Applies changes only after you review a proposed diff and explicitly confirm.
  • Async messaging patterns: Uses span Links (not parent-child) for Kafka/SQS and Laravel queue job context carry patterns.

Quick Start

Use the otel-php skill to update OTel setup for your PHP service, then ask it to audit and propose the exact code changes needed.

Frequently Asked Questions about otel-php

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

FAQPage Schema
How do I fix broken OpenTelemetry SDK setup and instrumentation in a PHP service?

To fix broken OpenTelemetry instrumentation in a PHP service, you need to correct SDK wiring and ensure the required auto-instrumentation prerequisites are met. This involves auditing code to produce correct traces, metrics, logs, and resource attributes.

Does OpenTelemetry PHP auto-instrumentation require the ext-opentelemetry C extension?

Yes, OpenTelemetry PHP auto-instrumentation requires the ext-opentelemetry C extension and the correct framework auto-packages to be installed and enabled. Ensuring these dependencies are present is critical for reliable trace and metric export.

What is the best way to handle OpenTelemetry context propagation for Laravel queue jobs?

For Laravel queue jobs and async messaging patterns like Kafka or SQS, the best way to handle context propagation is by using span Links rather than parent-child relationships. This ensures accurate distributed tracing across asynchronous boundaries.

How do I configure OpenTelemetry traces and metrics correctly for a Symfony application?

Configuring OpenTelemetry traces and metrics for Symfony requires proper framework-specific integration and manual SDK wiring. You must apply correct resource attributes and verify exported signals after deployment to ensure production-grade telemetry.

Can I safely apply OpenTelemetry code changes to a production PHP codebase?

Yes, you can safely apply OpenTelemetry code changes to production PHP by using a safe mutation workflow. This process proposes a diff for your review and requires explicit confirmation before any instrumentation or SDK setup modifications are applied.

Why are my OpenTelemetry logs not correlating with traces in my PHP application?

OpenTelemetry logs might not correlate with traces in a PHP application due to incorrect SDK setup or common lifecycle and context-propagation pitfalls. Auditing your instrumentation ensures logs, traces, and metrics flow reliably with proper correlation.