Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum values in statistics can be incorrect #59

Closed
GoogleCodeExporter opened this issue Jun 25, 2015 · 4 comments
Closed

Maximum values in statistics can be incorrect #59

GoogleCodeExporter opened this issue Jun 25, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

In the report, values in the column "Maximum" of the statistics for the periods 
Day, Week, Month, Year or Customized.
For example, the maximum value in statistics for the period Day can be the 
maximum value of the same request for the period Week or Month.

This issue does not concern the values in the graphics which are correct.

Original issue reported on code.google.com by evernat@free.fr on 9 Nov 2010 at 6:51

@GoogleCodeExporter
Copy link
Author

It is fixed in trunk of svn (revision 1398) and ready for next release (v1.22).
A new build of the trunk with the fix is available for download:
http://javamelody.googlecode.com/files/javamelody-20101109.jar

Thanks to my colleague Benoit and to Pether Sorling for informations on this 
issue.

Original comment by evernat@free.fr on 9 Nov 2010 at 7:04

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Dear Emeric,

I studied our Javamelody Reports from Production and I also discovered this 
bug. I am very happy that it is already fixed. A question to that:

Is it a problem of the reporting or the monitoring? I mean, by switching to 
v1.22 but keeping the data collected by javamelody will solve the problem?

Thanks in advance!
Géza

Original comment by tak...@gain.nyme.hu on 24 Jan 2011 at 11:07

@GoogleCodeExporter
Copy link
Author

It is a problem of the monitoring, but you can certainly keep the data 
collected:
it will be displayed but with the "false" values for some time and:
- there should be no more incorrect values for the day period after 24h
- there should be no more incorrect values for the week period after 7 days
- there should be no more incorrect values for the month period after 1 month
- there should be no more incorrect values for the year period after 1 year

Emeric

Original comment by evernat@free.fr on 24 Jan 2011 at 9:39

@GoogleCodeExporter
Copy link
Author

Thank you for the quick reply.
Géza

Original comment by tak...@gain.nyme.hu on 25 Jan 2011 at 8:53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant