See how the LoadStrike Grafana Loki sink fits into transaction-aware reporting and public Grafana starter assets.
The Grafana Loki integration is the built-in LoadStrike sink for teams that want log-style reporting events in Loki while keeping projected metrics available through a companion OTLP path. The site also publishes the matching datasource and dashboard starter assets.
That lets self-hosted teams keep a transaction-aware runtime and still route the final reporting story into Grafana-oriented observability workflows they already operate.
Teams already using Loki and Grafana for observability and wanting LoadStrike event data in that same environment.
Request-only tooling often produces endpoint metrics without a clear path for transaction-level event data and grouped correlation detail. That makes the observability handoff harder once the workflow crosses system boundaries.
LoadStrike documents Grafana Loki as a built-in sink, explains the OTLP metrics companion path, and publishes a Loki datasource YAML, dashboard provider YAML, and overview dashboard JSON file for the public workflow.
These public assets already exist for the Grafana Loki workflow.
Read the sink behavior and configuration surface.
Download the datasource provisioning file.
Download the public overview dashboard.
Download the shared dashboard-provider file.
Yes. The downloads include a Loki datasource YAML, a shared dashboard-provider YAML, and a Loki overview dashboard JSON file.
Yes. The docs describe Grafana Loki as a built-in reporting sink on Business and Enterprise rather than as a custom sink the user must implement manually.
Open the Grafana Loki sink docs, the realtime reporting landing page, and the reports overview so the Loki-specific workflow stays connected to the broader transaction reporting model.
Start with the implementation details that match this page.
Use the Grafana Loki sink when you want log-style LoadStrike events in Loki and projected metrics through a companion OTLP path.
Realtime reporting streams LoadStrike data to the customer portal or external backends during the run and again when the run finishes.
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 comparison pages if you still need a tool-level decision.
Compare LoadStrike and Apache JMeter across scenario design, protocol coverage, downstream correlation, browser workflows, reporting, and self-hosted operations.
Connect the run output to the observability backend your team already uses.
See how the LoadStrike InfluxDB sink fits into transaction-aware reporting workflows and public Grafana starter assets.
See how the LoadStrike TimescaleDB sink fits into transaction-aware reporting workflows and public Grafana starter assets.
Keep moving with the most relevant follow-up pages.
See a category where grouped event reporting matters.
Connect cluster execution back to the observability backend.
Review the methodology checklist for artifacts, topology, and report evidence.
Download the Loki starter assets, wire the sink and OTLP companion path where needed, then verify the exported run events beside the local report.
