Fix for the OS field and scenarios

[IgorGuz2000]

What does this PR do?

added OS field to the steps and one scenario

Why is it important?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests (make unit-test), and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

Author's Checklist

• [ ]

How to test this PR locally

Related issues

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-07-27T19:50:35.639+0000

• Duration: 37 min 1 sec

• Commit: aabc2ed

Test stats 🧪

Test	Results
Failed	0
Passed	231
Skipped	0
Total	231

Trends 🧪

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	231
Skipped	0
Total	231

[IgorGuz2000]

This is the ticket for this problem
#1324

[mdelapenya]

For upcoming PRs, the preferred logging style should be something like this:

log.WithFields(log.Fields{
	"last_activity_ms": item.Path("last_activity_ms").Data().(float64),
	"startTime":        startTime,
	"os":        os,
	"integration":   name,
	"metricset":       set,
}).Info("Last activity greater than start time")

And maybe using Debug level.

[mdelapenya]

Great work with the PR @IgorGuz2000! Let's not forget to open a bug in the dev team repo (See my comment here #1324 (comment)) so that they can work on the fix for Centos