[O11y][MongoDB Atlas] Fix single event object returned by evaluation error for hardware, process and disk data streams

[harnish-crest-data]

Proposed commit message

• Fix single event object returned by evaluation error that causing agent degrade issue for the following data streams
  • hardware
  • process
  • disk

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Closes [mongodb_atlas]: Parsing errors in multiple datasets/datastreams and agent instability in Beta version #11576

Screenshots

Before

After

[harnish-crest-data]

/test

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: efa3c3a

History

• 💔 Build #17969 failed 81b921e05b02392249eb90aee9de2e5bd9d0cab7
• 💔 Build #17965 failed 81b921e05b02392249eb90aee9de2e5bd9d0cab7

cc @harnish-elastic

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[ishleenk17]

Since we are changing from single event to an array, is there a change in how the event is now formed ?
If yes, lets update the sample json as well

[harnish-crest-data]

Since we are changing from single event to an array, is there a change in how the event is now formed ? If yes, lets update the sample json as well

No, there is not a change in the event format!

[efd6]

@ishleenk17 The relevant part of the input is here. Single events are promoted to an array, but the single event is a signal that the data was an error condition. Also noted here and in the docs.

[elastic-vault-github-plugin-prod]

Package mongodb_atlas - 0.0.10 containing this change is available at https://epr.elastic.co/package/mongodb_atlas/0.0.10/