<?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: Volume Monitoring using server visibility in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739718#M11557</link>
    <description>&lt;P&gt;even i am searchingfor this answer- please update me as well.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jan 2021 04:14:45 GMT</pubDate>
    <dc:creator>atulwadyalkar</dc:creator>
    <dc:date>2021-01-15T04:14:45Z</dc:date>
    <item>
      <title>Volume Monitoring using server visibility</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739717#M11556</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have checked the official doc for volume metrics in server visibility but unable to comprehend it clearly, so in other words here is my requirement:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- We want to monitor all volumes like /tmp, /var, /var/log&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-Monitoring should be dynamic, which means if tomorrow any mount point is removed/added appd should automatically start that monitoring&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;-Should we create individual conditions for every volume or use the metric: Hardware Resources|Volumes|Used(%) ?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2020 07:56:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739717#M11556</guid>
      <dc:creator>Rohit_Sharma3</dc:creator>
      <dc:date>2020-12-10T07:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Monitoring using server visibility</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739718#M11557</link>
      <description>&lt;P&gt;even i am searchingfor this answer- please update me as well.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2021 04:14:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739718#M11557</guid>
      <dc:creator>atulwadyalkar</dc:creator>
      <dc:date>2021-01-15T04:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Monitoring using server visibility</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739719#M11558</link>
      <description>&lt;P&gt;There is a ServerMonitoring.yml file under &amp;lt;machine agent home&amp;gt;/extensions/ServerMonitoring/conf directory.&lt;/P&gt;&lt;P&gt;Under the section, VolumeMonitorConfig, there is a maxNumberVolumes parameter that is defaulted to 5.&amp;nbsp; Changing this value and restarting the MA will increase or decrease the number of volumes seen under Volumes in Servers.&amp;nbsp; I can't speak to the other requests but that is a start if you haven't already receive an answer or given up.&amp;nbsp; Note that an upgrade will overwrite this value.&amp;nbsp; I know because I have done this before and was on here searching how to do it again when I stumbled onto your thread.&amp;nbsp; Good luck!&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2022 15:10:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739719#M11558</guid>
      <dc:creator>Jim_Zimmer</dc:creator>
      <dc:date>2022-07-27T15:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Monitoring using server visibility</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739720#M11559</link>
      <description>&lt;P&gt;and I take that back in that we have a health rule that says if any partition is over a certain percentage, throw and alert.&amp;nbsp; Here is the custom metric:&lt;/P&gt;&lt;P&gt;Hardware Resources|Volumes|*|Used(%)&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2022 15:18:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Volume-Monitoring-using-server-visibility/m-p/739720#M11559</guid>
      <dc:creator>Jim_Zimmer</dc:creator>
      <dc:date>2022-07-27T15:18:26Z</dc:date>
    </item>
  </channel>
</rss>

