Metrics

Metrics are exposed through observability tooling (for example Application Insights, OpenTelemetry, or Prometheus-style endpoints), not a single standalone “metrics-only” package in the v9 reference set.

Overview #

In Genocs Library, metrics usually means application and infrastructure counters surfaced through:

• HTTP endpoints such as /metrics (Prometheus-style) or /healthz, often excluded from noisy log paths—see Logging for excludePaths and related options.
• Azure Application Insights when you enable metrics in logging or monitoring integrations—see Logging (azure.enableMetrics, and similar) and Monitoring.
• OpenTelemetry pipelines where you configure tracing and metrics—see Monitoring and Distributed tracing.

There is no separate Genocs.Metrics package in the current v9.0 package reference; behavior is package-specific (for example telemetry hooks on a given integration).

What to configure #

1. Pick your observability stack (App Insights, Jaeger, Prometheus scrapers, and so on).
2. Enable the relevant sinks and flags in Genocs.Logging, Genocs.Monitoring, or related packages.
3. Use versioned package docs for exact settings—search the v9.0 index for “metrics”, “telemetry”, or “OpenTelemetry” in the package you use.

Reference documentation #

Start from Genocs Library v9.0 and open the package you have installed (for example Logging, HTTP, or persistence packages that mention tracing).

Related: Logging · Monitoring · Distributed tracing