Capture historic information

Open
#263 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
observability

Research direction

The issue names no files, tests, or entry points. Start by defining which metrics must be retained, graphed, aggregated, and alerted on, then assess whether Otava fits; done requires an agreed scope and implementation plan for historic data and alerting.

Written by the indexing model from the issue text.

Description

new-visualisation

Capturing historic information is a great thing to have.
Some graphs that capture some selected and potentially aggregated metrics over time, and maybe some "alerting".
Maybe worth to leverage a tool like Otava for the statistical parts.

Dominant language
HTML
Stars
13
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarkusio/benchmarks

All issues in quarkusio/benchmarks

Similar issues

More Observability & SRE issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.