<?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: Help on Aggregation types in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-on-Aggregation-types/m-p/113561#M1222</link>
    <description>&lt;P&gt;1. Redis uptime - I guess you then refer to following metrics:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;uptime_in_seconds:846988&lt;BR /&gt;uptime_in_days:9&lt;/PRE&gt;&lt;P&gt;values will be reset every Redis restart, so using "max" makes no sense - as you'll report what was the longest uptime in a given timeframe. Using "sum" also makes no sense as that metric grows. I believe you want to report "availability". If I were you, I'd report "1" if uptime_in_seconds &amp;gt; 0. And report "0" if "INFO" command fails (or not report at all). By that you'll know what state is when Redis is running and when it is not. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2. Cache hits - depends what you want to measure. If you want to measure the total hits over time - then use "sum". If you want to measure the ratio use "avg/min" or similar. If you want to see what was the best cache hit value - use "max". It all depends from understanding what you want to measure and WHY.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jul 2020 11:37:09 GMT</pubDate>
    <dc:creator>Radoslaw_Szulgo</dc:creator>
    <dc:date>2020-07-07T11:37:09Z</dc:date>
    <item>
      <title>Help on Aggregation types</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-on-Aggregation-types/m-p/113560#M1221</link>
      <description>&lt;P&gt;My service uses redis for caching responses . Redis also tells about its uptime through its info method. I use this method to create a jmx plugin which exposes this uptime information in my java service updated every 5 seconds. I created a jmx extension to record this metric in dynatrace. So what kind of aggregation should I use to obtain the uptime of the service as a line graph -&amp;gt; sum, avg or max?&lt;/P&gt;&lt;P&gt;Another question, we also count the number of cache hits in our app. what would the aggregation be to obtain the cache hits?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 07:33:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-on-Aggregation-types/m-p/113560#M1221</guid>
      <dc:creator>reshov_roy</dc:creator>
      <dc:date>2020-06-11T07:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Help on Aggregation types</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-on-Aggregation-types/m-p/113561#M1222</link>
      <description>&lt;P&gt;1. Redis uptime - I guess you then refer to following metrics:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;uptime_in_seconds:846988&lt;BR /&gt;uptime_in_days:9&lt;/PRE&gt;&lt;P&gt;values will be reset every Redis restart, so using "max" makes no sense - as you'll report what was the longest uptime in a given timeframe. Using "sum" also makes no sense as that metric grows. I believe you want to report "availability". If I were you, I'd report "1" if uptime_in_seconds &amp;gt; 0. And report "0" if "INFO" command fails (or not report at all). By that you'll know what state is when Redis is running and when it is not. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;2. Cache hits - depends what you want to measure. If you want to measure the total hits over time - then use "sum". If you want to measure the ratio use "avg/min" or similar. If you want to see what was the best cache hit value - use "max". It all depends from understanding what you want to measure and WHY.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 11:37:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/Help-on-Aggregation-types/m-p/113561#M1222</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2020-07-07T11:37:09Z</dc:date>
    </item>
  </channel>
</rss>

