search

WiproOpenSource / galaxia

Next Generation Universal monitoring framework for infrastructure, applications & microservices
Apache License 2.0
20 stars 19 forks source link

Design galaxia alert component api #10

Open ashishjain14 opened 8 years ago

ashishjain14 commented 8 years ago

Galaxia alert api would require an integration of galaxia api running on host A with prometheus component running on host B. Following are the steps in successfully implementing CRUD with alert API

1) User sends a set of inputs to create an alert refer issue #7 2) Galaxia API layer receives the input and parses the input 3) Galaxia now creates rules in prometheus alert rules format and adds it into a rule file 4) Galaxia now updates prometheus.yml file and adds the new rule in it. 5) Galaxia now pushes these 2 files to host running prometheus 6) Galaxia now reloads prometheus configuration to reflect the changes.

Here step #5 is not an elegant way of doing this as it will required the credentials of server which is running prometheus to be shared, secondly if it may fail because of some reason and hence tracking this out may be difficult.

ashishjain14 commented 8 years ago

Probably we will have to consider using a configuration management which will trigger an auto deploy on any change to alert rules

ashishjain14 commented 8 years ago

We should support CRUD operation for alert api. the end point here could be /v1/alert. Depending on POST, GET, DELETE and PUT the api will provide functionalities for Create, Read, Delete and Update of a alert rule.

ashishjain14 commented 8 years ago

Consul to be used for configuration management