Use the Analyzer API
Use the Analyzer API to discover recordings, investigate a time window, run automated JDK Mission Control rules, or inspect raw JVM events.
Forward the HTTP service to your workstation:
kubectl -n jafra-system port-forward svc/jafra-analyzer 8080:8080
Health, metrics, and status
curl http://127.0.0.1:8080/health
curl http://127.0.0.1:8080/q/health
curl http://127.0.0.1:8080/q/metrics
curl http://127.0.0.1:8080/api/v1/status
Status includes durable chunk count and stitched bytes.
Find recordings
curl 'http://127.0.0.1:8080/api/v1/recordings'
curl 'http://127.0.0.1:8080/api/v1/recordings?namespace=default'
curl 'http://127.0.0.1:8080/api/v1/recordings?namespace=default&pod=auth-cache-abc&container=auth-cache'
Queries use namespace, Pod name, and container name. Pod UID remains the durable workload-instance identity on disk.
Automated JMC report
base='http://127.0.0.1:8080/api/v1/namespaces/default/pods/auth-cache-abc/containers/auth-cache'
curl "$base/report"
curl "$base/report?filter=heap"
curl "$base/recordings/profile-3.jfr/report"
Without a recording or window, /report analyzes the latest closed
rotation. It skips the live file because JMC rules require a complete chunk
set. The response maps rule IDs to score, name, topic, and description.
Raw event summary
curl "$base/summary"
curl "$base/summary?filter=heap"
curl "$base/recordings/profile-3.jfr/summary"
/summary does not run JMC rules. It groups recorded event types and reports
counts, selected text values, and numeric min/max/average statistics.
Time windows
Both report and summary endpoints accept:
curl "$base/report?last=5m"
curl "$base/summary?last=1h"
curl "$base/report?from=2026-08-17T09:00:00Z&to=2026-08-17T09:10:00Z"
curl "$base/report?before=2026-08-17T09:10:00Z"
curl "$base/report?after=2026-08-17T09:00:00Z"
last accepts seconds, minutes, hours, or days up to seven days. Absolute
values use ISO-8601. Do not combine the last, from/to, before, and
after families. A valid window with no overlapping recording returns
404.
Time-window analysis selects every overlapping rotation and temporarily concatenates multiple stitched recordings when necessary.