Frequently Asked Questions

Yes. LoadStrike requires a valid runner key for licensed execution. The active runner key also decides which transports, clustering options, reporting sinks, and extensions are available for the run.

Local runner access is intended for workstation or host-based execution with plan-specific device limits. Eligible paid plans can also include CI or distributed runner support for automated and multi-node runs.

The current run is allowed to finish, but the next run is blocked until the license is valid again.

Yes. In GenerateAndCorrelate mode, destination can be omitted and the source result drives pass or fail reporting.

Yes. CorrelateExistingTraffic mode supports consume-to-consume correlation for existing traffic instead of generating a new source message.

LoadStrike supports HTTP, Kafka, RabbitMQ, Azure Event Hubs, NATS, Redis Streams, Push Diffusion, and delegate-based custom stream endpoints.

Yes. TrackingField supports header selectors and JSON selectors. The selector prefix is case-insensitive, but the header name or JSON path segments after the prefix are exact-case. When the tracking id is in the body, you can also supply MessagePayloadType and serializer settings to parse it correctly.

Yes when TimeoutCountsAsFailure is true. The default correlation timeout is 30 seconds.

Yes. Redis can be used as a correlation store option, and Redis Streams is also supported as a transport endpoint.

Yes. Kafka endpoint configuration supports common SASL mechanisms, security protocol settings, and other client connection options needed by the underlying client library.

GatherByField is configured on the destination endpoint and groups matched correlation results by a header or JSON field so the report can show grouped percentile summaries and grouped charts. Grouping is case-sensitive by default unless GatherByFieldValueCaseSensitive is set to false.

The runtime can generate HTML, CSV, TXT, and Markdown reports. Those formats keep the same LoadStrike layout, ordering, formatting, and displayed data across supported languages. The HTML report includes scenario metrics, latency percentiles, status-code tables, failed rows, grouped and ungrouped correlation summaries, summary charts, and plugin tabs.

Yes. Business and Enterprise include built-in reporting sinks for InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OTEL Collector. The public downloads area includes Grafana starter assets for the Grafana-backed sinks and ready-to-edit JSON infra-config templates for Datadog, Splunk, and OTEL Collector.

Yes. Business and above include custom reporting sinks, custom worker plugins, and runtime policy hooks that can skip scenarios or run code before and after scenarios and steps. Plan limits such as agent counts and timeout ceilings are enforced separately at run start.

Yes. LoadStrike supports local coordinator and agent execution, and distributed clustering using NATS for coordinator-agent communication.

Yes. LoadStrike can orchestrate Playwright-driven and Selenium-driven scenario execution so UI journeys can be exercised under controlled load and reported through the same runtime model.

Teams usually evaluate LoadStrike when they need a self-hosted load testing tool that combines API load testing, browser-driven flows, and source-to-destination event correlation in one runtime and one report model.

Yes. You can configure runs in code, load settings from JSON, and apply CLI overrides for one-off execution changes.