Right now, I am using the car’s built in CAN monitoring application. It is only accessible in diagnostic or developer mode, which is not something that you can get to without having access to tesla toolbox (Which only SCs and authorized body shops have at the moment), or by seriously hacking apart your car (like I’ve done).
This data is readily accessible on the car’s PT can bus, but nobody has yet created a reasonable complete “decoder ring” for those messages yet. (We know/have reverse engineered a few, including someone of the ones from my screenshot but most remain unidentified at this point).
The BT OBD interfaces are not really fast enough to stream the Tesla’s CAN data without dropping frames, but are fine for mostly static data... if you have one fan DB the needed cable to connect to your TDC connector under your CID), then get TMSpy. You’ll be able to see/decode at least some data. Note that the car’s actual OBD port is useless, so you do need to connect to the TDC to collect any actual data.
I recently got a panda, which can log up 3 busses at full speed over USB or WiFi; I am looking to make a logging app for it, but that will take some time. Their web based Cabana app is actually pretty handy too.