[docs] Update usage docs for sending logs to IP
@@ -64,7 +64,6 @@ When the task-schedule is executed multiple times, timers related to compilation
The options `-Dtornado.profiler=True -Dtornado.log.profiler=True` print a full report only when the method `ts.getProfileLog` is called.
-
### Save profiler into a file
Use the option `-Dtornado.profiler=True` `-Dtornado.profiler.dumps.dir=FILENAME`. `FILENAME` can contain the finename and the full path (e.g. profiler-log.json).
@@ -205,8 +204,12 @@ $ cat tornado-features.json
```
### Save features into a file
-Use the option `-Dtornado.feature.extraction=True` `-Dtornado.features.dump.dir=FILENAME`. `FILENAME` can contain the finename and the full path (e.g. features.json).
+Use the option `-Dtornado.feature.extraction=True` `-Dtornado.features.dump.dir=FILENAME`. `FILENAME` can contain the filename and the full path (e.g. features.json).
### Send log over a socket.
-Use the option `-Dtornado.dump.to.ip=IP:PORT`.
\ No newline at end of file
+TornadoVM allows redirecting profiling and feature extraction logs to a specific port. This feature can be enabled with the option `-Dtornado.dump.to.ip=IP:PORT`.
+The following example redirects the profiler output to the localhost (127.0.0.1) and to a specified open port (2000):
+```bash
+$ tornado -Dtornado.profiler=True -Dtornado.dump.to.ip=127.0.0.1:2000 uk.ac.manchester.tornado.examples.VectorAddInt 100000
+```
\ No newline at end of file
