investigate tracking historical data

Open
  • Is something wrong?
#6 0 comments 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
Tech stack
python
Domain
performance

Research direction

No repository files, tests, or entry points are identified in the issue. Start by reviewing the linked LinkedIn performance report and then inspect the repository to determine how performance data is currently tracked. The scope and completion criteria for historical-data tracking still need to be defined.

Written by the indexing model from the issue text.

Description

see https://www.linkedin.com/posts/tarekziade_perf8-performance-report-activity-7025616439717859328-Ed5z

Dominant language
Python
Stars
24
Forks
4
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 elastic/perf8

All issues in elastic/perf8

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.