You can pretty much ask anything Jetson NX in this forum. It is better to start new threads if the topic changes, but this is still about disk filling up. In regards to that, which directories are filling up? This offers a clue as to the cause.
I’ve never heard of any limitations on run time, but there are different “models” of choosing power consumption which might be faster/slower, but produce more/less heat, but so far as I know, as long as the unit is kept at a suitable temperature, you can run this 24/7. Someone else will probably have a more explicit answer.
The diversion of logs to another computer will be no different on the Jetson than it is for any other desktop Ubuntu. I haven’t used it, but here is an example article:
Here is one more specific (which is probably what you want if you are logging from one computer to another):
Note that in the above I am assuming you are talking about something other than just mounting another drive to hold local log content, and want to actually redirect logging to another computer on the network.
I’m not sure it makes sense to divert cache to another computer. Technically you could do something like create an iSCSI partition on another host, and then use that to mount on a temp or cache location (iSCSI can be complicated, but performance is very good). The down side is that if anything stops this from functioning, even momentarily, then probably the system would crash and behave badly until rebooted.
Note that local memory getting used up over time, if not from running more programs, is a “memory leak” bug. It should not do this no matter how much time the system runs. If it does, then you can ask to get a memory leak bug fixed by showing how to produce the leak.