NetApp Harvest Graphite Issue
2017-04-11 10:30 PM
I dumped database information with the following command.
# Whisper- dump.py rx_bytes_per_sec.wsp
There are places where information can be acquired and places where information can not be obtained.
4071: 1491891300, 0.02686699231414656598650479679690761259
4072: 0, 0
4073: 0, 0
· Why is "0" displayed?
· Is it OK even if "0" is displayed?
· There are places where "0" is displayed for a long period of time.
Since information can not be obtained from Filre, will it become "0"?
1 REPLY 1
Re: NetApp Harvest Graphite Issue
2017-04-24 05:58 AM
Graphite's whisper db creates .wsp files that have one or more internal archives that support some number of points at some resolution. The whisper-dump output is basically showing (index id: timestamp, value). In a fresh system most of the points would be emply showing 0,0 for timestamp,value. Even on a longer running system where the datapoints have passed the retention and wrapping would occur I have seen that the output is not always in order.
So for your question, if you see 0,0 as timstamp,value it simply means that index in the file hasn't been used yet or no data was submitted for a given index. If you are trying to relate this datapoints where Harvest didn't, or was unable to submit values, then whisper-fetch.py might be a better utility to use:
# whisper-fetch.py --help Usage: whisper-fetch.py [options] path Options: -h, --help show this help message and exit --from=_FROM Unix epoch time of the beginning of your requested interval (default: 24 hours ago) --until=UNTIL Unix epoch time of the end of your requested interval (default: now) --json Output results in JSON form --pretty Show human-readable timestamps instead of unix times
Hope this helps!
Solution Architect - 3rd Platform - Systems Engineering NetApp EMEA (and author of Harvest)
Blog: It all begins with data
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!