-
Notifications
You must be signed in to change notification settings - Fork 4
/
index.html
676 lines (675 loc) · 39.3 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
<!DOCTYPE html>
<html>
<head lang="en">
<meta charset="UTF-8">
<title>Splunk Sizing</title>
<meta name="viewport" content="width=device-width, user-scalable=no">
<link rel="stylesheet" href="jquery-ui.css" />
<link rel="stylesheet" href="ui-textfield.css" />
<link rel="stylesheet" href="index.css" />
<script src="jquery.min.js"></script>
<script src="jquery-ui.min.js"></script>
<script src="ui-textfield.js"></script>
<script src="sliderWithLabel.js"></script>
<script src="index.js"></script>
<script src="jquery.ba-bbq.min.js"></script>
<script src="numeral.min.js"></script>
</head>
<body>
<div class="head">
<h1>Splunk Storage Sizing</h1>
<a id="whatsnew" href="#">
What's New
<div class="dialog" title="What's New" style="display: none;">
<ul style="font-size: smaller;">
<li>12th March 2015: Increased maxiumum Compression and Metadata Size Factors</li>
<li>9th March 2015: Changed index path name "main" to "defaultdb"</li>
<li>27th Februrary 2015: Improved cluster configuration</li>
<li>15th December 2014: Added IOPS information based on RAID calculation</li>
<li>15th December 2014: Merged RAID 10 and RAID 01</li>
<li>15th December 2014: Added RAID 50, RAID 60 and RAID 6</li>
<li>4th November 2014: Added slider for changed the average event size</li>
<li>4th November 2014: In case no data is not archived, related sections are hidden</li>
<li>4th November 2014: Added coldToFrozenDir to indexes.conf</li>
<li>3rd November 2014: Roadmap loaded dynamically fom github.com</li>
<li>13th October 2014: Allow sizing from Events/Second (instead of Daily Volume)</li>
<li>13th October 2014: Added description texts and tooltip</li>
<li>13th October 2014: Added smaller disk sizes</li>
<li>7th October 2014: Retention time visualization</li>
<li>6th October 2014: Estimate number of required nodes/indexers based on daily input data volume</li>
<li>29th September 2014: Added 'Configuration Files' section previewing indexes.conf</li>
<li>25th September 2014: Added 'Share' button allowing users to copy and send the link to the current configuration</li>
<li>24th September 2014: Added 'Feedback' button that opens an email to developer</li>
<li>23th September 2014: Added 'Subscribe' button to allow users to subscribe for news/updates</li>
<li>22th September 2014: New Storage Configuration (supporting per volume RAID configuration)</li>
<li>11th August 2014: Disk Space Contingency</li>
<li>11th August 2014: Calculation of number of required physical disk based on selected RAID level and disk size</li>
<li>11th August 2014: Defaults for Enterprice Tier Prices per GB</li>
<li>11th August 2014: Changed retention time range (minimum 0 days, maximum 7 years)</li>
<li>8th August 2014: Changed input volume range (minimum 1 GB, maximum 100 TB)</li>
<li>7th August 2014: Fixed bug storage calculation</li>
<li>5th August 2014: Changed input data and retention sliders from linear scale to scale with incrementing step values</li>
<li>31th July 2014: Split 'Data Retention' into three categories ('Hot, Warm', Cold, Frozen), Added option to select pricing model (Physical Disks, Enterprice Tier), Allow 'Frozen' retention period to be set to zero, Allow daily data volume up to 3 TB (slider starts with 10 GB values changes, later 50 GB and at the end of the slider 100 GB)</li>
</ul>
</div>
</a>
<a id="feedback" href="mailto:[email protected]">
Feedback
</a>
<a id="subscribe" href="#">
Subscribe
<div class="dialog" title="Subscribe for Updates" style="display: none;">
<div id="subscribe_subscribe">
<p>
Email address:
<input id="subscribe_address" type="text" style="width: 10em;">
<button type="button" id="subscribe_button">Subscribe</button>
</p>
</div>
<div id="subscribe_successful">
<p>
Subscription successful!
</p>
<p style="font-style: italic">
Please check your inbox to confirm the email address.
</p>
</div>
<div id="subscribe_failed">
<p>
Subscription failed!
</p>
<p id="subscribe_failed_message" style="font-style: italic"></p>
<p>
<button type="button" id="subscribe_failed_back">Back</button>
</p>
</div>
</div>
</a>
<a id="share" href="#">
Share
<div class="dialog" title="Share Configuration" style="display: none;">
<p>Just copy and share the link below:</p>
<form id="share_form" method="post" style="display: inline">
Link
<input type="text" value="test" readonly="true" id="share_link" style="width: 50%;" autofocus>
<button type="submit">Send</button>
</form>
</div>
</a>
</div>
<div class="flow group">
<h2>
Input data
<span style="display: inline-block; font-size: small; margin-left: 2em;" title="To get the most accurate sizing, enter the expected data volume per day. Select this check box if you prefer to estimate storage based on a number of Events per second – this calculates volume based on a 'typical' event size.">
<input type="checkbox" id="size-by-events-per-sec">
<label for="size-by-events-per-sec">Size by Events/Sec</label>
</span>
</h2>
<p id="input-data-description-events-per-second" class="description">Estimate the amount of data based on a number of events per second – this calculates based on a typical event size. The more data you send to Splunk Enterprise, the more time Splunk needs to index it into results that you can search, report and generate alerts on.</p>
<p id="input-data-description-daily-amount" class="description">Estimate the average daily amount of data to be ingested. The more data you send to Splunk Enterprise, the more time Splunk needs to index it into results that you can search, report and generate alerts on.</p>
<div class="flow sliders">
<div id="events-per-second" title="The average number of events per second that Splunk will ingest.">
<h3>Events per Second</h3>
<div id="events-per-second-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div id="average-event-size" title="The average message size that Splunk will ingest.">
<h3>Average event Size</h3>
<div id="average-event-size-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div id="raw-volume-div" title="The average amount of uncompressed raw data that Splunk will ingest.">
<h3>Daily Data Volume</h3>
<div id="raw-volume-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div title="Typically, the compressed rawdata file is 15% the size of the incoming, pre-indexed raw data. The number of unique terms in the data affect this value.">
<h3>Raw Compression Factor</h3>
<div id="compression-factor-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div title="Typically, metadata is 35% of the raw data. The type of data and index time field extractions will affect this value.">
<h3>Metadata Size Factor</h3>
<div id="index-factor-slider"></div>
<div><span class="slider-value"></span></div>
</div>
</div>
<p style="display: none;">Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.</p>
</div>
<div class="flow group">
<h2>Data Retention</h2>
<p class="description">Specify the amount of time to retain data for each category. Data will be rolled through each category dependant on its age.</p>
<div class="flow sliders">
<div title="Hot/Warm data will generally be accessed regularly. It should reside on the fastest disk to improve indexing and search performance.">
<h3>Hot, Warm</h3>
<div id="hotwarm-retention-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div title="Cold data is generally older and not accessed regularly. It should reside on slower, cheaper disk as search performance is generally not critical.">
<h3>Cold</h3>
<div id="cold-retention-slider"></div>
<div><span class="slider-value"></span></div>
</div>
<div title="Frozen data is not searchable and should reside on the slowest, cheapest disk">
<h3>Archived (Frozen)</h3>
<div id="frozen-retention-slider"></div>
<div><span class="slider-value"></span></div>
</div>
</div>
<div class="itunes">
<h3>Retention Time</h3>
<div class="bar-container">
<div class="bar">
<div class="inner"></div>
<div class="home"></div>
<div class="cold"></div>
<div class="frozen"></div>
</div>
<div class="legend">
<div><span class="home"></span>Hot, Warm</div>
<div><span class="cold"></span>Cold</div>
<div><span class="frozen"></span>Archived</div>
</div>
</div>
<div class="info">
<p>
Total = <span id="total-rentention">XX</span>
</p>
</div>
</div>
</div>
<div class="flow group">
<h2>
Architecture
<span style="display: inline-block; font-size: small; margin-left: 2em;">
<input type="checkbox" id="enable-cluster-replication">
<label for="enable-cluster-replication">Cluster Replication</label>
</span>
<span style="display: inline-block; font-size: small; margin-left: 1em;">
<input type="checkbox" id="calculate_number_of_nodes">
<label for="calculate_number_of_nodes">Estimate automatically</label>
</span>
</h2>
<p class="description">Specify the number of nodes required. The more data to ingest, the greater the number of nodes required. Adding more nodes will improve indexing throughput and search performance.</p>
<div class="flow sliders">
<div title="The number of indexers needed to meet the requirements.">
<h3>Number of Nodes</h3>
<div id="indexers-retention-slider"></div>
<div><span class="slider-value"></span> node(s)</div>
</div>
<div id="search-factor-retention" style="display: none;" title="The number of searchable copies of the data to be retained across the cluster. This must be the same or less than the Replication Factor">
<h3>Searchability Factor</h3>
<div id="search-factor-retention-slider"></div>
<div><span class="slider-value"></span></div>
<p style="display: none; text-align: center;" id="search-factor-max-message" class="message">
(reached replication factor limit)</p>
</div>
<div id="replication-factor-retention" style="display: none;" title="The total number of searchable and non-searchable copies of the data to be retained across the cluster. This must be the same or greater than the Searchability Factor.">
<h3>Replication Factor</h3>
<div id="replication-factor-retention-slider"></div>
<div><span class="slider-value"></span></div>
<p style="display: none; text-align: center;" id="replication-factor-max-message" class="message">
(reached number of nodes limit)</p>
</div>
</div>
</div>
<div class="group storage-required">
<h2>Storage Required</h2>
<p class="description">This is a breakdown of the overall storage requirement.</p>
<table style="width: 100%;">
<thead>
<tr class="message">
<td></td>
<td>(per Indexer)</td>
<td>(all Indexers)</td>
</tr>
</thead>
<tbody>
<tr>
<td>Hot, Warm</td>
<td><div id="hotwarm-indexer-storage" ></div></td>
<td><div id="hotwarm-storage"></div></td>
</tr>
<tr>
<td>Cold</td>
<td><div id="cold-indexer-storage" ></div></td>
<td><div id="cold-storage"></div></td>
</tr>
<tr>
<td>Archived</td>
<td><div id="frozen-indexer-storage"></div></td>
<td><div id="frozen-storage"></div></td>
</tr>
<tr>
<td>Total</td>
<td><span id="indexer-storage"></span></td>
<td><span id="total-storage"></span></td>
</tr>
</tbody>
</table>
</div>
<div class="group storage-configuration">
<h2>Storage Configuration</h2>
<p class="description">Specify the location of the storage configuration. If possible, spread each type of data across separate volumes to improve performance. Hot/Warm data should be on the fastest disk, cold data on slower disk and archived data on the slowest disk.</p>
<table cellspacing="10px">
<tr>
<th>Buckets</th>
<th>Storage Type</th>
</tr>
<tr>
<td><label for="storage-configuration-hotwarm">Hot, Warm</label></td>
<td>
<select id="storage-configuration-hotwarm">
<option value="detailed">Detailed</option>
<option value="summary">Summary</option>
</select>
</td>
<td>
<label for="storage-configuration-hotwarm-volume"></label>
<select id="storage-configuration-hotwarm-volume">
<option value="1">Volume 1</option>
<option value="2">Volume 2</option>
<option value="3">Volume 3</option>
</select>
</td>
</tr>
<tr>
<td><label for="storage-configuration-cold">Cold</label></td>
<td>
<select id="storage-configuration-cold">
<option value="detailed">Detailed</option>
<option value="summary">Summary</option>
</select>
</td>
<td>
<label for="storage-configuration-cold-volume"></label>
<select id="storage-configuration-cold-volume">
<option value="1">Volume 1</option>
<option value="2">Volume 2</option>
<option value="3">Volume 3</option>
</select>
</td>
</tr>
<tr id="storage-configuration-archived-row">
<td><label for="storage-configuration-archived">Archived</label></td>
<td>
<select id="storage-configuration-archived">
<option value="detailed">Detailed</option>
<option value="summary">Summary</option>
</select>
</td>
<td>
<label for="storage-configuration-archived-volume"></label>
<select id="storage-configuration-archived-volume">
<option value="1">Volume 1</option>
<option value="2">Volume 2</option>
<option value="3">Volume 3</option>
</select>
</td>
</tr>
</table>
</div>
<div class="group physical-storage" id="detailed-storage-volume1">
<h2>Detailed Storage on Volume 1 for <span id="detailed-storage-volume1-buckets"></span> Buckets</h2>
<p class="description">Specify the RAID level, size of individual disks and contingency required for this volume. RAID configurations that stripe will yield significantly superior performance to parity based RAID. That is, RAID 0, 10 and 0+1 will give the best performance, while RAID 5 will offer the worst performance.</p>
<div class="flow options">
<div>
<label for="raid-level-volume1">RAID Level:</label>
<select id="raid-level-volume1">
<option value="0">RAID 0</option>
<option value="5">RAID 5</option>
<option value="6">RAID 6</option>
<option value="10,01">RAID 10 or 01</option>
<option value="50">RAID 50</option>
<option value="60">RAID 60</option>
</select>
</div>
<div>
<label for="disk-size-volume1">Disk Size:</label>
<select id="disk-size-volume1">
<option value="50">50 GB</option>
<option value="100">100 GB</option>
<option value="150">150 GB</option>
<option value="200">200 GB</option>
<option value="300">300 GB</option>
<option value="400">400 GB</option>
<option value="500">500 GB</option>
<option value="600">600 GB</option>
<option value="700">700 GB</option>
<option value="800">800 GB</option>
<option value="900">900 GB</option>
<option value="1024">1 TB</option>
<option value="2048">2 TB</option>
<option value="3072">3 TB</option>
<option value="4096">4 TB</option>
<option value="5120">5 TB</option>
</select>
</div>
<div id="physical-storage-volume1-raid-parity-warning" class="message">
Splunk does not recommend use of Parity based RAID, since this will have a very negative impact on performance
</div>
<div class="flow">
<div style="vertical-align: sub;">Disk Space Contingency:</div>
<div style="width: 5em; padding-left: 1em; padding-right: 1em; margin-top: 0.2em;">
<div id="disk-space-contingency-slider-volume1"></div>
</div>
<div style="vertical-align: sub;" id="disk-space-contingency-volume1">???</div>
</div>
</div>
<p class="description">
The selected storage configuration would typically be expected to achieve about
<span id="detailed-storage-volume1-volumeMaxReadIOPS" class="highlight"></span>
IOPS when doing 100% read operation, and about
<span id="detailed-storage-volume1-volumeMaxWriteIOPS" class="highlight"></span>
IOPS for 100% write operation.
These numbers assume that array is dedicated to Splunk and consists of
<span id="detailed-storage-volume1-diskVolumes" class="highlight"></span>
with <span id="detailed-storage-volume1-disksPerVolume" class="highlight"></span>
disk(s) (typically 200 IOPS per disk).
</p>
<table style="width: 100%;">
<thead>
<tr class="message">
<td></td>
<td>(per Indexer)</td>
<td>(all Indexers)</td>
</tr>
</thead>
<tbody>
<tr>
<td>Number of Disks</td>
<td><div id="disk-count-per-indexer-volume1">???</div></td>
<td><div id="disk-count-total-volume1">???</div></td>
</tr>
<tr>
<td>Physical Disk Space</td>
<td><div id="physical-space-per-indexer-volume1">???</div></td>
<td><div id="physical-space-total-volume1">???</div></td>
</tr>
<tr>
<td>Effective Disk Space</td>
<td><div id="effective-space-per-indexer-volume1">???</div></td>
<td><div id="effective-space-total-volume1">???</div></td>
</tr>
</tbody>
</table>
</div>
<div class="group physical-storage" id="detailed-storage-volume2">
<h2>Detailed Storage on Volume 2 for <span id="detailed-storage-volume2-buckets"></span> Buckets</h2>
<p class="description">Specify the RAID level, size of individual disks and contingency required for this volume. RAID configurations that stripe will yield significantly superior performance to parity based RAID. That is, RAID 0, 10 and 0+1 will give the best performance, while RAID 5 will offer the worst performance.</p>
<div class="flow options">
<div>
<label for="raid-level-volume2">RAID Level:</label>
<select id="raid-level-volume2">
<option value="0">RAID 0</option>
<option value="5">RAID 5</option>
<option value="6">RAID 6</option>
<option value="10,01">RAID 10 or 01</option>
<option value="50">RAID 50</option>
<option value="60">RAID 60</option>
</select>
</div>
<div>
<label for="disk-size-volume2">Disk Size:</label>
<select id="disk-size-volume2">
<option value="50">50 GB</option>
<option value="100">100 GB</option>
<option value="200">200 GB</option>
<option value="300">300 GB</option>
<option value="400">400 GB</option>
<option value="500">500 GB</option>
<option value="600">600 GB</option>
<option value="700">700 GB</option>
<option value="800">800 GB</option>
<option value="900">900 GB</option>
<option value="1024">1 TB</option>
<option value="2048">2 TB</option>
<option value="3072">3 TB</option>
<option value="4096">4 TB</option>
<option value="5120">5 TB</option>
</select>
</div>
<div id="physical-storage-volume2-raid-parity-warning" class="message">
Splunk does not recommend use of Parity based RAID, since this will have a very negative impact on performance
</div>
<div class="flow">
<div style="vertical-align: sub;">Disk Space Contingency:</div>
<div style="width: 5em; padding-left: 1em; padding-right: 1em; margin-top: 0.2em;">
<div id="disk-space-contingency-slider-volume2"></div>
</div>
<div style="vertical-align: sub;" id="disk-space-contingency-volume2">???</div>
</div>
</div>
<p class="description">
The selected storage configuration would typically be expected to achieve about
<span id="detailed-storage-volume2-volumeMaxReadIOPS" class="highlight"></span>
IOPS when doing 100% read operation, and about
<span id="detailed-storage-volume2-volumeMaxWriteIOPS" class="highlight"></span>
IOPS for 100% write operation.
These numbers assume that array is dedicated to Splunk and consists of
<span id="detailed-storage-volume2-diskVolumes" class="highlight"></span>
with <span id="detailed-storage-volume2-disksPerVolume" class="highlight"></span>
disk(s) (typically 200 IOPS per disk).
</p>
<table style="width: 100%;">
<thead>
<tr class="message">
<td></td>
<td>(per Indexer)</td>
<td>(all Indexers)</td>
</tr>
</thead>
<tbody>
<tr>
<td>Number of Disks</td>
<td><div id="disk-count-per-indexer-volume2">???</div></td>
<td><div id="disk-count-total-volume2">???</div></td>
</tr>
<tr>
<td>Physical Disk Space</td>
<td><div id="physical-space-per-indexer-volume2">???</div></td>
<td><div id="physical-space-total-volume2">???</div></td>
</tr>
<tr>
<td>Effective Disk Space</td>
<td><div id="effective-space-per-indexer-volume2">???</div></td>
<td><div id="effective-space-total-volume2">???</div></td>
</tr>
</tbody>
</table>
</div>
<div class="group physical-storage" id="detailed-storage-volume3">
<h2>Detailed Storage on Volume 3 for <span id="detailed-storage-volume3-buckets"></span> Buckets</h2>
<p class="description">Specify the RAID level, size of individual disks and contingency required for this volume. RAID configurations that stripe will yield significantly superior performance to parity based RAID. That is, RAID 0, 10 and 0+1 will give the best performance, while RAID 5 will offer the worst performance.</p>
<div class="flow options">
<div>
<label for="raid-level-volume3">RAID Level:</label>
<select id="raid-level-volume3">
<option value="0">RAID 0</option>
<option value="5">RAID 5</option>
<option value="6">RAID 6</option>
<option value="10,01">RAID 10 or 01</option>
<option value="50">RAID 50</option>
<option value="60">RAID 60</option>
</select>
</div>
<div>
<label for="disk-size-volume3">Disk Size:</label>
<select id="disk-size-volume3">
<option value="50">50 GB</option>
<option value="100">100 GB</option>
<option value="200">200 GB</option>
<option value="300">300 GB</option>
<option value="400">400 GB</option>
<option value="500">500 GB</option>
<option value="600">600 GB</option>
<option value="700">700 GB</option>
<option value="800">800 GB</option>
<option value="900">900 GB</option>
<option value="1024">1 TB</option>
<option value="2048">2 TB</option>
<option value="3072">3 TB</option>
<option value="4096">4 TB</option>
<option value="5120">5 TB</option>
</select>
</div>
<div id="physical-storage-volume3-raid-parity-warning" class="message">
Splunk does not recommend use of Parity based RAID, since this will have a very negative impact on performance
</div>
<div class="flow">
<div style="vertical-align: sub;">Disk Space Contingency:</div>
<div style="width: 5em; padding-left: 1em; padding-right: 1em; margin-top: 0.2em;">
<div id="disk-space-contingency-slider-volume3"></div>
</div>
<div style="vertical-align: sub;" id="disk-space-contingency-volume3">???</div>
</div>
</div>
<p class="description">
The selected storage configuration would typically be expected to achieve about
<span id="detailed-storage-volume3-volumeMaxReadIOPS" class="highlight"></span>
IOPS when doing 100% read operation, and about
<span id="detailed-storage-volume3-volumeMaxWriteIOPS" class="highlight"></span>
IOPS for 100% write operation.
These numbers assume that array is dedicated to Splunk and consists of
<span id="detailed-storage-volume3-diskVolumes" class="highlight"></span>
with <span id="detailed-storage-volume3-disksPerVolume" class="highlight"></span>
disk(s) (typically 200 IOPS per disk).
</p>
<table style="width: 100%;">
<thead>
<tr class="message">
<td></td>
<td>(per Indexer)</td>
<td>(all Indexers)</td>
</tr>
</thead>
<tbody>
<tr>
<td>Number of Disks</td>
<td><div id="disk-count-per-indexer-volume3">???</div></td>
<td><div id="disk-count-total-volume3">???</div></td>
</tr>
<tr>
<td>Physical Disk Space</td>
<td><div id="physical-space-per-indexer-volume3">???</div></td>
<td><div id="physical-space-total-volume3">???</div></td>
</tr>
<tr>
<td>Effective Disk Space</td>
<td><div id="effective-space-per-indexer-volume3">???</div></td>
<td><div id="effective-space-total-volume3">???</div></td>
</tr>
</tbody>
</table>
</div>
<div class="group physical-storage" id="summary-storage">
<h2>Summary Storage for <span id="summary-storage-buckets"></span> Buckets</h2>
<p class="description">Specify the price per GB of storage. Hot/Warm data should be on the most expensive disk, cold data on cheaper disk and archived data on the cheapest disk.</p>
<table style="width: 100%;">
<thead>
<tr class="message">
<td></td>
<td>Price per GB</td>
<td>Size</td>
<td>Totel Price</td>
</tr>
</thead>
<tbody>
<tr id="summary-storage-hotwarm-row">
<td>Hot Warm</td>
<td><label for="hotwarm-price-gb">$</label> <input type="text" id="hotwarm-price-gb" value="0.02"></td>
<td><div id="hotwarm-summary-storage-size">?</div></td>
<td><div id="hotwarm-price">?</div></td>
</tr>
<tr id="summary-storage-cold-row">
<td>Cold</td>
<td><label for="cold-price-gb">$</label> <input type="text" id="cold-price-gb" value="0.02"></td>
<td><div id="cold-summary-storage-size">?</div></td>
<td><div id="cold-price">?</div></td>
</tr>
<tr id="summary-storage-archived-row">
<td>Archived</td>
<td><label for="frozen-price-gb">$</label> <input type="text" id="frozen-price-gb" value="0.02"></td>
<td><div id="archived-summary-storage-size">?</div></td>
<td><div id="frozen-price">?</div></td>
</tr>
<tr>
<td><b>Total</b></td>
<td></td>
<td></td>
<td><div id="total-price">?</div></td>
</tr>
</tbody>
</table>
</div>
<div class="group config-files">
<h2>Configuration Files</h2>
<p class="description">This is an example configuration file that describes the volume configuration for each data type. Note: The path should be modified to point to each disk type. It assumes that all data will be stored in the main index.</p>
<div class="file">
<h3>indexes.conf</h3>
<pre># volume definitions
<div id="conffile-volume1">
[volume:<span id="conffile-volume1-name" class="important-conf-value"></span>]
path = /mnt/<span id="conffile-volume1-pathname" class="important-conf-value"></span>
maxVolumeDataSizeMB = <span id="conffile-volume1-maxVolumeDataSizeMB" class="important-conf-value"></span>
</div><div id="conffile-volume2">
[volume:<span id="conffile-volume2-name" class="important-conf-value"></span>]
path = /mnt/<span id="conffile-volume2-pathname" class="important-conf-value"></span>
maxVolumeDataSizeMB = <span id="conffile-volume2-maxVolumeDataSizeMB" class="important-conf-value"></span>
</div><div id="conffile-volume3">
[volume:<span id="conffile-volume3-name" class="important-conf-value"></span>]
path = /mnt/<span id="conffile-volume3-pathname" class="important-conf-value"></span>
maxVolumeDataSizeMB = <span id="conffile-volume3-maxVolumeDataSizeMB" class="important-conf-value"></span>
</div><div id="conffile-summaryvolume">
[volume:<span id="conffile-summaryvolume-name" class="important-conf-value"></span>]
path = /mnt/<span id="conffile-summaryvolume-pathname" class="important-conf-value"></span>
</div>
# index definition (calculation is based on a single index)
[main]
homePath = volume:<span id="conffile-index-hotwarm-volumename" class="important-conf-value"></span>/defaultdb/db
coldPath = volume:<span id="conffile-index-cold-volumename" class="important-conf-value"></span>/defaultdb/colddb
thawedPath = $SPLUNK_DB/defaultdb/thaweddb
homePath.maxDataSizeMB = <span id="conffile-index-hotwarm-maxDataSizeMB" class="important-conf-value"></span>
coldPath.maxDataSizeMB = <span id="conffile-index-cold-maxDataSizeMB" class="important-conf-value"></span>
maxWarmDBCount = <span class="important-conf-value">4294967295</span>
frozenTimePeriodInSecs = <span id="conffile-index-frozenTimePeriodInSecs" class="important-conf-value"></span>
maxDataSize = <span id="conffile-index-maxDataSize" class="important-conf-value"></span><span id="conffile-index-coldToFrozenDir-section">
coldToFrozenDir = /mnt/<span id="conffile-index-coldToFrozenDir" class="important-conf-value"></span>/defaultdb/frozendb</span></pre>
</div>
</div>
<div class="group">
<h2>Roadmap</h2>
<p class="description">
This is a list of potential features/enhancements that may be added in future.
Please use the link on top of the page to send feedback and request additional features.
</p>
<ul>
<li id="todo-item-template">
<a target="_blank">Loading...</a>
</li>
</ul>
</div>
<div class="group">
<h2>Legal</h2>
<p>
This sizing application is not supported by Splunk.
</p>
<p>
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
</p>
</div>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
</script>
</body>
</html>