The most important thing is to pull a log from the car every couple of months so you keep a complete detailed history.
If you drive a lot, capturing log files every couple of months won't give you a complete record. It's the one-second drive records that fill up the detailed transient section. That section fills up with about 60 hours of driving, give or take a couple of hours. Distance doesn't matter; it's time driving.
I just analyzed all of my log files. I see log files that cover anywhere from 29 days to 4 months, between 1500 and 2100 miles, but the driving time is in the narrow band between 58 and 62 hours.
I try to grab a log file once a month, or after any significant road trip.
If you want to know how often to capture your log file, just run one of your files through my parser with no command line options. You'll see a summary of your driving and charging sessions. Note how far back that history goes. That should give you an idea of how often you need to download the log file, more often if you're doing an unusual amount of driving, less often if you do less driving.
There are a couple of potential issues with service calls...
Occasionally, the techs will do something that erases the log file. So, it's a good idea to grab a log file just before each service visit.
Tesla has a way to turn on more verbose logging which dumps a record every second, 24x7. That drops the cycle time to about a week. This issue seems to be a rare problem, but it's a good idea to take a look at your log file to make sure things look right especially if you're about to do a drive that you want to capture in the logs.
I'll add this stuff to my page, and the next release of my parser will show a warning if your log looks like it's capturing verbosely.