Knowledge Management

Example of how to measure datastore storage?

sloshburch
Splunk Employee
Splunk Employee

Does anyone have examples of how to use Splunk to measure datastore storage?

Tags (1)
0 Karma
1 Solution

sloshburch
Splunk Employee
Splunk Employee

The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.

*For more information about this example see [Virtualization

Module KPIs and thresholds](https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds) in the Splunk IT Service Intelligence Modules manual.*

System administration teams need to know the amount of space used by the datastore. Set up this example use case to troubleshoot your virtualization infrastructure by searching and analysis of virtualization related logs, events, and metrics.

Load data

How to implement: This example use case depends on logs and events from virtualization platforms.

Install the appropriate add-ons for the platforms that exist in your environment.

You can find installation and configuration instructions in the Details tab of each Splunkbase item. Additional configuration details are available in the Virtualization Module configurations manual.

Best practice: For more granular results with scripted inputs, you can increase the frequency at which the input runs using the interval setting in inputs.conf. Running the input more frequently consumes more storage, and running it less frequently uses less, which can affect license consumption. The default interval is 60 seconds. See Scripted Input in the input.conf topic of the Splunk Enterprise Admin manual.

Best practice: For all of the data inputs, specify a desired target index to provide a more sustainable practice for data access controls and retention models. By default, Splunk collects the data in the default index named main.

Get insights

Run the following search.

index=* tag=datastore tag=storage tag=performance tag=virtualization
| timechart span=15min avg(datastore_used_percent) BY host

Best practice: In searches, replace the asterisk in index=* with the name of the index that contains the data. By default, Splunk stores data in the main index. Therefore, index=* becomes index=main. Use the OR operator to specify one or multiple indexes to search. For example, index=main OR index=security. See About managing indexes and How indexing works in Splunk docs for details.

Help

The Virtualization Module troubleshooting section in the Splunk IT Service Intelligence Modules manual lists troubleshooting resources that you can apply to this example use case.

If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See About installing Splunk add-ons in the Splunk Add-ons manual.

For troubleshooting tips that you can apply to all add-ons, see Troubleshoot add-ons in the Splunk Add-ons manual.

For more support, post a question to the Splunk Answers community.

View solution in original post

0 Karma

sloshburch
Splunk Employee
Splunk Employee

The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.

*For more information about this example see [Virtualization

Module KPIs and thresholds](https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds) in the Splunk IT Service Intelligence Modules manual.*

System administration teams need to know the amount of space used by the datastore. Set up this example use case to troubleshoot your virtualization infrastructure by searching and analysis of virtualization related logs, events, and metrics.

Load data

How to implement: This example use case depends on logs and events from virtualization platforms.

Install the appropriate add-ons for the platforms that exist in your environment.

You can find installation and configuration instructions in the Details tab of each Splunkbase item. Additional configuration details are available in the Virtualization Module configurations manual.

Best practice: For more granular results with scripted inputs, you can increase the frequency at which the input runs using the interval setting in inputs.conf. Running the input more frequently consumes more storage, and running it less frequently uses less, which can affect license consumption. The default interval is 60 seconds. See Scripted Input in the input.conf topic of the Splunk Enterprise Admin manual.

Best practice: For all of the data inputs, specify a desired target index to provide a more sustainable practice for data access controls and retention models. By default, Splunk collects the data in the default index named main.

Get insights

Run the following search.

index=* tag=datastore tag=storage tag=performance tag=virtualization
| timechart span=15min avg(datastore_used_percent) BY host

Best practice: In searches, replace the asterisk in index=* with the name of the index that contains the data. By default, Splunk stores data in the main index. Therefore, index=* becomes index=main. Use the OR operator to specify one or multiple indexes to search. For example, index=main OR index=security. See About managing indexes and How indexing works in Splunk docs for details.

Help

The Virtualization Module troubleshooting section in the Splunk IT Service Intelligence Modules manual lists troubleshooting resources that you can apply to this example use case.

If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See About installing Splunk add-ons in the Splunk Add-ons manual.

For troubleshooting tips that you can apply to all add-ons, see Troubleshoot add-ons in the Splunk Add-ons manual.

For more support, post a question to the Splunk Answers community.

0 Karma
Get Updates on the Splunk Community!

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...