Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

Commit

Permalink
New Scenarios for the System integration test (#1291) (#1333)
Browse files Browse the repository at this point in the history
* Adding new Scenarios for the System integration

* Fix linting

* remove a tag

* rename feature

* Change per Manu request

* Change per Manu request

* Change per Manu request

* Change per Manu request

* Change per Manu request

* Change per Manu request

* fix mistype in the step

* Update .ci/.e2e-tests.yaml

Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com>

* removed println statements

* moved metrics.json to the features folder

* Removed the all of the Print statements

* Added process.summary scenario

* moved metrics.json file to the testsources directory

* changed code to use filepath

Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com>
Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
(cherry picked from commit 1d4b190)

Co-authored-by: IgorG <56408662+IgorGuz2000@users.noreply.github.com>
  • Loading branch information
mergify[bot] and IgorGuz2000 committed Jul 20, 2021
1 parent 1c8d2d7 commit 0f801a0
Show file tree
Hide file tree
Showing 5 changed files with 713 additions and 2 deletions.
5 changes: 5 additions & 0 deletions .ci/.e2e-tests.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,11 @@ SUITES:
- name: "Linux Integration"
pullRequestFilter: " && ~debian"
tags: "linux_integration"
- name: "System Integration"
platforms:
- "ubuntu-18.04"
pullRequestFilter: " && ~debian"
tags: "system_integration"
- name: "Stand-alone"
pullRequestFilter: " && ~ubi8"
tags: "stand_alone_agent"
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
@agent_endpoint_integration
@skip:arm64
@agent_endpoint_integration @skip:arm64
Feature: Agent Endpoint Integration
Scenarios for Agent to deploy Endpoint and sending data to Fleet and Elasticsearch.

Expand Down
224 changes: 224 additions & 0 deletions e2e/_suites/fleet/features/system_integration.feature
Original file line number Diff line number Diff line change
@@ -0,0 +1,224 @@
@system_integration
Feature: System Integration
Scenarios for System Integration logs and metrics packages.

@deploy-system_integration-with-core
Scenario Outline: Adding core System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "core"
Then "system/metrics" with "core" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-cpu
Scenario Outline: Adding cpu System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "cpu"
Then "system/metrics" with "cpu" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-diskio
Scenario Outline: Adding diskio System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "diskio"
Then "system/metrics" with "diskio" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-fsstat
Scenario Outline: Adding fsstat System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "fsstat"
Then "system/metrics" with "fsstat" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-load
Scenario Outline: Adding load System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "load"
Then "system/metrics" with "load" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-memory
Scenario Outline: Adding memory System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "memory"
Then "system/metrics" with "memory" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-network
Scenario Outline: Adding network System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "network"
Then "system/metrics" with "network" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-process
Scenario Outline: Adding process System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "process"
Then "system/metrics" with "process" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-socket_summary
Scenario Outline: Adding socket_summary System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "socket_summary"
Then "system/metrics" with "socket_summary" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-uptime
Scenario Outline: Adding uptime System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "uptime"
Then "system/metrics" with "uptime" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

@deploy-system_integration-with-process_summary
Scenario Outline: Adding process_summary System Integration to an Policy
Given a "<os>" agent is deployed to Fleet with "tar" installer
And the agent is listed in Fleet as "online"
When the policy is updated to have "system/metrics" set to "process.summary"
Then "system/metrics" with "process.summary" metrics are present in the datastreams

@centos
Examples: Centos
| os |
| centos |

@debian
Examples: Debian
| os |
| debian |

#@deploy-system_integration-with-filesystem
#Scenario Outline: Adding the System Integration to an Policy
# Given a "<os>" agent is deployed to Fleet with "tar" installer
# And the agent is listed in Fleet as "online"
# When the policy is updated to have "system/metrics" set to "filesystem"
# Then "system/metrics" with "filesystem" metrics are present in the datastreams
#
#@centos
#Examples: Centos
#| os |
#| centos |

#@debian
#Examples: Debian
#| os |
# | debian |

# @deploy-logfile-for-system-auth
# Scenario Outline: Adding the System Integration to an Policy
# Given a "<os>" agent is deployed to Fleet with "tar" installer
# And the agent is listed in Fleet as "online"
# When the policy is updated to have "logfile" set to "syslog"
# And verify that "logfile" with "syslog" metrics in the datastreams
#
# @centos
# Examples: Centos
# | os |
# | centos |

# @debian
# Examples: Debian
# | os |
# | debian |
Loading

0 comments on commit 0f801a0

Please sign in to comment.