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.

Sign up for GitHub

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

Jump to bottom

Rule administration #63

Open
effibennekers opened this issue Apr 20, 2016 · 1 comment
Open

Rule administration #63

effibennekers opened this issue Apr 20, 2016 · 1 comment
Assignees
@Neojume
Labels
in progress

Comments

@effibennekers
Copy link
Contributor

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
@effibennekers effibennekers changed the title Rule registration Rule administration Apr 20, 2016
@effibennekers effibennekers changed the title Rule administration Alerting Rule administration Apr 20, 2016
@jordi133 jordi133 changed the title Alerting Rule administration Rule administration Apr 20, 2016
@jordi133 jordi133 added the ready label Apr 20, 2016
@Neojume Neojume self-assigned this Apr 20, 2016
@Neojume Neojume added in progress and removed ready labels May 4, 2016
@geerdink
Copy link
Contributor

geerdink commented May 4, 2016

Dependent on #38

Neojume added a commit that referenced this issue May 18, 2016
@Neojume
Merge branch 'develop' of https://github.com/scala-academy/performanc…
1f88d9e 
…e-analysis into feature/#63-rule-administration

Conflicts:
	src/it/scala/performanceanalysis/ComponentRegistrationTest.scala
	src/it/scala/performanceanalysis/base/IntegrationTestBase.scala
	src/main/scala/performanceanalysis/LogParserActor.scala
	src/main/scala/performanceanalysis/administrator/AdministratorActor.scala
	src/test/scala/performanceanalysis/LogParserActorSpec.scala
effibennekers added a commit that referenced this issue May 25, 2016
@effibennekers
Merge pull request #82 from scala-academy/feature/#63-rule-administra…
56e6177 
…tion

Feature/#63 rule administration [WIP]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Neojume Neojume

Labels
in progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@geerdink @Neojume @jordi133 @effibennekers