lexigram-monitor

Observability, health checks, and metrics for the Lexigram Framework. Supports Prometheus, OpenTelemetry, structured log export, and /health endpoints that integrate with Kubernetes probes and load-balancer health checks.

Overview

lexigram-monitor provides metrics collection, distributed tracing, health checks, and alerting for Lexigram applications. It integrates with Prometheus and OpenTelemetry backends, supports composable health checks with liveness and readiness flavours, and includes decorators for instrumenting services with custom metrics and traces. All services are wired via MonitorProvider, which registers monitoring protocols with the DI container.

Full documentation: docs.lexigram.dev

Install

uv add lexigram-monitor
# Optional extras
uv add "lexigram-monitor[prometheus]"    # Prometheus + Grafana
uv add "lexigram-monitor[opentelemetry]" # OTLP / Jaeger / Zipkin

Quick Start

from lexigram import Application
from lexigram.di.module import Module, module

# Import the module from the package
from lexigram.monitor import MonitorModule

@module(imports=[MonitorModule.configure()])
class AppModule(Module):
    pass

app = Application(modules=[AppModule])
if __name__ == "__main__":
    app.run()

Module Factory Methods

Key Features

• Prometheus — Auto /metrics endpoint; request counters, histograms, gauges
• OpenTelemetry — Distributed tracing via OTLP exporter to Jaeger / Honeycomb
• Health checks — Composable checks with liveness + readiness flavours
• Cached checks — Per-check TTL to avoid thundering-herd on slow dependencies
• DB instrumentation — Automatic query timing and error tagging
• HTTP instrumentation — Outbound request tracking for lexigram-http
• Messaging instrumentation — Kafka / RabbitMQ consumer lag, publish rate
• Alerting — Configurable alert rules with tier-aware webhook delivery
• SLO Monitoring — Burn-rate evaluation with configurable suppression window
• Tiered alerts — P0 (PagerDuty) / P1 (business hours Slack) / P2 (weekly digest) routing
• Log export — Structured log export to OTLP log backend
• Grafana dashboards — Pre-built dashboard JSON in lexigram-monitor/dashboards/

SLO Monitoring

Service Level Objectives are evaluated on a configurable interval. Each SLO tracks a metric percentile against a threshold and fires alerts on budget exhaustion.

Defining an SLO

from datetime import timedelta
from lexigram.contracts.monitor import ProjectionTier
from lexigram.monitor.slo import SLO, SLOMonitor

monitor = SLOMonitor()

slo = SLO(
    name="api.p99_latency",
    metric="http.request.duration",
    percentile=0.99,
    threshold_ms=200.0,
    window=timedelta(hours=1),
    tier=ProjectionTier.P1_BUSINESS_HOURS,
    owner="team-api",
    runbook_url="https://ops.runbook/api-slo",
)
monitor.register(slo)

Recording Samples

monitor.record_sample("http.request.duration", 150.0)
monitor.record_sample("http.request.duration", 350.0)

Evaluating and Dispatching

violations = await monitor.evaluate_and_dispatch()

Violations are routed through the configured AlertDispatcherProtocol. Alerts for the same SLO are suppressed within the suppression window (default 300s) to avoid storms.

Projection Tiers

Worker Configuration

Enable periodic evaluation via config:

# application.yaml
monitor:
  slo:
    enabled: true
    evaluation_interval: 60
    suppression_window_seconds: 300

Or via environment variables:

export LEX_MONITOR__SLO__ENABLED=true
export LEX_MONITOR__SLO__EVALUATION_INTERVAL=60
export LEX_MONITOR__SLO__SUPPRESSION_WINDOW_SECONDS=300

Testing

async with Application.boot(modules=[MonitorModule.stub()]) as app:
    # your test code
    ...

Key Source Files

Config Reference