chore: bring back system integration scenarios#2233
chore: bring back system integration scenarios#2233mdelapenya merged 18 commits intoelastic:mainfrom
Conversation
|
This task is stuck until we know how the |
|
@IgorGuz2000 this is ready and working! Thanks for your help!! |
| if name == "linux/metrics" { | ||
| file = "/linux_metrics.json" | ||
| metrics = "linux" | ||
| packageDS, err = fts.kibanaClient.GetIntegrationFromAgentPolicy(fts.currentContext, metrics, fts.Policy) |
There was a problem hiding this comment.
For safety, linux metrics keeps the old behaviour and reading the metrics inputs from the "linux_metrics" golden file. @IgorGuz2000 I think it could follow the same approach, although I do not see any scenario using the "linux/metrics" scenario.
There was a problem hiding this comment.
Yes there is only one scenario there to verify the metrics exist
There was a problem hiding this comment.
But with current project layout, I cannot see it anymore. Do you have any clue on where it is?
There was a problem hiding this comment.
@IgorGuz2000 I'm going to merge this one, we can revisit the "linux_metrics" in follow ups. Thanks!
|
@Mergifyio refresh |
|
@Mergifyio backport 7.17 |
✅ Pull request refreshed |
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d)
✅ Backports have been createdDetails
|
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d)
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d)
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d) Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d) Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
* chore: bring back system integration scenarios * chore: simplify system integration scenarios to use Examples * fix: retrieve system metrics from Kibana, not from the file * fix: use example in scenario name * fix: get package policy right * chore: eval error the soonest * chore: handle not supported package policy * chore: use new method for retrieving the package policy by name * revert: log inputs from the package policy first * fix: committed by mistake * chore: retrieve package policy by ID * fix: read response properly * chore: simplify wati strategy * chore: remove unused file * chore: enable syslog integration too * chore: abstract scenario (cherry picked from commit ac1503d) Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
* main: (72 commits) fix: always quote variables in shell scripts (elastic#2284) chore: bring back system integration scenarios (elastic#2233) chore: do not notify build green for fleet nightly builds (elastic#2277) chore: include suite, platform and tags in test reports name (elastic#2273) bump stack version 8.2.0-dcff22d7 (elastic#2270) bump stack version 8.2.0-4509f321 (elastic#2265) chore: bump Godog to v0.12.4 (elastic#2245) bump stack version 8.2.0-5cc993c1 (elastic#2254) bump stack version 8.2.0-82b803a1 (elastic#2250) fix: never process elasticsearch CI artifacts (elastic#2246) bump stack version 8.2.0-ff67d7b8 (elastic#2242) ci: periodic builds for the last two minor versions (elastic#2241) bump stack version 8.2.0-9bac538c (elastic#2240) fix: add end-of-file line in templates (elastic#2237) chore: add Christos to SSH users bump stack version 8.2.0-fee3b8d2 (elastic#2234) Separate ES workload from Agent spec and make it req for the scenarios (elastic#2203) bump stack version 8.2.0-d02c907a (elastic#2228) bump stack version 8.2.0-63265ec9 (elastic#2225) fix: wrong link (elastic#2220) ...
What does this PR do?
It brings back the system_integration scenarios, which were skipped in the past with the move to the VM support.
Why is it important?
We want to double check why the data_streams are not showing the inputs.streams elements when updating a policy, which was detected while trying to restore the stand-alone mode scenarios.
We noticed that both scenarios (standalone and system integration) share the steps to update the policy, and wanted to double check that the issue that we see with standalone is not present in the system integration. Why?
metrics.jsonfile is outdatedChecklist
make unit-test), and they are passing locallymake noticein the proper directory)