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

[BUG] Overview page Requests/sec incorrect. #86

Closed
azilber opened this issue Aug 11, 2014 · 10 comments
Closed

[BUG] Overview page Requests/sec incorrect. #86

azilber opened this issue Aug 11, 2014 · 10 comments

Comments

@azilber
Copy link

azilber commented Aug 11, 2014

I'm seeing '85070586659632214952926045871129231360,000' Requests/sec for every entry (3 sites).

This is a dev server with maybe 5 requests/sec.....

@azilber
Copy link
Author

azilber commented Aug 11, 2014

Seeing more of the same for newly accessed hosts:

screen shot 2014-08-11 at 4 59 42 pm

@azilber
Copy link
Author

azilber commented Aug 11, 2014

The graph looks messed up as well:

screen shot 2014-08-11 at 5 15 58 pm

@azilber
Copy link
Author

azilber commented Aug 12, 2014

I'm still seeing the issue, any ideas?

screen shot 2014-08-12 at 11 16 41 am

@azilber
Copy link
Author

azilber commented Aug 12, 2014

It looks like the generated data is wrong... looks like maybe an issue with the cron generator:
MariaDB [pinba]> SELECT created_at, avg(req_per_sec) as req_per_sec FROM ipm_report_by_hostname_and_server limit 10;
+---------------------+-----------------------+
| created_at | req_per_sec |
+---------------------+-----------------------+
| 2014-08-11 01:28:40 | 1.6774481876547198e37 |
+---------------------+-----------------------+
1 row in set (0.00 sec)

@azilber
Copy link
Author

azilber commented Aug 12, 2014

It seems some of the ipm data logged is in exponential format...

MariaDB [pinba]> SELECT created_at, req_per_sec FROM ipm_report_by_hostname_and_server limit 10;
+---------------------+-------------+
| created_at | req_per_sec |
+---------------------+-------------+
| 2014-08-11 01:28:40 | 3.40282e38 |
| 2014-08-11 01:28:40 | 3.40282e38 |
| 2014-08-11 01:28:40 | 3.40282e38 |
| 2014-08-11 01:30:01 | 0.0521437 |
| 2014-08-11 01:30:01 | 0.0834299 |
| 2014-08-11 01:30:01 | 0.0023175 |
| 2014-08-11 01:45:01 | 0.0499432 |
| 2014-08-11 01:45:01 | 0.0635641 |
| 2014-08-11 01:45:01 | 0.00340522 |
| 2014-08-11 02:00:01 | 0.051168 |
+---------------------+-------------+

@azilber
Copy link
Author

azilber commented Aug 12, 2014

Truncating the table seems to have fixed it for now....

@azilber
Copy link
Author

azilber commented Aug 12, 2014

And looks like it didn't help at all. Any ideas?

screen shot 2014-08-12 at 1 16 27 pm

@azilber
Copy link
Author

azilber commented Aug 15, 2014

Going through the pinba data, it looks like the following pinba tables may have wrong data:

report_by_hostname
INSERT INTO report_by_hostname VALUES (425,3.40282e38,103.853,100,3.40282e38,37.6142,100,3.40282e38,0.0301947,100,3.40282e38,1070.34,100,3.40282e38,'XXXX.com',1526500,100,0.0518176,NULL);

report_by_hostname_and_schema
INSERT INTO report_by_hostname_and_schema VALUES (425,3.40282e38,103.853,100,3.40282e38,37.6142,100,3.40282e38,0.0301947,100,3.40282e38,1070.34,100,3.40282e38,'XXXX.com','',1526500,100,0.0518176,':XXXX.com');

report_by_hostname_and_script
report_by_hostname_and_server
report_by_hostname_and_status
...

It's looking like it might be an engine problem....

@azilber
Copy link
Author

azilber commented Dec 3, 2014

Why was this closed? Issue is unresolved.

@muxx
Copy link
Member

muxx commented Dec 7, 2014

Because It is issue of pinba, not Pinboard.

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

No branches or pull requests

2 participants