[O11y] Address skipped validation SVR00004

[harnish-elastic]

Proposed commit message

• Here is a list of packages (8 packages) that have SVR00004 with the current kibana.version:

activemq == ^8.8.0
apache_tomcat == ^8.8.0
cassandra == ^8.8.0
kafka == ^8.8.0
mongodb == ^8.8.0
mysql == ^8.8.2
nginx == ^8.8.0
postgresql == ^8.8.0

• Fixed SVR00004 validation and bump the Kibana version to 8.10.1 for those packages which contains kibana < 8.10

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.

Author's Checklist

• Verified all dashboards are working as expected after fixing SVR00004

Related issues

• Relates elastic/obs-infraobs-integrations: Address skipped validation SVR00004 (batch 2) #8938

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[shmsr]

Let me resolve the conflict in #8423 to enable merging batch 1 before this one, even though both are independent. Also, approval is required from other teams for this PR.

But I see the CI failed because of some issue in mongodb. PTAL?

[harnish-elastic]

Let me resolve the conflict in #8423 to enable merging batch 1 before this one, even though both are independent. Also, approval is required from other teams for this PR.

Sure

But I see the CI failed because of some issue in mongodb. PTAL?

For the mongodb, the system tests are failing and showing this error!

mongodb/collstats collstats:
[0] found error.message in event: ['top' command failed: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service_mongodb_1:27017, Type: RSGhost, Average RTT: 1714128 }, ] }]
mongodb/dbstats dbstats:
[0] found error.message in event: [could not retrieve database names from Mongo instance: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service_mongodb_1:27017, Type: RSGhost, Average RTT: 465420 }, ] }]
mongodb/metrics metrics:
[0] found error.message in event: [failed to retrieve data from 'serverStatus' command: server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service_mongodb_1:27017, Type: RSGhost, Average RTT: 412015 }, ] }]
mongodb/status status:
[0] found error.message in event: [failed to retrieve 'serverStatus': server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: elastic-package-service_mongodb_1:27017, Type: RSGhost, Average RTT: 355797 }, ] }]

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 5e89cc8

Failed CI Steps

• Check integrations cassandra
• Check integrations mongodb

History

• 💔 Build #8554 failed 232e6f9
• 💔 Build #8472 failed 00d044c
• 💔 Build #8471 failed 91e7dfe
• 💔 Build #8470 failed 1cab9c4

cc @harnish-elastic

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!

[ishleenk17]

@shmsr : Still valid?