opensearch-project / opensearch-project/.github

[GitHub Request] Archive traffic-replayer and traffic-comparator

Open
#549 6 comments 0 reactions 1 assignee View on GitHub

@peterzhuamazon is already working on this.

Since Jun 17, 2026.

github-request
Dominant language
No language data
Stars
41
Forks
74
Avg merge
3d 19h
Merged PRs (30d)
1

Description

What is the type of request?

Repository Management

Details of the request

Both the traffic-replayer and traffic-comparator repositories were added in 2023 as part of the original OpenSearch Migrations vision. Neither project really took off, though, leaving both repositories orphaned.

We have outstanding issues in both repositories asking for them to be archived, but think we will get more traction with a .github issue (since this is related to repository management).

Additional information to support your request

This is part of a broader effort by @epugh to archive orphaned repositories that are probably not worth trying to revive.

I'd also like to use this issue as a starting point for the question of whether the Build TAG should vote on archiving repositories (the way that we vote on whether or not to create a repository). My opinion is that we should, but it's not a very strongly-held opinion.

@bugmakerrrrrr, @mishail, @anirudha, @getsaurabh02, @peterzhuamazon -- what do y'all think? Should we wield the power of both life and death over repositories?

When does this request need to be completed?

No rush

Notes

Track the progress of your request here: https://github.com/orgs/opensearch-project/projects/208/views/33.
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!

Contributor guide

Open the 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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.