Are there any properties that allow us to capture images only when any errors happen in the configured flows? As of now, we can see more than 1 TB of Data utilized within 1 month and only with 2-3 flows.
Hi @shahidraza , on synthetics we do support the option CLI Options of setings --screenshots=false
to not capture screenshots, depending on your setup you can pass that flag. In that case it will not capture step snaps.
Hi @shahidraza - Just to expand on Shahzad's reply, we're looking at putting in proper lifecycle management and scenario rules on when to capture screenshots as well as how long to keep the really rich object-level detail. Whilst his solution is a good temporary fix to the significant data volumes you're seeing, I just wanted to let you know that we will be addressing this properly as well.
@shahzad31 what is the flag I can use in heartbeat.docker.yml.
I am using heartbeat.docker.yml and todo folder to run my docker synthetic environment.
Thanks for sharing the option --screenshots=false but please share the parameters which I can use in my configuration either in heartbeat.docker.yml or run.sh file.
To be clear, this needs to be present in Heartbeat as an option to be passed through, apologies for the confusion here. I'm thinking we should prioritize switching to jpeg screenshots here: Add option for JPEG screenshots · Issue #233 · elastic/synthetics · GitHub as a first step, that should cut down on file size to start with.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.