You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: