Tomás Lima

The new version that is under testing (https://github.com/certtools/intelmq-beta) is possible to enable 'load_balance' which is in the reality a splitte. https://github.com/certtools/intelmq-beta/blob/master/intelmq/lib/pipeline.py#L82 What do you think about the idea? Is not...

Parsers will have the load_balance option equal True, so they will send one event to cymru-1 and second one to cymru-2, and so on... PS: manager graph will need the...

@aaronkaplan check the code and propose. Its a little bit hard to get a simple solution like the current one.

@aaronkaplan I think we miss something in the picture. Look carefully to arrows and you will see: collector -> parser -> experts -> output To be clear, new image: 

> Do you want to work on these issues or should I revise this bot? I did some work on this one. Waiting confirmation from @aaronkaplan https://github.com/aaronkaplan/intelmq/pull/1

@wagner-certat validate the following please: Is this situation happens in Parsers, Experts and Outputs? I think it only happens with Collectors which I think is "ok", although if there is...

> There's no difference in dump files handling for the bot types. This is the case for every kind of bot. Correct me if I'm wrong but if a KeyboardInterrupt...

Ok, so dump file will be always corrupted on the scenario that you present and data loss will just happens on Collectors which is something that we are already aware...

Ok, after talked on IRC with @wagner-certat I understood that the problem here is the fact that all dumped data is loaded when bot needs to dump new bad events...

_If you are looking for ATT&CK represented in STIX 2.1, please see the [attack-stix-data](https://github.com/mitre-attack/attack-stix-data) GitHub repository. Both MITRE/CTI (this repository) and attack-stix-data will be maintained and updated with new ATT&CK...