You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extensions/splunk/tests/features/splunk.feature
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Feature: Sending data to Splunk HEC using PutSplunkHTTP
25
25
And PutSplunkHTTP is EVENT_DRIVEN
26
26
And a QuerySplunkIndexingStatus processor
27
27
And QuerySplunkIndexingStatus is EVENT_DRIVEN
28
-
And the "Splunk Request Channel" properties of the PutSplunkHTTP and QuerySplunkIndexingStatus processors are set to the same random guid
28
+
And the "Splunk Request Channel" properties of the PutSplunkHTTP and QuerySplunkIndexingStatus processors are set to the same random UUID
29
29
And the "Source" property of the PutSplunkHTTP processor is set to "my-source"
30
30
And the "Source Type" property of the PutSplunkHTTP processor is set to "my-source-type"
31
31
And the "Host" property of the PutSplunkHTTP processor is set to "my-host"
@@ -45,7 +45,7 @@ Feature: Sending data to Splunk HEC using PutSplunkHTTP
45
45
And PutFile's success relationship is auto-terminated
46
46
47
47
When the MiNiFi instance starts up
48
-
Then a single file with the content "foobar" is placed in the "/tmp/output" directory in less than 120 seconds
48
+
Then a single file with the content "foobar" is placed in the "/tmp/output" directory in less than 20 seconds
49
49
And an event is registered in Splunk HEC with the content "foobar" with "my-source" set as source and "my-source-type" set as sourcetype and "my-host" set as host
50
50
51
51
Scenario: A MiNiFi instance transfers data to a Splunk HEC with SSL enabled
@@ -56,7 +56,7 @@ Feature: Sending data to Splunk HEC using PutSplunkHTTP
56
56
And PutSplunkHTTP is EVENT_DRIVEN
57
57
And a QuerySplunkIndexingStatus processor
58
58
And QuerySplunkIndexingStatus is EVENT_DRIVEN
59
-
And the "Splunk Request Channel" properties of the PutSplunkHTTP and QuerySplunkIndexingStatus processors are set to the same random guid
59
+
And the "Splunk Request Channel" properties of the PutSplunkHTTP and QuerySplunkIndexingStatus processors are set to the same random UUID
60
60
And the "Source" property of the PutSplunkHTTP processor is set to "my-source"
61
61
And the "Source Type" property of the PutSplunkHTTP processor is set to "my-source-type"
62
62
And the "Host" property of the PutSplunkHTTP processor is set to "my-host"
@@ -79,5 +79,5 @@ Feature: Sending data to Splunk HEC using PutSplunkHTTP
79
79
And SSL is enabled for the Splunk HEC and the SSL context service is set up for PutSplunkHTTP and QuerySplunkIndexingStatus
80
80
81
81
When the MiNiFi instance starts up
82
-
Then a single file with the content "foobar" is placed in the "/tmp/output" directory in less than 120 seconds
82
+
Then a single file with the content "foobar" is placed in the "/tmp/output" directory in less than 20 seconds
83
83
And an event is registered in Splunk HEC with the content "foobar" with "my-source" set as source and "my-source-type" set as sourcetype and "my-host" set as host
0 commit comments