observability-metrics

Integrate OpenTelemetry metrics into CritterCab services for performance monitoring.

Updated Apr 21, 2026

Search Tags:#metrics #opentelemetry #performance monitoring #distributed tracing #system health

Ready to run

npx skills add https://github.com/erikshafer/CritterCab --skill observability-metrics-erikshafer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-metrics
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/observability-metrics
Command: npx skills add https://github.com/erikshafer/CritterCab --skill observability-metrics-erikshafer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires OpenTelemetry, OpenTelemetry.Instrumentation.AspNetCore, OpenTelemetry.Instrumentation.Http, OpenTelemetry.Instrumentation.Runtime, OpenTelemetry.Instrumentation.Polly, OpenTelemetry.Instrumentation.Grpc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive solution for integrating OpenTelemetry metrics into CritterCab services, enabling detailed system performance monitoring and analysis.

Core Features & Use Cases

OpenTelemetry Metrics Integration: Collects and reports metrics using OpenTelemetry, supporting counters, histograms, and gauges.
Service Performance Monitoring: Tracks message throughput, latency, and system health metrics.
Use Case: Use this Skill to monitor the performance of your ride-sharing platform, ensuring smooth operations and quick identification of potential issues.

Quick Start

Use the observability-metrics skill to enable OpenTelemetry metrics collection in your CritterCab service.

Frequently Asked Questions about observability-metrics

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

FAQPage Schema

How do I integrate OpenTelemetry metrics for system performance monitoring?▼

Integrate OpenTelemetry metrics by adding the SDK and instrumentation libraries to collect counters, histograms, and gauges for comprehensive performance monitoring. This enables detailed analysis of your service's message throughput and latency.

What is the best way to track message throughput and latency in a distributed system?▼

Tracking message throughput and latency requires OpenTelemetry instrumentation libraries to collect metrics from HTTP, gRPC, and runtime components. This approach provides detailed system health data for quick identification of operational issues.

Do I need specific OpenTelemetry instrumentation libraries to monitor ASP.NET Core services?▼

Yes, monitoring ASP.NET Core services requires the OpenTelemetry SDK and specific instrumentation libraries for AspNetCore, HTTP, Runtime, Polly, and Grpc. These dependencies enable comprehensive data collection on system health and performance.

Can I use OpenTelemetry to monitor system health metrics for a ride-sharing platform?▼

You can use OpenTelemetry to monitor system health metrics for a ride-sharing platform by collecting data on message throughput and latency. This integration ensures smooth operations by enabling quick identification of potential performance issues.

What types of OpenTelemetry metrics are supported for performance monitoring?▼

OpenTelemetry metrics supported for performance monitoring include counters, histograms, and gauges. These metric types collect comprehensive data on service performance, tracking message throughput, latency, and overall system health.

Why collect distributed tracing data alongside system health metrics?▼

Collecting distributed tracing data alongside system health metrics provides comprehensive performance monitoring by correlating latency across HTTP, gRPC, and Polly instrumentations. This integration ensures quick identification of potential service issues.