<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Example of how to measure hypervisor network usage? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-hypervisor-network-usage/m-p/493984#M8346</link>
    <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;*For more information about this example see [Virtualization&lt;/P&gt;

&lt;H2&gt;Module KPIs and thresholds](&lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds"&gt;https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds&lt;/A&gt;) in the &lt;EM&gt;Splunk IT Service Intelligence Modules&lt;/EM&gt; manual.*&lt;/H2&gt;

&lt;P&gt;System Administration teams often need to know the network usage across the host's physical adapter. For example, the combined transmit-and receive-rates and the sum of data transmitted and received across all physical NIC instances connected to the host. &lt;/P&gt;

&lt;P&gt;Set up this example use case to analyze and troubleshoot your virtualization infrastructure.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on logs and events from virtualization platforms.&lt;/P&gt;

&lt;P&gt;Install the appropriate add-ons for the platforms that exist in your environment.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://splunkbase.splunk.com/app/1253/"&gt;Splunk Add-on for Microsoft Hyper-V&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://splunkbase.splunk.com/app/3215/"&gt;Splunk Add-on for VMware&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;You can find installation and configuration instructions in the &lt;STRONG&gt;Details&lt;/STRONG&gt; tab of each Splunkbase item. Additional configuration details are available in the &lt;EM&gt;&lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleconfigurations"&gt;Virtualization Module configurations&lt;/A&gt;&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; For more granular results with scripted inputs, you can increase the frequency at which the input runs using the &lt;CODE&gt;interval&lt;/CODE&gt; 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 &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Scripted_Input:"&gt;Scripted Input&lt;/A&gt; in the &lt;EM&gt;input.conf&lt;/EM&gt; topic of the &lt;EM&gt;Splunk Enterprise Admin&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; 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 &lt;CODE&gt;main&lt;/CODE&gt;.&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=hostsystem tag=network tag=performance tag=virtualization &lt;BR /&gt;
| timechart span=15min avg(network_usage) BY host&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuletroubleshooting"&gt;Virtualization Module troubleshooting&lt;/A&gt; section in the Splunk IT Service Intelligence &lt;EM&gt;Modules&lt;/EM&gt; manual lists troubleshooting resources that you can apply to this example use case.&lt;/P&gt;

&lt;P&gt;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 &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jan 2020 18:10:14 GMT</pubDate>
    <dc:creator>sloshburch</dc:creator>
    <dc:date>2020-01-29T18:10:14Z</dc:date>
    <item>
      <title>Example of how to measure hypervisor network usage?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-hypervisor-network-usage/m-p/493983#M8345</link>
      <description>&lt;P&gt;Does anyone have examples of how to use Splunk to measure hypervisor network usage?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2020 18:10:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-hypervisor-network-usage/m-p/493983#M8345</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-29T18:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: Example of how to measure hypervisor network usage?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-hypervisor-network-usage/m-p/493984#M8346</link>
      <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;*For more information about this example see [Virtualization&lt;/P&gt;

&lt;H2&gt;Module KPIs and thresholds](&lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds"&gt;https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleKPIsandthresholds&lt;/A&gt;) in the &lt;EM&gt;Splunk IT Service Intelligence Modules&lt;/EM&gt; manual.*&lt;/H2&gt;

&lt;P&gt;System Administration teams often need to know the network usage across the host's physical adapter. For example, the combined transmit-and receive-rates and the sum of data transmitted and received across all physical NIC instances connected to the host. &lt;/P&gt;

&lt;P&gt;Set up this example use case to analyze and troubleshoot your virtualization infrastructure.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on logs and events from virtualization platforms.&lt;/P&gt;

&lt;P&gt;Install the appropriate add-ons for the platforms that exist in your environment.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://splunkbase.splunk.com/app/1253/"&gt;Splunk Add-on for Microsoft Hyper-V&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://splunkbase.splunk.com/app/3215/"&gt;Splunk Add-on for VMware&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;You can find installation and configuration instructions in the &lt;STRONG&gt;Details&lt;/STRONG&gt; tab of each Splunkbase item. Additional configuration details are available in the &lt;EM&gt;&lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuleconfigurations"&gt;Virtualization Module configurations&lt;/A&gt;&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; For more granular results with scripted inputs, you can increase the frequency at which the input runs using the &lt;CODE&gt;interval&lt;/CODE&gt; 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 &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Scripted_Input:"&gt;Scripted Input&lt;/A&gt; in the &lt;EM&gt;input.conf&lt;/EM&gt; topic of the &lt;EM&gt;Splunk Enterprise Admin&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; 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 &lt;CODE&gt;main&lt;/CODE&gt;.&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=hostsystem tag=network tag=performance tag=virtualization &lt;BR /&gt;
| timechart span=15min avg(network_usage) BY host&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/VirtualizationModuletroubleshooting"&gt;Virtualization Module troubleshooting&lt;/A&gt; section in the Splunk IT Service Intelligence &lt;EM&gt;Modules&lt;/EM&gt; manual lists troubleshooting resources that you can apply to this example use case.&lt;/P&gt;

&lt;P&gt;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 &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2020 18:10:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-hypervisor-network-usage/m-p/493984#M8346</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-29T18:10:14Z</dc:date>
    </item>
  </channel>
</rss>

