Problems / AI security and governance, medium
Every model call is written to an audit log (SIEM) that accepts 30 writes in flight.
Free to open. Runs in your browser, no sign-up.
Success ≥ 99%, p99 ≤ 5 s.
800 requests a second for 30 seconds: 100% request (reads).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls AI app.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| AI appApp service | Load balancer forwards to it.Calls Audit log (SIEM), GPU serving pool.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 500 slots · timeout 30 s |
| Audit log (SIEM)SIEM / audit log | AI app calls it.A SIEM collects logs from everywhere and correlates them to spot attacks. | 30 slots |
| GPU serving poolSelf-hosted serving pool | AI app calls it.GPU servers batch requests together; throughput rises with batch size until memory runs out. | 4000 slots |
Try it first. Open one hint at a time if you get stuck.
Audit writes a second × write time.
Look at what got through, or what was wrongly blocked: which filter is responsible for this kind of traffic?
Give the audit log more capacity.