skills.rest
featbit
featbitOFFICIAL
Explore all skills by this author →
Website𝕏@RealFeatBitGitHub

featbit-opentelemetry

Collect metrics, traces, and logs from FeatBit services using OpenTelemetry.

11|1|Updated Jan 27, 2026
Search Tags:#logs#backend#metrics#observability#opentelemetry#traces
One-click install
npx skills add https://github.com/featbit/featbit-skills --skill featbit-opentelemetry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: featbit-opentelemetry
Source: https://github.com/featbit/featbit-skills/tree/main/skills/featbit-opentelemetry
Command: npx skills add https://github.com/featbit/featbit-skills --skill featbit-opentelemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FeatBit backend services require unified observability to monitor performance, troubleshoot issues, and optimize resource usage by collecting metrics, traces, and logs through OpenTelemetry.

Core Features & Use Cases

  • Instrument FeatBit Api Service, Evaluation-Server, and Data Analytic Service with OpenTelemetry to publish metrics, traces, and logs.
  • Configure backends such as Seq (logs), Jaeger (traces), and Prometheus (metrics) for centralized visibility.
  • Follow ready-to-run examples and best practices to deploy observability in production.

Quick Start

Configure ENABLE_OPENTELEMETRY, OTEL_SERVICE_NAME, and OTEL_EXPORTER_OTLP_ENDPOINT for each FeatBit service, then start the Api Service, Evaluation-Server, and Data Analytic Service to enable telemetry.

Frequently Asked Questions about featbit-opentelemetry

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

FAQPage Schema
How do I enable OpenTelemetry observability for FeatBit backend services?▼

FeatBit backend observability requires configuring ENABLE_OPENTELEMETRY, OTEL_SERVICE_NAME, and OTEL_EXPORTER_OTLP_ENDPOINT environment variables for each service before starting the Api Service, Evaluation-Server, and Data Analytic Service to collect traces, metrics, and logs.

What observability backends work with FeatBit OpenTelemetry instrumentation?▼

FeatBit OpenTelemetry instrumentation works with Seq for logs, Jaeger for traces, and Prometheus for metrics, providing centralized visibility to observe performance and diagnose issues across your backend services.

Which FeatBit services support OpenTelemetry traces, metrics, and logs collection?▼

FeatBit supports OpenTelemetry collection of metrics, traces, and logs across the Api Service, Evaluation-Server, and Data Analytic Service, requiring specific OpenTelemetry instrumentation configured in each service to publish telemetry data.

Do I need environment variables to configure OpenTelemetry for FeatBit?▼

Yes, configuring OpenTelemetry for FeatBit requires setting ENABLE_OPENTELEMETRY, OTEL_SERVICE_NAME, and OTEL_EXPORTER_OTLP_ENDPOINT environment variables for each backend service to successfully export traces, metrics, and logs.

Why use OpenTelemetry to monitor FeatBit performance and troubleshoot issues?▼

OpenTelemetry provides unified observability for FeatBit backend services, allowing you to monitor performance, troubleshoot issues, and optimize resource usage by centrally collecting metrics, traces, and logs from all services.

Related Skills

Explore More Software Engineering Skills→
elasticelastic
31

observability-edot-python-instrument

Automates EDOT telemetry instrumentation for Python services via zero-code changes.

Official
Intermediate
cedriczielcedricziel

opentelemetry-go

Instrument Go applications with OpenTelemetry for traces, metrics, and OTLP export.

Community
Advanced
BagelHoleBagelHole
46

opentelemetry

Instrument applications and infrastructure with OpenTelemetry for unified traces, metrics, and logs.

Community
Intermediate
Adam-GuerinAdam-Guerin
1

performance-engineer

Diagnose application bottlenecks using observability, profiling, and load testing techniques.

Community
Advanced