Uses of Class
org.mockserver.metrics.OtelMetricsExporter

Packages that use OtelMetricsExporter
Package
Description
org.mockserver.metrics
 

  • Uses of OtelMetricsExporter in org.mockserver.metrics

    Methods in org.mockserver.metrics that return OtelMetricsExporter
    Modifier and Type
    Method
    Description
    static OtelMetricsExporter
    OtelMetricsExporter.startIfEnabled()
    Start the exporter if enabled in configuration, returning the running instance, or null if disabled or startup failed (fail-soft — telemetry must never prevent the server from running).
    static OtelMetricsExporter
    OtelMetricsExporter.startIfEnabled(Configuration configuration)
    As startIfEnabled() but preferring the values carried on the supplied Configuration instance, falling back to the static ConfigurationProperties store for each value the instance leaves unset.
    static OtelMetricsExporter
    OtelMetricsExporter.startWithReader(io.opentelemetry.sdk.metrics.export.MetricReader reader)
    Build a meter provider with the given reader and register observable instruments: One gauge per Metrics.Name (existing behaviour). JVM memory, thread, and GC gauges (same data as JvmMetricsCollector on the Prometheus side). A gauge mirroring the slow-request counter so OTLP-only consumers can observe it without a Prometheus scrape. A gauge mirroring the per-fault-type chaos-injection counter. A gauge mirroring the active service-scoped chaos count. A histogram for request-handling duration (seconds), fed from the same observation path as the Prometheus histogram. Visible for testing (a test can pass an in-memory reader instead of the OTLP periodic reader).