-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added support for couchdb v3. #26950
base: main
Are you sure you want to change the base?
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
|
I am not allowed to add labels to the PR. |
cc: @sayden |
Pinging @elastic/integrations (Team:Integrations) |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @StephanU 🙂 Thanks for contributing with this. Please, can you create a V3.go
instead of the current implementation? The idea is to make it explicit even on the filesystem instead of "implicit" (hidden) in a switch case.
Redis and MySQL modules also have the ability to test multiple versions of the same product using docker compose. Do you think you can take a quick look to add the same functionality here, please? 🙂
I added support for testing multiple versions of CouchDB. I tested the startup of the docker images by calling |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request does not have a backport label. Could you fix it @StephanU? 🙏
NOTE: |
@elastic/obs-service-integrations could some look at this PR? |
If the output format is exactly the same than in CouchbDB v2 (it seems it is) and the dashboards are still working (it will be nice to see a screenshot of the dashboard attached to the PR as reference), this PR is good to go without any more changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bturquet can your re-route this to the appropriate team to merge, please? I think it is ready to merge 🙂 |
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request is now in conflicts. Could you fix it? 🙏
|
Happy belated 3rd birthday. ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What does this PR do?
Added Metricbeat support for CouchDB version 3. It seems like the result format of the couchdb stats endpoints did not change from version 2 to 3 (the release notes do not mentioned changes to the stats endpoints).
So I'm just reusing the stats format of version 2.
Why is it important?
Added support for the lastest major CouchDB version 3.
Checklist
[ ] 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 worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Related issues