PromQL subset
Run rate, increase, aggregation by/without, histogram quantiles, instant queries, and range queries.
Query Prometheus-shaped metrics with PromQL, inspect labels and cardinality, and move from a spike to the responsible service and traces.

Use the query language your team knows while the data remains available to the rest of the investigation.
Run rate, increase, aggregation by/without, histogram quantiles, instant queries, and range queries.
Inspect top labels, statistical summaries, active series, and related metrics beside the chart.
Use service and time context to continue from a metric anomaly into traces, logs, and topology.
Keep metrics on the same object-storage and query plane as the other two signals.
workflow
The useful workflow explains the change instead of ending at a chart.
Start from a dashboard, PromQL query, or alert with the relevant labels and time range.
Separate the affected service, route, status, or cluster from the background traffic.
Carry the time and entity constraints into the trace and service-map surfaces.
Inspect the events tied to the failing operation without restarting the search.
proof / shipped
molesignal documents the current evaluator rather than claiming full Prometheus compatibility.
Query Prometheus-shaped metrics with PromQL, inspect labels and cardinality, and move from a spike to the responsible service and traces.