Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[discussion] Mispwarninglist analyzer speed issue and proposed improvement #731

Closed
dadokkio opened this issue Mar 26, 2020 · 1 comment
Closed
Assignees
Labels
category:enhancement Issue is related to an existing feature to improve scope:analyzer Issue is analyzer related
Milestone

Comments

@dadokkio
Copy link
Contributor

It happens that we run this analyzer on multiple osservable and then the server situation is something like:

immagine

All the scripts runs for dozens of hours and nothing else can be run until they finish so we decided to change approach.
Our solution is to put everything on a postgres database and search it if enable.
You still need to pull lists as usual and then with a script provided you can insert them on the database. The script provides also a simple validation in order to avoid entering invalid tld or wrong ip.

The results and template are very similar, the main difference is timing.

@jeromeleonard jeromeleonard added this to the 2.7.0 milestone Apr 6, 2020
@jeromeleonard jeromeleonard added scope:analyzer Issue is analyzer related category:enhancement Issue is related to an existing feature to improve labels Apr 6, 2020
@garanews
Copy link
Contributor

garanews commented May 1, 2020

new version available in 2.7.0

@garanews garanews closed this as completed May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:enhancement Issue is related to an existing feature to improve scope:analyzer Issue is analyzer related
Projects
None yet
Development

No branches or pull requests

3 participants