Splunk® Enterprise

Inherit a Splunk Enterprise Deployment

Download manual as PDF

Download topic as PDF

Draw a diagram of your deployment

Drawing a diagram of your deployment is a useful tool for you to visualize the details as you learn about your deployment, as well as to refer to in the future.

As you read the topics in this manual, create a diagram of your Splunk deployment. Add details as you discover them.

Your diagram can be on paper, which is preferable at the beginning. If you prefer to work with a diagramming tool like Visio or Omnigraffle, here are some icons you can use:

http://wiki.splunk.com/Community:Splunk_Visio_Stencil

Your diagram should show the following items:

  • Each search head.
  • Each indexer.
  • Any additional components such as
    • cluster master (if you have indexer clustering)
    • search head deployer (if you have search head clustering)
    • deployment server
    • license master
    • monitoring console
    • KV store
  • Forwarders, or with a large number of forwarders, server classes, which are sets of forwarders.
  • The connections between each instance.


Leave room around each node in the diagram so that you can add information as you discover it. For each node, include the following information:

  • The version of Splunk Enterprise it is running.
  • Whether it is running a KV store.
  • All open ports.
  • Machine information like operating system, CPU, physical memory, storage type, and virtualization.


See the next topic, Deployment topologies, for definitions of most of the components. Continue to the following topics for steps for discovering them using either the monitoring console, if you have it, or configuration file inspection if you do not have the monitoring console. See Review your apps and add-ons for information and steps for discovering server classes and the KV store in your deployment.

PREVIOUS
Inherited deployments
  NEXT
Deployment topologies

This documentation applies to the following versions of Splunk® Enterprise: 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.3.0, 7.3.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters