New Relic showing wrong RPM for transaction while selecting for longer ranges

I am monitoring transaction throughput(RPM) for 7 days through New relic enterprise edition then it shows correct data but when I change date range for 3 months it shows wrong measurement for the same 7 days.

What exactly do you mean by wrong? Could it be aggregation?

For instance, when you are looking at 7 days, you are probably looking at a period of some hours. Usually apps have a peak of activity during some hours of the day, and much less activity on other hours of the day.
Now when you look at 3 months, you are likely looking at a period of one or more days. So the peaks in throughput (RPM) will be diluted with the periods of less activity.

1 Like