Repository navigation
Week 5 — AlertDesk Observability and Benchmarks - #11
vanna-cloud wants to merge 3 commits into
Conversation
skodie-genkey
left a comment
skodie-genkey
left a comment
There was a problem hiding this comment.
Request changes
The logging and the benchmark script meet Week 5. RequestLoggingMiddleware logs method, path, status, and duration as JSON and leaves out headers, tokens, query strings, and bodies. scripts/benchmark.py warms up, then reports mean, median, p95, min, and max for create and list. It refuses a non-2xx response, and the writeup correctly says list latency grows because the endpoint returns every ticket.
docs/BENCHMARKS.md never records a run. Paste one real JSON summary: command, date, iteration count, and the create/list numbers.
|
|
||
| ## Baseline | ||
|
|
||
| No latency target is specified in the client brief. Capture a baseline on the |
There was a problem hiding this comment.
Week 5 asks for the baseline to be recorded here. Paste one real run: the command, date, iteration count, database size, and the emitted create/list JSON summary.
|
I've updated BENCHMARKS.md with actual benchmark results from two recorded runs (October 28 and November 3, 2026). The documentation now includes the commands, dates, iteration counts, database size, and emitted JSON summaries for ticket creation and listing. The latest update is in commit 53c4e17. Please review the changes. |
Completed the Week 5 AlertDesk observability and benchmarking work.
This PR includes: