JMX Recorder Chrome

Purpose & User Intent: The tool records and exports JMX metrics from Java applications accessible via remote or local JVMs. Target users include Java developers, SREs, QA engineers, and performance analysts who need repeatable metric collection during load tests, incident diagnosis, or performance tuning. The tool solves the problem of instrumenting apps for metrics without code changes and provides portable data suitable for dashboards and alerts. Core Logic & Features: It connects to a JVM over JMX, queries specified MBeans, and samples defined attributes at a given interval. Required features: network connectivity config (host, port), optional authentication, a defined set of MBeans/attributes, sampling interval, and export format. Optional/advanced features: dynamic MBean discovery, filtering, percentiles, aggregation over windows, export to JSON/CSV/Prometheus, and batch runs. It does not perform application instrumentation or real-time alerting. Inputs & Outputs: Inputs include target_host (string), target_port (int), username (optional string), password (optional string), mbeans (array of objectsName patterns with attributes), interval_seconds (int), duration_seconds (optional int). Outputs: time-stamped metric rows with fields: timestamp (ISO 8601 string), mbean (string), attribute (string), value (numeric or string). Exports: JSON, CSV, Prometheus text; formatting rules described by format. Algorithms & Calculations: The core method uses periodic polling; for each sample, the attribute value is recorded with timestamp; numeric values preserve precision; if multiple samples exist, aggregates can be computed (min, max, avg, stddev) over a window when requested; export format adheres to standard schemas. Error & Edge Cases: If host unreachable or port closed, connection attempts fail with backoff; authentication failures are reported as errors; missing MBeans or attributes yield skipped rows or nulls based on mode; partial data due to timeouts should be indicated in metadata; export may fail if format is invalid. Industry/Region & Localization: Standards follow Java JMX; timestamps use ISO 8601 UTC; supports teams across regions; units are as provided by MBean attributes; no locale-specific number formatting unless requested. Assumptions & Exclusions: Assumes remote JMX is enabled and accessible; excludes instrumentation, in-app changes, or real-time alerting; not a full APM; rock solid for data capture only.