Add generic performance metrics support to Allure reports - #719
Open
formaceft-93 wants to merge 7 commits into
Open
Add generic performance metrics support to Allure reports#719formaceft-93 wants to merge 7 commits into
formaceft-93 wants to merge 7 commits into
Conversation
formaceft-93
force-pushed
the
metric-dashboard
branch
from
June 18, 2026 09:19
23fed63 to
283f20e
Compare
Allure perf metricsGenerated at:
Artifacts: allure-perf-metrics |
formaceft-93
marked this pull request as ready for review
June 19, 2026 06:42
formaceft-93
force-pushed
the
metric-dashboard
branch
from
July 2, 2026 08:13
e8803a5 to
b67f307
Compare
formaceft-93
force-pushed
the
metric-dashboard
branch
from
August 6, 2026 14:20
d1b640e to
645cb36
Compare
formaceft-93
force-pushed
the
metric-dashboard
branch
2 times, most recently
from
August 12, 2026 07:17
d994ee5 to
ed72351
Compare
formaceft-93
force-pushed
the
metric-dashboard
branch
from
August 14, 2026 14:58
ed72351 to
864d309
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The main use case of the feature is performance measurements, but the format is intentionally not tied to Allure’s own benchmark phases, so other projects can publish their own numeric metrics through perf.json.
The report now reads explicit metric samples, adapts the current allure-perf-metrics.json format, and can also flatten arbitrary numeric JSON values into metric keys. Metrics are stored separately from test results, exported to widgets/metrics.json, attached as raw input for audit/debugging, and included in report history as stable key -> value pairs for trend views.
On the UI side, Awesome gets a dedicated Metrics section with grouped summary rows, current values, deltas, trends, and a selected history metric. Dashboard gets a compact metrics widget. The internal perf writer also emits an allure.total summary metric so the default history view can show an end-to-end report generation number instead of a project-specific phase.
Example perf.json: