Israel Fruchter

I've played a bit with vector yesterday, I've checked the configuration capabilities something like the following, can generate same output logs as we expect in SCT: ```yaml data_dir: "/var/lib/vector" sources:...

next phase would be to install on nodes, and send the data back to sct-runner

@mykaul FYI, vector isn't installed in SMI in general we are running into multiple issue with mirrors of EPEL and such, hopefully installing vector is easier and more stable

> I wonder what https://vector.dev/docs/reference/vrl/functions/#parse_syslog is for and if it's useful here. it's backward to what I need, I want to present the logs in specific type of output

> [@fruch](https://github.com/fruch) the config looks quite complicated and possibly taking some CPU power of nodes. Maybe we could align with format as in scylla-cloud instead of specific for SCT one?...

@pehala you'll now need to update the sub-module in dtest

I can confirm it work, like the following ``` uv python install 3.11 uv venv -p 3.11 ~/ttt source ~/ttt/bin/activate python -m pip install https://github.com/pehala/scylla-ccm/archive/refs/heads/change-version.zip ccm --help ``` with master...

The direction is something we sure want, but this change alone isn't really getting us any closer to that target. We do have examples of nemesis that were written outside...

> > The direction is something we sure want, but this change alone isn't really getting us any closer to that target. > > I can use this PR to...

similar error happen to me as well: https://github.com/scylladb/scylla-cluster-tests/actions/runs/12040015357/job/33569050808 I tried adding `docker.io`, it didn't helped getting the exact traceback with this `Expected content to change!` ``` updater | 2024/11/26 22:23:52...