Israel Fruchter

> Uh, I didn't `spot` that. Is it worth/feasible to fix this confusion? yes it worth it, we are running into it quite a lot, I think I've open issue...

seem like events weren't reported to Argus the jenkins job is gone now, so we can't really investigate, next time we need to look at it right away in such...

found more recent case of it: https://jenkins.scylladb.com/job/scylla-master/job/longevity/job/longevity-10gb-3h-gce-test/573

send mail stage failed like this: ``` 03:10:22 (no stderr) 03:10:22 ['/home/ubuntu/sct-results/20240612-235801-036873/test_id'] 03:10:22 Results file not found 03:10:23 Cleaning SSH agent 03:10:23 Agent pid 7182 killed ```

seems like we getting preemption, during the setup (i.e. running node benchmarks, which he disable recently) ``` ====================================================================== ERROR: test_custom_time (longevity_test.LongevityTest) Run cassandra-stress with params defined in data_dir/scylla.yaml ---------------------------------------------------------------------- Traceback...

from sct log, we can see we got here: ``` self.destroy_localhost() > self.stop_event_device() if self.params.get('collect_logs'): self.collect_sct_logs() with silence(parent=self, name='Cleaning up SSL config directory'): cleanup_ssl_config() self.finalize_teardown() self.argus_finalize_test_run() self.argus_heartbeat_stop_signal.set() ``` but never...

@k0machi let's send the events again, during log collection phase do we have a way to test with Argus if it got events yet or not ?

> did you ever considered to send events as they happen (not only at the end)? I mean ERROR/Critical only ones Argus need to support it first

question is when to put those default into the configuration file of the dashboard ? when we collect the, or during the show-monitor command itself. few more issues related: *...

@soyacz `update_default_time_range` should be noop, for cases we don't have monitor setup...