Description

I adapted two monitoring jobs to the repository pattern introduced in #624 :

• MonitorHoneypots
• MonitorLogs

Should have done this in #624 , sorry about that.

Note: in MonitorHoneypots I intentionally ignored Cowrie and Log4j since they will be in the GeneralHoneypot table soon anyway.

Also note: I did not write tests for the new methods yet. I will open an issue for that since we have a lot of new contributors and writing tests is a good first issue in my opinion.

Related issues

• closes Missing ElasticJob Class Definition #648

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue).

Checklist

• I have read and understood the rules about how to Contribute to this project.
• The pull request is for the branch develop.
• I have added documentation of the new features.
• Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
• I have added tests for the feature/bug I solved. All the tests (new and old ones) gave 0 errors.
• If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
• If the GUI has been modified:
  • I have a provided a screenshot of the result in the PR.
  • I have created new frontend tests for the new component or updated existing ones.

Important Rules

• If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
• If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
• Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.