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 propose changing this flag to a Float64Var to allow non-integer rates. My specific use case is to set this value to something like 0.2, to send a metric once every 5 seconds. Currently, the slowest rate I can set is 1, exporting a metric every second (which is an aggressive rate).
Describe the solution you'd like
Support rates <1/second
Describe alternatives you've considered
We could also use rate.Every() to specify something like this, which might be clearer. But this just parses to a rate.Limit, so I think it is just syntactical sugar
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
cmd/telemetrygen
Is your feature request related to a problem? Please describe.
Using float values in
--rate
returns the following error:The
--rate
flag for telemetrygen is an Int64Var, however this is ultimately parsed to arate.Limit
value, which is an alias for float64.I propose changing this flag to a Float64Var to allow non-integer rates. My specific use case is to set this value to something like
0.2
, to send a metric once every 5 seconds. Currently, the slowest rate I can set is1
, exporting a metric every second (which is an aggressive rate).Describe the solution you'd like
Support rates <1/second
Describe alternatives you've considered
We could also use
rate.Every()
to specify something like this, which might be clearer. But this just parses to arate.Limit
, so I think it is just syntactical sugarAdditional context
No response
The text was updated successfully, but these errors were encountered: