Specifying Data Granularity
You can query statistics at different granularity levels using the dataFrequency parameter. The minimum granularity Introscope provides is 15 seconds. Specify the dataFrequency value in multiples of 15 seconds. Use the XML dateTime format to indicate the query start and end times. The query returns one record for each time slice in your specified time range. Here are two examples.
apmdevops106
You can query statistics at different granularity levels using the dataFrequency parameter. The minimum granularity Introscope provides is 15 seconds. Specify the dataFrequency value in multiples of 15 seconds. Use the XML dateTime format to indicate the query start and end times. The query returns one record for each time slice in your specified time range. Here are two examples.
You specify a time range of two hours and a data frequency of one hour (3600 seconds) as shown. The query returns two time slices and two records.
<dataFrequency xsi:type="xsd:int">3600</dataFrequency> <startTime xsi:type="xsd:dateTime">2015-04-01T20:30:00.000Z</startTime> <endTime xsi:type="xsd:dateTime">2015-04-01T22:30:00.000Z</endTime>
You specify a time range of two hours and a data frequency of one minute (60 seconds) as shown. The query returns 120 time slices and 120 records.
<dataFrequency xsi:type="xsd:int">60</dataFrequency> <startTime xsi:type="xsd:dateTime">2015-04-01T20:30:00.000Z</startTime> <endTime xsi:type="xsd:dateTime">2015-04-01T22:30:00.000Z</endTime>
Data granularity in queries affects the performance. For example, a query for two weeks of data for 1000 metrics at 15-second data frequency can cause OutOfMemory errors. These errors can occur on both the Enterprise Manager and your web services client. Such large queries can also cause the Enterprise Manager to slow down significantly. We recommend a one-hour granularity for queries requesting data for a large time range.