Access logs and JSON-lines application logs, for testing log parsers, tailers, and ingestion pipelines.
Each card starts with one representative test file. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
47 test families · 136 available files · Page 1 of 3
Logs
A .NET exception whose inner exception is introduced by the ---> marker and closed by End of inner exception stack trace, wrapped in pipe-delimited log lines. Error groupers that key on the outermost message alone merge
Restaurant Costing
Daily Z-read and cash-up for Alder Table Bistro. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 896.00 less discounts 89.60 and comps 11.50 gives net sales 794.90; w
Alerts
Sixteen state transitions across four alerts, each moving inactive to pending to firing to resolved with the previous state recorded. The pending stage is where a for: duration is being served and no notification is sent
Logs
An Apache access log in the Combined Log Format: the Common fields plus referer and user-agent. A realistic web-server log for testing access-log parsers, analytics, and grok patterns.
Graphs
Cargo's tree output, which writes versions with a leading `v` and marks already-shown subtrees with `(*)`: close enough to npm's tree to fool a parser, different enough to break one. Every package, version, hash and lice
Restaurant Costing
Daily Z-read and cash-up for Cedar Street Tacos. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1197.00 less discounts 119.70 and comps 11.00 gives net sales 1066.30
Restaurant Costing
Daily Z-read and cash-up for Copper Oven Bakery. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 396.75 less discounts 39.68 and comps 4.25 gives net sales 352.82; wi
Profiles
A CPU profile in the folded-stack format every flamegraph tool reads: one line per unique stack, frames separated by semicolons, then a space and a sample count. Twelve stacks up to seven frames deep, with the runtime's
Logs
The CRI log format Kubernetes nodes actually write: an RFC 3339 nanosecond timestamp, a stream name, and an F or P tag marking whether the line is full or a partial continuation. One long message is split across several
Bdd
The same six pickles reported as JUnit XML, which is what a BDD suite hands to a generic CI dashboard. One <testcase> per pickle means the three expanded outline rows appear as three tests with identical names, enough to
Logs
A Docker json-file container log: one JSON object per line with the log text, stream (stdout/stderr), and an RFC 3339 timestamp, exactly as Docker's default logging driver writes it. A fixture for container-log shippers
Restaurant Costing
Daily Z-read and cash-up for Ember Lane Pizza. A 61-line printed till report for 2026-08-28, 46 characters wide with no line longer than that. Gross 1582.50 less discounts 158.25 and comps 20.00 gives net sales 1404.25;
Logs
Forty service-mesh proxy access records with the fields that make mesh debugging possible: response_flags distinguishing an upstream failure from an overflow, upstream_service_time against total duration, upstream host a
Flaky Runs
Build #301 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is errored while the other five cases pass every time. The underlying cause is a real call to the fictional payments host in
Flaky Runs
Build #201 of five consecutive runs of cart.DiscountTest, in which stacksDiscountsInDeclaredOrder is passing while the other five cases pass every time. The underlying cause is a shared coupon cache left populated by a s
Flaky Runs
Build #401 of five consecutive runs of cart.PricingTest, in which appliesTaxToSubtotal is failing while the other five cases pass every time. The underlying cause is a rounding boundary that only trips when the tax rate
Flaky Runs
Build #101 of five consecutive runs of checkout.SessionTest, in which expiresSessionAfterTimeout is passing while the other five cases pass every time. The underlying cause is a 250 ms sleep racing the session expiry swe
History
The stable machine format of git blame: a full header block the first time a commit appears and a bare `<sha> <old> <new>` line every time after, with each source line following on a tab-prefixed line. A parser that expe
