devloperdevesh / devloperdevesh/FaultPlane

[Feat/Chaos]: Build an Embedded Network Emulation & Chaos Simulator inside runtime gateway structures

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
2
Forks
1
Avg merge
14m
Merged PRs (30d)
57

Description

Problem

Evaluating low-level proxy resiliency parameters requires deploying external third-party traffic generation tools. Relying on external modules injects unpredictable latency testing metrics and restricts automated testing loops inside closed integration environments.


Proposed Solution

Build an integrated simulation layout inside a dedicated testing package internal/gateway/chaos/.

  • Implement non-blocking asynchronous routines that can programmatically inject artificial socket drops, variable latency spikes, and payload bit corruption directly into local ring buffers.
  • Expose discrete configuration variables via the gateway config daemon to execute runtime performance tests on local multi-node configurations cleanly.
  • Link the metrics output natively to the Prometheus trackers established under issue #6.

Alternatives

  • Relying on heavy external Kubernetes chaos operators, which introduce infrastructure dependencies and lack sub-millisecond network injection resolution.

Use Case

Provides deep-tech enterprise operators with an automated framework to perform rigorous reproducible evaluation and stress tests on critical code paths natively.

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.

Research direction

Start with the proposed internal/gateway/chaos/ package and inspect the gateway config daemon and the Prometheus trackers established under issue #6. The work is complete when asynchronous routines can inject socket drops, latency spikes, and payload corruption into local ring buffers, expose configuration for runtime tests, and link their metrics output to those trackers.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, prometheus
Domain
networking, observability, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.