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
Per the specification available at https://github.com/b/statsd_spec, gauges can take any uint64 value and counters can take any int64 value. Using an int for gauge raises the possibility of measuring a negative number, or attempting to pass a value that's too large for the int type on a given machine.
Should we change the type definitions to better match the specification?
The text was updated successfully, but these errors were encountered:
Per the specification available at https://github.com/b/statsd_spec, gauges can take any uint64 value and counters can take any int64 value. Using an int for gauge raises the possibility of measuring a negative number, or attempting to pass a value that's too large for the int type on a given machine.
Should we change the type definitions to better match the specification?
The text was updated successfully, but these errors were encountered: