-
Notifications
You must be signed in to change notification settings - Fork 191
introduce VMAnomalyModel and VMAnomalyScheduler #1472
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
base: master
Are you sure you want to change the base?
Conversation
7b569bb to
a7fc951
Compare
840964f to
9e5ab0f
Compare
f41gh7
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's required to add documentation in first place. Is it possible that model could interfere on each other? Is it required to config VMAnomaly itself somehow? What is a relations between VMAnomaly and VMAnomalyModel?
Currently it's not possible to use this new API.
Also, I suggest to add -configCheckInterval to the vmanomaly in the same way as other components have it. It solves configuration reload without need of external config reloaders.
|
removed config reloader since python watchdog, which implements hot reload listens to fs events |
0ec9f87 to
1ba5e13
Compare
1ba5e13 to
4558e7c
Compare
|
added scheduler CR, added docs |
1b8eb91 to
2216f0a
Compare
2216f0a to
d0a06c0
Compare
66eac73 to
bfc5203
Compare
cdea53b to
5914c18
Compare
5906c87 to
e4fa7eb
Compare
e4fa7eb to
6ff94d9
Compare
6ff94d9 to
43d711a
Compare
43d711a to
705f5b3
Compare
705f5b3 to
39439b5
Compare
f2ca6be to
3ea8911
Compare
b5b1dfe to
3def4c6
Compare
3def4c6 to
4573011
Compare
starting 1.25.0 anomaly supports hot-reload, adding VMAnomalyModel and VMAnomalyScheduler CRs for VMAnomaly dynamic configuration