![]() However, you cannot request 1-hour periods, because that is less than the default (3 hours). In the command example above, you cannot request 1-minute periods, since that is less than the default (half hour) granularity for the time range.Įxample #2: If you request a range > 7 days but ≤ 3 weeks, where the default period is 3 hours, you can specify periods such as 6, 12, or 24 hours.In the command example above, you can request 1-hour periods, since that is greater than the default (half hour) granularity for the time range.You cannot specify a period smaller than the default for the time range you are requesting. By adding period=3600, the data will be returned as 60-minute periods. Ensure your specifications follow our data aggregation schedules.Įxample #1: Following New Relic's table summarizing granularity of collected data, the following API call would normally return data in 30-minute periods, since the request is for 4 days ( from= and to=). To control this, include the period= parameter in the query command as the number of seconds you want each time period to report. Sometimes the output data's granularity may be too fine, or the time period for the data returned may be too short. ![]() Returning only ten values prevents oversampling and presents a smoother chart, which eliminates a possibly misleading "plateau" effect. Obtaining data at less than an hourly period in the time range would cause oversampling, resulting in duplicate values being returned. This means that for any one hour period, only a single data value is available. When the start time for a requested time range is older than eight days, data has been aggregated or averaged to one hour periods due to the data aggregation schedule.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |