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.

Sign up for GitHub

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

Jump to bottom

Care about counter reset and max #4

Closed
maddyblue opened this issue Jan 31, 2014 · 1 comment
Closed

Care about counter reset and max #4

maddyblue opened this issue Jan 31, 2014 · 1 comment

Comments

@maddyblue
Copy link
Contributor

Our WMI counters are uint64s, but opentsdb only accepts int64s. Thus, our big counters could roll over. We should convert these data to int64s so opentsdb doesn't start throwing errors at us, and, since the conversion could render them negative, should start to use the counter max values.
@maddyblue
Copy link
Contributor Author

Docs for the query string format: http://opentsdb.net/docs/build/html/api_http/query/index.html#metric-query-string-format

maddyblue added a commit that referenced this issue Dec 4, 2014
@maddyblue
cmd/scollector: Ignore lacking redis config file
f45024e 
fixes #4
@maddyblue maddyblue mentioned this issue Dec 4, 2014
Closed
hermanschaaf pushed a commit to hermanschaaf/bosun that referenced this issue Sep 11, 2018
Merge pull request bosun-monitor#4 from data-platform/revert-3-DATA-5…
979d365 
…355-forward-tracing-headers

Revert "DATA-5355: Forward referer header from grafana to opentsdb"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maddyblue