ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Product Release

JMX-based observability for the gRPC microservice fleet

The microservice runtime exposes interceptor metrics and manifest metadata through JMX, surfacing operational state to Prometheus, Grafana and the customer's existing JVM monitoring stack. Server-status endpoints become Kubernetes-ready health checks.

Enterprise operations teams already monitor JVMs through JMX — Prometheus' JMX exporter, Grafana dashboards keyed off MBean attributes, JVisualVM for ad-hoc inspection. The platform's microservice fleet now publishes its operational state through the same surface, so customer operators inherit the metrics without adopting a platform-specific dashboard.

  • Interceptor metrics as MBeans. Per-method request counts, latency histograms, error rates and active-request gauges expose as MBean attributes ; Prometheus' JMX exporter scrapes them with a standard configuration.
  • Manifest metadata. Build version, commit hash, image tag and start time are available as MBean attributes for fleet inventory and drift detection.
  • Kubernetes-ready health checks. Server-status endpoints align with the Kubernetes livenessProbe and readinessProbe contracts — HTTP 200 on healthy, 503 on shutting-down or unready. Pod lifecycle hooks (terminating, restarting) integrate without custom probes.
  • Non-intrusive instrumentation. The metrics path runs on a separate JMX thread and does not contend with the gRPC request path ; observability overhead stays under 1 % of request CPU.

See the feature →

← All posts