Engineering
featbit-opentelemetry avatar

featbit-opentelemetry

Expert guidance for configuring FeatBit observability via OpenTelemetry. Use for setting up metrics, logs, traces, and connecting OTEL backends like Seq, Jaeger, or Prometheus for FeatBit backend monitoring.

Introduction

This skill provides specialized assistance for integrating OpenTelemetry (OTEL) into the FeatBit platform's backend infrastructure. It is designed for DevOps engineers and system administrators tasked with maintaining high availability and observability for FeatBit's core services: the Api Service, Evaluation-Server, and Data Analytic Service. By leveraging this skill, agents can guide users through the process of enabling native OTEL instrumentation to capture vital telemetry data including CPU and memory usage, network latency, request flows, and application logs.

  • Enables comprehensive observability by configuring environment variables like ENABLE_OPENTELEMETRY and setting service-specific OTEL_SERVICE_NAME identifiers for the Api, Evaluation-Server, and Data Analytic services.

  • Supports integration with industry-standard OTEL-compatible backends including Seq for centralized logging, Jaeger for distributed tracing, and Prometheus for real-time metrics collection.

  • Provides a ready-to-run reference architecture using Docker Compose, allowing users to spin up a full telemetry stack alongside FeatBit to validate their observability pipeline.

  • Includes best practices for production deployment, such as implementing sampling rates to optimize data volume, ensuring unique service naming conventions, and correlating logs with traces to accelerate debugging cycles.

  • This skill is intended specifically for monitoring FeatBit backend infrastructure and should not be used for client-side SDK instrumentation or Azure-specific monitoring services like Application Insights.

  • Inputs expected include details about your existing monitoring stack, backend service environment configurations, and any specific performance issues or anomalies being investigated.

  • Users should follow the provided documentation to ensure consistent configuration across distributed service environments, ensuring that the gRPC collector endpoint (OTEL_EXPORTER_OTLP_ENDPOINT) is reachable from all FeatBit container instances.

  • Utilize this skill when setting up alerts for latency spikes or investigating bottlenecks in flag evaluation request paths.

Repository Stats

Stars
11
Forks
1
Open Issues
2
Language
Not provided
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 05:30 PM
View on GitHub