Getting Data In

Which instance should host the console?

xindeNokia
Path Finder

REF - http://docs.splunk.com/Documentation/Splunk/7.0.5/DMC/WheretohostDMC

Doc seems not straightforward to me for the case: one indexer + one search head

it suggests "not to host the console on a production search head"
does this mean console should sit on the indexer?

Thanks inadvance

0 Karma
1 Solution

horsefez
Motivator

Hi @xindeNokia,

it says it in the second column:

Otherwise, run the Monitoring Console on a search head that is dedicated to running Monitoring Console searches.

If you don't have too much load/too many searches running on your Searchhead its also fine to host the DMC on the Searchhead.
But you would normally go for a secondary instance that takes on tasks as the license master etc.

View solution in original post

0 Karma

horsefez
Motivator

Hi @xindeNokia,

it says it in the second column:

Otherwise, run the Monitoring Console on a search head that is dedicated to running Monitoring Console searches.

If you don't have too much load/too many searches running on your Searchhead its also fine to host the DMC on the Searchhead.
But you would normally go for a secondary instance that takes on tasks as the license master etc.

0 Karma

xindeNokia
Path Finder

Thank you for the quick reply

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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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 ...