-
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
Redis: remove deprecated fields #27948
Conversation
This pull request doesn't have a |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errorsExpand to view the tests failures
|
Test | Results |
---|---|
Failed | 4 |
Passed | 20056 |
Skipped | 1386 |
Total | 21446 |
Genuine test errors
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Build&Test / metricbeat-pythonIntegTest / test_info – metricbeat.module.redis.test_redis.Test_0
- Name:
Build&Test / metricbeat-pythonIntegTest / test_module_processors – metricbeat.module.redis.test_redis.Test_0
- Name:
Build&Test / metricbeat-pythonIntegTest / test_info – metricbeat.module.redis.test_redis.Test_1
- Name:
Build&Test / metricbeat-pythonIntegTest / test_module_processors – metricbeat.module.redis.test_redis.Test_1
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request does not have a backport label. Could you fix it @aspacca? 🙏
NOTE: |
What does this PR do?
This PR removes deprecated fields from Redis Metricbeat module.
Why is it important?
We don't want these fields to be present in 8.0 distribution.
Checklist
- [ ] 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 worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues