<?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: Database Server Monitoring in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737045#M10197</link>
    <description>&lt;P&gt;The database monitoring agent would provide much more granular details not only about server hardware usage but about that usage specific to individual databases, procedures, queries, and granular comparison data.&lt;/P&gt;

&lt;P&gt;Server Visbility would not provide that without adding several Performance Counters and even then you would never truly know what queries were causing you the most resource usage pain without a lot of time comparing with your database analysis toolset.&lt;/P&gt;

&lt;P&gt;Edit:&amp;nbsp; This is also something to consider from the standpoint of target audience.&amp;nbsp; If you have a group that is monitoring overall server health they may not care about the specific metrics by query.&amp;nbsp; In the event that you wanted to monitor overall server health the Server Visibility agent is better suited to present OS-critical metrics to evaluate health by.&amp;nbsp; In the event you are concerned with Root Cause regarding the execution and operation of SQL, then database monitoring is more aptly suited to your needs.&lt;/P&gt;

&lt;P&gt;It is my opinion however, that there are specific needs for each agent so I would advise if the budget and hardware allows for you to implement both where you are able.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Sep 2018 22:49:45 GMT</pubDate>
    <dc:creator>Michael_Horstma</dc:creator>
    <dc:date>2018-09-17T22:49:45Z</dc:date>
    <item>
      <title>Database Server Monitoring</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737044#M10196</link>
      <description>&lt;P&gt;Dears,&lt;/P&gt;

&lt;P&gt;I would like to know which is a better approach to have Monitor Database Server Metrics using hardware monitoring&amp;nbsp;feature in Database Agent or install Server Visibility on Database Server&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Sep 2018 18:58:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737044#M10196</guid>
      <dc:creator>Ahmedkhalil</dc:creator>
      <dc:date>2018-09-15T18:58:53Z</dc:date>
    </item>
    <item>
      <title>Re: Database Server Monitoring</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737045#M10197</link>
      <description>&lt;P&gt;The database monitoring agent would provide much more granular details not only about server hardware usage but about that usage specific to individual databases, procedures, queries, and granular comparison data.&lt;/P&gt;

&lt;P&gt;Server Visbility would not provide that without adding several Performance Counters and even then you would never truly know what queries were causing you the most resource usage pain without a lot of time comparing with your database analysis toolset.&lt;/P&gt;

&lt;P&gt;Edit:&amp;nbsp; This is also something to consider from the standpoint of target audience.&amp;nbsp; If you have a group that is monitoring overall server health they may not care about the specific metrics by query.&amp;nbsp; In the event that you wanted to monitor overall server health the Server Visibility agent is better suited to present OS-critical metrics to evaluate health by.&amp;nbsp; In the event you are concerned with Root Cause regarding the execution and operation of SQL, then database monitoring is more aptly suited to your needs.&lt;/P&gt;

&lt;P&gt;It is my opinion however, that there are specific needs for each agent so I would advise if the budget and hardware allows for you to implement both where you are able.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Sep 2018 22:49:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737045#M10197</guid>
      <dc:creator>Michael_Horstma</dc:creator>
      <dc:date>2018-09-17T22:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: Database Server Monitoring</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737046#M10198</link>
      <description>so at the end it's license point of view if i have server visibility license it will be nice to monitor the server using server visibility module , if not then Remote hardware monitoring of database agent will provide me with basic info that i need to troubleshoot issue</description>
      <pubDate>Thu, 20 Sep 2018 19:59:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Database-Server-Monitoring/m-p/737046#M10198</guid>
      <dc:creator>Ahmedkhalil</dc:creator>
      <dc:date>2018-09-20T19:59:34Z</dc:date>
    </item>
  </channel>
</rss>

