Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update readme #274

Merged
merged 1 commit into from
Mar 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions selfhosted/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,12 +184,13 @@ To monitor your Kubernetes Cluster, you need to run the [Ddosify eBPF Agent (Ala
|----------------------|---------------------------------------------------------------------------------------------------|
| `Hammer` | The engine responsible for executing load tests. You can add multiple hammers to scale your load testing capabilities. |
| `Hammer Manager` | Manages the engines (Hammers) involved in load testing. |
| `Backend` | Handles load test management and stores results. |
| `Backend` | Handles Kubernetes Monitoring and Performance Testing |
| `Alaz Backend` | Handles eBPF Agent (Alaz) Metrics, Traces and Logs |
| `InfluxDB` | Database that stores metrics collected during testing. |
| `Postgres` | Database that preserves load test results. |
| `RabbitMQ` | Message broker enabling communication between Hammer Manager and Hammers. |
| `SeaweedFS Object Storage` | Object storage for multipart files and test data (CSV) used in load tests. |
| `Nginx` | Reverse proxy for backend and frontend services. |
| `Nginx` | Reverse proxy for backend, alaz-backend and frontend services. |
| `Prometheus` | Collects the Kubernetes Monitoring metrics from the Backend service. |

## Telemetry Data
Expand Down
Loading