dfir

Obviously, this is a mistake on my part, but I assume we want zeek to fail a little cleaner.

event zeek_init(){
	local sh: string = "";
	local gi =  global_ids();
        for (myfunc in gi) {
		if(gi[myfunc]?$value){
			if(strstr(myfunc,"lambda") > 0){
				sh = sha256_hash(gi[myfunc]$value);
				print(sh);
			}
		}
	}
}

Is your feature request related to a problem? Please describe.
I'm always frustrated when I upload a timeline via the web UI and it times out.

Describe the solution you'd like
I'd like the form for uploading the files to also list a CLI command (with a link to docs) for uploading files.

Describe alternatives you've considered

1. Update our docs so the default timeout for the w

I was wondering the benefit of using Modular File Management vs Single Config File Management? Why do you consider it easier to use multiple files and then compile? Trying to figure out what the best case is for my use case. Thanks. #

Right now a lot of the logging from the tasks does not get propagated back to the user, so we should make sure that all of the tasks are adding logs and errors to the results so that at minimum the data gets put into the worker-log.txt. Ideally we would store this info in datastore so that the clients could query it later (this part is in #115).