42356821ad
Missing communication between analytics and server in production #91 ( #95 )
...
* analytics ipc config via env vs dev mode
* binding to zmq before child python start
* better usage of ipc and handling server process stopping
* ipc via /tmp
* ZQM_DEV_PORT to config
6 years ago
72e8c4520e
LF eol in all files & add doc about that & setting to settings.json
6 years ago
aba8f97a8d
data_service, renamings and detectors imports
6 years ago
29e0243d6b
refactor zmq-releated logic from server.py to ServerService
6 years ago
cccbf1193b
asyncio usage ( #88 )
...
* asyncio integration (buggy)
PEAKS_DETECTION doesnt works
6 years ago
1e11be2657
worker.py fix
6 years ago
9da8bbcf11
worker->analytic_worker
6 years ago
02160209e2
Server/Analytics - Client/Server switch #75 & #74 & #72
6 years ago
f7a63cefaf
small refactoring
6 years ago
081b9607cb
Use anomaly IDs #42
6 years ago
56969bdb9d
__task_id -> _taskId
6 years ago
rozetko
e85df8c2c1
Change anomaly id to predictor id everywhere ( #65 )
...
* Change anomaly id to predictor id everywhere
* some fiex
6 years ago
rozetko
c9722abf76
Fix analytics error "the JSON object must be str, not 'bytes'"
6 years ago
52b3a1286d
Analytics server messaging #24 v2 ( #49 )
...
* add zmq to deps
* basic zmq usage & build system fxs
* continue zmq integration & refactorings
* server.py + logging
* some commit
* ping-pong server-analytics & pair type
* packing zmq.node for production
6 years ago
Alexey Velikiy
rozetko