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

API for anomaly detection config #512

Open
aldrinjenson opened this issue Sep 20, 2023 · 0 comments
Open

API for anomaly detection config #512

aldrinjenson opened this issue Sep 20, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@aldrinjenson
Copy link
Contributor

  • Let's say Parseable does anomaly detection.
  • let's scope it under stream

So from the UI(console) the user can set up different parameters to watch out for anomaly

eg: to train a model for z-score, the user could pass in a JSON like the following:

{
  "start_time": "2023-09-20T08:41:11.398Z",  // training interval start timestamp
  "end_time": "2023-09-20T13:41:11.398Z", //  // training interval end timestamp
  "stream": "frontend",
  "interval_window": '1m', // string with number and a unit of (h,m,s)
  "algorithm": "z-score" // the model to be used
}

We could save this in parseable server and then an anomaly detection server or plugin could just get this from parseable whenever it requires (eg: say when it restarts).
Hence, an API for config eg: /api/v1/anomaly/config (both GET and PUT methods to get and update configs) would be great.
As soon as the config is set, parseable can then call the anomaly detection server to start training based on the this new config (or some other way based on a good architecture)

We could also have another api to list out models/algorithms etc in future maybe.

P.S. This plan is in early stages and we can ideate and discuss on better solutions too.

@nitisht nitisht added this to the Release v0.7.1 milestone Sep 22, 2023
@nitisht nitisht added the enhancement New feature or request label Sep 22, 2023
@aldrinjenson aldrinjenson mentioned this issue Oct 9, 2023
3 tasks
@nitisht nitisht removed this from the Release v0.7.1 milestone Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants