And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

And referred sink must have active state on response within 120 seconds

And 20 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Sink idle after 5 minutes without metrics flow

Given the Orb user has a registered account

And the Orb user logs in

When stop the orb-agent container

Then referred sink must have idle state on response after 660 seconds

Scenario: Sink with invalid endpoint

Given the Orb user has a registered account

And the Orb user logs in

And no dataset should be linked to the removed group anymore

And 0 dataset(s) have validity valid and 4 have validity invalid in 30 seconds

Scenario: Sink with invalid username

Given the Orb user has a registered account

And the Orb user logs in

And referred sink must have error state on response within 120 seconds

And 4 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Sink with invalid password

Given the Orb user has a registered account

And the Orb user logs in

And last container created is exited after 120 seconds

And 2 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Edit sink active and use invalid remote host

Given the Orb user has a registered account

And the Orb user logs in

Then referred sink must have error state on response within 120 seconds

And 10 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Edit sink active and use invalid username

Given the Orb user has a registered account

And the Orb user logs in

Then referred sink must have error state on response within 120 seconds

And 10 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Edit sink active and use invalid password

Given the Orb user has a registered account

And the Orb user logs in

Then referred sink must have error state on response within 120 seconds

And 10 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Edit sink with invalid username and use valid one

Given the Orb user has a registered account

And the Orb user logs in

Then referred sink must have active state on response within 120 seconds

And 4 dataset(s) have validity valid and 0 have validity invalid in 30 seconds

Scenario: Edit sink with password and use valid one

Given the Orb user has a registered account

And the Orb user logs in

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the name of this sink is updated

Then the name updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

Scenario: Partial Update: sink status after updating only sink description

Given the Orb user has a registered account

And the Orb user logs in

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the description of this sink is updated

Then the description updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the tags of this sink is updated

Then the tags updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the config of this sink is updated

Then the config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the name and description of this sink is updated

Then the name and description updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the name and config of this sink is updated

Then the name and config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the name and tags of this sink is updated

Then the name and tags updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the description and tags of this sink is updated

Then the description and tags updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the tags and config of this sink is updated

Then the tags and config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds

And this agent's heartbeat shows that 2 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

And the container logs that were output after all policies have been applied contain the message "scraped metrics for policy" referred to each applied policy within 180 seconds

When the name, description and tags of this sink is updated

Then the name, description and tags updates to the new value and other fields remains the same

And referred sink must have active state on response after 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the name, description and config of this sink is updated

Then the name, description and config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the name, tags and config of this sink is updated

Then the name, tags and config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds

And 3 simple policies are applied to the group

And this agent's heartbeat shows that 3 policies are applied and all has status running

And the container logs contain the message "policy applied successfully" referred to each policy within 30 seconds

When the description, tags and config of this sink is updated

Then the description, tags and config updates to the new value and other fields remains the same

And referred sink must have active state on response within 360 seconds