Splunk HEC
Use the Splunk HEC sink when you want LoadStrike reporting events and projected metrics delivered through Splunk.
Matching docs
Search across docs titles, summaries, groups, and section headings.
Use Up and Down Arrow to move through results, then press Enter to open the active page.
No indexed docs matched that search. Try a broader term or open the docs hub.
What this page helps you do
What this page helps you do
Use the Splunk HEC sink when you want LoadStrike reporting events and projected metrics delivered through Splunk.
Who this is for
Teams exporting final run data and realtime metrics into supported observability backends.
Prerequisites
- A run result or sink destination you want to wire into the wider observability stack
By the end
A sink-specific setup path that stays tied to the same LoadStrike report model.
Use this page when
Use this page when the local report is not the only destination and you need to wire realtime or final export into a supported sink.
Visual guide
Sample Report Data Rows
Scope Scenario Result Count RPS LatencyP50Ms LatencyP80Ms LatencyP85Ms LatencyP90Ms LatencyP95Ms LatencyP99Ms
Scenario reports-demo OK 675 15.0 21.4 30.2 33.0 36.8 48.6 72.1
LatencyTable Scenario Result Count LatencyP50Ms LatencyP95Ms
LatencyTable reports-demo OK 675 21.4 48.6
LatencyTable reports-demo FAIL 12 35.9 79.2
StatusCode Result Percent
200 OK 97.48
500 FAIL 2.52
FailedStatus Scope Scenario Step StatusCode Count Percent
FailedStatus Scenario reports-demo 500 12 1.75
Reporting
Realtime reporting
Choose the built-in sink page that matches the backend your team already runs, or open Custom Reporting when you need to implement your own destination. Each tab opens a dedicated page with the settings, behavior, and lifecycle details for that reporting path.
Guide
When To Use Splunk HEC
Choose Splunk when the team already searches and alerts on HEC event streams and wants both reporting events and projected metrics from the same LoadStrike run.
What LoadStrike Sends
SplunkReportingSink sends both reporting events and metric projections through the Splunk HEC event endpoint. Final export also includes final metric snapshots plus run-result metadata in the same sink flow.
Configuration Surface
Configure the sink in code or through LoadStrike:ReportingSinks:Splunk. Common options include BaseUrl, Token, Source, Sourcetype, Index, and StaticFields.
Downloads
Splunk setup is supported through the downloadable JSON infra-config template and the shared observability asset guide.
Splunk HEC realtime reporting
Use SplunkReportingSink when you want reporting events and projected metrics sent through the Splunk HEC event endpoint.
If you run these examples locally, add a valid runner key before execution starts. Set it with WithRunnerKey("...") or the config key LoadStrike:RunnerKey.
HTML reports also include the top-right Light/Dark theme toggle. Light is the default report theme.
Splunk HEC Sink
using LoadStrike;
var splunkSink = new SplunkReportingSink(new SplunkReportingSinkOptions
{
BaseUrl = "https://splunk.example.com",
Token = "splunk-hec-token",
Source = "loadstrike",
Sourcetype = "_json",
Index = "observability",
StaticFields =
{
["environment"] = "preprod",
["service"] = "checkout"
}
});
LoadStrikeRunner.RegisterScenarios(scenario)
.WithReportingSinks(splunkSink)
.WithRunnerKey("rkl_your_local_runner_key")
.Run();
package main
import loadstrike "loadstrike.com/sdk/go"
var splunkSink = loadstrike.SplunkReportingSink{
Options: loadstrike.SplunkSinkOptions{
BaseURL: "http://127.0.0.1:8088",
Token: "splunk-hec-token",
Index: "performance",
},
}
import com.loadstrike.runtime.LoadStrikeRuntime.LoadStrikeRunner;
import com.loadstrike.runtime.LoadStrikeRuntime.LoadStrikeScenario;
import com.loadstrike.runtime.LoadStrikeRuntime.LoadStrikeSimulation;
import com.loadstrike.runtime.LoadStrikeSinks;
var scenario = LoadStrikeScenario.empty("orders-realtime-reporting")
.withLoadSimulations(LoadStrikeSimulation.inject(20, 1d, 120d));
var options = new LoadStrikeSinks.SplunkSinkOptions();
options.baseUrl = "https://splunk.example.com";
options.token = "splunk-hec-token";
options.source = "loadstrike";
options.sourcetype = "_json";
options.index = "observability";
options.staticFields.put("environment", "preprod");
options.staticFields.put("service", "checkout");
var sink = new LoadStrikeSinks.SplunkReportingSink(options);
LoadStrikeRunner.registerScenarios(scenario)
.withReportingSinks(sink)
.withRunnerKey("rkl_your_local_runner_key")
.run();
from loadstrike_sdk import LoadStrikeRunner, LoadStrikeScenario, LoadStrikeSimulation, SplunkReportingSink
scenario = (
LoadStrikeScenario.empty("orders-realtime-reporting")
.with_load_simulations(LoadStrikeSimulation.inject(20, 1, 120))
)
sink = SplunkReportingSink(
base_url="https://splunk.example.com",
token="splunk-hec-token",
source="loadstrike",
sourcetype="_json",
index="observability",
static_fields={
"environment": "preprod",
"service": "checkout",
},
)
LoadStrikeRunner.register_scenarios(scenario) \
.with_reporting_sinks(sink) \
.with_runner_key("rkl_your_local_runner_key") \
.run()
import {
LoadStrikeRunner,
LoadStrikeScenario,
LoadStrikeSimulation,
SplunkReportingSink,
SplunkReportingSinkOptions
} from "@loadstrike/loadstrike-sdk";
const scenario = LoadStrikeScenario
.empty("orders-realtime-reporting")
.withLoadSimulations(LoadStrikeSimulation.inject(20, 1, 120));
const sink = new SplunkReportingSink(new SplunkReportingSinkOptions({
BaseUrl: "https://splunk.example.com",
Token: "splunk-hec-token",
Source: "loadstrike",
Sourcetype: "_json",
Index: "observability",
StaticFields: {
environment: "preprod",
service: "checkout"
}
}));
await LoadStrikeRunner
.registerScenarios(scenario)
.withReportingSinks(sink)
.withRunnerKey("rkl_your_local_runner_key")
.run();
const {
LoadStrikeRunner,
LoadStrikeScenario,
LoadStrikeSimulation,
SplunkReportingSink,
SplunkReportingSinkOptions
} = require("@loadstrike/loadstrike-sdk");
(async () => {
const scenario = LoadStrikeScenario
.empty("orders-realtime-reporting")
.withLoadSimulations(LoadStrikeSimulation.inject(20, 1, 120));
const sink = new SplunkReportingSink(new SplunkReportingSinkOptions({
BaseUrl: "https://splunk.example.com",
Token: "splunk-hec-token",
Source: "loadstrike",
Sourcetype: "_json",
Index: "observability",
StaticFields: {
environment: "preprod",
service: "checkout"
}
}));
await LoadStrikeRunner
.registerScenarios(scenario)
.withReportingSinks(sink)
.withRunnerKey("rkl_your_local_runner_key")
.run();
})();
SplunkReportingSinkOptions fields
Defaults to LoadStrike:ReportingSinks:Splunk when binding from infra config.
Required Splunk base URL.
HEC event endpoint path.
Required HEC token.
Splunk event metadata attached to exported log and metric envelopes.
HTTP timeout for Splunk export calls.
Additional fields attached to every Splunk envelope.
{
"LoadStrike": {
"ReportingSinks": {
"Splunk": {
"BaseUrl": "https://splunk.example.com",
"Token": "splunk-hec-token",
"Source": "loadstrike",
"Sourcetype": "_json",
"Index": "observability"
}
}
}
}
Downloads and templates
Use the Splunk HEC template when you want to load sink settings from infra config.
Splunk template JSON
A ready-to-edit infra-config template for SplunkReportingSink.
Download fileObservability asset guide
A combined guide for sink templates and Grafana starter assets.
Download file