rubenf
rubenf13mo ago

remote workers

they just need to connect to the same db
8 Replies
Alper
Alper13mo ago
i did that and get this in the logs:
flickvibe-remote-windmill_worker-1 | 2023-10-09T08:26:00.904212Z INFO job_run: windmill_audit: operation="redacted" action_kind=Execute resource="EE only" parameters={"redacted":"-"}
flickvibe-remote-windmill_worker-1 | 2023-10-09T08:26:00.904212Z INFO job_run: windmill_audit: operation="redacted" action_kind=Execute resource="EE only" parameters={"redacted":"-"}
does that mean i can't use remote workers without EE?
rubenf
rubenf13mo ago
no you can, you just don't get audit logs
Alper
Alper13mo ago
does that mean there is no way to see the logs of the scripts that run inside the remote worker?
rubenf
rubenf13mo ago
audit logs != logs there are no difference between remote workers and normal workers they're all just workers
Alper
Alper13mo ago
you are right, i can't see logs in the other workers too, sorry for the confusion
rubenf
rubenf13mo ago
you can see logs, but audit logs in particular are redacted you still have the script logs and a lot of other logs
Alper
Alper13mo ago
i see logs like these:
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:31.163849Z INFO request: windmill_api::tracing_init: response latency=6 status=200 method=GET uri=/api/w/flickvibe/variables/get_value/u/Alp/MONGODB_PASS username="Alp" email="*******@gmail.com" workspace_id="flickvibe"
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:31.580542Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:32.079995Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:32.580221Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.410795Z INFO windmill_worker::common: child process 'python run' for 018b13a1-7411-213f-37e4-66287aa69c12 took 6332ms job_id=018b13a1-7411-213f-37e4-66287aa69c12
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.411636Z INFO windmill_worker::worker: finished Python3 job 018b13a1-7411-213f-37e4-66287aa69c12 worker_name=wk-82b4116318c2-4Grpu job_id=018b13a1-7411-213f-37e4-66287aa69c12 workspace_id=flickvibe is_ok=true
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.424279Z INFO windmill_worker::worker_flow: update flow status id=018b13a1-6635-b547-16a5-e720657393b1 root_id=none
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:31.163849Z INFO request: windmill_api::tracing_init: response latency=6 status=200 method=GET uri=/api/w/flickvibe/variables/get_value/u/Alp/MONGODB_PASS username="Alp" email="*******@gmail.com" workspace_id="flickvibe"
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:31.580542Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:32.079995Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:32.580221Z INFO windmill_worker::common: 018b13a1-7411-213f-37e4-66287aa69c12 in flickvibe still running. mem peak: 62840kB
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.410795Z INFO windmill_worker::common: child process 'python run' for 018b13a1-7411-213f-37e4-66287aa69c12 took 6332ms job_id=018b13a1-7411-213f-37e4-66287aa69c12
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.411636Z INFO windmill_worker::worker: finished Python3 job 018b13a1-7411-213f-37e4-66287aa69c12 worker_name=wk-82b4116318c2-4Grpu job_id=018b13a1-7411-213f-37e4-66287aa69c12 workspace_id=flickvibe is_ok=true
flickvibe-hq-windmill_worker-3 | 2023-10-09T08:50:36.424279Z INFO windmill_worker::worker_flow: update flow status id=018b13a1-6635-b547-16a5-e720657393b1 root_id=none
what would be particularly interesting is flow/script output, but that does not seem to appear it makes total sense to not have them there, but would be nice to have a flag to forward flow output to worker logs
rubenf
rubenf13mo ago
👍