Splunk Cloud delivers Operational Intelligence as a cloud service, enabling you to gain critical insights from your machine data without the need to manage any infrastructure. Splunk Cloud offers the features of award-winning Splunk Enterprise as an easy-to-use cloud service.
The Splunk Cloud integration requires a qualifying plan. Contact Sales to get started.
Enable the HTTP Event Collector (HEC)
Follow the instructions provided by Splunk to enable the HEC data input on your Splunk Cloud instance. HEC is not enabled by default. Make note of your instance host name and the configured port for use later on.
Create an HEC Token
Once HEC is enabled, create a token using the instructions provided by Splunk. You may want to create a separate index dedicated to BlazeMeter API Monitoring event data. The index used cannot be configured within BlazeMeter, so make sure you have the correct index and other settings set in Global Settings or the token config.
Connecting Your Accounts
Once you have your instance host name/port number and an HEC token, you can connect your Splunk Cloud instance with BlazeMeter API Monitoring (Runscope).
- From your Profile and Account Settings icon on top-right, click Connected Services.
- Find and select Connect Splunk Cloud.
- Enter the instance host name (excluding https://) and port number. Do not prefix the instance hostname with
input-orhttp-inputs-, we will do this automatically based on the instance type you select. - Select your instance type: self-serve or managed. If you have a Splunk Cloud trial or do not know your instance type, it is most likely self-serve. Contact your Splunk administrator to confirm.
- Select which data to send to Splunk:
- Test runs: create an event for every completed test run
- Test steps: create an event for every test step within a test run (currently limited to request steps only, contact Support to request additional step types)
Event Reference
The following values will be sent for each sourcetype:
sourcetype=runscope:test_run
| Attribute | Description |
|---|---|
test_name | The name of the test. |
test_id | The unique ID for the test. |
test_run_id | The unique ID for the individual test run instance. |
result | The outcome of the test run, either 'passed' or 'failed'. |
started_at | The timestamp when the test run started. |
finished_at | The timestamp when the test run completed. |
assertions_defined | The number of assertions defined for all requests in the test. |
assertions_passed | The number of assertions that passed in this test run. |
assertions_failed | The number of assertions that failed in this test run. |
variables_defined | The number of variables defined in this test run. |
variables_passed | The number of variables that passed in this test run. |
variables_failed | The number of variables that failed in this test run. |
scripts_defined | The number of scripts defined in this test run. |
scripts_passed | The number of scripts that passed in this test run. |
scripts_failed | The number of scripts that failed in this test run. |
requests_executed | The number of requests executed for this test run. |
bucket_name | The name of the Runscope bucket the test belongs to. |
environment_name | The name of the environment used in this test run. |
environment_id | The ID for the environment used in this test run. |
bucket_key | The unique key for the Runscope bucket the test belongs to. |
team_name | The name of the Runscope team this test belongs to. |
team_id | The unique ID for the Runscope team this test belongs to. |
agent | The agent used to execute this test run, or null if a default Runscope location was used. |
region | The region code for the location the test was run from, or null if an agent was used. |
region_name | The full region name and location the test was run from, or null if an agent was used. |
initial_variables.* | The variable state after the initial scripts and variables have been processed (bucket-wide and test-specific) prior to the execution of the first request. |
sourcetype=runscope:test_step
| Attribute | Description |
|---|---|
test_name | The name of the test. |
test_id | The unique ID for the test. |
test_run_id | The unique ID for the individual test run instance. |
request_url | The URL that was requested for this test step. |
request_method | The HTTP method used for this request. e.g. GET, POST, PUT, PATCH, DELETE, etc. |
response_status_code | The HTTP status code for the response, if the request completed. |
response_size_bytes | The size of the HTTP response body. |
response_time_ms | The time it took for the server to respond, in milliseconds. |
finished_at | The timestamp when the test run started. |
assertions_defined | The number of assertions defined for this request. |
assertions_passed | The number of assertions that passed for this request in this test run. |
assertions_failed | The number of assertions that failed for this request in this test run. |
variables_defined | The number of variables defined for this request. |
variables_passed | The number of variables that passed for this request in this test run. |
variables_failed | The number of variables that failed for this request in this test run. |
scripts_defined | The number of scripts defined for this request. |
scripts_passed | The number of scripts that passed for this request in this test run. |
scripts_failed | The number of scripts that failed for this request in this test run. |
environment_name | The name of the environment used for this request in this test run. |
environment_id | The ID for the environment used for this request in this test run. |
bucket_name | The name of the API Monitoring bucket the test belongs to. |
bucket_key | The unique key for the API Monitoring bucket the test belongs to. |
team_name | The name of the API Monitoring team this test belongs to. |
team_id | The unique ID for the API Monitoring team this test belongs to. |
agent | The agent used to execute this test run, or null if a default API Monitoring location was used. |
region | The region code for the location the test was run from, or null if an agent was used. |
You can disconnect Splunk Cloud at any time by disconnecting the service in your team's Connected Services settings.
0 Comments