[MongoDB] Update the Kibana version condition for the fix of disk space exhaustion.

[ritalwar]

Proposed commit message

This PR updates the Kibana version condition for MongoDB integration to address the fix for MongoDB disk space exhaustion.

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.

Related issues

• Closes [MongoDB] Update the Kibana version condition for MongoDB integration to address the fix for MongoDB disk space exhaustion #9220

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 15980c0

History

• 💚 Build #9192 succeeded 77f1667

[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

[elasticmachine]

Package mongodb - 1.13.2 containing this change is available at https://epr.elastic.co/search?package=mongodb

[lucabelluccini]

Hello @ritalwar,
The bug #9220 / #8683 is solved via elastic/beats#37688, which means we need beats to be upgraded to 8.12.2.

I do not get why we've bumped the Kibana minimum versions.
Even if Kibana is updated, a user might still run an old Elastic Agent version and therefore an old Beats version - and would still be affected by the original bug.

We should not confuse the Kibana minimum version by the Elastic Agent version IMHO.

[ishleenk17]

@lucabelluccini : I completely get your point here, that Elastic Agent and Kibana version can be different.

Since there is no specific versioning for the Elastic agent as discussed earlier as well , it is expected that if customers want to utilize a feature added in a new Beats release, they should update the agent to match the stack version. Given the current constraints with Elastic agent versioning, this is the best method to ensure compatibility and feature availability.

Until the Elastic agent versioning issue is resolved, this approach remains the most effective way to communicate the need for updates to customers.

Please let me know if you have some other thoughts on this Luca.

[lucabelluccini]

I agree.

As a mitigation until the package spec will have the EA version, my suggestion would be to "hint" users the Kibana version is also the "recommended" version of EA to use, maybe via enhancing the integration docs page.

Right now we do not even have a public documentation on the meaning of the "Minimum Kibana version", plus the release notes might be confusing:

[ishleenk17]

my suggestion would be to "hint" users the Kibana version is also the "recommended" version of EA to use, maybe via enhancing the integration docs page.

Yes, I agree we can mention in the changelog about the requirement to have the same EA version and Kibana version for these type of changes