Pub/Sub requirement seems to be overkill

[netdata-be]

Currently this project relies to the following:

• Tesla Telemetry reference implementation => Pub/Sub
• PubSub HTTP post => this websocket project
• Teslamate ( or any other legacy streaming API ) => this web socket project

I think the hurdle ( and the costs) of having Pub/Sub is overkill for most projects, It would make more sense to directly do an HTTP post towards this project. There is a PR open to implement a HTTP dispatcher.

https://github.com/teslamotors/fleet-telemetry/pull/91

Would create a cleaner integration, the issue with the HTTP dispatcher is that it is does not support ACK, but currently I think having the Pub/Sub http post does not ack the messages as well, so no difference here.

[jlestel]

I agree, it's overkill, but it was the quickest way for me while waiting for the http dispatcher PR you mentioned to be merged.