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

Possible issue with new tcollector collector. #315

Closed
johann8384 opened this issue Apr 14, 2016 · 1 comment
Closed

Possible issue with new tcollector collector. #315

johann8384 opened this issue Apr 14, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@johann8384
Copy link
Member

Hello

I recently standardized all our dev servers on on tcollctor 1.3.0. Since doing so, I have been getting these errors across the entire lot:

2016-04-07 15:57:56,403 tcollector[28152] ERROR: Timestamp out of order: metric=tcollector.mem_bytes name=python type=rss, old_ts=1460069860 >= new_ts=1460069860 - ignoring data point (value='11309056', collector=tcollector.py)
2016-04-07 15:57:56,403 tcollector[28152] ERROR: Timestamp out of order: metric=tcollector.cputime name=python, old_ts=1460069860 >= new_ts=1460069860 - ignoring data point (value='4', collector=tcollector.py)

It doesn't look like those metrics have had anything written since deploying 1.3.0. I haven't looked into this any further than to verify /proc/$proc_id/mem and cpu set contain a strange character or an error. Thought I would ask here before digging into it. Thanks for any info.

-Anna

@johann8384 johann8384 self-assigned this Apr 14, 2016
@johann8384 johann8384 added the bug label Apr 14, 2016
@johann8384 johann8384 added this to the 1.3.2 milestone Apr 14, 2016
@benrubson
Copy link
Contributor

See #337 which solves this 👍

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

No branches or pull requests

2 participants