Alexey Velikiy

I think this repo should ba called `hastic/hastic` and we should move all code related to server to `hastic/server`. After that we should refactor build system here and fix links.

The analytics or server could be supstituted with another logic app. We can describe the protocol we use with tasks and try use hastic for different scenarios.

AssertionError 2 columns passed

4

 I use prometheus and get this error: 

If you create a task and then put it's promise to resolve map but analytic fails for any reason without returning any error for that task, than that task will...

Enter / Exit segment

1

What if we make two different state for detector: activated and deactivated. For example, when you are above threshold, then you are "in" and below -- out. You can apply...

We have many performance issues and we start to collect this issues, but for now this link: https://github.com/thlorenz/v8-perf

MongoDB persistence

2

Hastic has to save it's artifacts to a database. We chose [nedb](https://github.com/louischatriot/nedb/) as a small test storage which we can easily add as a requirement to run Hastic. We can't...

We have `DATA_PATH` hard coded in config. It would be nice to have option to set it as environment variable. It's useful for users and tests.

The classes in https://github.com/hastic/hastic-grafana-app/tree/master/src/panel/graph_panel/models have big overlap with https://github.com/hastic/hastic-server/tree/master/server/src/models we can make a repo which is submodule for hastic-grafana-app and hastic-server with this classes. Mirror issue: https://github.com/hastic/hastic-grafana-app/issues/377

We somehow need to define performance metrics which we want to optimize. Maybe we can create a tool for this. I propose to start with benchmarks for server (node.js) part....