Rate Limiting Telemetry Signals?

[StephenPorter]

Is there any possibility of implementing a rate limit feature in the POST fleet_telemetry_config endpoint? Not seeing it anywhere in the docs at the moment. If it's on the roadmap, I would be interested to know!

Since there is now a price associated with each telemetry signal, managing rate throttling on our end has become a challenge. As far as I can tell, we need to monitor our rate each time we receive a signal and throttle by deleting the configuration from every vehicle that exceeds the desired rate. There is (of course) a lot of potential overhead to regularly pushing new fleet_telemetry_configs just to control rates. It'd be nice to have a daily rate limit on the vehicle that is enforced at the config level!

If not on the plan, any suggestions on how to practically implement this on our end?

[KarlF-KFLOE]

Simply having a billing limit at the app level (that triggers the entire fleet to stop sending telemetry) isn't sufficient or practical for our use case. Any app that is subject to the unknowns of a large, non-owned fleet and/or wants to offer some degree of "free use" really needs to be able to safeguard against runaway spending at the vehicle level.

We're in the process of designing our own mechanism to enforce a daily telemetry allowance, but pushing and revoking config to achieve this feels clunky and prone to error/delays.

Your help is much appreciated!