scala-academy / performance-analysis

This is a project to be used in the "Scala and akka in practise" course
Other
5 stars 3 forks source link

Rule administration #63

Open effibennekers opened 8 years ago

effibennekers commented 8 years ago

As an administrator I would sometimes like to administer some alerting rules. This includes getting a listing of registered alerting rules and being able to clear them.

Given the server is running and I registered component "logsObtainableComp" with a metric with metric-key "a-numerical-metric" And an alerting rule has been registered to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules with payload {"threshold": {"max": "2000 ms"}, "action": {"url": "dummy-action"}} When I do a GET to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules Then the result should have statuscode 200 And the content should contain "{"threshold": {"max": "2000 ms"}, "action": {"url": "dummy-action"}}"

Given the server is running and I registered component "logsObtainableComp" with a metric with metric-key "a-numerical-metric" And an alerting rule has been registered to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules When I do a DELETE to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules Then the result should have statuscode 204

Given the server is running and I registered component "logsObtainableComp" with a metric with metric-key "a-numerical-metric" And an alerting rule has been registered to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules When I do a DELETE to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules And I do a GET to /components/logsObtainableComp/metrics/a-numerical-metric/alerting-rules Then the result should have statuscode 404

geerdink commented 8 years ago

Dependent on #38