An operator selects "Average Values" and "Past 30 Minutes" for statistics type and timeframe on the Analytics tab of a Virtual Service and notices the graph only provides a new data point every five…

Question

Options

• AThe Real Time Metrics option has been disabled by another operator.
• BThe GUI Refresh Interval has been increased to five minutes.
• CThe statistics type should be set to "Current Values" rather than "Average Values."
• DThe timeframe should be set to "Real Time" rather than "Past 30 Minutes."

• A
  3% (1)
• B
  6% (2)
• D
  91% (30)

Explanation

Selecting "Past 30 Minutes" as the timeframe switches the display from live streaming data to historical aggregated data, which is stored at a coarser resolution (typically one point per 5 minutes) to conserve system resources. When the Virtual Service was new, it was likely using the "Real Time" timeframe, which streams live data points at a much finer interval. Switching back to "Real Time" would restore the high-frequency updates the operator saw initially.

Why the distractors fail:

• A is wrong because disabling Real Time Metrics would affect data collection globally, not produce a neat 5-minute interval pattern for a specific operator's view.
• B is wrong because the GUI Refresh Interval controls how often the browser polls for updates, not the granularity of the underlying data points stored in the analytics engine.
• C is wrong because "Average Values" vs. "Current Values" determines the aggregation method (mean vs. snapshot), not the time resolution of the data - both would still render at 5-minute granularity under "Past 30 Minutes."

Memory tip: Think of it like a weather app - checking "current conditions" gives you a live reading updated every minute, but viewing the "past 30 minutes" chart shows you pre-bucketed historical data at a coarser interval. The timeframe drives the resolution, not the statistic type.

No community discussion yet for this question.