Knowledge Management

Resource utilization

attgjh1
Communicator

i am confused with the setup guide's explanation. Currently i've deployed splunk only on an individual PC for testing etc. however, if SPLUNK is set up in a larger environment, how would resource utilization and management comes in?

Scenario:
There's an existing server for database.
Several indexers and forwarders all set up through the network. High density flow of data happens in real time.

So, indexing occurs. But where does these indexed info goes? are these search indexes memory based? How are these indexed data accessed by other search heads then? How will this affect memory and resource management (from the view of the entire network, and from the single PC operator point of view)

I'm not sure if im phrasing the question correctly, but im trying to find out how the indexed data is handled by Splunk as the database is going to be accessed alot of time by various PCs via SPLUNK to generate various reports.

Appreciate any help to clarify my confusion here.

Tags (1)
0 Karma
1 Solution

Ayn
Legend

Ayn
Legend

Resource planning is available in this section of the docs: http://docs.splunk.com/Documentation/Splunk/latest/installation/capacityplanningforalargersplunkdepl...

Does this address your concerns?

0 Karma

attgjh1
Communicator

thanks. but it doesnt mention how much resources it would use or occupy. supposedly my data is never archived and i have to constantly add months n months of logs to be indexed; what happens to the datastore the indexer used?

hence, im concerned about the memory used or resourced utilized in this case and any possible consequences.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...