Closed PyDeps closed 1 year ago
elastalert is no longer maintained. Use elastalert2. https://github.com/jertel/elastalert2
@PyDeps
If you install with "python setup.py install", the library will be installed with the following setup.py settings. The "requirements.txt" you are pointing out is when you install by directly specifying "requirements-dev.txt" or "requirements.txt". "Requirements.txt" is for development and is slightly out of sync with setup.py. elastalert2 is in sync.
'apscheduler>=3.3.0',
'aws-requests-auth>=0.3.0',
'blist>=1.3.6',
'boto3>=1.4.4',
'configparser>=3.5.0',
'croniter>=0.3.16',
'elasticsearch==7.0.0',
'envparse>=0.2.0',
'exotel>=0.1.3',
'jira>=2.0.0',
'jsonschema>=3.0.2',
'mock>=2.0.0',
'prison>=0.1.2',
'PyStaticConfiguration>=0.10.3',
'python-dateutil>=2.6.0,<2.7.0',
'PyYAML>=3.12',
'requests>=2.10.0',
'stomp.py>=4.1.17',
'texttable>=0.8.8',
'twilio>=6.0.0,<6.1',
'cffi>=1.11.5'
@PyDeps
If you really want to use yelp / elastalert, fork and maintain it yourself. Don't ask other people for help. No one can help. This repository is dead. Please understand that fact first.
@PyDeps
yelp / elastalert does not support elasticseach8 or opensearch. It doesn't work with python 3.9 / 3.10. Line, zabbix, stomp and pagertree alerts don't work properly. There are many other bugs. If you can't maintain it yourself, use elastalert2.
@PyDeps
Did you understand?
OK
Hi, In elastalert, inappropriate dependency versioning constraints can cause risks.
Below are the dependencies and version constraints that the project is using
The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict. The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project, The version constraint of dependency elasticsearch can be changed to >=0.4.1,<=1.0.0.
The above modification suggestions can reduce the dependency conflicts as much as possible, and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
The calling methods from the elasticsearch
The calling methods from the all methods
Could please help me check this issue? May I pull a request to fix it? Thank you very much.