Browse the public LoadStrike examples, quick-start references, protocol docs, browser docs, and reporting assets that already exist on the site.
Start with the quick start if you want the shortest path to a working scenario, then move into the protocol, browser, reporting, and cluster docs that match the workload you already need to test. The public site also links to a sample-reference repository and downloadable observability assets.
This page is meant to shorten that search. It groups the examples already published in the docs so you can move from use case to concrete setup without guessing where the relevant surface lives.
Engineers and technical buyers who already understand the workload shape they care about and want the fastest path into the relevant public examples.
Example discovery often breaks down when docs are organized strictly by API surface. Teams know they need Kafka, Playwright, clustered execution, or observability exports, but they still waste time opening unrelated pages before they find the right sample or download.
LoadStrike already documents quick start flows, browser runtimes, broker and stream endpoints, clustered execution, and reporting sinks publicly. This hub turns those verified examples into a tighter discovery path.
These links cover the fastest public on-ramp into a working LoadStrike run.
Build one correlated transaction and run it.
Pick the right package and runtime first.
Review the public sample-reference repository linked from the site footer and docs.
Use the docs that match the way the workload enters and completes.
Model browser journeys inside the same scenario contract.
Run Selenium-based browser workflows under the same reporting surface.
Define Kafka producer and consumer endpoints with tracking fields.
Connect reports to Datadog, Loki, OTEL, Splunk, InfluxDB, or TimescaleDB.
These questions are rendered on the page and mirrored in the matching FAQ structured data when the route is indexable.
Yes. Every link on this page points to documentation, downloads, or sample references that are already public in the repo and website.
Start with the Playwright or Selenium protocol pages, then read the browser load testing category page so the browser workflow stays connected to the broader transaction model.
Open the realtime reporting docs first, then jump to the specific Datadog, Grafana Loki, OTEL Collector, Splunk HEC, InfluxDB, or TimescaleDB page that matches your sink.
Keep moving from positioning into concrete product detail.
Build one simple transaction, attach correlation, and run it. Use this page when you want the shortest path to a working LoadStrike test.
Use this guide when Playwright browser journeys should run inside the same LoadStrike scenario and reporting model.
This page explains how to read a LoadStrike report. Use it when you want to know what each section means and where to look first.
Use these routes when the next question is tool choice rather than implementation detail.
Compare LoadStrike and k6 across code ergonomics, protocol scope, downstream correlation, reporting depth, browser workflows, and distributed self-hosted execution.
Compare LoadStrike and Apache JMeter across scenario design, protocol coverage, downstream correlation, browser workflows, reporting, and self-hosted operations.
These reporting pages connect the transaction model to the observability systems already documented publicly.
See how the LoadStrike Datadog sink fits into transaction-aware, self-hosted load testing workflows.
See how the LoadStrike OTEL Collector sink fits into OpenTelemetry-oriented reporting workflows.
Every published route should help you move to the next concrete question instead of ending in a dead end.
Start with the core category page if you need the product framing first.
Jump straight to browser-specific positioning and docs.
See how the example set maps to async workflows.
Open the quick start if you want the shortest path to a working scenario, or choose the docs path that matches the transaction surface you already need to validate.
