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
Execute the following to bring up your deployment:
51
52
```
@@ -55,9 +56,9 @@ $ SPLUNK_PASSWORD=<password> docker-compose up -d
55
56
## Create standalone with license
56
57
Adding a Splunk Enterprise license can be done in multiple ways. Please review the following compose files below to see how it can be achieved, either with a license hosted on a webserver or with a license file as a direct mount.
57
58
58
-
<details><summary>docker-compose.yml - license from URL</summary><p>
59
+
<details><summary>docker-compose.yml - license from URL</summary>
59
60
60
-
```
61
+
```yaml
61
62
version: "3.6"
62
63
63
64
services:
@@ -71,11 +72,11 @@ services:
71
72
ports:
72
73
- 8000
73
74
```
74
-
</p></details>
75
+
</details>
75
76
76
-
<details><summary>docker-compose.yml - license from file</summary><p>
77
+
<details><summary>docker-compose.yml - license from file</summary>
77
78
78
-
```
79
+
```yaml
79
80
version: "3.6"
80
81
81
82
services:
@@ -91,7 +92,7 @@ services:
91
92
volumes:
92
93
- ./splunk.lic:/tmp/license/splunk.lic
93
94
```
94
-
</p></details>
95
+
</details>
95
96
96
97
97
98
Execute the following to bring up your deployment:
@@ -102,9 +103,9 @@ $ SPLUNK_PASSWORD=<password> docker-compose up -d
102
103
## Create standalone with HEC
103
104
To learn more about what the HTTP event collector (HEC) is and how to use it, please review the documentation [here](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector).
104
105
105
-
<details><summary>docker-compose.yml</summary><p>
106
+
<details><summary>docker-compose.yml</summary>
106
107
107
-
```
108
+
```yaml
108
109
version: "3.6"
109
110
110
111
services:
@@ -118,7 +119,7 @@ services:
118
119
ports:
119
120
- 8000
120
121
```
121
-
</p></details>
122
+
</details>
122
123
123
124
Execute the following to bring up your deployment:
Splunk apps can also be installed using this Docker image.
136
137
137
-
```
138
+
<details><summary>docker-compose.yml</summary>
139
+
140
+
```yaml
138
141
version: "3.6"
139
142
140
143
services:
@@ -148,17 +151,19 @@ services:
148
151
ports:
149
152
- 8000
150
153
```
151
-
</p></details>
154
+
</details>
152
155
153
156
Execute the following to bring up your deployment:
154
157
```
155
158
$ SPLUNK_PASSWORD=<password> docker-compose up -d
156
159
```
157
160
158
161
## Create standalone with SplunkBase app
159
-
<details><summary>docker-compose.yml</summary><p>
162
+
Apps showcased on SplunkBase can also be installed using this Docker image.
160
163
161
-
```
164
+
<details><summary>docker-compose.yml</summary>
165
+
166
+
```yaml
162
167
version: "3.6"
163
168
164
169
services:
@@ -174,17 +179,19 @@ services:
174
179
ports:
175
180
- 8000
176
181
```
177
-
</p></details>
182
+
</details>
178
183
179
184
Execute the following to bring up your deployment:
180
185
```
181
186
$ SPLUNKBASE_PASSWORD=<splunkbase_password> SPLUNK_PASSWORD=<password> docker-compose up -d
182
187
```
183
188
184
189
## Create standalone and universal forwarder
185
-
<details><summary>docker-compose.yml</summary><p>
190
+
You can also enable distributed deployments. In this case, we can create a Splunk universal forwarder running in a container to stream logs to a Splunk standalone, also running in a container.
186
191
187
-
```
192
+
<details><summary>docker-compose.yml</summary>
193
+
194
+
```yaml
188
195
version: "3.6"
189
196
190
197
networks:
@@ -225,7 +232,7 @@ services:
225
232
- 8000
226
233
- 8089
227
234
```
228
-
</p></details>
235
+
</details>
229
236
230
237
Execute the following to bring up your deployment:
231
238
```
@@ -235,9 +242,9 @@ $ SPLUNK_PASSWORD=<password> docker-compose up -d
235
242
## Create heavy forwarder
236
243
The following will allow you spin up a forwarder, and stream its logs to an independent, external indexer located at `idx1-splunk.company.internal`, as long as that hostname is reachable on your network.
237
244
238
-
<details><summary>docker-compose.yml</summary><p>
245
+
<details><summary>docker-compose.yml</summary>
239
246
240
-
```
247
+
```yaml
241
248
version: "3.6"
242
249
243
250
networks:
@@ -263,7 +270,7 @@ services:
263
270
ports:
264
271
- 1514
265
272
```
266
-
</p></details>
273
+
</details>
267
274
268
275
Execute the following to bring up your deployment:
269
276
```
@@ -273,9 +280,9 @@ $ SPLUNK_PASSWORD=<password> docker-compose up -d
273
280
## Create heavy forwarder and deployment server
274
281
The following will allow you spin up a forwarder, and stream its logs to an independent, external indexer located at `idx1-splunk.company.internal`, as long as that hostname is reachable on your network. Additionally, it brings up a deployment server, which will download an app and distribute it to the heavy forwarder.
Additionally, review the `docker-compose.yml` below to understand how linking Splunk instances together through roles and environment variables is accomplished:
333
-
<details><summary>docker-compose.yml</summary><p>
340
+
<details><summary>docker-compose.yml</summary>
334
341
335
-
```
342
+
```yaml
336
343
version: "3.6"
337
344
338
345
networks:
@@ -445,7 +452,7 @@ services:
445
452
volumes:
446
453
- ./default.yml:/tmp/defaults/default.yml
447
454
```
448
-
</p></details>
455
+
</details>
449
456
450
457
Execute the following to bring up your deployment:
Additionally, review the `docker-compose.yml` below to understand how linking Splunk instances together through roles and environment variables is accomplished:
462
-
<details><summary>docker-compose.yml</summary><p>
469
+
<details><summary>docker-compose.yml</summary>
463
470
464
-
```
471
+
```yaml
465
472
version: "3.6"
466
473
467
474
networks:
@@ -575,7 +582,7 @@ services:
575
582
volumes:
576
583
- ./default.yml:/tmp/defaults/default.yml
577
584
```
578
-
</p></details>
585
+
</details>
579
586
580
587
Execute the following to bring up your deployment:
Additionally, review the `docker-compose.yml` below to understand how linking Splunk instances together through roles and environment variables is accomplished:
592
-
<details><summary>docker-compose.yml</summary><p>
599
+
<details><summary>docker-compose.yml</summary>
593
600
594
-
```
601
+
```yaml
595
602
version: "3.6"
596
603
597
604
networks:
@@ -776,17 +783,17 @@ services:
776
783
volumes:
777
784
- ./default.yml:/tmp/defaults/default.yml
778
785
```
779
-
</p></details>
786
+
</details>
780
787
781
788
Execute the following to bring up your deployment:
782
789
```
783
790
$ docker-compose up -d
784
791
```
785
792
786
793
## Enable root endpoint on SplunkWeb
787
-
<details><summary>docker-compose.yml</summary><p>
794
+
<details><summary>docker-compose.yml</summary>
788
795
789
-
```
796
+
```yaml
790
797
version: "3.6"
791
798
792
799
services:
@@ -800,7 +807,7 @@ services:
800
807
ports:
801
808
- 8000
802
809
```
803
-
</p></details>
810
+
</details>
804
811
805
812
Execute the following to bring up your deployment:
806
813
```
@@ -810,9 +817,9 @@ $ SPLUNK_PASSWORD=<password> docker-compose up -d
810
817
Then, visit SplunkWeb on your browser with the root endpoint in the URL, such as `http://localhost:8000/splunkweb`.
811
818
812
819
## Create sidecar forwarder
813
-
<details><summary>k8s-sidecar.yml</summary><p>
820
+
<details><summary>k8s-sidecar.yml</summary>
814
821
815
-
```
822
+
```yaml
816
823
apiVersion: v1
817
824
kind: Pod
818
825
metadata:
@@ -842,7 +849,7 @@ spec:
842
849
- name: shared-data
843
850
emptyDir: {}
844
851
```
845
-
</p></details>
852
+
</details>
846
853
847
854
Execute the following to bring up your deployment:
0 commit comments