How k-k-j123/incident-tester works
Cloud Incident Tester is a Flask service that exposes health and information endpoints alongside configurable incident simulations. A client requests an endpoint; its handler returns a JSON response and, for incident scenarios, emits logs or creates CPU load. The application loads configuration from environment variables (and an optional .env file). All runtime behavior is implemented in one source file, so the graph groups related handlers rather than implying separate modules. The repository shows no external incident-management integrations.
Main entry points: cloud_incident_tester.py Application logging
Components 11
HTTP endpoints
- Health check
cloud_incident_tester.py - Home response
cloud_incident_tester.py - Data response
cloud_incident_tester.py - Application info
cloud_incident_tester.py
Incident simulation
- Exception event
cloud_incident_tester.py - Resource spike
cloud_incident_tester.py - CPU worker
cloud_incident_tester.py - Security event
cloud_incident_tester.py
Runtime support
- Environment config
cloud_incident_tester.py - Application logging
cloud_incident_tester.py
Other components
- HTTP client
Connections 17
- HTTP client → Health check: requests
cloud_incident_tester.py - HTTP client → Home response: requests
cloud_incident_tester.py - HTTP client → Data response: requests
cloud_incident_tester.py - HTTP client → Application info: requests
cloud_incident_tester.py - HTTP client → Exception event: requests
cloud_incident_tester.py - HTTP client → Resource spike: requests
cloud_incident_tester.py - HTTP client → Security event: requests
cloud_incident_tester.py - Resource spike → CPU worker: spawns
cloud_incident_tester.py - Environment config → Home response: sets error rate
cloud_incident_tester.py - Environment config → Data response: sets error rate
cloud_incident_tester.py - Environment config → Resource spike: controls spikes
cloud_incident_tester.py - Health check → Application logging: logs request
cloud_incident_tester.py - Home response → Application logging: logs outcome
cloud_incident_tester.py - Data response → Application logging: logs outcome
cloud_incident_tester.py - Exception event → Application logging: logs exception
cloud_incident_tester.py - Resource spike → Application logging: logs activity
cloud_incident_tester.py - Security event → Application logging: logs event
cloud_incident_tester.py