Skip to content
Snippets Groups Projects
Commit caf17e04 authored by Nikolay Stanchev's avatar Nikolay Stanchev
Browse files

Updates alerts test - replaced the cpu usage alert rule, causing issues when running on givry

parent 6fcf514c
No related branches found
No related tags found
No related merge requests found
......@@ -31,18 +31,18 @@ topology_template:
action:
implementation:
- http://172.40.231.200:9999/
high_cpu_usage:
description: This event triggers when the cpu system usage is too high.
increase_in_running_processes:
description: This event triggers when the max number of running processes increases.
event_type: threshold
metric: cpu.usage_system
metric: processes.running
condition:
threshold: 10
granularity: 10
aggregation_method: mean
threshold: 1
granularity: 12
aggregation_method: max
resource_type:
flame_location: DC1
flame_sfp: nginx
comparison_operator: lte
comparison_operator: gte
action:
implementation:
- http://172.40.231.200:9999/
......
......@@ -54,7 +54,7 @@ def rspec_config():
return data_loaded
@fixture(autouse=True, scope="module")
@fixture(scope="module")
def set_up_tear_down_fixture(rspec_config):
"""
Set up/tear down fixture for the alerts integration test.
......
......@@ -85,7 +85,7 @@ topology_template:
Bristol: eu.ict-flame.sfe.state.lifecycle.connected
tigger_b:
condition:
constraint: clmc::high_cpu_usage
constraint: clmc::increase_in_running_processes
period: 600 # integer required, unit: seconds
action:
frontend:
......
......@@ -35,7 +35,7 @@ NGINX_PORT = 80
class TestAlerts(object):
def test_alert_triggers(self, rspec_config):
def test_alert_triggers(self, rspec_config, set_up_tear_down_fixture):
"""
Test is implemented using the following steps:
* Send clmc service a TOSCA alert spec. file
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment